996P2 bug on San Diego RCS??

[darunimal]

I didn't realize they set patches to the 3A Fire Dispatch channel (thus confusing the scanner), i understand the 4A TAC having patches (and confusing the scanner).

Once again the fix should be out shortly even the ones for the P2s, be patient, and it will be here before you know it. Now whether earlier Unidens will receive the update, has yet to be seen.

 

[W6KRU]

I didn't realize they set patches to the 3A Fire Dispatch channel (thus confusing the scanner), i understand the 4A TAC having patches (and confusing the scanner).

Once again the fix should be out shortly even the ones for the P2s, be patient, and it will be here before you know it. Now whether earlier Unidens will receive the update, has yet to be seen.

Currenttly Noncomm Dispatch 3A is patched to Noncomm TAC 4A. There are also SDSO patches and CHP patches and the scanners seem to lump them all together.

I'm OK now. The firmware for the 436 with the patch fix is working great but there are several people with Uniden scanners other than the 436 with the problem.

 

[djpaulino]

Yes Dan, that is the exact problem I' m having with the p2, very frustrating , all I want is a response from UPMan or any Uniden person that there is a fix, we are working on one..but no dice....

 

[darunimal]

Uniden does Not say future plans, until it's available and ready for consumer use, they never have and never will.

 

[Anderegg]

My great hope is that this bug fix will be made available in a final f/w revision for the affected discontinued models, like the T's and XT's. I would hope/think that just implementing the single bug fix code to the existing last f/w would be simple enough as to make it convenient for Uniden to do for us........crossing fingers.

And for those new to the issue, it has been around for years on the RCS, but you are only noticing it now because of all the fire patches from old talkgroups to their new versions. 10A used to always be patched with 5B, and when SO and Harbor PD patched in the middle of the night, I had to lock out 10A and 5B because they would patch through those talkgroups onto the FD ones........and that was years ago.

Paul

 

[Voyager]

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.

Read this thread. The question has been answered several times.

That sounds good but did not work on my 436. The scanner would just stop on the TGID +3 (patched) while receiving the error TG with the digital noise blaring due to the Analog setting for the desired TG.

Are you using the latest beta firmware?

As was stated, the fix is currently being tested in the x36 series. I'm sure once the fix is known to work it will be ported to other models.

 

[Anderegg]

Read this thread. The question has been answered several times.



Are you using the latest beta firmware?

As was stated, the fix is currently being tested in the x36 series. I'm sure once the fix is known to work it will be ported to other models.

Does dj not know that the "fix" was just found in a beta f/w for the 436 that was tested like a week ago? Maybe he will get a faster fix if he PM's UPman, and also he can PM him to ask for our Siren Android app by next week.

But seriously dj, I am waiting/hoping for a response as to if the fix will make it's way into any other platform than the HP.

Paul

 

[UPMan]

http://forums.radioreference.com/un...-firmware-motorola-patch-bug.html#post2605533

 

[W6KRU]

Are you using the latest beta firmware?

As was stated, the fix is currently being tested in the x36 series. I'm sure once the fix is known to work it will be ported to other models.

Reading is obviously not one of your strong points. :roll::roll::roll:

 

[IBScan]

I'm coming from a BCD996T that I programed manually and has been flawless.

I have to turn STATUS BIT off and have SITE HOLD set. If I have STATUS BIT on the radio doesn't receive anything.

EX: IMPERIAL BEACH and LEMON GROVE TG's are always patched. Say the console or whatever decides this is on IB TG, the radio picks it only up on IB and not LMG. But it's not uniform. It's what worked the best.

Now I'm working with a BCD436HP, it's like starting all over again on the learning curve.

Is there a better way to program the RCS? I mainly follow LE. Rarely I follow FD.

I've attached the 996 programing. Which I basically imported to the 436 and it works fine. Except for the issue it's spamming between the control channel and the voice channel right after someone finishes transmitting. As the RCS system seems like it's set to keep the VC for 5-10 seconds after the last transmission before it releases it back to the pool. On the 996 I can compensate for that via SITE HOLD which keeps the VC before it resumes scanning. On the 436 that option has been removed.

I have status bit and end code turned off and doesn't seem to make a difference.

I also have an ATT repeater less than 100 ft away which I've noticed issues since that went online...

Just curious if better way to program the RCS on 436.

 

[jonwienke]

Import the system from the Sentinel database and tweak that if necessary, rather than trying to convert programming designed for a completely different memory architecture. Unless it is a new system, and not fully documented, that is almost always the best approach.

 

[Anderegg]

I program my sites as independent systems with individual QK's....so I have like bank 3 for North RCS FD, and bank 2 for South RCS FD. If you put all the north and south talkgroups in each sites system, it work well.

I got so tired of the error prone Uniden patch bug, that I just leave status bit set to on for my FD banks, but off for my law banks. You don't really get the bleedover problem on the law stuff, it's just law bleeding onto FD!

Paul

 

[Anderegg]

Import the system from the Sentinel database and tweak that if necessary, rather than trying to convert programming designed for a completely different memory architecture. Unless it is a new system, and not fully documented, that is almost always the best approach.

Import, make a copy for each site, then delete all but the specific site for each new copy, maybe leave one with all the CC's as a sort of roaming mobile scanner bank