I have a riddle for you guys. I have a G5 programmed with the Baltimore County P25 Phase 1 system in Zone 1. In PPS, under D-5, Zone 1 Knob Position 1, the setting is for receiving mode = Trunking TG-Scan. Under the knob - talk group list, there is only one entry: TG 9450 (which is Baltimore County Fire - Main). This is the only TG I should receive in this knob position - and 95% of the time, this is how it works. However, on random occasions, I will start receiving TG 9606 in addition to the programmed TG which is 9450. TG 9606 is the Parkville PD precinct on Baltimore County's P25 system. What's weird is that this is random behavior and if I turn off my G5 and turn it back on, the problem goes away. Even more weird is that I never receive any other random talk group. When it happens, it is always TG 9606, but it only happens 5% of the time (about once a week) and power cycling the G5 fixes it.
Let's take it a step further in weirdness. I program 2 other G5s of members of my FD crew. It happens to them also. Now granted, they have the same code plug as me. But this proves it's not the radio itself. But my code plug appears to be programmed correctly - at least I think. On all of our radios, its always this random popup transmission on TG 9606. Power cycling the G5 makes it go away for about a week. It randomly returns.
Anyone else see anything like this type of behavior? They run FW 1.2 and I run a beta 5 of FW 1.3 but this behavior happens on all three of our radios.
It was happening this evening and I power cycled the G5 and now its fixed again. Figured I would post something about it.
Let's take it a step further in weirdness. I program 2 other G5s of members of my FD crew. It happens to them also. Now granted, they have the same code plug as me. But this proves it's not the radio itself. But my code plug appears to be programmed correctly - at least I think. On all of our radios, its always this random popup transmission on TG 9606. Power cycling the G5 makes it go away for about a week. It randomly returns.
Anyone else see anything like this type of behavior? They run FW 1.2 and I run a beta 5 of FW 1.3 but this behavior happens on all three of our radios.
It was happening this evening and I power cycled the G5 and now its fixed again. Figured I would post something about it.