I did the update exactly as when I first got the scanner. My TRX-2 SCANNER IS NOW BRICKED. It keep saying "Waiting for MAIN unit" and will not turn on. Please advise. Thank you.
NEW UPDATE available - 7/11/16
- Thread starter WhistlerWendy
- Start date
- Status
OK, I disconnected power plug for 30 sec and scanner restarted with new firmware updates. Has anyone else encountered this message "Waiting for MAIN unit." TRX-2 seems be working well and receiving lots of Slot 2 traffic.
Steve that was what happened to me the 1st time out of the box but I had made a backup of the original sd card and started over. Also if you have a power loss on the TRX-2 when it recovers it ask to start all over with the band plan. It remembers the scanlist but forgets all other settings. So this will be very important to use a UPS on AC and power off the scanner before starting a car with a low battery.
Budd,
Thank you. I also made a backup SDR card and used that after 30 sec power cord detachment to reset. It worked, This TRX-2 has some quirks, but so do all scanners. Meanwhile, slot 2 DMR working fine. Sounds good. Like you Budd, hope we get some remote control and logging software for these new scanners. That to me is still a distict advantage of 536HP. Audio though on TRX units is really nice.
Regards
Steve.
Thank you. I also made a backup SDR card and used that after 30 sec power cord detachment to reset. It worked, This TRX-2 has some quirks, but so do all scanners. Meanwhile, slot 2 DMR working fine. Sounds good. Like you Budd, hope we get some remote control and logging software for these new scanners. That to me is still a distict advantage of 536HP. Audio though on TRX units is really nice.
Regards
Steve.
MichaelBhere
Member
- Joined
- Mar 6, 2015
- Messages
- 151
Someone commented on this once or twice before but the procedure I believe went something like this..
Remove power, press and hold the power button for 30~60 seconds to discharge the capacitors in the power circuit, release the power button, plug power back in, then press and hold the power button until the display tells you to release it.
Once it has turned on, you may want to turn the clock display on so the internal battery will charge when the scanner is off as long as it has power applied to the scanner. It takes several days to fully charge the battery that maintains the clock settings if the battery was low.
Remove power, press and hold the power button for 30~60 seconds to discharge the capacitors in the power circuit, release the power button, plug power back in, then press and hold the power button until the display tells you to release it.
Once it has turned on, you may want to turn the clock display on so the internal battery will charge when the scanner is off as long as it has power applied to the scanner. It takes several days to fully charge the battery that maintains the clock settings if the battery was low.
Happens to me all the time on a 1098, randomly. Upload, download, import, firmware update- never know when it's going to happen. I have to disconnect the power and reinsert the SD card. Real PITA popping the remote off and on (the magnet works). Just switched to different card and things are better, so far, else it's going back.
BTW, I am now receiving DMR again with latest firmware.
Great upgrade for my 1095 Whistler, and thanks!
Not even into the DMR stuff yet and there is a 100% improvement in reception
of digital P2 stations. Like a new radio!!!
Nice to see a company support their products and respond to their customers in a TIMELY fashion.
Not even into the DMR stuff yet and there is a 100% improvement in reception
of digital P2 stations. Like a new radio!!!
Nice to see a company support their products and respond to their customers in a TIMELY fashion.
Last edited:
scotttish
Member
Thanks Troy! Sometimes it sucks being new at this stuff...Gotta be smarter than the average bear!
Is everything working in the DMR trunking or is it just me. Since the upgrade, I have not had the first decode in my DMR trunking scanning. Worked fine before the upgrade.
Don't forget to also update the DSP code! Double check that.
Thanks for the reply. I have updated the PC Application to Version 2.11-Bld 441, The CPU Firmware to Version 3.6, and the DSP Firmware to 2.3. Today I finally got 1 talk group to decode a single reply from dispatch. With my MD-380 and my WS-1080 setting side by side and both only scanning the same site with 3 frequencies the MD-380 decodes every message and the WS-1080 has been silent.
I know the latest upgrade was addressing Conventional DMR channels. I only hope that it did not break DMR Trunking.
I know the latest upgrade was addressing Conventional DMR channels. I only hope that it did not break DMR Trunking.
Did you have a list of talkgroups without a TG wildcard? I noticed that somehow my TG list, to include the wildcard, was eliminated right around the same time as the software/firmware upgrade. I'm not sure if it was something I did and the timing was a coincidence or if the upgrade hosed it. I wouldn't think the latter would be the case, but if you haven't checked your TG list, and you probably have, give it a look.
I do have a wildcard in the TG scan list and it was not eliminated. Just for testing, I will take that out and see if it makes a difference. Thanks
Removing the wildcard TG from the scan list did not make any difference.
Although the procedure is a little different between the two, I decided to program a scan group as close as possible to the MD-380. Both now are only scanning one site with 3 frequencies and 16 TGs with a wildcard in the WS-1080. Now with both side by side the MD-380 is catching all the traffic and the WS-1080 is silent most of the time. After double checking the programming I have determined something has changed. It seems as if the sensitivity or something has dropped on the TGs decode with the Whistler.
KF5MWE
Although the procedure is a little different between the two, I decided to program a scan group as close as possible to the MD-380. Both now are only scanning one site with 3 frequencies and 16 TGs with a wildcard in the WS-1080. Now with both side by side the MD-380 is catching all the traffic and the WS-1080 is silent most of the time. After double checking the programming I have determined something has changed. It seems as if the sensitivity or something has dropped on the TGs decode with the Whistler.
KF5MWE
Did the Global Attenuator get enabled somehow? Will show as an A or GA on the display.
Make sure those 0.00000 frequency entries are locked out. That issue apparently was not fixed with this latest firmware update. That definitely sends the TRX off into space and causes it to miss a great deal of traffic.
I will lock out all the 0 freqs and report back if there is any change in behavior. I am still testing and when I conclude that something is now broken I will submit an email report as whistler has requested.
KF5MWE
KF5MWE
Continuing with experimental programming of DMR in the WS-1080 after the latest firmware update, I programmed all 4 sites with 3 frequencies each as Conventional channels with the Color Code as any, Time Slot ans any, and the Talkgroup Id as 0. Now with this configuration all works as expected.
This for me though would not be feasible. That's 12 frequencies that I would have to duplicate for each of 16 out of 40 or so talk groups that I am interested in. DMR trunking does not work as expected after the latest firmware update.
This is a DMR Capacity Plus system I am working with. I am wondering if it has something to do with the timeslot changes since there is no way to set timeslots in DMR trunking. Seems like there should be an additional column so we could set timeslot to any as with conventional.
KF5MWE
This for me though would not be feasible. That's 12 frequencies that I would have to duplicate for each of 16 out of 40 or so talk groups that I am interested in. DMR trunking does not work as expected after the latest firmware update.
This is a DMR Capacity Plus system I am working with. I am wondering if it has something to do with the timeslot changes since there is no way to set timeslots in DMR trunking. Seems like there should be an additional column so we could set timeslot to any as with conventional.
KF5MWE
Last edited:
DonS
Member
When programmed as a trunked system, did you leave each programmed frequency's Color Code set to "Any"?
When scanning the trunked system, do you see the inverted 'S' indicator a lot (but not the inverted 'T' indicator)? If so, you have the squelch set too low. Turn the knob clockwise just until the 'S' indicator disappears. If you're seeing that inverted 'S' (but not inverted 'T'), you'll definitely miss DMR traffic.
In the Whistler scanners, DMR trunking is always "time slot 'any'". The scanner doesn't care about time slot. It only cares about talkgroup ID and, if set for a particular frequency, color code.
Are you referring to any trunked radio system? Indiana uses P25 trunked radio systems and in the EZScan software, it lists the control channel frequency up top followed by 32 "0.000000" frequency and the option to L/O each one. Are you saying those should be Locked Out or are you just referring to DMR systems?
Thanks,
Del
- Status
