PSR-500/600 1.4 firmware released (and new DSP 1.3)

[tglendye]

I don't know whether this is mentioned in the docs or not (haven't downloaded this update yet), but remember that LTR trunked system do not have individual radio IDs, so you should not see any IDs when watching an LTR channel except talkgroups.

I think that's in GRE's doc's if I remember correctly. They said it is for Motorola and EDACS systems, but did not include LTR... now I understand why. Thanks.

 

[DonS]

I wonder if removing the DG indication was an update oversight by GRE. I think this is something that needs to be addressed by GRE because the digital or analog information can be important to a bunch of us. Anybody agree?

The removal of the 'DG' indication was an oversight. GRE is aware of it.

 

[mtindor]

Hmm, I never noticed that. Either it only happens on true P25 systems or it happens on Ohio MARCS and I just never noticed it. Once again I've been schooled Thanks.

Mike

Mine used to say VC on an analog Voice Channel and DC on a Digital Voice Channel, Now it says VC all the time..

See this link from a question about that previously, Hope it helps! Just curious, It doesn't matter that it says VC, It was just odd it says VC instead of the usual DC...

VC Analog Voice Channel
DC Digital Voice Channel

http://www.radioreference.com/forums/showthread.php?t=106944

 

[wm8s]

Same here i cant get the ID to work either either im too tired or im slow tonight

After enabling Show Radio IDs, my local P25 system still didn't display them. After letting it run a while, though, I saw a few blip up for a millisecond or two. Apparently, decoding on that system is still spotty (even though I get near 100% quality in Analyze). EDACS systems decode much easier, and show RadioIDs more frequently.

...R

 

[fmon]

Not getting the Radio ID on STARS but working ok on 5 Smartnet 800, a Smartzone 800, an EDACS 800 Standard, 1 of 3 Smartzone 400 and none of 2 LTR regular.

Thanks Dave and Todd for the reminder on LTR ID's.

I found the problem on the 2 400 Smartzone's. [FONT=&quot] Norfolk NavBase and Norfolk NavShpYd[/FONT] in this [FONT=&quot] Eastern Virginia Regional Communications System were the problem due to Mot 800/900 set in the TSYS. [/FONT]
[FONT=&quot]
I think it is this Win500 [/FONT]Version 0.32[FONT=&quot] which Don helped us use this system with controls of both 800 and 400 in the same TSYS. This version included the table for 800 freqs but also sets the system to 800/900. [/FONT][FONT=&quot]Changing to VHF/UHF is the fix for getting the RadID's to display.[/FONT]

 

[WayneH]

EDACS systems decode much easier, and show RadioIDs more frequently.

EDACS systems use transmission (versus "message") trunking so when the conversation is over the carrier immediately drops resulting with the scanner going back to the control channel. Motorola systems typically have a hang-time so you end up staying on the voice channel more often than with EDACS as users have to be quick to get the same channel.

 

[DonS]

EDACS systems use transmission (versus "message") trunking so when the conversation is over the carrier immediately drops resulting with the scanner going back to the control channel. Motorola systems typically have a hang-time so you end up staying on the voice channel more often than with EDACS as users have to be quick to get the same channel.

Which, of course, means:
* EDACS systems get a new "grant" message for any reply, yielding the ID for the replying radio
* Mot systems don't get a new grant, since they never went back to the CC, so we're stuck with the ID (if any) that we see when we started monitoring the call

Result:
* EDACS systems can show Radio IDs for every radio involved in a conversation
* Mot systems will likely show Radio IDs only for the first radio involved, unless other participants take a long time to reply

 

[patin]

it would be nice to be able to show the tag for each bank (CONV) instead of it being blank on the fourth line (like the pro96) and remove the TSYS and be able to put a tag name there for trunking

 

[DonS]

it would be nice to be able to show the tag for each bank (CONV) instead of it being blank on the fourth line (like the pro96) and remove the TSYS and be able to put a tag name there for trunking

As has been asked here many times... what would you display? Any CONV or TGRP object can belong to zero, one, two, ... , twenty scan lists that are "enabled" for scanning at one time. Which of those (up to twenty) tags would you display when the CONV or TGRP object was active?

 

[BVince]

Upgraded

Just upgraded the GRE PSR 500 to CPU 1.4 and DSP 1.3. It is great to see the Radio ID displayed. A great radio just keeps getting better!

We have very high % of good displays on many TRS systems in the Shelby Co, Tn/Desoto Co, Ms area; digital and analog.

Way to go GRE!!!!!!! Keep up the good work!

 

[jehm1212]

The radio ID feature works perfectly on a local SmartZone system, but will not work at all on this EDACS system: http://www.radioreference.com/apps/db/?sid=134. I tried adjusting some of the advanced global settings, such as unmute delay, but to no avail. Any ideas as to why it may not be working?

 

[patin]

tags

As has been asked here many times... what would you display? Any CONV or TGRP object can belong to zero, one, two, ... , twenty scan lists that are "enabled" for scanning at one time. Which of those (up to twenty) tags would you display when the CONV or TGRP object was active?

like in ICIS when it stops on a CC you can tell what site its from,,,or in CONV that im scanning LAPD ,LAFD, etc,,(just like the pro 96)in stead of it being blank or have TSYS

 

[captaincraig44]

like in ICIS when it stops on a CC you can tell what site its from,,,or in CONV that im scanning LAPD ,LAFD, etc,,(just like the pro 96)in stead of it being blank or have TSYS

Why don't you just tag the CONV memory item as "LAFD"? Again, you can have the same memory item in multiple scan lists, so just tag that memory item with your descriptor. Maybe we're misunderstanding you, but there is no point or practical way to have the fourth line display what you're listening to on the 500. That's what the alpha tagging of memory items accomplishes.

 

[fmon]

like in ICIS when it stops on a CC you can tell what site its from,,,or in CONV that im scanning LAPD ,LAFD, etc,,(just like the pro 96)in stead of it being blank or have TSYS

Line above bottom line will indicate Programmed Alpha Tag for CONV Object, just like the Pro-96

 

[patin]

Line above bottom line will indicate Programmed Alpha Tag for CONV Object, just like the Pro-96

like the pro96 it can read like this i can see im montoring LAPD bank and what station its on also at the same time 484.2875 harbor division LAPD

 

[DonS]

like the pro96 it can read like this i can see im montoring LAPD bank and what station its on also at the same time 484.2875 harbor division LAPD

The PRO-96 has "banks", and any conventional channel or talkgroup belongs to exactly one bank. However, the "bank alpha tag" is NEVER displayed for

• talkgroups (you see only the talkgroup's tag on line 4 and the control channel's tag on line 3)
• conventional channels that have CTCSS/DCS programmed (line 3 has the channel's tag, line 4 has the CTCSS/DCS value)

The PRO-96's "bank alpha tag" is ONLY displayed for conventional channels that have no CTCSS/DCS programmed.

The PSR-500 does not have "banks"; it has "scan lists". Any object (e.g. conventional channel, talkgroup) can belong to MULTIPLE active scan lists. If the scanner was to display a "scan list tag" on line 4, which scan list should it choose?

The PSR-500 already displays:

• CONV, with CTCSS/DCS/NAC programmed: 16-character tag on line 3, any CTCSS/DCS/NAC info on line 4 (this is identical to PRO-96)
• CONV, with no CTCSS/DCS/NAC programmed (Sq Mode: None): 16-character tag on line 3. Line 4 is empty
• TGRP: 16-character TGRP tag on line 3 (just like PRO-96), alternating with 16-character TSYS tag. VC frequency on line 2 (just like PRO-96), alternating with CC index and frequency (if option enabled). Line 4 contains either softkey text or Radio ID (private calls, plus group calls if new feature enabled)

 

[DonS]

Radio IDs

In addition to the GRE release notes regarding cases where Radio IDs may not be displayed:

• Scanning multiple trunking systems, or a single trunking system with any CONV objects enabled. By the time the scanner is able to sample the CC, the initial "grant" messages will likely have been issued, leaving only the "update" messages
• Scanning a single TSYS, multiple TGRPs (or even a wildcard TGRP in MAN mode), where the radio is in a voice call, returns to the CC when that call ends, then immediately goes to a new, in-progress voice call based on "update" messages
• Motorola systems, even within a single call, may only give the ID of the radio that initiated the call. Responses within the same call, if the scanner never returns to the CC, will continue to show that initial ID - even though other radios are involved. This is due to "transmission" versus "message" trunking

here are a few more:

• MOT or P25 systems where you have Multi-Site set to Stat. The scanner is going through all the control channels, and won't necessarily be on a given control channel when the RadioID-containing "call grant" message appears
• MOT systems that use "Scan Markers", where you have the Dwell value set to the default of 0 (zero). That value will make the scanner leave the CC after it sees two Scan Markers, and it may miss "call grant" messages during the time it's not actively looking at the CC. Changing the Dwell to 10 (ten) will make the scanner behave as if Scan Markers were not used on the system (i.e. same as a no-Scan-Marker system with Dwell set to zero)
• Priority turned on, with "priority TGRPs" in the TSYS. While the scanner is looking for "priority TGRPs", it may ignore "call grant" messages for non-priority TGRPs. By the time it actually decides to monitor a non-priority TGRP, the "call grant" message is gone.

 

[patin]

The PRO-96 has "banks", and any conventional channel or talkgroup belongs to exactly one bank. However, the "bank alpha tag" is NEVER displayed for

• talkgroups (you see only the talkgroup's tag on line 4 and the control channel's tag on line 3)
• conventional channels that have CTCSS/DCS programmed (line 3 has the channel's tag, line 4 has the CTCSS/DCS value)

The PRO-96's "bank alpha tag" is ONLY displayed for conventional channels that have no CTCSS/DCS programmed.

The PSR-500 does not have "banks"; it has "scan lists". Any object (e.g. conventional channel, talkgroup) can belong to MULTIPLE active scan lists. If the scanner was to display a "scan list tag" on line 4, which scan list should it choose?

The PSR-500 already displays:

• CONV, with CTCSS/DCS/NAC programmed: 16-character tag on line 3, any CTCSS/DCS/NAC info on line 4 (this is identical to PRO-96)
• CONV, with no CTCSS/DCS/NAC programmed (Sq Mode: None): 16-character tag on line 3. Line 4 is empty
• TGRP: 16-character TGRP tag on line 3 (just like PRO-96), alternating with 16-character TSYS tag. VC frequency on line 2 (just like PRO-96), alternating with CC index and frequency (if option enabled). Line 4 contains either softkey text or Radio ID (private calls, plus group calls if new feature enabled)

oh okay theirs a differance i understand why now makes sense

 

[Skud]

I have not done the firmware yet, going to tonight, but would live to see where it tells me the tower ID when it is on a P25 control just like when I hit TSYS then manual. Usfull on Multi-Site setups.

 

[kikito]

I have not done the firmware yet, going to tonight, but would live to see where it tells me the tower ID when it is on a P25 control just like when I hit TSYS then manual. Usfull on Multi-Site setups.

Maybe GRE could add an "option choice" to show either the Radio ID or the Tower ID. I don't think there's any space left to put them both unless they make that bottom line alternate between Radio ID and Tower ID. With the third line already alternating between TG ID and System tag, it would be a really convoluted/confusing display I would think.