Model Differences – BCT15X, UBC3500XLT & UBC800XLT

Summary: Real differences between BCT15X, UBC3500XLT and UBC800XLT that affect what you should expect from Squawker PC’s Programmer – worth reading before you rely on any of these for something you can’t afford to lose.

All three models share the same Systems/Groups/Channels screen and workflow, but the scanners themselves aren’t identical, and Squawker PC’s behaviour genuinely differs between them in a few places. This article is a single reference for those differences – the rest of the guide describes the shared workflow and points back here where it matters.

UBC800XLT: No 700 MHz, and a Trimmed Set of Fields

The UBC800XLT cannot tune 758.0-806.0 MHz. If a channel in that range gets written to a UBC800XLT, it’s silently skipped – the write still reports success, and there’s no on-screen count of how many channels were dropped, so it’s worth checking your channel list for anything in that band before programming a UBC800XLT specifically.

The UBC800XLT also uses an older, trimmed version of the programming protocol, which means a few fields simply don’t exist on it: Number Tag (on both Systems and Channels), Alert Pattern, and Volume Offset. You can still see these fields in Squawker PC’s grid, but they won’t be read from or written to a UBC800XLT – don’t rely on them surviving a round trip through this model.

UBC3500XLT: A Different Connection Path for Reading vs Writing

The UBC3500XLT is the one model in this family where Read from Scanner and Send to Scanner genuinely connect differently. Reading uses the same fixed connection settings as the BCT15X. Writing, on the other hand, automatically tries several different connection speeds until it finds the one your scanner responds to – which can take a few seconds longer to connect than a Read does. If a Read succeeds but a Write seems to hang or fail (or vice versa) on a UBC3500XLT, that’s a known quirk of how the two operations connect, not necessarily a fault with your cable or scanner.

One upside: writing to a UBC3500XLT tells you if something didn’t make it – the completion message reports exactly how many channels out of your total were successfully programmed. BCT15X and UBC800XLT don’t give you this – see the note in Writing to Your Scanner.

Auto Backup Before Sending: Verified Reliable on BCT15X Only

The Auto backup before sending option (see Reading, Backing Up & Restoring) is designed to read your scanner’s current programming and save it before overwriting anything. At the moment, this pre-write backup is confirmed to correctly capture your System/Group/Channel data on a BCT15X. On a UBC3500XLT or UBC800XLT, we can’t currently confirm the automatic pre-write backup captures your System/Group/Channel data correctly. Until this is confirmed, if you’re programming a UBC3500XLT or UBC800XLT, take a manual backup with the Save button yourself right before you click Send to Scanner, rather than relying solely on the automatic one.

Bear Tracker / Radar-Detector Categories Always End Up Locked Out

For BCT15X and UBC800XLT, every write to the scanner locks out the Bear Tracker-related categories (police, DOT, highway patrol and Bear Tracker alerts) as a fixed part of the write process – there’s no setting in Squawker PC to change this. This doesn’t happen on a UBC3500XLT write. If you use these alert categories on your scanner, you’ll need to re-enable them on the scanner itself after programming a BCT15X or UBC800XLT from Squawker PC.