Random TG appearing, not even in the pager

[AdamHLG]

I am going to open a ticket at Rays. I also know there is a way to record a log file when it happens (from reading other posts). My question is whether Unication support even exists anymore. I am beta testing these radios for 3 members in my station. If this does not get addressed we will not proceed with a possible company rollout. My inbox would explode every time it happens.

Please keep this thread updated on your progress and I will do as well. And if anyone else has this issue please chime in if you hear anything about a fix. I hope its just a firmware update.

 

[FishScan]

This is all happening on the same system?

 

[RaleighGuy]

This is all happening on the same system?

There are multiple people in different states having the issue.

 

[AdamHLG]

different states - - and different systems - both P25 Phase 1 and P25 Phase 2

 

[OnYourSix]

There is Unication support still, I was on an email chain with them and Ray. They provided me a beta firmware update (1.32) but it didn't fix the issue.

I just shipped out my pager today. I will let you know when I get a new pager back.

I am going to open a ticket at Rays. I also know there is a way to record a log file when it happens (from reading other posts). My question is whether Unication support even exists anymore. I am beta testing these radios for 3 members in my station. If this does not get addressed we will not proceed with a possible company rollout. My inbox would explode every time it happens.

Please keep this thread updated on your progress and I will do as well. And if anyone else has this issue please chime in if you hear anything about a fix. I hope its just a firmware update.

 

[AdamHLG]

Thanks for the update. That’s encouraging. It’s not your radio bud. Sorry. I’m at the firehouse now and 3 other people with unications having the same issue… but it only started last 2 weeks or so for all of us. It’s so bizarre. It’s almost as if Motorola is the one that had some sort of nationwide firmware update and now Unication needs one too.

There is a way to generate log files. Once I have a ticket open I’ll send these to Uni if they want them.

 

[OnYourSix]

@AdamHLG I think Unication was calling it a "bleed over" issue. Good luck!

 

[AdamHLG]

Oddly, there has been no "bleed over" today after 4 of us with Unications got it really bad at the firehouse last night simultaneously (all identical talk groups identified during the 'bleed' across each of our radios). I also heard our dispatch testing pagers 3 or 4 times this morning by monitoring the dispatch channel. I cannot ignore that evidence. It is not beyond the realm of possibility that this issue is on the broadcast system side in my county. Maybe - just maybe - they are testing this unbeknownst to me, others complained, and they fixed it? Maybe its the 'patched talk group' scenario and its on their end? In addition, I am not eliminating myself as a suspect yet. The other radios in our station are all based on my config file. While I am confident that I am not the source of the problem, I can not eliminate myself as a suspect (despite the fact it was working fine for 2 years).

So.... I will monitor this (literally and figuratively). If it persists, I am going to create a new config file from scratch. I will only program the Zone we need. The radio will basically be empty except for zone 1 and the talk groups we need. I will see if the error replicates as I run it along side my other Unication. This way I can also report this back to Unication. There is a benefit that all of our radios are having the same issue - so this would establish conclusively if something happened along the way during programming additions over the years. But its been fine for 2 years until recently. Still a necessary step in troubleshooting. But this will not happen this week. I need to see if it goes away by itself first.

One would think the problem would be way more widespread and reported on this forum and on Facebook if it was such a known issue. I am trying to apply critical thinking here.

I will post updates as I learn anything new.

 

[west-pac]

Briefly scanning thru the thread here, have you guys ruled out 'skip'? I saw someone mentioned it in a comment. I've had this happen before monitoring P25 sites on scanners, not a pager. The CC for your local site is also likely a CC for another site, either on your same statewide system, or on another system entirely. Your pager may be briefly picking up the CC data from another nearby site/system on the same frequency you have programmed for your local site. If you have a CC, and ACC freqs programmed it may be recieving CC data off of one of your local ACC freqs in your pager, thus receiving some miscellaneous site, system, and TG.

I've yet to see anyone figure out what/who the miscellaneous TGs are. Eventually you'll hear a city/town name, dispatcher's voice, units numbers, locations, or something that you'll recognize. Even the TG number can be traced back to a site or frequency to see how and/or why your pager is receiving it.

 

[AdamHLG]

I can only speak for my issue, but the bleed is our local PD talk groups that share the same system with FD. So far today fingers crossed it has not happened. Reeeealllllly hoping this was a programming issue on our county's P25 system. Time will tell.

 

[RaleighGuy]

Briefly scanning thru the thread here, have you guys ruled out 'skip'? I saw someone mentioned it in a comment. I've had this happen before monitoring P25 sites on scanners, not a pager. The CC for your local site is also likely a CC for another site, either on your same statewide system, or on another system entirely. Your pager may be briefly picking up the CC data from another nearby site/system on the same frequency you have programmed for your local site. If you have a CC, and ACC freqs programmed it may be recieving CC data off of one of your local ACC freqs in your pager, thus receiving some miscellaneous site, system, and TG.

I've yet to see anyone figure out what/who the miscellaneous TGs are. Eventually you'll hear a city/town name, dispatcher's voice, units numbers, locations, or something that you'll recognize. Even the TG number can be traced back to a site or frequency to see how and/or why your pager is receiving it.

The Unication pagers do not work the same way as a scanner, the pager only monitors one site at a time, they don't sample other freqs (CC or ACC) and they are supposed to ignore any TGs not in your programming, thus even if it was skip the site number would be different (hence ignored) and the TG should be rejected.

 

[AdamHLG]

Like clockwork I jinxed it. The issue is back. I wont keep posting replies. But its time for me to create the clean pps file and continue the testing regiment.

 

[OnYourSix]

I appreciate the suggestion. I have two people who have G5's who monitor the same system as me and they don't have the bleed over, so I know it is a radio by radio basis.

Unfortunately, I have identified the TG, it's one of Raleigh PD's TG's. They are the second busiest agency in the County, if not the entire State. If it was random once a week, I would be okay with it, but you're talking 10 times a day easily. And when you have the pager set to receive only one TG and NOTHING else it programmed into that knob position, it defeats the purpose of a $707.00 pager.

Briefly scanning thru the thread here, have you guys ruled out 'skip'? I saw someone mentioned it in a comment. I've had this happen before monitoring P25 sites on scanners, not a pager. The CC for your local site is also likely a CC for another site, either on your same statewide system, or on another system entirely. Your pager may be briefly picking up the CC data from another nearby site/system on the same frequency you have programmed for your local site. If you have a CC, and ACC freqs programmed it may be recieving CC data off of one of your local ACC freqs in your pager, thus receiving some miscellaneous site, system, and TG.

I've yet to see anyone figure out what/who the miscellaneous TGs are. Eventually you'll hear a city/town name, dispatcher's voice, units numbers, locations, or something that you'll recognize. Even the TG number can be traced back to a site or frequency to see how and/or why your pager is receiving it.

 

[west-pac]

I appreciate the suggestion. I have two people who have G5's who monitor the same system as me and they don't have the bleed over, so I know it is a radio by radio basis.

Unfortunately, I have identified the TG, it's one of Raleigh PD's TG's. They are the second busiest agency in the County, if not the entire State. If it was random once a week, I would be okay with it, but you're talking 10 times a day easily. And when you have the pager set to receive only one TG and NOTHING else it programmed into that knob position, it defeats the purpose of a $707.00 pager.

Maybe its not a "pager" problem. Maybe it's a - location- issue. Have you tried swapping pagers with one of the other two guys for a day or two? It shouldn't take long to figure out if it's the pager, or location. Do all 3 pagers have the EXACT same programming? You could read all three then compare the profiles to see what's different, provided the other 2 don't receive the PD TG.

Is the site number part of the programming? Is the NAC programmed in your pager?...Is the PD and FD NAC the same?

 

[OnYourSix]

@west-pac I haven't swapped pagers with anyone. My thought process to my communication with Unication was that my pager was two weeks old, and that it was defective from the factory. I told them I took several steps to help them diagnose it, uploaded new FW, send them my files, so would they consider swapping my pager out. The technician agreed, so (for now) I don't have to troubleshoot any further on my end.

The other two pagers in the area that are not experience this are older units, so maybe they have better selectivity from interference? I will see what happens when I get the new pager and let everyone know. USPS states they received my old pager on 1/28.

Maybe its not a "pager" problem. Maybe it's a - location- issue. Have you tried swapping pagers with one of the other two guys for a day or two? It shouldn't take long to figure out if it's the pager, or location. Do all 3 pagers have the EXACT same programming? You could read all three then compare the profiles to see what's different, provided the other 2 don't receive the PD TG.

Is the site number part of the programming? Is the NAC programmed in your pager?...Is the PD and FD NAC the same?

 

[firebal]

@AdamHLG Is your issue with Baltimore County? I did not see this was a thread and started another one. G4 Bleeding Over

 

[OnYourSix]

No need for another thread, this is not specific to anywhere, it's all over the US

@AdamHLG Is your issue with Baltimore County? I did not see this was a thread and started another one. G4 Bleeding Over

 

[AdamHLG]

Yes. Baltimore County! It’s driving us crazy.

 

[ResQguy]

Yes. Baltimore County! It’s driving us crazy.

Please take a look at this in your pager profile:

PPS->Group ID Setting->Private Call ID->P25T SUID, and disable this function.

 

[AdamHLG]

Just disabled it! Will test. Fingers crossed !