I am still curious as to Uniden's progress on this point.
Paul, since we know the LCN's and how they are applied now (indeed for almost 3 months now), is there a reason we have not heard any buzz at all on this issue?
The programmers back in Japan appear to move at a snail's pace and even simple fixes seem to take forever.
A rebanding patch requires a
per-system change (another system type choice, or a new entry in the system options menu), which means changes to UASD and to the serial protocols used by the 246T, 396, 996, 330...
And then there are the owner's manuals that need updating...
To Uniden, this is a big deal and something they shy away from. How many (hidden!)
scanner-wide options have they added so far that should've been system specific? There are the analog/digital AGC settings and that new P25 Waiting Time; so now I can "improve" things on one problematic system by missing the start of comms on every other Moto 3600 bps system! Uniden just won't bite the bullet and do these things properly.
To this day, every time I use my 396 in the car with the audio routed through the stereo, I have to listen to the ticking sound it makes as it briefly enables, then disables the 396's audio amp as it switches from one trunking system to the next. We're supposed to handle the 200 talkgroup limit by splitting them across two systems (never mind how that causes its own problems), but how do we handle the never ending "tick tock" it creates?
Fixing that bug is dead simple - no new poweron sequence, no menu changes, no protocol change, no UASD or manual updates, nada. But they won't do it. If that fix can't happen, how long will a major change take?
Y'know, when fixes take this long, it's a pretty good indication that the code (scanner firmware and UASD) are poorly written, inflexible and prone to breaking when changes are attempted.