Mode | Bandwidth | Speed | Frame Length | Mininum SNR |
---|---|---|---|---|
Slow | 25 Hz | 8 WPM | 30 seconds | -28 dB |
Normal | 50 Hz | 16 WPM | 15 seconds | -24 dB |
Fast | 80 Hz | 24 WPM | 10 seconds | -20 dB |
Turbo | 160 Hz | 40 WPM | 6 seconds | -18 dB |
To get started, have a look at these pages:
Under File
→ Settings...
Radio
→ CAT Control
:
Radio
→ Rig Options
Cat Control
page
Audio
At normal speed, JS8Call transmits in blocks of 15 seconds.1) For two stations to be able to communicate, the start of these blocks has to be synchronized to within about 2 seconds of the horizontal lines on each station's scope. That's why it's really important for everyone to keep their computer clock as accurate as possible (to within 2 seconds of each other). You can easily test the accuracy of your clock by going to https://time.is
Here's an example of a block that is within the horizontal lines, so it's well synchronized (with my station anyways):
There are three ways to adjust your clock:
View
→ Show Waterfall Controls
→ Timing
tab. Use the up and down arrows to adjust your time drift (more on this below):
Time Delta
entries would be 0 ms. Realistically, there's always be a bit of variance, but you should try to ensure that your clock is synchronized with most other operators.
Time Drift
to -500 ms to cancel out the Time Delta
(and vice versa). Note the sign (+/-) of the Time Drift
is opposite that of the Time Delta
For example, here I had to put a Time Drift
of -100 on mine to match the other operators:
The Issue: Sometimes the QSOs in JS8Call don't get decoded properly: The waterfall shows the data blocks being received, but the text doesn't show, or parts of it do, but with gaps showing as “…” instead.
The Reason: At first, I thought that the YAAC (the APRS program I was running at the same time) was causing the issue because when I close it, JS8Call would start behaving again. But it turns out that it was simply a lack of CPU power. I'm running JS8Call on a cheap mini computer and was reaching 100% CPU when running JS8Call, YAAC, and Firefox at the same time.
Turns out that running any two of these programs is fine, but not all three.
To check on your CPU usage, press CTRL+ALT+DEL on your keyboard, then select Task Manager
.
If the waterfall on the JS8Call screen shows a narrow light blue region with darker areas on either side, it could be that your radio filter is too narrow. Roughly, the filter should be set to 3kHz. I usually have mine set between 500Hz and 2700Hz.
Some tricks:
Mode | Bandwidth | Speed | Frame Length | Mininum SNR |
---|---|---|---|---|
Slow | 25 Hz | 8 WPM | 30 seconds | -28 dB |
Normal | 50 Hz | 16 WPM | 15 seconds | -24 dB |
Fast | 80 Hz | 24 WPM | 10 seconds | -20 dB |
Turbo | 160 Hz | 40 WPM | 6 seconds | -18 dB |