I have some firmware for testing against some of the reported issues. Specifically, the items below.
To apply this test firmware, download http://info.uniden.com/twiki/pub/PartnerWeb/SDS100-beta/SDS-100_V1_02_05a.bin
Copy this file to the FIRMWARE folder on your SDS100, then reboot the scanner.
To report in this thread, follow this format:
To make a log, first set up to scan only a single system that exhibits the problem you are logging. Best approach is to put directly from the main database to a favorites list, then scan only that favorites list.
Then, turn off the scanner and turn it on while holding AVOID.
MENU --> SETTINGS --> SET DEBUG MODE --> SD Card (File)
Capture a log long enough to catch the problem.
MENU --> SETTINGS --> SET DEBUG MODE --> Off
The file is put in the debug folder. If you make multiple logs against different problems, keep track of the order in which you tested so that you describe each log file correctly.
I will ask admins to delete any post that either does not follow the above format or is not in a direct response to a followup from me so that this thread only contains reports (or clarifications/follow ups).
- P25 systems holding on site with good signal, but RSSI indication blanks and many comms are missed.
- EDACS system missing many comms.
- Some Harris P25 systems missing many comms.
- Inconsistent backlight operation
To apply this test firmware, download http://info.uniden.com/twiki/pub/PartnerWeb/SDS100-beta/SDS-100_V1_02_05a.bin
Copy this file to the FIRMWARE folder on your SDS100, then reboot the scanner.
To report in this thread, follow this format:
Tested Against:
1. P25 systems holding on site with good signal, but RSSI indication blanks and many comms are missed.
2. EDACS system missing many comms.
3. Some Harris P25 systems missing many comms.
4. Inconsistent backlight operation
(keep only the lines above that apply to your test)
Results: Problem is fixed/not fixed (for each item you checked)
Link(s) to system(s) checked:
Discussion: (describe how you tested/what specific results were for each item you checked)
Log File(s):
<log file name> : Which system this log is from and which problem is still occurring.
To make a log, first set up to scan only a single system that exhibits the problem you are logging. Best approach is to put directly from the main database to a favorites list, then scan only that favorites list.
Then, turn off the scanner and turn it on while holding AVOID.
MENU --> SETTINGS --> SET DEBUG MODE --> SD Card (File)
Capture a log long enough to catch the problem.
MENU --> SETTINGS --> SET DEBUG MODE --> Off
The file is put in the debug folder. If you make multiple logs against different problems, keep track of the order in which you tested so that you describe each log file correctly.
I will ask admins to delete any post that either does not follow the above format or is not in a direct response to a followup from me so that this thread only contains reports (or clarifications/follow ups).