Uniden SDS100

Contents

Section	Topic
1	About this volume
2	Hardware tour
3	Operating modes
4	Programming workflow
5	Codeplug backups
6	Field use
7	Tips and tricks
8	Resources

---

1. About this volume

The Uniden SDS100 (released 2018, still the current flagship handheld in 2026) is the top-end digital scanner in the lineup and the daily-driver portable on Jeff’s belt. It earns the bench slot for two distinct reasons: it is the only handheld in the lineup with a software-defined-radio “TrueIQ” baseband decoder rather than the discrete heterodyne-and-narrowband-FM architecture used in every prior Uniden handheld, and it is the only handheld that has kept up with the slow drift of US public-safety systems through P25 Phase I → P25 Phase II → simulcast P25 Phase II → DMR Tier II → NXDN 4800/9600 → MotoTRBO Connect Plus encoded over the same infrastructure. The previous-generation BCD396XT (covered in Vol 13) can decode P25 Phase I and analog conventional/trunked just fine; the SDS100 is what you need for everything that came after 2014.

The “TrueIQ” architecture matters because the alternative — discrete narrowband-FM with software demodulation — falls down hard on Linear Simulcast Modulation (LSM), the modulation scheme used by most modern P25 simulcast systems. LSM is a continuous-phase 4-level FSK variant that constructively combines the partially-overlapping signals from multiple co-channel transmitter sites. A scanner that just demodulates one signal hears all the others as noise; a scanner that captures full-bandwidth IQ and runs the LSM-correlator in software recovers clean audio from the same RF that sounds like garbage on the older scanners. Uniden’s implementation is good enough that the SDS100 is the de-facto recommendation in the RadioReference and ScannerMaster forums for any operator within range of an LSM simulcast system — and for newer systems being built today, LSM is the default.

Why the SDS100 over the SDS200 (Vol 11). Same TrueIQ architecture in a base/mobile form factor — AC and 12V powered, larger transflective LCD, no battery, no GPS, slightly better front-end (SDS200 has a tunable preselector). The SDS200 wins for the home base behind an outdoor discone; the SDS100 wins for incident scanning, the go-bag, and travel. Jeff runs both — SDS200 at home, SDS100 portable.

Why the SDS100 over the BCD536HP (Vol 12) or BCD396XT (Vol 13). Both are pre-TrueIQ architecture — no LSM, no DMR Tier II, no NXDN; the BCD396XT also lacks P25 Phase II without paid firmware. Either is the right scanner for a 2014-vintage system; the SDS100 is the right scanner for a 2026-vintage system. Both stay on the bench as backups and as scanner history.

This is a receive-only scanner — no transmit hardware. The legal envelope is “what is legal to monitor” rather than “what is legal to transmit”; see Vol 22 (Frequency Planning & License Envelope) for the deep treatment, and the brief framing in §3.5 below.

---

2. Hardware tour

The SDS100 is a ~5.5” × 2.7” × 1.7” (140 × 69 × 43 mm) handheld weighing approximately 369 g (13 oz) with the standard BP100 lithium-ion battery installed. Build quality is plastic-shell over a die-cast internal chassis; the splash rating is IPX5 (water-jet from any direction, ~12.5 L/min for 3 min) — survives rain, survives being set down in a puddle, does not survive submersion. The front face is dominated by a 320 × 240 color transflective TFT that remains readable in direct sunlight (transflective means the LCD reflects ambient light back through the pixel layer when the backlight is too dim to overcome sunlight — a property the SDS100 shares with high-end GPS units and very few other scanners). The screen is not touch-sensitive; all input is via the keypad below it.

2.1 Front-panel controls

The keypad is laid out as a four-row matrix below the display, with a knob cluster above:

• Volume knob (left, dual-concentric with a push-to-mute function) — outer rotation is volume, push toggles between speaker and the headphone jack output level
• Squelch / function knob (right, dual-concentric) — outer rotation is squelch, inner ring (when pulled out or in function mode) is the channel/menu selector
• Side PTT slot — physically present (the chassis is shared with some Uniden GMRS transceiver bodies) but electrically not connected in the scanner build; do not press it expecting any action
• Number pad 0-9 — direct frequency entry in any tune-able mode; the 0 key is also “favorites lists on/off” in scan mode, and 1-9 select quick-key groups
• Side function key — toggles between primary and secondary keypad functions (printed on the keypad face in two colors; the function-shifted label is the secondary action)
• Hold / scan toggle — locks the scanner to the current channel for sustained monitoring, or releases back to scan
• E / Yes and . / No keys — menu navigation confirm/cancel; “E” is also “enter” for numeric entry
• Menu / function key (the gear icon) — opens the main configuration menu tree
• Backlight key — manually toggles the backlight; the radio also has an ambient-light sensor that can auto-control it (configurable in menu)

The knob-cluster ergonomics are good but require muscle-memory to be fast. The dual-concentric design (outer ring + inner ring + push) gives the volume and squelch knobs each three functions; learning which combination of pull, push, and turn does what is part of mastering the radio. Operators coming from older Uniden scanners (BCD396XT, BC246T) will find the basic operation familiar but the favorites-list architecture different (see §3.2 below).

2.2 Connectors

The top of the radio has a female SMA antenna jack. This is the standard scanner connector — not the more rugged BNC or N that some operators prefer on the older Uniden models — and it imposes the standard SMA frequency ceiling of ~6 GHz (well above anything the SDS100 actually tunes). Any 50-Ω SMA-male antenna mounts directly; for a BNC antenna there is an SMA-to-BNC adapter in the cable kit; for an N antenna (e.g., a base-station discone via a coax run) terminate the coax in SMA-male or use a short SMA-male-to-N-female adapter pigtail.

The bottom of the radio has:

• USB-C jack — combined data, charging, and USB-audio output. The USB-C connection enumerates on a PC as both a USB Mass Storage Device (the SD card) and a USB Audio Device (the scanner’s speaker audio as a sound source) — meaning you can record scanner audio to PC by selecting the SDS100 as the audio input device in any recording application, with no separate cable
• 2.5 mm 3-pole jack — speaker-microphone connector (Uniden BC-style pinout); accepts the optional BP-Speaker-Mic accessory for use on the belt with the radio in a hip pouch. The headphone audio uses the same jack with the BP-Headset adapter
• 3.5 mm headphone jack — stereo TRS, but the scanner output is mono (both channels driven the same); any consumer headphones plug directly

The right side has the microSD card slot behind a rubber cover — accepts microSDHC up to 32 GB officially; community reports of microSDXC 64 GB cards working if formatted to FAT32 (the SDS100 firmware does not handle exFAT, so a stock-formatted 64 GB card needs to be reformatted before use). The SD card carries the entire scanner configuration in /SDS100/ directories — favorites lists, system definitions, recordings, GPS logs, and the master Sentinel.dat database — which is what makes SD-card backups so important (see §5).

The back of the radio has the battery compartment, secured by a single Phillips screw and a sliding latch. The standard battery is the Uniden BP100 lithium-ion pack — confirmed nominal 3.7 V, ~3000 mAh on this generation per the user manual; runtime in active scanning with the backlight on auto is typically 8-10 hours, dropping to ~6 hours with the backlight forced on and the volume up, climbing to ~14-16 hours in scan-and-sleep mode where the radio only wakes for active transmissions. (TBD — verify with Jeff: the exact mAh rating may have changed across battery revisions; the original BP100 was 3000 mAh, later revisions reportedly went to 3200 mAh. Jeff has a spare; check the label on the spare for the actual rating.) The battery compartment also accommodates a Uniden BCD-Alkaline tray for 4× AA alkaline cells — emergency runtime is ~4-6 hours but the AA tray is rarely used in practice.

2.3 GPS receiver

The SDS100 has an integrated GPS receiver (the antenna is internal; no external GPS antenna jack). Cold-start lock time is typically 1-3 minutes outdoors with clear sky view; warm-start (resuming from a recent fix) is 15-30 seconds. The GPS feeds two functions: location-based scanning (auto-enabling sites and systems based on physical location — see §3.7 below) and GPS logging to the SD card for later review of where the radio was when specific transmissions were captured. The GPS does not lock indoors reliably and does not lock at all in steel-frame buildings; for indoor-only use it can be disabled to save battery.

2.4 Display modes and brightness

The transflective TFT runs in three modes selectable in the menu: Day (backlight off, transflective mode only — uses ambient light, very battery-friendly, readable in sunlight), Night (dim red backlight to preserve night vision), and Auto (ambient-light sensor controls backlight intensity). The Auto mode is the daily-driver default and tracks well in most lighting; the only place it gets confused is bright artificial light mixed with shadow (the sensor sees the bright source and dims the backlight while the LCD is in the shadow zone).

The font is configurable for size (Small / Medium / Large) — Large is the only one Jeff finds readable without glasses for the trunked-system status display, and the trade-off is fewer lines of information visible at once. Most operators end up at Medium.

2.5 Accessories worth knowing about

• BP100 spare battery — at least one spare for full-day events; swap-in takes 30 seconds with the battery-compartment screw
• External speaker-microphone (Uniden SMK40 or similar) — for belt-pouch carry
• Wall charger — any USB-C PD-capable phone charger works; the radio negotiates 5V/2A and ignores higher voltages
• Battery-only desktop charger (Uniden BCT-100 or similar) — for charging spares while the radio runs on a different battery
• External GPS antenna — does not exist for the SDS100; the GPS antenna is internal with no external port. If GPS lock is poor at a fixed location, set a manual GPS location in the menu

---

3. Operating modes

The SDS100’s RF coverage, modulation support, and trunked-system handling are the depth of the radio. The signal-processing chain is the same end-to-end for every mode — RF-front-end → mixer to baseband → IQ digitization → DSP demodulation in firmware — but the demodulator selected for any given channel depends on the channel’s Modulation parameter or the trunked-system definition.

3.1 RF coverage

The full tuning range, with the US-market mandatory cellular gaps in place per 47 CFR §15.121 (consumer scanner gear must not tune cellular bands):

Range	Coverage	Notes
25 - 512 MHz	Continuous	HF tail / 6m amateur, marine VHF, public-safety VHF, federal VHF, MURS, amateur 2m, FRS/GMRS, public-safety UHF, federal UHF, amateur 70cm
758 - 824 MHz	Continuous	700 MHz public-safety band
849 - 869 MHz	Continuous	(gap 824-849 = uplink cellular A/B, 869-894 = downlink cellular A/B — both blocked by §15.121)
894 - 960 MHz	Continuous	900 MHz public-safety, 900 MHz business LMR, amateur 33cm
1240 - 1300 MHz	Continuous	Amateur 23cm

The HF tail (25-30 MHz) is for legacy 10m / business HF / CB-adjacent monitoring — not the prime use case. The 700/800/900 MHz public-safety bands are the prime use case for any modern scanner; the SDS100’s tuning range covers all current US public-safety allocations. The 1240-1300 MHz band is included because of the amateur 23cm allocation; the band is sparsely used (microwave amateur work and a small number of repeaters) but the coverage is appreciated when it is needed.

The SDS100 does not tune below 25 MHz; for HF/SWL monitoring the Tecsun PL-880 (Vol 8) is the right radio. The SDS100 does not tune above 1300 MHz; for L-band (1.5 GHz aero datalinks, ADS-B at 1090 MHz) the radio covers it; for S-band (2.4 GHz Wi-Fi, ISM) it does not.

3.2 Favorites lists — the new scan-list architecture

The single biggest operational difference between the SDS100 and previous Uniden scanners (BCD396XT and prior) is the favorites list architecture. Older scanners used “scan lists” — a flat list of memory channels, with bank-grouping to organize them. The SDS100 uses a hierarchical model:

Favorites list (256 max, each named)
  └─ System (within a favorites list, multiple systems per list)
      └─ Site (for trunked systems, multiple sites per system)
          └─ Channel/Talkgroup (within a site, the actual frequencies/TGIDs)

A favorites list is a named collection of systems — e.g., “Home county”, “Travel - NYC”, “Weather”, “Aviation 118-137”. You can enable or disable an entire favorites list with a single keypress (the quick keys 0-9 map to favorites lists 1-10, and shift+0-9 maps to favorites lists 11-20; the full 256 favorites lists are accessed via menu). This is the killer ergonomic feature — if you have a “Weather” list always loaded but only want to hear it when there is a watch in effect, you toggle quick-key-9 to bring it in or take it out without editing any underlying configuration.

A system within a favorites list is one of: a trunked-radio system (P25 Phase I, P25 Phase II, DMR Tier II, NXDN 4800/9600, MotoTRBO Connect Plus, EDACS narrowband, EDACS wideband, LTR Standard, LTR Multi-Net), or a conventional analog/digital channel group. Trunked systems carry per-talkgroup configuration (Alpha tag, priority, alert tone, alert color); conventional systems carry per-frequency configuration (Alpha tag, modulation, CTCSS/DCS/NAC, priority).

A site within a trunked system is one of the physical transmitter sites that participates in the system — for a multi-site simulcast system, each transmitter site has its own control channel frequency, and the scanner needs to know about each one to follow the system as the user (or the talkgroup chatter) moves between sites. Sites can be enabled/disabled individually (useful for ignoring distant simulcast sites that create interference at your location) and can be tied to GPS coordinates so the scanner auto-enables them when you are within range and disables them when you leave.

A channel (within a conventional system) or talkgroup (within a trunked system) is the actual unit of monitoring — a frequency + modulation for conventional, or a TGID (talkgroup ID, a 16-bit integer) + system context for trunked. Each channel/talkgroup has its own Alpha tag (display name), priority flag, alert tone, alert color, attenuator setting, and record-on-hit flag.

The hierarchy is deeper than older scanners but more powerful — you can hold an entire metropolitan area’s public-safety, business, amateur, and aviation systems in a single favorites list, and toggle the whole thing in or out with one keypress. The trade-off is configuration complexity: you do not program the SDS100 by hand-entering frequencies the way you did a BCD396XT; you use ProScan or Sentinel and pull pre-built system definitions from RadioReference.

3.3 Modulation support

The SDS100 demodulates:

• Analog FM — wideband (~25 kHz) and narrowband (~12.5 kHz) — the workhorse for legacy public-safety, business LMR, and amateur 2m/70cm
• Analog AM — for the 118-137 MHz aero band and the 225-400 MHz mil-air band
• P25 Phase I (C4FM) — 12.5 kHz channels, single-slot, the original APCO-25 standard
• P25 Phase II (H-CPM TDMA) — 12.5 kHz channels carrying two simultaneous voice slots via TDMA, the current standard for new US public-safety systems
• DMR Tier II — 12.5 kHz channels, 2-slot TDMA, the dominant standard for business LMR worldwide
• NXDN 4800 — 6.25 kHz channels, single-slot, used by some utilities and railroads
• NXDN 9600 — 12.5 kHz channels, single-slot, mostly business
• MotoTRBO Connect Plus — Motorola’s proprietary trunking control overlay on DMR Tier II, common for large commercial fleets
• EDACS narrowband and wideband — legacy 800 MHz public-safety trunking (analog by default; ProVoice digital with paid upgrade)
• ProVoice / EDACS ProVoice — paid firmware unlock (Uniden charges approximately $60-70 mid-2026; TBD — verify with Jeff if he has bought it. The unlock is per-radio-serial-number, tied to a hardware ID; purchase is via Uniden’s online portal); decodes the digital voice variant used on some legacy EDACS systems, mostly in the southeastern US
• DMR with encryption keys loaded — the SDS100 itself does not decrypt encrypted DMR; encrypted talkgroups show as encrypted in the display and play no audio. (Decrypting encrypted public-safety traffic is illegal in the US even passively per 18 USC §2511 — the radio does the right thing by not implementing it)

The radio does not demodulate: P25 Phase II encryption (same legal reason), TETRA (European public-safety standard, not used in US), DMR Tier III (lightly-deployed Motorola variant), iDEN (extinct Nextel system), Tetrapol (French/EU), or any modern cellular protocol (GSM/UMTS/LTE/NR — irrelevant to a scanner).

3.4 LSM and the simulcast story

Linear Simulcast Modulation (LSM) is the single feature that most differentiates the SDS100 from prior-generation scanners. Legacy P25 Phase I and II uses C4FM (four-level continuous-phase FSK) — works fine on a single-site system, but on a simulcast system where multiple transmitter sites emit on the same frequency with slight time offsets, the partial-overlap RF creates phase chaos that the C4FM demodulator hears as garbled audio. LSM pre-distorts the waveform at each transmitter site to compensate for multi-site combining; the scanner applies an inverse-LSM correlator before the C4FM demodulator. The SDS100 does this automatically (Auto Modulation setting on a P25 system enables LSM-detect-and-handle).

The result: on a simulcast P25 system within range of two or more co-channel transmitter sites, the SDS100 hears clean audio where the BCD396XT, BCD536HP, or any non-TrueIQ scanner hears garbled mess. Most major US metropolitan areas now run LSM simulcast P25 for primary public-safety; if you are within ~50 miles of a major metro, you probably need an LSM-capable scanner. The corner case: on a few unusual systems the auto-detect picks wrong; manually set LSM to On or Off rather than Auto. The RadioReference wiki for any specific system flags this when it applies.

3.5 The legal envelope (scanner edition)

The SDS100 is receive-only — no transmit hardware, no FCC type-acceptance issue around emission. The legal question is what you may legally monitor:

• Public-safety bands (police, fire, EMS, federal) — legal to monitor in most US jurisdictions; a few states (CA Vehicle Code §11220, NY Penal Law §397) restrict carrying a scanner in a vehicle even though monitoring itself is legal — Michigan is permissive
• Aviation, marine, business LMR, amateur, weather, GMRS, FRS — legal to monitor everywhere in the US
• Cellular bands — the §15.121 hardware gap enforces 18 USC §2511 (ECPA) on the scanner-hardware side; cannot intentionally intercept cellular content
• Encrypted public-safety traffic — legal to receive the encrypted signal; illegal to decrypt it (18 USC §2511); the SDS100 does the right thing by not implementing decryption

Cross-reference Vol 22 §3 (Receive-only legal envelope) and Vol 1 §4 (License envelope).

3.6 Squelch, attenuator, and tone-controlled access

The SDS100 supports the full standard set of squelch and access tone systems:

• Standard FM squelch — RSSI-based, threshold set by the squelch knob
• CTCSS (Continuous Tone-Coded Squelch System) — 50 standard sub-audible tones (67.0 - 254.1 Hz); the scanner only un-squelches when the configured CTCSS tone is detected on a received signal
• DCS (Digital-Coded Squelch) — 104 standard codes; same idea, digital sub-audible code instead of analog tone
• NAC (Network Access Code) — P25-specific, 12-bit code carried in the P25 framing; used to differentiate P25 systems on shared frequencies
• Search NAC — the scanner can be set to learn the NAC of any P25 transmission heard, useful for discovery

Each channel can be configured for a specific access code (filter mode) or for “Search” (display the access code of any received signal and pass audio for all). In Search mode, the radio is essentially documenting what is on a frequency rather than filtering for a known user.

The attenuator is per-channel, 20 dB nominal, useful in three situations: strong-signal overload (a nearby paging transmitter dragging the front end into compression and creating intermod), multi-site simulcast where a too-strong nearby site is interfering with the LSM decode of a more-distant target site, and antenna-substitution testing (where you have switched to a larger antenna and want to roll back the gain to match the smaller-antenna behavior).

3.7 GPS-based site enable/disable

For trunked systems with multiple physical sites, each site can be tagged with a GPS coordinate (lat/lon) and radius. The scanner enables the site when its GPS fix shows you within the radius, and disables it otherwise. This is the killer feature for road-trip scanning: pre-load a multi-state set of public-safety systems (one favorites list per state), tag every site with its GPS bounds, and the radio auto-selects which systems and sites are active as you drive across state lines. The RadioReference database carries GPS coordinates for every documented site; ProScan and Sentinel both import them automatically when you pull a system definition.

For static (home or office) operation, set a manual GPS location in the menu (latitude/longitude or grid square) and the radio behaves as if it has a GPS fix at that location; this works around the indoor-GPS-lock problem.

3.8 Discovery and Close Call modes

Two non-trunked scan modes deserve mention:

Discovery mode sweeps a frequency range, logs every hit (with frequency, signal strength, modulation, and timestamp) to the SD card, and continues sweeping. Useful for finding what is active in a new area — set Discovery to 450-470 MHz business UHF in an unfamiliar city, leave the radio running for a few hours, then review the log to see what business systems are transmitting nearby.

Close Call is Uniden’s near-field detector — the radio listens for any nearby transmitter within ~50-200 feet (depending on the transmitter’s power and the SDS100’s antenna), regardless of what frequency it is operating on, and auto-tunes to it. Useful for finding the security guard’s radio frequency at an event, or for identifying what frequency a nearby paging transmitter is on. Close Call’s range is far enough that it can be a nuisance in dense RF environments (every nearby cell phone hand-shake will trigger it); it works best in low-RF environments where the targets are within direct sight.

---

4. Programming workflow

The SDS100 is not programmed by hand. The codeplug is too complex (hundreds of talkgroups, dozens of sites, multiple system types per favorites list, per-talkgroup metadata) for manual entry to be practical. The standard workflow uses ProScan (third-party CPS, paid) or Sentinel (Uniden CPS, free) on Windows, pulling system definitions from RadioReference.com (paid database subscription).

4.1 ProScan vs Sentinel — choosing the CPS

Both program the SDS100 (and SDS200, BCD536HP, BCD436HP, Homepatrol). Same job at the machine level — read the codeplug, edit on PC, write it back — different user experience.

Sentinel is Uniden’s free first-party CPS. Simple interface mirroring the radio’s menu structure. Pulls system definitions from RadioReference (paid RR subscription required); manages firmware updates; manages favorites-list selection and quick-key mapping. Adequate for most users; what Uniden recommends to a new owner.

ProScan is a third-party paid CPS (one-time license, mid-2026 pricing roughly $40-60 — TBD — verify with Jeff). Originally written for the older Uniden scanners (BCD396XT, BC246T) when first-party software was weaker; carried into the SDS-series with a richer feature set: bulk-edit on talkgroups (rename/retag/retone by pattern), virtual-radio simulation, advanced quick-key planning, CSV / RR-XML import-export, richer playback UI. Worth the license for an operator who programs often (Jeff reprograms when traveling).

Jeff runs ProScan 24.4 as the daily-driver, with 24.0 archived in programs/proscan/v24.0/ as a known-good fallback. License file at programs/proscan/license-key.txt. Both versions co-exist in the ProScan Wine prefix on Parrot at ~/.wine-proscan/; see Vol 21 §4 (ProScan on Linux via Wine). Sentinel is also installed on the Windows partition for fallback firmware updates (Sentinel’s update path is more reliable). Full CPS comparison in Vol 21.

4.2 RadioReference — the database

System definitions are not entered by hand. They come from RadioReference.com, the canonical community-maintained database — per-system control channels, per-site GPS coordinates, per-talkgroup names, modulation parameters. A paid RadioReference subscription (mid-2026 approximately $30/year — TBD — verify with Jeff’s most-recent renewal) unlocks the database-API access that ProScan and Sentinel use for direct system imports. Without a subscription you can still browse the web UI and manually enter frequencies, but that defeats most of the SDS100’s productivity. Pays for itself the first time you import a 200-talkgroup metro public-safety system in one click.

RadioReference workflow with ProScan: connect SDS100 via USB-C → ProScan reads current codeplug → open RR Browser within ProScan → navigate to system (e.g., MPSCS) → “Import to ProScan”, choose target favorites list + quick-key → review imported alpha tags / talkgroup priorities / attenuator settings → write codeplug back to radio. Total ~5 minutes per new system, most of it reviewing the import.

4.3 Codeplug structure on the SD card

The SDS100’s “codeplug” is not a single file — it is the entire /SDS100/ directory tree on the SD card. Key files:

• /SDS100/Sentinel.dat — the master database; Sentinel’s native format; contains favorites lists, systems, sites, channels, talkgroups, GPS coordinates, all configuration
• /SDS100/Favorites/*.hpf — individual favorites list files (HomePatrol-Favorites format), one per favorites list
• /SDS100/Recordings/*.wav — recorded audio captures (per per-channel record-on-hit setting); WAV format, mono, ~16 kHz sample rate
• /SDS100/Logs/*.log — GPS logs and Discovery-mode logs
• /SDS100/Firmware/*.bin — firmware images (uploaded by Sentinel or ProScan during update)
• /SDS100/Profiles/*.hpd — user profile configurations (favorites-list-selection snapshots; see §7 for the profile-switching trick)

Both ProScan and Sentinel read and write this directory tree directly when the radio is connected via USB-C (the radio presents the SD card as a USB Mass Storage Device when first plugged in; the CPS then operates on the mounted filesystem). The radio can also be programmed with the SD card removed and read in a card reader — useful for backup and for bulk-editing offline.

4.4 Firmware updates

Pushed via Sentinel (more reliable) or ProScan (also works but Jeff has had occasional hiccups). The current firmware on Jeff’s SDS100 is TBD — verify with Jeff; Uniden publishes updates 2-3× per year addressing decode quality, new modulation variants, and bug fixes. Check Uniden’s support page (linked in §8) periodically.

Process: connect via USB-C → launch Sentinel → “Firmware Update” → radio reboots into bootloader → Sentinel writes firmware → radio reboots into operating mode. ~5 minutes total; do not unplug or power-cycle mid-update (bricks the radio, requires a Uniden service ticket). Always back up the codeplug immediately before a firmware update — normal updates preserve SD card contents, but a failed update can corrupt the SD filesystem.

---

5. Codeplug backups

Backup discipline is non-negotiable on the SDS100 because the codeplug is large, deeply customized, and time-expensive to recreate. The radio’s /SDS100/ directory on the SD card runs ~50-200 MB depending on how many recordings are stored; a full backup is just an SD-card image copied to programs/uniden-sds100/codeplug-backups/.

5.1 Backup cadence

Backup the SD card:

• After every meaningful favorites-list edit — adding a new system, reorganizing favorites lists, changing quick-key assignments, adjusting site GPS coordinates
• Before every firmware update — without exception
• Before any “experimental” change — testing a new attenuator setting across many channels, importing a large new system, manual-editing Sentinel.dat
• On a calendar schedule — at minimum monthly, even with no changes, just to capture any cumulative state drift (recording logs, GPS logs, quick-key state)

5.2 Backup location and naming convention

Backup files live in ../../programs/uniden-sds100/codeplug-backups/ (relative to this volume source — absolute path is Scanners_and_Radios/programs/uniden-sds100/codeplug-backups/). The naming convention is sds100-{nickname}-YYYY-MM-DD.tar.gz where {nickname} is the SDS100 unit nickname from MY_GEAR (TBD — verify with Jeff which unit nickname is current; the SDS100 should have a registered nickname like sds100-belt or similar). For Jeff’s primary SDS100, recent backups should look like:

programs/uniden-sds100/codeplug-backups/
├── sds100-{nickname}-2026-05-01.tar.gz    (pre-update baseline)
├── sds100-{nickname}-2026-05-08.tar.gz    (after MPSCS site additions)
├── sds100-{nickname}-2026-05-15.tar.gz    (after firmware update to X.Y.Z)
└── sds100-{nickname}-2026-05-22.tar.gz    (current)

The most-recent backup file is TBD — verify with Jeff. Each backup tarball should contain the entire /SDS100/ directory tree from the SD card. The Sentinel .dat file alone is not sufficient as a backup because it does not capture per-favorites-list HPF files, recordings, GPS logs, or firmware images. Tar the whole tree.

5.3 Backup mechanics

The two practical paths:

Via ProScan / Sentinel — both have a “Backup” function that writes a copy of the codeplug to a chosen path. ProScan’s backup writes a single .hpdb file (Uniden’s compact HomePatrol-database format); Sentinel’s backup writes a directory tree. Either is valid; both have been observed to truncate or skip files under rare conditions (CPS bugs), so the direct SD-card tar is more trustworthy for “I really need this to work in three months when the radio is in pieces.”

Via direct SD-card copy — remove the SD card from the radio, insert into a card reader on the host PC, and tar czf sds100-{nickname}-$(date +%Y-%m-%d).tar.gz /media/jeff/SDS100/SDS100/. This is the gold-standard backup. Takes ~30 seconds. Restore is a tar extract back to a fresh SD card formatted FAT32; the radio boots into the restored configuration the next time it powers on.

5.4 Restore procedure

If the radio’s SD card corrupts (rare but happens, especially with the older smaller microSDHC cards), the restore is:

1. Format a known-good microSDHC (32 GB or smaller, FAT32) in a PC card reader
2. Extract the most-recent backup tarball to the SD card root: tar xzf sds100-{nickname}-YYYY-MM-DD.tar.gz -C /media/jeff/SDS100/
3. Verify the directory structure is /SDS100/Sentinel.dat, /SDS100/Favorites/, etc. at the root
4. Insert SD card into radio, power on — radio should boot to the same configuration as the backup date

Note that recordings made after the backup date are lost, GPS logs after the backup date are lost, but the operational codeplug is restored.

5.5 The “I’m about to do something risky” backup

For substantial changes (importing a 500-talkgroup system, hex-editing Sentinel.dat, testing a beta firmware), take a pre-change backup with a descriptive suffix: sds100-{nickname}-2026-05-24-PRE-mpscs-import.tar.gz. Makes it obvious in three weeks which backup to restore when you realize the import broke something subtle.

---

6. Field use

6.1 Antenna pairing

The stock antenna is a Uniden-branded SMA-male rubber duck, approximately 15 cm (6 in) long, with a broadband design that compromises gain on every band in favor of covering the full 25-1300 MHz tuning range. Performance is mediocre by design: the OEM rubber duck is electrically short on VHF (where 1/4λ = 50 cm at 150 MHz, vs 15 cm physical length), close to 1/4λ at 460 MHz UHF (where it performs best), and inefficient again at 700-900 MHz (where the design is in a higher-order resonance with reduced gain).

For incident-portable use where the radio is on the belt, the stock rubber duck is acceptable but not ideal. The standard upgrade is the Diamond SRH77CA dual-band whip — approximately 40 cm (16 in) long, SMA-male, broadband VHF/UHF — which adds ~3-6 dB of effective sensitivity across the 144-470 MHz range that covers most public-safety, amateur, and business VHF/UHF. The SRH77CA is the same antenna recommended for the AnyTone D878UVII and the Yaesu VX-8DR; it covers the radios cross-functionally. Mid-2026 pricing approximately $25-30 from Ham Radio Outlet or DX Engineering. Cross-reference [Antennas Vol 9 (Portable & mobile monopoles)](../../../Hack Tools/Antennas/02-inputs/volume_sources/vol9.md) for the full treatment of handheld-scanner antenna upgrades.

For 700-900 MHz public-safety reception specifically, the SRH77CA is still better than the stock antenna but is not optimized for the band; if your primary use case is 800 MHz public-safety, a dedicated 800 MHz whip (Diamond SRH519, ~$25 mid-2026) is the better choice. For 23cm (1240-1300 MHz) reception, no handheld whip is well-optimized; the rubber duck is fine since you are not going to do serious 23cm monitoring from a handheld.

For base-station scanning at home (the SDS100 sitting on the desk or in a car cradle), the right answer is a discone outdoor antenna — the Diamond D-130J (~$130 mid-2026) is the standard. Mount the discone outdoors with a clear sky view, run LMR-400 down to the desk (50-foot run is ~1.3 dB loss at 460 MHz, ~2.6 dB at 900 MHz; the discone’s broadband gain mostly offsets), terminate in SMA-male at the radio end. Cross-reference [Antennas Vol 12 (Discone & wideband)](../../../Hack Tools/Antennas/02-inputs/volume_sources/vol12.md) for the discone-design and -installation deep dive, and [Antennas Vol 29 (Use-case Matrix)](../../../Hack Tools/Antennas/02-inputs/volume_sources/vol29.md) for the explicit SDS100-antenna pairing matrix with all four pairing tiers.

6.2 Posture — incident-portable and EDC

The SDS100 is on Jeff’s belt in two postures:

Incident-portable — at an event (parade, concert, neighborhood emergency), pulled out of the bag and onto the belt with a speaker-mic. Favorites list set to the local public-safety + the event-specific frequencies (event radios are usually business UHF 460-470 MHz with CTCSS, easy to find with Close Call if not pre-programmed). Volume up enough to hear over crowd noise. Battery usually fresh; expect 8-10 hours of use.

Everyday-carry — in the day bag for trips out of town. Favorites list set to whatever metropolitan area is current (GPS-based site enable handles the cross-state-line drift automatically). Volume low; mostly in scan-and-sleep mode. Battery usage minimal; one charge lasts the trip.

6.3 Battery management

Practical numbers on the BP100 3000 mAh pack (TBD — verify with Jeff if the spare is the higher-capacity revision):

• Active scanning, backlight on auto, volume audible — 8-10 h
• Active scanning, backlight forced on, volume loud — 5-7 h
• Scan-and-sleep (intermittent traffic), backlight off — 14-18 h
• GPS-on, active scanning — subtract ~10-15%
• Recording-on-hit — negligible additional drain unless continuous

For a full-day event, carry a spare BP100. Swap takes 30 seconds with the included screwdriver. For multi-day trips, carry the wall charger or a USB-C power bank — the radio charges while operating, so a 10000 mAh bank in the bag keeps it running indefinitely.

6.4 GPS lock practicalities

Cold-start lock is 1-3 minutes outdoors with clear sky; in a vehicle, ~30 seconds after leaving the driveway (windshield is not a serious obstacle). Indoors, lock is unreliable — concrete and steel-framed buildings block; wood-framed residential sometimes locks weakly near windows. For indoor operation, set a manual GPS location in the menu so GPS-based site-enable operates from the fixed location instead of searching continuously.

6.5 Common gotchas

• “Hearing everything as garbage” — LSM detection confused on a simulcast P25 system. In the system menu, force Modulation Type to LSM or C4FM instead of Auto. If you cannot tell which system is affected, disable favorites lists with quick-keys and re-enable systems one at a time
• “Hearing nothing on a known-active system” — check favorites-list enabled (active-quick-key bar at bottom of display), system enabled within the list, and at least one site enabled (GPS-disable can silently disable all sites if your GPS is too far from the system’s sites or has no lock)
• “Audio drops out mid-transmission” — radio is hopping between simulcast sites where one is weaker. Site indicator top-right; if it is hopping rapidly, force-select the dominant site (Site Lock = On)
• “SD card is full” — recordings accumulate; delete old /SDS100/Recordings/ periodically. Always format new cards in the radio (Menu → Settings → Format SD), never in a PC — the radio’s format applies an SDS100-specific FAT32 layout
• “Radio is hot to the touch” — TrueIQ baseband processing is computationally expensive; warm during active scanning is normal, not a fault
• “Battery life is suddenly much worse” — first suspect: GPS is searching indoors without ever locking. Move outdoors, disable GPS, or set a manual GPS location

---

7. Tips and tricks

Eight non-obvious operations and configurations that aren’t in the manual but are worth knowing.

7.1 Quick-key combos for situational mode switching

The quick-keys 0-9 (and shift-0 through shift-9 for keys 10-19) give 20 instant on/off toggles for favorites lists. Plan them in advance:

• QK 1 — local public-safety (always on by default)
• QK 2 — local fire/EMS (on)
• QK 3 — local business (off; on during events)
• QK 4 — amateur 2m/70cm (on; for repeater monitoring)
• QK 5 — aviation 118-137 (off; on near airports)
• QK 6 — weather (off; on when watches/warnings issued)
• QK 7 — federal (off; on for federal-presence events)
• QK 8 — railroad AAR (off; on near tracks)
• QK 9 — military (off; on near bases)
• QK 0 — discovery/scratch (off; on for active discovery work)

The arrangement varies by operator but the principle is the same: each quick-key represents a coherent monitoring use case, and you toggle them in and out as the situation changes. The radio remembers quick-key state across power cycles.

7.2 Profile-switching for major scenario changes

When the scenario changes more dramatically than a quick-key toggle can handle (e.g., traveling to a different metropolitan area, going to a multi-day event), use profiles. A profile is a saved snapshot of the current favorites-list selection and quick-key state. Save your home configuration as “Home” profile, your travel configuration as “Travel-{city}” profile, your event configuration as “Event-{event-name}” profile. Loading a profile is one menu pick and switches the entire active configuration. Profiles are stored in /SDS100/Profiles/*.hpd on the SD card.

7.3 Recording-on-hit for incident review

Each channel has a Record on Hit flag (configurable in ProScan or Sentinel). When set, every transmission on that channel is recorded to /SDS100/Recordings/ as a WAV file (mono, ~16 kHz, ~250 KB per 30-second transmission). Turn on for critical channels (police dispatch, fire main). A 32 GB card holds ~100,000 average-length transmissions. Review via Sentinel/ProScan playback UI or directly on a PC. The TrueIQ recording alternative writes raw IQ baseband (~10 MB per 30 s capture) for re-demodulation in software — forensic use only, not daily-driver.

7.4 Manual modulation override for stubborn systems

The Auto Modulation setting works for ~99% of P25 systems but a few outliers exist. The two known categories: (1) very-old P25 Phase I systems whose modulation parameters drift slightly out of spec, and (2) P25 Phase II systems with non-standard slot-timing. If a known-active system is producing garbled audio with Auto, manually configure the system’s Modulation Type to the specific decoder (C4FM, LSM, CQPSK) — the right value is usually documented in the RadioReference wiki for that specific system.

7.5 SD-card formatting — always in the radio, never in a PC

The SDS100 expects FAT32 with a specific partition layout that PC tools (especially Windows’ built-in format) do not produce reliably. When using a new microSDHC card, format it in the radio: insert the card, power on, Menu → Settings → SD Card → Format. The radio writes its own partition table and FAT32 filesystem. Recordings, codeplug, and firmware updates then work correctly. Cards formatted in a PC sometimes work but produce subtle bugs (recordings that won’t play back, codeplug that won’t write); reformat in the radio if any of these symptoms appear.

7.6 Avoid running on stock antenna in dense indoor environments

The stock rubber duck is electrically short on most bands and is severely degraded inside steel-framed buildings, basements, and underground garages. RF performance can drop 10-15 dB below the antenna’s already-mediocre nominal sensitivity. For indoor operation, either use the SRH77CA whip (better but still indoor-limited) or connect the radio to an outdoor antenna (the discone, or even a $30 magnetic-mount on the metal roof of the car parked outside, run in through a coax cable).

7.7 Backlight intensity tuning for battery life

The auto-backlight is a good default but the ambient-light sensor over-drives the backlight in bright indoor environments (where the LCD is in shadow but the sensor sees room lights). Manually setting the backlight to “Low” or “Medium” in most indoor environments saves significant battery without compromising readability. The setting persists across power cycles.

7.8 Discovery-mode logs for new-area exploration

When traveling to an unfamiliar area, run Discovery mode on the 460-470 MHz business-UHF range for an hour or two in the evening. Review the log to see what business systems are active locally; cross-reference with RadioReference to identify them. The log is /SDS100/Logs/Discovery_*.log, plain text, parseable by any tool. This is the fastest way to build an accurate picture of local RF activity before importing pre-built RadioReference system definitions.

---

8. Resources

8.1 Manuals

Located in ../manuals/uniden-sds100/:

• Easier to Read SDS100_200 Manual.pdf — Bill Cleare’s community-edited version of the official Uniden manual, reformatted for readability; covers both SDS100 and SDS200 since they share most operational features
• Uniden SDS100 Original Manual.pdf — Uniden’s official user manual (the PDF on the SDS100 product page); the canonical reference for menu trees and parameter descriptions
• Keys for SDS100.xlsx — community hotkey-reference spreadsheet; useful for printing as a desk reference

8.2 Software

• Sentinel (Uniden CPS, free) — bundled with SDS100 firmware updates; download from Uniden’s support page. Daily-driver for firmware updates; secondary CPS
• ProScan (third-party CPS, paid) — https://www.proscan.org; Jeff’s license file at programs/proscan/license-key.txt; daily-driver CPS for favorites-list management. Current installed version 24.4 with 24.0 archived as known-good fallback
• RadioReference (database subscription, paid) — https://www.radioreference.com; required for direct ProScan/Sentinel system imports

8.3 Vendor and community resources

• Uniden SDS100 product page — https://www.uniden.com/products/sds100 — current firmware downloads, accessory list, warranty info
• Uniden SDS100/SDS200 Yahoo/Groups.io community — https://groups.io/g/UnidenSDS — the active community for SDS-series questions, firmware betas, codeplug sharing
• RadioReference SDS100 wiki — https://wiki.radioreference.com/index.php/SDS100 — community-maintained reference, includes the per-system LSM/C4FM/Auto-modulation guidance
• RadioReference forums — https://forums.radioreference.com — peer support, scanner-specific subforums, the de-facto place to ask “why isn’t my SDS100 decoding this system?”
• ScannerMaster — https://www.scannermaster.com — alternative vendor (vs Uniden direct), often has the BP100 spare batteries and SRH77CA antennas in stock when Uniden does not
• BCAvalon’s SDS100 review — the canonical long-form independent review from initial release; useful for design-rationale context, although now somewhat dated on firmware specifics

8.4 Cross-references within this series

• Vol 1 (Overview, decision graph) — the entry point; the SDS100 is row 10 in the lineup table
• Vol 11 (Uniden SDS200) — the base/mobile flagship sibling; same TrueIQ architecture, different form factor
• Vol 12 (Uniden BCD536HP) — the previous-generation base/mobile; covers what the SDS100 architecture replaced
• Vol 13 (Uniden BCD396XT) — the previous-generation handheld; the backup scanner
• Vol 21 (Programming software) — full ProScan / Sentinel / RadioReference treatment, including Wine setup on Parrot OS
• Vol 22 (Frequency planning & license envelope) — the legal envelope for receive monitoring

8.5 Cross-references to sibling antenna deep dive

• [Antennas Vol 9 (Portable & mobile monopoles)](../../../Hack Tools/Antennas/02-inputs/volume_sources/vol9.md) — SRH77CA, SRH519, and other handheld whip options
• [Antennas Vol 12 (Discone & wideband)](../../../Hack Tools/Antennas/02-inputs/volume_sources/vol12.md) — Diamond D-130J and other base-station discone options
• [Antennas Vol 29 (Use-case Matrix)](../../../Hack Tools/Antennas/02-inputs/volume_sources/vol29.md) — explicit per-radio antenna matrix; the SDS100 row enumerates all four tiers of antenna pairings with prices and feedline recommendations