GRE Releases PSR-500/600 CPU Firmware U1.7

[AZScanner]

GRE did (does) care about it. However, as mentioned in the posts pro92b referenced above, there are some problems with implementing it in the current PSR-500 family hardware.

Here's some more detail on the difficulties described in those posts:

The primary problem is code space. That is, at present, "P25 encryption muting" won't fit in the hardware where it needs to run. In order to implement the feature, substantial effort is required - not just for the feature itself, but to move other functionality around so that the desired feature would even fit in the hardware. Moving that other functionality, in order to make room, involves substantial risk - the risk that these changes would cause many other "things" to break.

It's not merely a matter of "let's add P25 encryption muting to this one module, because we know how to do that". Instead, it's that, preceded by "let's move a bunch of functionality from one place to another, and add all of the internal communications required to handle that 'move', hoping we don't break anything or run into any other roadblocks in the process, and hoping that the internal communications can even handle the moves in the first place".

I know this is a firmware thread but my ancient BC250D and 796D don't have that newfangled fancy P25 Encryption Skipper doo-dad thingie on them either. So I created a little workaround.

Don - does the protocol for the 500 allow you to emulate pressing the scan key, and does the display indicate when an encrypted transmission is received? If so it should be a fairly simple matter to emulate this feature via control software. It's how I did it for my old unidens. On my 796, when it hits encryption, the display alternates P25/ENC instead of the usual P25/LNK. Whenever it saw ENC instead of LNK, I told the little control program I wrote to hit the scan button. Problem solved. Maybe you could add that to Win500 for these guys.

-AZ

 

[SCPD]

I had no problems doing my 500. Just read the instructions ... as I see some of you didn't, as per the screen shot above.

However I am disappointed that there is little in this update. Do I love my 500 ... yes it is still a very nice scanner.

I am still a little disappointed that they didn't fix the issue with patches on Edacs (As well as Motorola I assume) systems. But I can see that P25 encryption noise would be an annoying issue. So I guess I will just use my work around for now.

 

[SCPD]

Anyone know if the EDACS channel numbers are reported properly in CF1.6?

Jay ... I didn't have any problems with Edacs in ver 1.6 and I don't see any issues in 1.7.

This is other than the scanner avoiding Edacs patches .. which it doesn't understand. You miss ALL transmissions on patched edacs talkgroups (if you monitor the normal talkgroups when they are using a patch). I am using a work around and programming the talkgroups that they are using for patches .. and it works that way. Is it pretty ... NO, but it does get the job done. It is nice that the Uniden models don't have this issue.

 

[rdale]

Why do you insist on always throwing gas on the fire when someone post what they feel is a good idea, one user even asked you nicely not to do so.

Because this isn't the "what is a good idea" thread, this is the 1.7 firmware thread. Organization has its purpose...

 

[DonS]

Don - does the protocol for the 500 allow you to emulate pressing the scan key,

Yes.

and does the display indicate when an encrypted transmission is received?

No. (If it did, that would imply that the scanner "knows about" an encrypted transmission, making "skipping encrypted transmissions" a trivial matter within the scanner.)

 

[rocksteady]

So faf it seems better in my area..

 

[Jay911]

Just one tiny bit I want to chime in on about encryption: On Motorola Type II systems, any "status bit" value > 7 indicates encryption is in use on that talkgroup. That's part of the trunking data sent out, so it's going to be there.

 

[WayneH]

The lack of encryption is about discussing current firmware

No, it's not. Firmware release threads are not for complaining about what they don't have that you want. It's for discussion of the features provided by the recent firmware.

If the firmware is of no interest to someone, fine, you can say so but we don't need a sob story about how disappointed someone is. Give GRE some credit for friggin sake; they've done a lot in regard to listening to customers so if something doesn't happen it probably cannot. If the OT continues I'm going to cleanse this whole thread. Please do not muddy up Stickies.

 

[poppafred]

Aero Band Step

Now if we could just get rid of the 8.33 MHz step size default in the VHF aero band....

I contacted GRE about that today.

Apparently, the FCC has plans to change the step in the aero band from 25 to 8.33 kHz some time in the future and GRE is just ahead of the curve:

-----------------insert-------------------------

Hi Fredrick,

We picked 8.33 kHz because that step is compatible with both the current 25 kHz spacing and the future 8.33 kHz spacing for the band. At present we don't have a way to change the step to 25 kHz.

Best regards,

Jack
GRE Support Team
GRE America, Inc. - Powered By Kayako SupportSuite

-------------------end--------------------------

 

[bravo14]

I was testing FL Power Light 900 system in my area. It still locks up on the Control Channel or Talkgroup. I have to keep hitting scan or up/down button to get rid of the machine gun sound.

 

[DaveNF2G]

I contacted GRE about that today.

Apparently, the FCC has plans to change the step in the aero band from 25 to 8.33 kHz some time in the future and GRE is just ahead of the curve:

---

Correction, the FCC had plans - past tense - to go to European narrow spacing. The airlines aren't going to pay for the change, and neither is Congress, so it's not going to happen any time soon.

 

[DaveIN]

Do you have a reference that metions not using the 8.33 standad somewhere Dave?

 

[rdale]

Delete

 

[rdale]

I was testing FL Power Light 900 system in my area. It still locks up on the Control Channel or Talkgroup. I have to keep hitting scan or up/down button to get rid of the machine gun sound.

If it's locking up on the CC, it sounds like a problem with your programming. Might want to start a new thread and go into more detail.

 

[mobile1]

EDACS LCNs and Unitunker

So my scanner will not take the 1.7 firmware (DSP CF1.3, firmware CF1.6) and I presume that's because it's Canadian. . Anyone know if the EDACS channel numbers are reported properly in CF1.6? 'Cause I plan to go do some Unitrunker work with this radio next week in EDACS territory near here.

I have run my PSR600C/500C with Unitrunker on my local EDACS system and no LCN information shows up at all. Both of my GREs are CF1.3 / CF1.6

 

[K8PBX]

So far it seems better in my area..

Hey Rocky... what seems better in the Macomb County area?

 

[rocksteady]

I don't know why but my reception signal and sound quality is better, For some reason I have a stronger signal on my display. It seems to pick up p25 faster and no cutting out like it did before the upgrade, not that it did alot.. The upgrade doesn't say it should, but it does.. go figure..

Rocky

 

[Kel]

CPU 1.7 to Radio Shack

Just curious if anyone has tried to download this GRE update to there Radio Shack units to see if any thing does happen?

 

[iMONITOR]

Just curious if anyone has tried to download this GRE update to there Radio Shack units to see if any thing does happen?

\


It will not allow you to upload the GRE firmware to a Radio Shack scanner. You have to wait until GRE creates the Radio Shack branded firmware, and for Radio Shack to post it on their web site. My guess is it will show up very soon.

 

[wwhitby]

If GRE includes a P-25 Mask/Mute in a future update I hope they make it switchable.... Since I do a lot of snooping and logging, I like to know if a particular transmission is encrypted or if a particular TG or freq has gone that way.

Agree with you 110%! I'm also one of those folks who likes to figure out trunked systems or usage of conventional frequencies, even if you can't listen to all the traffic. There's a big difference between doing sleuthing and just listening.

I was disappointed when GRE removed the ability of the PSR-500 to stop on ProVoice talkgroups. Even though I coulnd't listen to the traffic, I was finally able to know what talkgroups were being used without using Unitrunker. BTW, I wouldn't be heartbroken if GRE brought this back and made it user selectable as well.

Warren