GRE PSR-500 Firmware Release Thread

[troymail]

Here's a placeholder for the expected first Firmware release/update....

What I'm hoping is that when the release is out, folks who were experiencing problems with the factory version of the firemware can start posting their post-upgrade findings here (hopefully, mostly good news!) rather than requiring everyone to wade down through the now 30 some pages of the Post Release thread.....

Bring on the update!

 

[mikey60]

Beta firmware was posted on the GRE web site @ 11:00 PM EST.

http://www.greamerica.com/support

Mike

 

[NYG]

Beta CPU & DSP firmware is available.

 

[jpryor]

Notes per their news release:

[FONT=Verdana, Arial, Helvetica, sans-serif]Bulletin Release - 11/05/2007 -
[/FONT][FONT=Verdana, Arial, Helvetica, sans-serif]
GRE [/FONT][FONT=Verdana, Arial, Helvetica, sans-serif]- A beta release of PSR-500 CPU and DSP Firmware has been released. Please be advised that this is a Beta Release only. We would like to get as much feedback as possible to help us find any know issues before an official Firmware update is released. Your feedback and support would greatly appreciated.

"CPU500_U01" (Beta) Release Note Fixes.
[/FONT] [FONT=Verdana, Arial, Helvetica, sans-serif]
[/FONT][FONT=Verdana, Arial, Helvetica, sans-serif] -Fixed: EDACS will no longer trunk to encrypted (Pro-Voice) calls

[/FONT] [FONT=Verdana, Arial, Helvetica, sans-serif]-Fixed: Properly display SiteID for M36 in trunking analysis mode (SiteID was
previously one too low in number)

-Fixed: Pressing ATT at power-up, changing the setting, then saving will now
preserve the new value

-Fixed: P25 dwell timeout when not holding/paused

-Fixed: Mot3600 CC dwell timeout when receiving RF SQ but no CC messages

-Fixed: RF Squelch timers on CCs. Should fix cases where CC could not be
found

-Fixed: Monitoring of DG signals in Tune mode (would pulse the audio every
few seconds)

-Improved: Unmuting on start of DG calls

-Improved: Less falsing of Mot subaudible detect in Tune mode

-Fixed: When paused while scanning, better handle changing CCs

-Improved: PC/IF remote control presents the radio's speaker mute state
within more real time[/FONT]
[FONT=Verdana, Arial, Helvetica, sans-serif]
[/FONT][FONT=Verdana, Arial, Helvetica, sans-serif]"DSP500_U01" (Beta) Release Note Fixes.[/FONT]
[FONT=Verdana, Arial, Helvetica, sans-serif]- Improve P25 DG decoding on all system types[/FONT]

Please download the Beta Release Firmware at: http://www.greamerica.com/support
[FONT=Verdana, Arial, Helvetica, sans-serif]
- The GRE Development Team -[/FONT]​

 

[doug408]

minonr glitches with firmware update process

Installing both updates was uneventful, though I saw the same thing that others have mentioned in the primary PSR-500 thread - V-scanner folders got 'shifted' as part of the process. Quoting user Kikito:

So far the only "adverse" effect I've noticed was that my V-Folders were moved or shifted around within the memory slots of the scanners for some reason. Somehow in the order of 7+ of where they used to be, i.e. what was folder 00 is now 07, folder 01 is now 08 and so on....
Also a small amount of confusion with the updater thinking this is "older" firmware, as it is labeled 0.1

I found a few other trivial problems:
There is a typo in the instructions in each of the .doc files that gets unzipped:

Please be advised that this is a Beta Release. We would like to get as much feedback as possible to help us find any know issues before an official Firmware update is released. Your feedback and support is greatly appreciated.

"any know[n] issues"

Also, the firmware download instructions posted on the GRE web site have a typo in the path:

C:/GRECOM should be C:\GRECOM

 

[SCPD]

V-Folder Shifting

My recommendation is to: DO NOT re-order your V-Folders to compensate for this. I am sure this is a small bug, and I'll see if I can convince them to re-issue a beta U0.2 to fix it

 

[wwhitby]

I just completed both CPU and DSP upgrades. The only thing that I noticed with the process was that the progress indicator bar disappeared after starting when I executed the CPU upgrade. The box was there, but the progress wasn't being updated.

Warren

 

[LEH]

Well, I downloaded and installed both the CPU and firmware upgrades.

I had no problems with either upgrade. The CPU upgrade status bar remained visible and moving throughout the entire process (Win XP SP2).

My P25 reception seems to be significantly improved, but I have not really sat and watched. I am hearing the same calls over two scanners though.

My only issue so far is that I seem to have lost (and this seems to be me only) my ability to capture the CC for a VHF P25 system. Even when I stop the scanner and analyze the system, the known CC does not immediately (like within 1 or 2 seconds) show the CC info. Typically the first display for a VC with a TGID that is well beyond any for the system (VA STARS). When and if it does display the CC data, the decode rate is extremely low (around 10%).

Other systems that I listen to include a 3600 baud 800 system and it seems to be running better. A 3600 baud UHF trunked system that also seems to be running better. An EDCAS 800 system (rarely listen to it). And of course my 9600 baud P25 system which is actually really working.

My frustration level with the scanner has gone done significantly.

 

[troymail]

Success....

In reference to my post on the first weekend (http://radioreference.com/forums/showpost.php?p=632226&postcount=263) -- this upgrade has signficantly improved the reception of two local systems that pretty much did not work at all!!

Howard County Md and Maryland Aviation/BWI are working extremely well now.

 

[DaveIN]

My only issue so far is that I seem to have lost (and this seems to be me only) my ability to capture the CC for a VHF P25 system. Even when I stop the scanner and analyze the system, the known CC does not immediately (like within 1 or 2 seconds) show the CC info. Typically the first display for a VC with a TGID that is well beyond any for the system (VA STARS). When and if it does display the CC data, the decode rate is extremely low (around 10%).

You may want to verify the setting for your VHF P25 system. They may have changed with the firmware revisions. If all is well with your settings be sure to post the details.

 

[LEH]

Dave,

The setting was part of the problem (something prior to the upgrade) changed the system from P25 to MOT VHF/UHF. Changing it back helped a bit. It is still very slow in capturing the CC. My 96 is showing the CC immediately when I stop on it. The 500 takes up to thirty seconds to show the CC info.

 

[DaveIN]

With attenuation/without? Any changes to the global settings? I know it's early in testing, but more data is helpful to GRE to troubleshoot problems.

 

[PC_Medic]

I just completed both CPU and DSP upgrades. The only thing that I noticed with the process was that the progress indicator bar disappeared after starting when I executed the CPU upgrade. The box was there, but the progress wasn't being updated.

Warren

I had the same problem on my first attempt. I just patently waited and then after a minute or two the scanner rebooted as expected and the PC screen advanced to indicate a successful update. Just to be sure I ran it a second time and it progressed normally that time.

I am however having issues with the DSP upgrade. When I click TEST the scanner immediately shows "Error - Turn Off" and after about 10 seconds the PC screen gets a pop-up indicating that No or partial data received from scanner and to try again. Have tried several times with the same result each time.

Any one else had problems like this?

 

[DaveIN]

You can do this and then try again.

0, CLR Erases DSP APP Upgrade code, restores
factory DSP version

If it does not work try downloading the file again, maybe something was wrong with the downloaded file.

 

[PC_Medic]

You can do this and then try again.

0, CLR Erases DSP APP Upgrade code, restores
factory DSP version

If it does not work try downloading the file again, maybe something was wrong with the downloaded file.

Unfortunately I have tried both these steps (more than once and same thing).

Attached is pics of the error from LCD and PC screen.

 

[DonS]

Unfortunately I have tried both these steps (more than once and same thing).

Attached is pics of the error from LCD and PC screen.

The instructions in the DSP Upgrade App don't say to press 0 PGM ENT before clicking the TEST button, do they? Your radio's LCD looks like you did that.

 

[PC_Medic]

The instructions in the DSP Upgrade App don't say to press 0 PGM ENT before clicking the TEST button, do they? Your radio's LCD looks like you did that.

Yes, Step 5 indicates that you need to pres 0 - PGM - ENT to place the radio in the DSP update mode.

I have tried both ways just in case it would work, but then get the expected error that was unable to communicate with radio and to please try again starting from Step 4.

 

[PC_Medic]

Never mind...just answered my own damn question. *** STEP 4 ***

It states in step 4 to turn the radio off, which I was not doing until it failed AND when I would do so I was then clicking EXIT and starting over again. That one little difference from the CPU update did not catch my eye until just now.

Boy do I feel like a Dummy Load

Went in like a hitch now and appears to have fixed my 'no audio' issues with Chesapeake Virginia's 3600 system.

 

[rckydenver]

Never mind...just answered my own damn question. *** STEP 4 ***

It states in step 4 to turn the radio off, which I was not doing until it failed AND when I would do so I was then clicking EXIT and starting over again. That one little difference from the CPU update did not catch my eye until just now.

Boy do I feel like a Dummy Load

Went in like a hitch now and appears to have fixed my 'no audio' issues with Chesapeake Virginia's 3600 system.

Dont feel so bad I was doing that too, plus i was leaving out the PRG while entering the 0-PRG-Enter. DUH...

 

[W4KRR]

I have just applied the DSP and CPU beta upgrades.

Right off the bat, it will now receive the Hollywood, Fla. (1f25) digital PD talkgroups where before I would get only silence, or maybe just digital noise 95% of the time. So it's already a big improvement here. And the Boca Raton Fla. system (813a), which was being decoded fine before the upgrade, still seems to be working fine....I think. Might be a little "iffy" now, not quite sure yet.

BTW, on the GRE site, I see a "PSR-500 Beta CPU Firmware U01" and also a "PSR-500 CPU Firmware 1.0". What's the difference? I used the "Beta" one because I assumed that the other one is the original factory loaded one, am I correct?