A practical guide to what changed in WSJT-CB 1.1 and how to use it confidently on 27 MHz / 11 meters if you already know WSJT-X.
This text is intentionally halfway between an operating guide and a feature update. It explains the real user-facing changes from the WSJT-CB README, but it keeps the focus on what an operator sees, clicks, decodes, and transmits during daily activity.
WSJT-CB is not a new family of digital modes. It is a CB-oriented fork of WSJT-X, shaped specifically for 27 MHz operation and for the kind of identifiers commonly used on 11 meters. If you already know WSJT-X, the menus, timing, and general rhythm still feel familiar. What changes is the amount of friction: WSJT-CB stops treating CB reality as an edge case.
The official README describes the code changes in technical terms. In operator language, version 1.1 is a maturity release. It improves the handling of CB-to-CB QSOs, tidies the interface, makes country information more useful in the decode window, and gives the application a more coherent identity from first launch onward.
CB-style identifiers are validated and carried through the message flow more naturally than in standard WSJT-X.
The software now includes the 11 meter segment directly, with CB working frequencies already present in the normal workflow.
Numeric CB prefixes can resolve to practical country names, and unknown prefixes no longer receive rough placeholder labels.
Auto Sequence and report parsing are more reliable when both stations use longer non-standard CB-style callsigns.
This software is provided for educational purposes only. You are solely responsible for complying with local, national, and international radiocommunication laws and regulations.
Before you open the program, make sure you are really starting the WSJT-CB package and not a standard WSJT-X build that happens to be on the same computer. That sounds obvious, but in practice it is one of the easiest ways to confuse yourself when settings, accepted callsigns, or available frequencies do not match what you expect.
The classic WSJT-X basics still apply in full. Your computer clock must be accurate, CAT or PTT control must already be dependable if you use it, and your audio path must be clean enough for digital work. WSJT-CB improves CB-specific behavior, but it cannot compensate for an unstable station or overdriven transmit audio.
The first-run experience is close to WSJT-X, so the normal station details still matter: your callsign, locator, radio control, audio input, and audio output. The difference is that WSJT-CB is happier with realistic CB-style identifiers, so you can configure the station the way you actually use it instead of trying to force it into amateur-radio conventions.
One small but useful change in version 1.1 is that PSK Reporter spotting is enabled by default. On a fresh installation, that makes the software useful more quickly because receiving activity can start contributing to spotting without extra menu digging.
If you already know WSJT-X, think of setup in the same order you always would: confirm the right rig, confirm the right audio devices, confirm the clock, then spend a minute watching the waterfall before you even consider transmitting.
The main operating window is more focused. WSJT-CB adds an explicit 11m band from 26.965 MHz to 27.405 MHz, and it keeps the modes that make sense for the project visible in the everyday interface: FT8, FT4, FST4, and Q65. Older or less relevant paths such as WSPR, Echo, FreqCal, and several legacy modes are no longer part of the normal front-line experience.
For the operator, that matters because the program no longer feels like a general-purpose lab bench that happens to have been pushed onto 27 MHz. It feels like a tool that expects 11 meter operation and has been trimmed around that expectation.
The reference frequencies are also clearer. FT8 activity centers on 27.265 MHz, with 27.045 MHz kept as an alternate FT8 choice. For FT4, FST4, and Q65, 27.045 MHz is the default CB working point exposed by the fork.
This is one of the biggest practical changes. WSJT-CB accepts CB-style callsigns using the pattern numeric prefix, then one or two letters, then a numeric unit number. In plain terms, that means the software recognizes a broad range of real on-air CB identifiers instead of rejecting them at the door.
| Example | Accepted? | What it means in practice |
|---|---|---|
1A1 |
Yes | A short CB-style identifier is valid and works normally in the UI and message flow. |
26AT101 |
Yes | A common international CB format is accepted exactly as an operator would expect. |
111TT999 |
Yes | Three-digit numeric prefixes are supported when the rest of the pattern stays within the normal CB shape. |
1AT1000 |
Yes | A four-digit unit number is allowed only in the special one-digit-prefix case. |
26AT1000 |
No | The four-digit unit extension does not apply when the prefix has two digits. |
AT1000 |
No | The software still expects a numeric prefix before the alphabetic club or group letters. |
The short version is simple: WSJT-CB is more forgiving than stock WSJT-X, but it is not free-form. If a callsign is rejected, the first thing to check is whether the numeric prefix exists and whether the final unit number falls inside the supported format.
Once the station is configured, daily use still follows the same logic that WSJT-X operators already know. In FT8 you are still working in a 15-second cadence, and in FT4 the exchange is still faster at 7.5 seconds. The sensible operating habit is still to listen first, watch a couple of cycles, pick a clear audio slot, and avoid calling directly on top of a stronger ongoing trace.
A normal WSJT-CB contact on 11 meters therefore starts in a familiar way: you move to the intended working frequency, monitor activity, click a station or answer a CQ, exchange signal reports, and let the software walk toward RR73 or 73. Where version 1.1 helps is in the awkward middle and final stages of CB-to-CB QSOs, especially when both callsigns are long and non-standard by classic WSJT-X assumptions.
The README for version 1.1 specifically mentions better parsing of signal reports, cleaner handling of RR73 and 73, and recovery paths when a partial decode might otherwise confuse the parser. Translated into operator terms, that means a long CB-to-CB QSO is less likely to stall between the report stage and the sign-off.
WSJT-CB now uses the numeric CB prefix to resolve many stations to a practical country label before falling back to normal DXCC-style logic. That is important because a line such as 1AT106 or 26AT101 becomes easier to read at a glance when the decode window can show the country in a CB-aware way instead of guessing through amateur-radio prefix rules.
Version 1.1 also cleans up some country naming behavior, including mismatches such as U.S.A., and it avoids showing rough placeholder names for unknown CB prefixes. The result is not magic, but it is cleaner and more trustworthy during real operating.
<...> in FT8 decodes
This remains one of the most confusing moments for people new to non-standard callsign exchanges. When two non-standard or CB-style callsigns are used in FT8, one side of the exchange may be transmitted as a hash. A third-party listener can therefore see something like <...> 26AT016 instead of the full callsign pair.
According to the WSJT-CB README, this is protocol behavior, not an Auto Sequence bug. If the software has not yet learned the hash-to-callsign mapping from a clear decode, the hidden callsign may remain masked until a later pass reveals it.
The practical advice is the same advice experienced WSJT-X operators already follow: judge the QSO by the whole sequence, not by one odd-looking line. If reports, roger messages, and the final exchange continue to progress coherently, the contact is usually behaving normally.
Clock discipline still comes first. If your system time is loose, decodes become unreliable and no amount of CB-specific improvement will save the contact. Keep the PC synchronized before blaming the software.
Transmit audio still needs restraint. Use the same good practice you would use in WSJT-X: clean audio, no speech processing, and as little ALC action as possible. WSJT-CB improves callsign handling, not the physics of a dirty transmitter.
Listening before calling is still the smart move. Spend a couple of cycles reading the band, find a free audio slot, and only then answer or call. That habit matters even more on a busy 27 MHz segment where local and long-distance activity can overlap quickly.
Auto Sequence is more useful here, but not a substitute for judgment. Version 1.1 improves non-standard CB flows, logging progression, and end-of-QSO behavior, yet the operator should still watch the exchange and intervene if the situation on frequency changes.
Beyond the on-air improvements, the application feels more finished. Branding is more consistent across the user interface, configuration naming, help areas, and log-related identity. The help section has been simplified, and the Telegram group is now part of the visible support path instead of something you have to discover elsewhere.
You may also notice that the program feels less cluttered than older experimental forks. The README notes that several legacy side tools and less relevant components were removed. From the operator chair that mostly shows up as a cleaner, more purposeful workflow rather than as a dramatic visual redesign.
On Windows, packaging has also been tightened up for the dedicated 1.1.0 installer, including fixes around country-file lookup in installed environments. In practical terms, the fork behaves less like a temporary test build and more like a maintained application.
WSJT-CB is strongest when you treat it as a focused 11 meter version of a workflow you already know. The software removes many of the awkward points that standard WSJT-X has with CB-style operation, but it still rewards the same disciplined habits: accurate timing, clean audio, careful observation, and operator judgment.
Telegram group: https://t.me/wsjtcb
Developer contact: info@xzgroup.net
WSJT-CB is based on WSJT-X by Joe Taylor K1JT and adapted for CB / 11 meter use by 1AT106 / 1XZ001 Vash.