- Status
I updated two 536s and two 436s this morning to 1.15.00 before left for day. Just returned home after long day to play with new versions. Immediately noticed squelch issue on LA Cities group of stations that has quite a few stations with CSQ/search (no CTCSS or DCS). Then read through all the posts. Oh well, I will revert to 1.14.00 (AKA 1.15.01) on one each 536 and 436 and hope update for real 1.15.00 is available soon.
Either way, thank you Paul (Uniden) for continuing to try and improve our scanner experience.
Either way, thank you Paul (Uniden) for continuing to try and improve our scanner experience.
I agree! I would like the option of having the scanner stop on an encrypted channel or talkgroup and (if I'm not able to give my full attention to the scanner) an audible indication that encryption is in use so it can be noted in my records and/or the Radio Reference database. Then, when I get tired of the scanner hanging on that encrypted channel or talkgroup, I'd like the ability to have the scanner ignore it.
richee2000
Communications. Breaking News. Photography
UPMAN: with the new firmware update, both my 436 and 536 are now getting "open squelch" noise while scanning on some channels. squelch at 2. never a problem before. tried increasing squelch up to 4 , up to 10.... still no good. UPMAN. please advise.....
Revert back to 1.14 . Sentenial is updated too make the change to go back.
richee2000
Communications. Breaking News. Photography
thanks... will do
Ubbe
Member
There's a huge improvement in audio quality with DMR channels!
It used to be overloaded a lot somewhere before the volume control so there where no way to avoid it. The overall volume might have decreased but the audio now is much improved while listening to DMR.
The false decode also seems to be more or less gone and can only be forced if I set the threshold to 5 to get more than 25 in biterror. But that high error rate also triggers scan to get a better site in the system, so that new function is excellent.
That analog squelch anomaly is strange. It clears itself up after different time periods, can be 30sec to 3 minutes.
This is supposed to be a DMA scanner with Dynamic Memory Allocation but the avoided frequencies in search are fixed to a limit of 252 avoids. It's a big restriction as I avoid all known frequencies and only want to search for new and unknown frequencies. If there was a way to copy and paste the avoided frequencies I could reduce my search ranges and copy the relevant frequencies into the avoid window, but as Sentinel works now there is no way to copy and paste in that window. I guess a $50 ProScan license is needed.
/Ubbe
It used to be overloaded a lot somewhere before the volume control so there where no way to avoid it. The overall volume might have decreased but the audio now is much improved while listening to DMR.
The false decode also seems to be more or less gone and can only be forced if I set the threshold to 5 to get more than 25 in biterror. But that high error rate also triggers scan to get a better site in the system, so that new function is excellent.
That analog squelch anomaly is strange. It clears itself up after different time periods, can be 30sec to 3 minutes.
This is supposed to be a DMA scanner with Dynamic Memory Allocation but the avoided frequencies in search are fixed to a limit of 252 avoids. It's a big restriction as I avoid all known frequencies and only want to search for new and unknown frequencies. If there was a way to copy and paste the avoided frequencies I could reduce my search ranges and copy the relevant frequencies into the avoid window, but as Sentinel works now there is no way to copy and paste in that window. I guess a $50 ProScan license is needed.
/Ubbe
I have been running my radios with the 1.15 firmware and I noticed when you get the open squelch, if you go into menu and come back out of it, you can resume normally again until the next time it does it.
I saw the radio ID aliases in the 1 NXDN system I have near me, but the results were inconsistent. Sometimes I got the alias, other times I got the uid instead.
I saw the radio ID aliases in the 1 NXDN system I have near me, but the results were inconsistent. Sometimes I got the alias, other times I got the uid instead.
troymail
Silent Key
Probably some type of buffer overflow or something. Over time, I'm seeing lots of 'creative' use of the recording header data fields for things that probably weren't considered 'way back when'. That and fields that aren't always cleared when they should be... (yes, some fields get a null inserted in position 1 of a given field to invalidate it - other fields are at times left uncleared - most likely for performance).
I suspect at some point, the radio receives something and either reads or writes a field that wasn't set, cleared, or bounds checked properly.... these types of things are hard to test for and can also be hard to find to fix them too (but it feels so good when you do find and fix it!).
This probably means that something is being properly 'prepped' when you exit and restart... until the field gets corrupted again....
Schumi1978
Member
I encountered the same issue as described in post 195.
Sent from my SM-G920W8 using Tapatalk
I'm getting the analog conventional squelch as well on my 536, no matter what I set the squelch too, it hangs on them for a while...
Sent from my iPod touch using Tapatalk
Sent from my iPod touch using Tapatalk
My NX5800 will sometimes show the UID instead of the alias for a couple of seconds during transmissions as well. I don't think the alias is transmitted near as often as the UID.
I also believe that DSD stores the alias, so when it sees the UID again, it can display the alias nearly instantaneously.
I also believe that DSD stores the alias, so when it sees the UID again, it can display the alias nearly instantaneously.
- Joined
- Jun 27, 2002
- Messages
- 1,968
This is a big issue at my location where some users eat the microphone and are unintelligible on the BCD536. The users on the system seem to have no problem communicating and these overloaded transmissions do not cause them to ask for a repeat of the transmission. If firmware 1.15 improves the dynamic range of the scanner's audio chain, that's an important feature to retain in whatever replaces 1.15.
For this function, set up a FL with all the known frequencies and ensure that it is being scanned. Then, set up a Conventional Discovery session. For "Set Compare to Database" select On. In this mode, the scanner will ignore all hits that occur that are already in the current scan selection, so that it will only discover new (not in the currently scanned database) frequencies.
I believe the alias is transmitted in the very beginning of a keyup. So if you miss the very beginning of the transmission then the scanner will miss it. I believe I read that here somewhere.
Sent from my iPhone using Tapatalk
I am too, Upman retracted the 1.15.00 version to fix some of the problems including that one, he is aware of it. And will fix it soon
Sent from my iPod touch using Tapatalk
Same issue here. It's a fun little feature to have. I'm not sure if this is system-related or firmware-related. But some of the aliases chosen are kind of funny with these businesses.
- Status
