GRE PSR-500 Firmware Release Thread

[thewenk]

I think you have good notes.

What is interesting is that you are getting variable results depending on time. Signals do change by time of day and even time of year (leaves, no leaves). In any case it seems that when conditions are good that you prefer CPU 0.1 and DSP 0.2?

Not exactly. I would say that when conditions are good CPU 0.1 and DSP 0.2 are about equal to CPU 1.0 and DSP 1.0 for me. I don't think I have had enough time with "good" conditions to say the new firmware is better. Right now I'm using the original firmware and ieverything is good for me. I'll try some further experimenting this morning.



EDIT - 1-Changed to CPU 0.1 left DSP at 1.0
The decode rate was as good or better on weak site (86-98)and as good or better on the two stronger sites(86-99). Listening test is good. CPU 0.1 seems good, maybe a little better than CPU 1.0 in this test.
2-Next changed from DSP 1.0 to DSP 0.2, with CPU 0.1.
The decode rate for the weak site went to highly variable (54-92). The low decode rates were seen, but not frequently, thus in a listening test problems would not be too obvious. I did observe several instances of the scanner locking on to the transmission but the audio was delayed by several seconds when compared with the 996. The two stronger sites also had more variable decode rates(80-94), but the low end was not as bad as the weaker site. Right now in listening tests things seem fine. I am using an outside 700 MHz tuned antenna with an Electroline unity gain amp to split the signal to my PSR 500 and 996T for the listening comparisons.

CONCLUSIONS:
1 - DSP 0.2 causes the problems I am observing. CPU 0.1, as far as decode rates go, maybe even improves things a little.
2 - DSP 0.2 causes the decode rate to become more variable and inconsistent, especially on weaker signals. It seems to cause a little more variability on stronger signals too. I can see how, as the decode rate jumps into the low reading more frequently, the reception problems observed while listening will obviously get worse too.

EDIT #2 - About 90 minutes after previous readings. Decode rate on weak site now 24-78 and missing some transmissions entirely that the 996 receives. Stronger sites not much change in decode; receiving OK.

EDIT #3 - Weak site is now showing decodes from 25-50. T indicator is intermittent. Missing some transmissions, but actually getting more than I would have thought. Stronger sites are decoding 78-98 and constant T indicator.
Switched back to DSP 1.0 with CPU 0.1. Now the weak site is 88-98 decode and constant T. Other sites are also better than before (88-98). I now am getting all transmissions that the 996 gets.


Dave

 

[Tom_G]

Follow-up #2 after Firmware Upgrades

Just an additional followup from my previous post here:
http://www.radioreference.com/forums/showpost.php?p=644793&postcount=38

I performed both the CPU and DSP upgrades.
The radio continues to impress me.
The Connecticut State Police system is working pretty flawlessly.
The digital audio is excellent. Its enjoyable to listen to.
At this point, I have to say that the PSR-500 is definately a step above the PRO-96 and 2096 as far as tracking the digital systems and in digital audio quality.
My house is not a great location for monitoring this system and I am very surprised how well this radio works here.

Thanks, Tom/G

 

[SCPD]

Not exactly. I would say that when conditions are good CPU 0.1 and DSP 0.2 are about equal to CPU 1.0 and DSP 1.0 for me. I don't think I have had enough time with "good" conditions to say the new firmware is better. Right now I'm using the original firmware and ieverything is good for me. I'll try some further experimenting this morning.



EDIT - 1-Changed to CPU 0.1 left DSP at 1.0
The decode rate was as good or better on weak site (86-98)and as good or better on the two stronger sites(86-99). Listening test is good. CPU 0.1 seems good, maybe a little better than CPU 1.0 in this test.
2-Next changed from DSP 1.0 to DSP 0.2, with CPU 0.1.
The decode rate for the weak site went to highly variable (54-92). The low decode rates were seen, but not frequently, thus in a listening test problems would not be too obvious. I did observe several instances of the scanner locking on to the transmission but the audio was delayed by several seconds when compared with the 996. The two stronger sites also had more variable decode rates(80-94), but the low end was not as bad as the weaker site. Right now in listening tests things seem fine. I am using an outside 700 MHz tuned antenna with an Electroline unity gain amp to split the signal to my PSR 500 and 996T for the listening comparisons.

CONCLUSIONS:
1 - DSP 0.2 causes the problems I am observing. CPU 0.1, as far as decode rates go, maybe even improves things a little.
2 - DSP 0.2 causes the decode rate to become more variable and inconsistent, especially on weaker signals. It seems to cause a little more variability on stronger signals too. I can see how, as the decode rate jumps into the low reading more frequently, the reception problems observed while listening will obviously get worse too.

EDIT #2 - About 90 minutes after previous readings. Decode rate on weak site now 24-78 and missing some transmissions entirely that the 996 receives. Stronger sites not much change in decode; receiving OK.

I will leave this configuration running and see if things get worse as they did yesterday. Hope this info helps.

Dave

What system type are you testing on, 3600CC or 9600CC?

Craig

 

[DonS]

What system type are you testing on, 3600CC or 9600CC?

So far, I think the only system thewenk has mentioned (in this thread, at least) has been:

Monitoring Idaho IIMARS System (700 MHz P25) http://www.radioreference.com/modules.php?name=RR&sid=4742

 

[thewenk]

What system type are you testing on, 3600CC or 9600CC?

Craig

9600. It's the Idaho 700MHz P25 System
http://www.radioreference.com/modules.php?name=RR&sid=4742

I am posting another update to my previous post. It essentially confirms my previous conclusions.

Dave

 

[IndyEmsGuy]

I have also noticed that with the new DSP firmware I am getting a lot of "machine gunning" noise now and that the audio doesn't seem nearly as clear. DSP 1.0 has none of this at least for me.

 

[thewenk]

I have also noticed that with the new DSP firmware I am getting a lot of "machine gunning" noise now and that the audio doesn't seem nearly as clear. DSP 1.0 has none of this at least for me.

I would agree the audio is somewhat different with CPU 0.1 & DSP 0.1, although most of the change I'm hearing I think came with CPU 0.1. DSP 0.1 may make it somewhat worse. I am not hearing the problems you're describing, but what I'm hearing is a little hard to describe - more high frequencies in the voices, or something like that. At times it seems unpleasant to listen to, but it still seems clear.

Dave

 

[IndyEmsGuy]

I had the oppertunity to set mine side by side with a friends Pro96 today. We have the same stuff programmed, I started with his Pro96 file. His will pickup at the beginning of a transmission and mine will pick up about 1/2 to 2/3 through the transmission. i am not sure if there is a setting somewhere that will help with that but it is pretty annoying to only listen to little parts of each transmission. This is only happening on trunked systems Motorola type II 800mhz

 

[DaveIN]

I had the oppertunity to set mine side by side with a friends Pro96 today. We have the same stuff programmed, I started with his Pro96 file. His will pickup at the beginning of a transmission and mine will pick up about 1/2 to 2/3 through the transmission. i am not sure if there is a setting somewhere that will help with that but it is pretty annoying to only listen to little parts of each transmission. This is only happening on trunked systems Motorola type II 800mhz

I see three Johnson Co. SAFE-T towers in the RR SAFE-T database. Are you listening to all three? Multisite Off, Roam, Stat? Same antenna? Attenuation? Just the control channels?

 

[thewenk]

I had the oppertunity to set mine side by side with a friends Pro96 today. We have the same stuff programmed, I started with his Pro96 file. His will pickup at the beginning of a transmission and mine will pick up about 1/2 to 2/3 through the transmission. i am not sure if there is a setting somewhere that will help with that but it is pretty annoying to only listen to little parts of each transmission. This is only happening on trunked systems Motorola type II 800mhz

Is this with DSP 0.1 or DSP 1.0 or both? I have seen this with DSP 0.1, but not with DSP 1.0. It seems to occur with DSP 0.1 and a weak signal, resulting in a low decode % on the control channel. If the decode rate is variable and gets better, the radio will suddenly pick up the transmission. I think it's a problem with DSP 0.1 and I haven't heard of any adjustment to fix it - - that is if it's the same problem I have seen.

Dave

 

[IndyEmsGuy]

I see three Johnson Co. SAFE-T towers in the RR SAFE-T database. Are you listening to all three? Multisite Off, Roam, Stat? Same antenna? Attenuation? Just the control channels?

Yes I have all three towers programmed. Just the CC frequencies. Multisite set to ROAM. Attenuation on because if it is off all audio is just garbled. Both scanners have the RS 800 rubber duckie antenna. This seems to be because of the new DSP firmware. I had some trouble with this on DSP 1.0 but it is constant with DSP 0.1

 

[DaveIN]

OK, maybe you should try this:
http://radioreference.com/forums/showpost.php?p=645126&postcount=47
or this for the "braap" also known as "machine gunning":
http://radioreference.com/forums/showpost.php?p=645867&postcount=58

 

[shaft]

Yes that is correct. The 1.0 firmware is the factory default one.

 

[SCPD]

CPU U0.2 and DSP U0.3 is out...

GRE just released new CPU and DSP firmware. The update notes are...

CPU U0.2:
-Fixed: FUNC key problem in V-Scanner mode (sometimes gave an error beep)

-Fixed: Disappearing "FrLO" softkey in TUNE mode

-Fixed: Cancel WX alerts when any WX mode "exit" key (including WX) key is pressed

-Fixed: SAME event/area matching when 000000 area codes are received

-Fixed: Allowed values in GLOB 'Dflt ScanList' item to match the [correct] help text

-Fixed: Default scan list' GLOB item to allow "0" (no scan list)

-Improved: While on a CONV object in MAN, pressing MAN again now resets the tuned object to allow a new mode detect (DG/FM, SQ:Search, etc.)

-Improved: While the "ShowCCInfo" GLOB setting is enabled: Removed control channel (CC) index/quality display from TGRP/MAN display. Within P25/M36 modes, while showing TGRP and the voice channel (VC), show the CC index-slot and CC freq (blinking/alternating) with the VC frequency. This is an aid to understanding which CC the radio used to trunk to the VC. This is especially useful within multi-site areas


DSP U0.3:
- Slight improvement over U0.2, especially on very weak signals.

 

[DonS]

RE: CPU U0.2 and DSP U0.3 is out

Working well here!

Media Player... File ... Open URL...
http://home.starrsoft.com:3767

or a direct (should be) clickable link:
mms://home.starrsoft.com:3767/

 

[detroit780]

No Audio is no great audio

Taking a suggestion from CPUNut and adjusting my Noise Threshold from 20 to 50 I noticed it actually got a but worse so I increased it to 80 and it got even worse. So I thought I would start at 01. It seems fine in the last 40 minutes comparing it to a 796D and Pro-2096 all are decoding the same thing at the same time.

That is monitoring the Michigan MPSCS system off tower 211 Howell;

1 control channel in SYS
Multi Site off
Super Track On
0% memory remaining (Hey it's a big system) Pretty much every known TG plus many conventional channels plus the Ingham County EDACS SYS.
CPU 0.2
DSP 0.3

Looks very good at this point.

I did notice comparing all 3 radios the PSR will miss most of the action if I scan everything so I have a FAV file of all the truly local stuff and it does just fine decoding as fast as the others and sounding awesome.

My earlier problem with the LED on and no audio is partially related to the LED. Nothing wrong with the LED it just draws your attention to the radio and you wait for audio. The 796 and 2096 were stopping on the same TG's with no audio.

So to quote others her Awesome Radio GRE. It gets better each day.

Les

GRE just released new CPU and DSP firmware. The update notes are...

CPU U0.2:
-Fixed: FUNC key problem in V-Scanner mode (sometimes gave an error beep)

-Fixed: Disappearing "FrLO" softkey in TUNE mode

-Fixed: Cancel WX alerts when any WX mode "exit" key (including WX) key is pressed

-Fixed: SAME event/area matching when 000000 area codes are received

-Fixed: Allowed values in GLOB 'Dflt ScanList' item to match the [correct] help text

-Fixed: Default scan list' GLOB item to allow "0" (no scan list)

-Improved: While on a CONV object in MAN, pressing MAN again now resets the tuned object to allow a new mode detect (DG/FM, SQ:Search, etc.)

-Improved: While the "ShowCCInfo" GLOB setting is enabled: Removed control channel (CC) index/quality display from TGRP/MAN display. Within P25/M36 modes, while showing TGRP and the voice channel (VC), show the CC index-slot and CC freq (blinking/alternating) with the VC frequency. This is an aid to understanding which CC the radio used to trunk to the VC. This is especially useful within multi-site areas


DSP U0.3:
- Slight improvement over U0.2, especially on very weak signals.

 

[thewenk]

CPU 0.2 and DSP 0.3

CPU 0.2 and DSP 1.0 = good

CPU 0.2 and DSP 0.3 - Decode rates on my weak site are not that good (30-72) compared with DSP 1.0 (86-96). I am missing transmissions on the 500 that the 996 is receiving (same as DSP 0.2). Switched back to DSP 1.0 and now getting all transmissions and decode rate back up to 85-95.

DSP 1.0 is still the best for me. DSP 0.3 doesn't seem much better than 0.2.

CPU 0.2 looks good

Thanks for trying, GRE.

Dave

 

[scnnr]

Working well here!

Media Player... File ... Open URL...
http://home.starrsoft.com:3767

or a direct (should be) clickable link:
mms://home.starrsoft.com:3767/

Don I am monitroing your live stream right now and saw you making a lttle adjustment there on the radio a few minutes ago. I was just wondering if it is possible if you could maybe try to switch off the DG AGC just to see if it will clean up the audio a little more. It still sounds a lot like our system here when the AGC is on. However we don't have much choice as the RCMP here use older firmware in there older xts 3000 portables.

 

[troymail]

GRE just released new CPU and DSP firmware. The update notes are...

CPU U0.2:
-Fixed: FUNC key problem in V-Scanner mode (sometimes gave an error beep)

-Fixed: Disappearing "FrLO" softkey in TUNE mode

-Fixed: Cancel WX alerts when any WX mode "exit" key (including WX) key is pressed

-Fixed: SAME event/area matching when 000000 area codes are received

-Fixed: Allowed values in GLOB 'Dflt ScanList' item to match the [correct] help text

-Fixed: Default scan list' GLOB item to allow "0" (no scan list)

-Improved: While on a CONV object in MAN, pressing MAN again now resets the tuned object to allow a new mode detect (DG/FM, SQ:Search, etc.)

-Improved: While the "ShowCCInfo" GLOB setting is enabled: Removed control channel (CC) index/quality display from TGRP/MAN display. Within P25/M36 modes, while showing TGRP and the voice channel (VC), show the CC index-slot and CC freq (blinking/alternating) with the VC frequency. This is an aid to understanding which CC the radio used to trunk to the VC. This is especially useful within multi-site areas


DSP U0.3:
- Slight improvement over U0.2, especially on very weak signals.

I just loaded the latest --- sounds pretty good. Not sure I've noticed a huge improvement over the previous BETA releases.

I just heard a digital I-Call on my local system (which is still analog but some I-Calls are digital)... crystal clear! For a moment, I didn't even think it was digital because I'm not used to hearing things that clear in digital on a scanner....

 

[bc780l]

800 MHz Interference

Analog 800 MHz interference, especially in close proximity (within a mile or so?) to what appears to be CDMA cell sites, gives a lot of grief to any 800 MHz transmission I'm trying to receive, whether an 800 MHz Motorola Type II Smartnet analog system or a simple 800 MHz repeater. This problem occurs in my static environment, as well as mobile--see a tower coming and the reception goes down the tubes. Activating the attenuator may in some limited circumstances help, but in most cases the noise, and in some cases chuffing, is still there. The attenuator may indeed even loose the desired signal. My thoughts have been that this is a front-end problem in the receiver, but had hopes that the DSP might tighten this up, and dubiously, the CPU upgrades might have helped. Alas, not.

I do note that the CPU 0.2 upgrade reduced the chuffing significantly, but not completely. DSP 0.3 had no effect, either with or without the other. Interference still is there. I have NO such problems with the BCD396T. Attached is a zip of a short wav file that causes me headaches, just for your consideration.