- Joined
- Dec 16, 2015
- Messages
- 372
Why bother wasting your time doing all of this when you could've easily read the threads and determined what works and what doesn't?
It's like people enjoy reinventing the wheel for no viable reason.
Pro-668: Radio Shack PRO-668 loaded with Whistler DMR firmware
- Thread starter trp2525
- Start date
- Status
It's like people enjoy reinventing the wheel for no viable reason.
FYI I have read this entire thread and as a matter of fact I am the OP who started this thread last August. That being said I performed my experiments this weekend as a learning experience for myself prior to sending in my PRO-668 for the official Whistler upgrade. I then shared my results on this thread hoping to possibly inform/help someone who might not be sending in their scanner for the official upgrade.
I haven't read anything in this thread specifically stating that someone lost their DMR and P25 receive (like I did) after updating to the latest DSP 3.1 currently available for download from Whistler. I have also not read anyone specifically posting that they rolled back their DSP to 3.0 and still had no DMR or P25 receive (like I experienced). I'm not trying to "reinvent the wheel" but rather share information and data that may be useful/helpful to others on this board. Isn't that the purpose of these forums?
PRO-668
My Pro-668 scanner is doing the same thing not picking up DMR any more after a 3.1. DSP upgrade ...it will not down grade to other firmwares either ...any way around this would be greatly appreciated..So i am stuck on 4.6 firmware with no DMR this suxs .
My Pro-668 scanner is doing the same thing not picking up DMR any more after a 3.1. DSP upgrade ...it will not down grade to other firmwares either ...any way around this would be greatly appreciated..So i am stuck on 4.6 firmware with no DMR this suxs .
That's exactly why I posted the information that I posted earlier today to possibly help someone who wasn't intending on sending in their PRO-668/PRO-18/PSR-800 for the official upgrade. Maybe someone else on this board has some other ideas or things to try that have not already been posted.
As for me I just got my PRO-668 packaged up and am heading out to the post office to send it in for the official upgrade. At least in my case I had already planned on sending it in today and was not forced into doing it because of the loss of DMR and P25 receive after the DSP 3.1 update. Also with a brand-new TRX-2 just purchased last week with the Walmart/Ebates blowout deal, I wanted both radios to be at the very latest CPU and DSP firmware versions so their performance would be comparable.
Good luck!
Pro-668
Some people can not afford the official up grade now ,so it's tough luck for them ...and me..
Some people can not afford the official up grade now ,so it's tough luck for them ...and me..
carbonfiber
Member
I have this exact issue after DSP 3.1 update two days ago and tried all mentioned procedures to revert to pre-CPU 4.6 with the same errors. However it has only broken DMR/MotoTRBO. It still receive P25 (stuck on CPU 4.6/DSP 3.0)
Well you are the second person to confirm my findings over the weekend that DSP 3.1 (the most current version on the Whistler server) may stop your scanner from receiving DMR and that you can no longer revert back to previous CPU versions. I would therefore HIGHLY RECOMMEND if you are using CPU 4.6 along with DSP 3.0 to NOT update to DSP 3.1. If you do, your only recourse if you want to continue to receive DMR may be to send your scanner to Whistler for the official upgrade. YMMV
My PRO-668 is on its way to Whistler as of today. I look forward to getting it back in the next few weeks and being able to update to the most recent CPU 4.8 and DSP 3.1 with DMR working again. IMHO $60 for the upgrade plus inbound shipping costs is a fair price to pay in order to receive any future CPU/DSP updates as they are released. DMR was released for the WS1080 back in May 2016 and Whistler continues to refine their CPU/DSP firmware for this scanner.
sibbley
Member
Make me the third person to confirm. I accidentally upgraded to DSP 3.1 on Friday. I haven't been able to hear DMR/TRBO or re-install an earlier firmware. Back to using my PSR-800 for P25 only.
sibbley,
Thank you for sharing and posting your confirmation information. It's interesting that I was called out in post #1142 above for "wasting my time doing all of this," not reading the threads and "reinventing the wheel" regarding DSP 3.1 firmware disabling DMR receive in the PRO-668/PRO-18/PSR-800.
The reality of the situation is that NO ONE had specifically posted this important information/data point in this thread until I did so yesterday. It was after my posting that the 3 confirmations of the same behavior (including yours) were posted in this thread and I'm sure there are more out there. Previous thread postings stated that DSP 3.1 was working OK with CPU 4.5 and 4.6 which leads me to suspect that Whistler made some further changes/modifications to the DSP 3.1 firmware after it was initially released.
sibbley
Member
Yeah, I thought I remembered some posting that 4.5 and 4.6 WERE working with DSP 3.1.
- Joined
- Feb 18, 2016
- Messages
- 1,956
They are working. for those that they are not, it is a localized issue. meaning it is between YOUR computer and YOUR scanner or you installed the dsp before the cpu firmware etc..
do the following In this EXACT order:
1) Archive your scanner, uninstall ezscan and all the files it put in your documents folder,
2) redownload ezscan for the ws1080 and reinstall,
3)install the CPU firmware BEFORE the DSP, if ezscan won't communicate with the scanner comport or times out in windows, assign a comport to the scanner (search google on how to).
4)Once the cpu firmware is installed then you can install the DSP firmware via ezscan.
If the dsp will not install or you want to roll it back then.Search these forums on how to, as it involves one file on the micro sd card. I think it is similar to "config_xxxx.bin"
Hello,
It is important when you downgrade the DSP by changing the CONFIG__.BIN on the SD Card, that you also change the CONFIG__.BIN file in the WS1080 Digital directory under your Documents folder. Otherwise the downgrade will be eliminated the next time EZ-Scan accesses the scanner.
73 Eric
It is important when you downgrade the DSP by changing the CONFIG__.BIN on the SD Card, that you also change the CONFIG__.BIN file in the WS1080 Digital directory under your Documents folder. Otherwise the downgrade will be eliminated the next time EZ-Scan accesses the scanner.
73 Eric
I no longer have my PRO-668 in my possession as it is on its way back to Whistler for the official upgrade, but I can add some additional data points here. First off my PRO-668 was already at the latest CPU version allowed with Eric's tool (CPU 4.6) before installing DSP 3.1. Immediately after installing DSP 3.1 I lost DMR receive capability and the functionality of Eric's tool to change the CPU versions back and forth. There was a direct cause-and-effect between those events.
Secondly I had a saved CONFIG__.BIN file that contained DSP 3.0 so I loaded that to roll back the DSP to 3.0 to try to regain DMR receive and to make Eric's tool work once again. After successfully rolling back the DSP to 3.0 (confirmed by an updates check in EZScan) I still had no DMR receive and Eric's tool still would not work at all to change the CPU versions back and forth. Something in DSP 3.1 broke both of those functions.
I had full communication with the scanner at all times as I could set the time with both DSP 3.0 and DSP 3.1. The fact that DSP 3.1 was simultaneously released with CPU 4.7 could be part of the problem here. CPU 4.6 may not be playing well with DSP 3.1 on some RR member's computers depending on their operating system and other factors specific to their personal computer. FYI I had the same negative results using a Windows XP SP3 computer and a Windows 10 Home (very latest version and updates) computer. All comports were working OK on both computers as seen in Device Manager.
sibbley
Member
Can't install any firmware. I even did a fresh 1080 EZScan install on a windows 7 machine that never had EZScan installed before. I've tried all versions of Eric's tool, tried to update CPU firmware through EZScan and the stand alone updater.
4.6 firmware was already installed with DSP 3.0 when I upgraded DSP to 3.1 by accident. Prior to that DMR/TRBO worked. I don't have a copy of the 3.0 config_bin file.
With sibbley's post above it appears that Whister may have introduced some sort of "check" with DSP 3.1 to make sure that you were updating a genuine WS1080 or a legacy scanner that had been officially upgraded by Whistler. If that was not the case they may be disabling DMR functionality. There may also be some intentional additional code in there to disable the functionality of Eric's tool (or it may be just by coincidence) if you are attempting to load DSP 3.1 into a non-officially upgraded PRO-18/PRO-668/PSR-800.
Eric's tool was EXCELLENT as an experiment and helped out MANY of us until Whistler stepped up to the plate and offered an official upgrade with support for our legacy scanners. I'm glad I sent mine in yesterday so that I know I will always have access to the very latest PC application, CPU firmware and DSP firmware and won't have to worry as to whether or not any of those 3 items will work with each other in my scanner.
Eric's tool was EXCELLENT as an experiment and helped out MANY of us until Whistler stepped up to the plate and offered an official upgrade with support for our legacy scanners. I'm glad I sent mine in yesterday so that I know I will always have access to the very latest PC application, CPU firmware and DSP firmware and won't have to worry as to whether or not any of those 3 items will work with each other in my scanner.
scannerjunkie
Member
Can the problem also lie within the most recent version of ezscan besides 3.1 dsp?
Last edited:
I think we are all formulating our own hypotheses at this point. I'm thinking that DSP 3.1 has possibly been modified since it was initially introduced and that might be the cause of the problem. I guess a newer version of the PC application could also be another variable. To be safe I wouldn't update the PC application beyond 2.19 as that was the latest version that was designed to work with CPU 4.6 and DSP 3.0 (which was the latest CPU version we could load with Eric's tool). If you have everything working with CPU 4.6 and DSP 3.1 consider yourself lucky and if I were you, I wouldn't update anything. I don't believe using EZScan to just do library updates will cause you any problems at this point. YMMV
I run 3.1 but on one of my 668's I found the newest 4.6 wasn't working well for whatever strange reason. So one of my radios is on 4.6 and working great while I had to revert back to 4.5 on the other one.
One thing I found out is you need to go in and delete the config.bin completely or the scanner won't work. I had no trouble on a win 7 machine downgrading the firmware using Eric's tool a few days ago. The problem was when I tried to run the scanner it errored out.
Deleting the config.bin then hitting copy to card put everything back right and it works great.
Don't know if that might help but try that and see.
One thing I found out is you need to go in and delete the config.bin completely or the scanner won't work. I had no trouble on a win 7 machine downgrading the firmware using Eric's tool a few days ago. The problem was when I tried to run the scanner it errored out.
Deleting the config.bin then hitting copy to card put everything back right and it works great.
Don't know if that might help but try that and see.
How long ago did you download DSP 3.1 from the Whistler update server using EZScan? Was it right after it was released back in May?
Also what version of the EZScan PC Application software are you running on your computer? Did you stay with version 2.19 or have you updated that also?
sibbley
Member
I've been able to load DSP 3.0 back on the scanner, confirmed by EZScan 2.19. Still haven't been able to change the firmware back to 4.5. Still NO DMR.
- Status
Similar threads
