SDS100 Firmware Update Change Log

All firmware updates are applied using Sentinel. Select Update --> Update Firmware

Before applying updates, you should back up your programming. Always use the latest version of Sentinel to update.

1.27.00 Main (11/06/2026)

New Features and Improvements OTA Alias Reception Requirements
  1. Configure the display. The customizable display layout must include the "Unit ID Name" field. If the field is not present in the active layout, decoded alias text will not be visible.
  2. Account for saved aliases. Aliases are saved automatically. Stale aliases are not updated, and previously alpha-tagged Unit IDs are not overwritten.
  3. Confirm system-side broadcasting. The monitored trunked network must actively transmit alias data. Some public-safety agencies disable OTA Alias broadcasting or limit it to dispatching consoles. If the system does not transmit the data stream, the scanner has nothing to decode.
  4. Verify signal quality. OTA Alias data blocks require a clean, high-quality RF signal. Weak reception or a high bit-error rate (BER) can prevent successful decoding. Under these conditions, the SDS100 prioritizes voice packets and may drop the limited sub-audible data packets that carry the alias text.
Technical Note: P25 Phase 1 and Phase 2 OTA Initial Alias Behavior

1.26.01 Main (03/27/2026)

1.24.00 Main (12/20/2025)

1.23.20 Main (10/17/2025)

Requires SUB V1.03.15 or later.

1.03.15 Sub (10/17/2025)

Requires Main V1.23.20 or later.

1.23.15 Main (03/24/2025)

1.03.06 Sub (7/11/2024)

1.23.07 Main (03/22/2024)

1.23.05 Main (2/2/2024)

This firmware applies the following bug fix:

1.03.05 Sub (1/19/2024)

This firmware applies fixes for the following issues:

1.23.03 Main (12/28/2023)

This firmware applies the following enhancements and bug fixes:

1.03.02 Sub /1.23.01 Main (12/21/2023)

This firmware applies the following enhancements and bug fixes:

1.21.00 Main (6/29/2022)

This firmware applies the following enhancements and bug fixes:

1.10.00 Main (4/15/2019)

This firmware applies the following enhancements and bug fixes:

1.09.02 Main (04/05/2019)

This update includes the following enhancements and bug fixes:

1.02.01 Sub / 1.08.05 Main (3/7/2019)

Be sure to also update Sentinel when applying this update.

This firmware update applies the following new settings and bug fixes:

1.07.04 Main Release Notes (01/28/2019)

1.07.02 Main Release Notes (01/25/2019)

1.07.00 Main / 1.02.00 Sub Release Notes (01/24/2019)

MENU --> SETTINGS --> GLOBAL AUTO FILTER

Note: If Auto is selected, conventional scan and search speed will be greatly slowed, as every frequency on which a signal is not detected on first pass will be rescanned using the inverted HPF setting.

MENU --> MANAGE FAVORITES --> REVIEW/EDIT SYSTEM --> EDIT SITE --> SET FILTER (Setting menu for trunked systems)

MENU --> MANAGE FAVORITES --> REVIEW/EDIT SYSTEM --> EDIT DEPARTMENT --> SET FILTER (Setting menu for conventional systems)

MENU --> SRCH/CLOCALL OPT --> SET FILTER (Setting menu for Close Call and Search)

1.05.01 Main / 1.01.05 Sub Release Notes (08/12/2018)

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.

1.03.01 Release Notes (06/29/2018)

The new display option allows you to see Unit ID names that are larger than a single field. The ID is provided in 4 parts. Put these fields next to each other, in order, to see the entire Unit ID.

1.02.03 Release Notes (06/01/2018)

Topic attachments
Attachment Size Date Comment
SDS100_V1.26.01_Main.zip 2.2 Mb 06 Nov 2026  
SDS100_V1.24.00_Main.zip 2.2 Mb 27 Mar 2026  
SDS100_V1.23.20_Main.zip 2.2 Mb 17 Oct 2025  
SDS100_V1.23.15_Main_V1.03.06_Sub.zip 2.2 Mb 17 Oct 2025  
SDS100_V1.23.07_Main.zip 2.2 Mb 22 Mar 2024  
SDS100 V1.03.05 Sub.zip 60 Kb 11 July 2024  
SDS100_Protocol_Docs_V0_01.zip 477.7 Kb 03 Jul 2018  
SDS100 V1.23.02 Main V1.03.02 Sub.zip 2.2 Mb 03 Jan 2024  
SDS100 V1.21.00 Main V1.02.01 Sub.zip 2.2 Mb 03 Jan 2024  
SDS100_RemoteCommand_Specification_V1_02.pdf 992 Kb 07 Feb 2024