I Understand there is a bug in the 996p2 firmware. The San Diego RCS recently changed their fire fleetmap and now I am getting p25 law on what's supposed to be a fire talkgroup, something about how the scanner handles patches?..can anyone confirm?
I have been a die hard Uniden customer..yes I have spent a lot of money over the years on Uniden scanners. Not happy with my 996P2 and Uniden customer support. RR is touted on their website as a place to have issues resolved well no luck here , and no response from UPman as to whether there is a fix for the 996p2 San Diego RCS bug or not. Being in the fire service this is a very serious issue for me as I use this scanner to monitor our neighboring county's fire agencies (San Diego RCS) All I want is a straight answer, Uniden, UPman, what do I do with my $500 paper weight?
There's probably going to be a fix shortly, about the same time as the Finalized DMR firmware is available for the BCDx36HP Series. Give it between 30 and 90 Days, all will be good again, until then: Flush-out each TGID's into individual Status bit channels:
Example: Fire Dispatch 4a has a TGID # 4096,break down channel for each status bit
4096 TGID 4a : 4096
4097 TGID 4a1: 4096+1=4097
4098 TGID 4a2: 4096+2=4098
....... and turn the System's 'Status Bit' 'On'.
Distinctly For the Fire Dispatch Channels /TGIDs you want to listen to. Then try LockingOut the accidental cross/patched PD/LEO channels out, as you hear them. This is a possible temporary fix, to the problem, and should work until fix is out.
Motorola Type II Smartnet - The RadioReference Wiki
I understand +3 (8051) did not decode the Digital Audio, leading to a motorboating sound during the entire transmission of a cross/patched channels even when Audio Type was set to Analog.
So did 3A Dispatch TGID 8048 +1(8049) and +7 (8055) with the Audio Type Set to Analog still receive digital-undecoded unsquelched transmissions?