http://info.uniden.com/twiki/pub/PartnerWeb/SDS100-Beta/SDS-100_V1_03_05M_V1_01_05S.zip
To apply this public beta, unzip the above file and put the two files in the scanner's firmware directory then reboot the scanner. Note that the sub-processor version did not change for this beta...it is included here for those who may not have applied the previous beta.
Release Notes:
1. Improved reception on trunked systems.
2. Improved reception for short communications on P25 trunked systems.
3. Fixed the issue of Unit ID Alert
4. Fixed several minor bugs
5. Added the feature of Site NAC Operation
Regarding Site NAC Operation:
You can select (use or ignore) Site NAC of P25 Trunked Systems (including P25 OFT) in RRDB and Favorites Lists. When we added NAC support, we did not anticipate that the NAC would be incorrect in RRDB for many sites. This has caused many reports that the scanner stopped working with the new firmware (it was actually working correctly and rejecting the site traffic with the "incorrect" NAC). So, we've added an option to ignore the programmed NAC.
MENU-->Settings-->Site NAC Operation
When you set to ignore, the scanner will pass all traffic, even if the programmed NAC does not match the received NAC. If the NAC does not match, the CTCSS/DCS/NAC field in the display will show "NAC:xxxh xxxh" (Display two NACs simultaneously.)
The first xxxh is the incorrect (dB setting) NAC, and the 2nd xxxh flashes the received NAC.
We hope that this will help to facilitate getting corrected information into RRDB.
PLEASE DO NOT ASK QUESTIONS IN THIS THREAD.
If you have a question, use either an existing other topic or create a new one. Keep this thread reserved for actual performance reports and test results.
If you see an operational issue that you wish to report, use the following format:
1) Clearly describe the issue.
2) Link to the specific system exhibiting the issue.
3) Report the RSSI, NOISE, and D-Error values (if applicable).
4) Attach a log file taking while the issue occurs.
To make a log file:
a) Isolate your scan list to the bare minimum needed to demonstrate the issue.
b) Hold AVOID while powering on the scanner.
c) MENU --> SETTINGS --> SET Debug Log Mode --> SD Card (File)
d) Let the scanner scan long enough to catch the issue.
e) MENU --> SETTINGS --> SET Debug Log Mode --> Off
The resulting log is in the scanner's debug folder.
Note that it can also be helpful for you to post the HPE file of the Favorites List you used to create the log. Export the FL in Sentinel and add it to your report.
To apply this public beta, unzip the above file and put the two files in the scanner's firmware directory then reboot the scanner. Note that the sub-processor version did not change for this beta...it is included here for those who may not have applied the previous beta.
Release Notes:
1. Improved reception on trunked systems.
2. Improved reception for short communications on P25 trunked systems.
3. Fixed the issue of Unit ID Alert
4. Fixed several minor bugs
5. Added the feature of Site NAC Operation
Regarding Site NAC Operation:
You can select (use or ignore) Site NAC of P25 Trunked Systems (including P25 OFT) in RRDB and Favorites Lists. When we added NAC support, we did not anticipate that the NAC would be incorrect in RRDB for many sites. This has caused many reports that the scanner stopped working with the new firmware (it was actually working correctly and rejecting the site traffic with the "incorrect" NAC). So, we've added an option to ignore the programmed NAC.
MENU-->Settings-->Site NAC Operation
When you set to ignore, the scanner will pass all traffic, even if the programmed NAC does not match the received NAC. If the NAC does not match, the CTCSS/DCS/NAC field in the display will show "NAC:xxxh xxxh" (Display two NACs simultaneously.)
The first xxxh is the incorrect (dB setting) NAC, and the 2nd xxxh flashes the received NAC.
We hope that this will help to facilitate getting corrected information into RRDB.
PLEASE DO NOT ASK QUESTIONS IN THIS THREAD.
If you have a question, use either an existing other topic or create a new one. Keep this thread reserved for actual performance reports and test results.
If you see an operational issue that you wish to report, use the following format:
1) Clearly describe the issue.
2) Link to the specific system exhibiting the issue.
3) Report the RSSI, NOISE, and D-Error values (if applicable).
4) Attach a log file taking while the issue occurs.
To make a log file:
a) Isolate your scan list to the bare minimum needed to demonstrate the issue.
b) Hold AVOID while powering on the scanner.
c) MENU --> SETTINGS --> SET Debug Log Mode --> SD Card (File)
d) Let the scanner scan long enough to catch the issue.
e) MENU --> SETTINGS --> SET Debug Log Mode --> Off
The resulting log is in the scanner's debug folder.
Note that it can also be helpful for you to post the HPE file of the Favorites List you used to create the log. Export the FL in Sentinel and add it to your report.
Last edited:
Happy Friday!
