R14.00.03 Priority Monitor Scan In Trunking Broken?

[kf4lhp]

Wondering if anyone else is having an issue with priority monitor scan on a P25 system with firmware R14.00.03? I'm noticing that the radio isn't picking up anything active in its scan list when I turn the radio on, but cycling scan off and back on and it starts working.

Ah, to be an early adopter...

HOST R14.00.03
DSP R14.00.03
SECURE R01.07.25
Flashcode 941238-011492-5
CPS R14.00.00

 

[motorola_otaku]

Is IV&D active? We've had ongoing issues with context activation disrupting scan traffic (and taking longer than it should specifically on the 7500s) but never on the parked channel, which is also what we have selected as priority. If you're using mode-slaved or user-selectable priority and it's not the channel you're parked on I could see IV&D traffic disrupting it.

I haven't popped any 7500 mobiles yet, but I'll post back with results when I do.

 

[kf4lhp]

IV&D is active on this radio. Don't know on missing traffic on the parked channel but it's certainly missing traffic on the other scan list members (we too set the selected channel as priority). Will experiment with turning off IV&D, not like I use it anyway.

 

[kf4lhp]

Turning off IV&D seems to resolve this issue.

 

[motorola_otaku]

Missing scan traffic while the radio is IV&D registering is a known issue. This firmware release was supposed to resolve missed priority scan traffic whether the priority channel is selected or not, though I'm not sure how since the data channel would have to be carrying priority activity OSWs for the radio to know to switch.

I have also observed that IV&D registration (registering with the ARS and context activation) may not take place at all on a 7500 mobile when the RSSI is extremely high - like, when you're parked under a site. When this occurs scan activity is erratic or nonexistent. Simply lowering the RSSI doesn't resolve it - you have to move off the system and back on, or power-cycle the radio. For this reason we've opted to stick with R13.05.00 firmware, even though the portables seem to not be affected.