A practical, detailed and non-technical guide to the user-facing features of WSJT-CB by 1AT106, based on the WSJT-X project by Joe Taylor K1JT.
This guide is written for operators who want to understand what is new in WSJT-CB and how to use it confidently on 27 MHz / 11 meters, without needing to read source code or developer notes.
WSJT-CB is a special fork of WSJT-X shaped for CB and 11 meter use. The purpose of the fork is simple: make the software feel more natural for operators using CB-style callsigns, the 11 meter band, and real-world 27 MHz digital operation.
This is important because a standard WSJT-X installation was not designed around the needs of CB operators. WSJT-CB changes that. It recognizes CB-style identifiers more naturally, works with the 11 meter band, and improves some contact flows that could otherwise feel awkward or unreliable with non-standard callsigns.
This guide is for you if:
This software is provided for educational purposes only. You are solely responsible for complying with local, national, and international radiocommunication laws and regulations.
Before starting the program, make sure you have:
If you already know standard WSJT-X, the interface will feel familiar. The difference is that WSJT-CB is more forgiving and more useful in the CB environment.
To start the program, go to the bin folder and open WSJT-CB.exe.
When the software opens, you should see the WSJT-CB branding in the application title. That confirms you are using the modified CB-oriented version and not a standard build by mistake.
WSJT-CB understands CB-style callsigns far better than a normal WSJT-X release.
The 11 meter band is added and the project includes a dedicated 27.265 MHz working frequency.
Many CB callsigns can be shown with the correct country information directly in decoded text.
Contacts using longer CB-style callsigns are handled more reliably during FT8 exchanges.
One of the most useful changes in WSJT-CB is better recognition of CB-style callsigns. In practice, this means the program is much more willing to accept the kind of identifiers CB operators actually use.
Without this improvement, a standard release may reject or mishandle some callsigns because they do not match the expectations of the amateur-radio world. WSJT-CB removes much of that friction.
| Example | Accepted? | What it means for the user |
|---|---|---|
1A1 |
Yes | A short CB-style callsign is accepted normally. |
26AT101 |
Yes | A very typical CB-style callsign works as expected. |
1AT1000 |
Yes | A 4-digit unit number is supported when used with a 1-digit country prefix. |
26AT1000 |
No | This specific longer ending is not accepted in the same way, so format matters. |
AT1000 |
No | A numeric prefix is still required. |
The simple user takeaway is this: WSJT-CB gives you much better support for realistic CB callsign formats, but the structure of the callsign still matters. If something is not accepted, double-check the numeric prefix and numeric suffix.
WSJT-CB adds the 11 meter band to the software and includes 27.265 MHz as the default FT8 working frequency for the CB environment.
For the operator, this matters because the software is no longer treating that frequency as if it were outside normal operation for this fork. That makes day-to-day use much more straightforward.
In practical terms, if you are using this project as intended, 27.265 MHz is the key reference frequency to know and recognize.
Another very visible improvement is country lookup for CB callsigns. WSJT-CB can use the numeric prefix of many CB-style callsigns to show the corresponding country directly in decoded text.
That means you can often see a more useful country label for calls like 1AT106 or 26AT101 instead of getting a less meaningful result from logic designed for standard amateur prefixes.
For normal use, this improves readability. You spend less time guessing where a station is from and more time focusing on the contact itself.
The exact radio and audio setup depends on your station, but from the user point of view the first contact flow can be understood in a very simple way.
wsjtx.exe from the bin folder.27.265 MHz for the CB FT8 activity described by this project.Standard message flow can become awkward when both operators use longer CB-style callsigns. This is one of the areas where WSJT-CB does meaningful work behind the scenes.
The fork improves Auto Sequence so that FT8 contacts can continue more smoothly instead of getting stuck or looping around the wrong part of the exchange. In user terms, this means less confusion during contacts with long or non-standard callsigns.
RR73 and 73 instead of stalling.For the operator, a smoother Auto Sequence means less manual recovery and less uncertainty. If you use CB-style identifiers regularly, this can make the whole experience feel much less fragile.
When WSJT-CB handles two long CB-style callsigns, it uses a message flow that is more dependable for this kind of contact. You do not need to memorize the internals, but it helps to know the general order:
RR73 or 73.That may sound obvious, but the value of WSJT-CB is that it is better at preserving this flow with CB-style callsigns that would otherwise cause problems.
<...> in decodes
One of the more confusing things for users is seeing a decode that contains <...> instead of a full callsign. This can happen when two non-standard or CB-style callsigns are exchanged in FT8.
The important point is that this is normal protocol behavior. It is not a sign that WSJT-CB is broken, and it is not specifically an Auto Sequence bug.
A third-party listener may see something like <...> 26AT016 instead of the full station pair. That can simply mean the software has not yet learned the mapping needed to display the hidden callsign in full.
Sometimes the full callsign becomes visible later, once the software receives enough information from a clear decode. So if you notice this behavior, do not panic and do not assume the contact is invalid.
bin\wsjtx.exe.<...>, remember that it may simply be normal FT8 behavior with non-standard callsigns.| Situation | What it usually means | What you should do |
|---|---|---|
| Your CB callsign is accepted | The fork recognizes your identifier format correctly | Continue normally |
| Your callsign is rejected | The structure may not match the accepted CB-style pattern | Check the numeric prefix and suffix carefully |
You see <...> in a decode |
The software has not yet resolved the hidden callsign mapping | Wait for later decodes before judging the contact |
| A country appears next to a CB callsign | WSJT-CB successfully resolved the numeric prefix | Use it as a practical activity aid |
| A QSO with long callsigns keeps moving smoothly | The improved sequence handling is doing its job | Let the exchange complete |
You do not need to know the internal rule set, but the general pattern is easy to understand:
Some formats are longer than others, and WSJT-CB supports more of them than standard WSJT-X. Even so, the format is not unlimited. If you enter a callsign that looks unusual even by CB standards, the software may still reject it.
26AT101 is a good example of the intended style.1AT1000 is accepted because this fork includes a special case for that style.26AT1000 is not accepted in the same way, so changing only one part of the format can matter.This document focuses on user-facing behavior introduced by the WSJT-CB fork. It does not try to be a full operating manual for every feature of WSJT-X, every radio model, every audio interface, or every station layout.
In other words, this guide explains what is new and important for everyday use of WSJT-CB, especially the CB-focused parts. For station-specific hardware setup, you should still rely on your own radio knowledge and normal WSJT-X experience.
No. The fork includes meaningful development work, especially around callsign support, 11 meter awareness, country display, and message flow for CB-style contacts.
No. The point of this guide is the opposite: you should be able to use the software confidently without reading developer notes or source files.
Because FT8 has protocol behavior that can hide or compress non-standard callsigns. WSJT-CB improves the experience, but it does not change the underlying FT8 protocol rules.
Because this fork reflects real adaptation work by 1AT106 / 1XZ001 Vash. It took effort to make the software more useful in the CB environment, and that work deserves visible credit.
https://t.me/wsjtcbinfo@xzgroup.netWSJT-CB is based on WSJT-X by Joe Taylor K1JT and has been adapted for CB / 11 meter use by 1AT106 / 1XZ001 Vash. This guide is based on the current README notes for the fork and translates the user-visible changes into plain operational language.
Disclaimer: This software is provided for educational purposes only.
You are solely responsible for ensuring full compliance with all applicable local, national, and international radiocommunication laws and regulations.
This project is distributed under the GNU General Public License v3.0 (GPLv3).
Final note: the real strength of WSJT-CB is not only that it runs on 27 MHz, but that it has been shaped to work more naturally in that environment. That is what makes this fork valuable for everyday users.