News Feed Links:
Today is Monday, 2019-08-19
The first step is to set up the IC-7300 and connect it to the computer.
VFOknob until it says “3.6k”
TWIN PBTknob (top left) to adjust the boundaries to 600 and 2600 (the picture shows 650 and 3400). This step can be tweaked anytime on the fly to filter out unwanted signals at the edge of the band. This is useful if say you've got strong RTTY signals activating your AGC, thus reducing the strength of the signals you're interested in.
JS8Call transmits in blocks of 15 seconds. 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). (see http://js8call.com/faq/)
There are three ways to adjust your clock:
Show Time Drift Controls, then at the bottom of the screen you'll see the
Time Drifttool. Use the up and down arrows to adjust your time drift (more on this below):
Time Deltaentries 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 Driftto -500 ms to cancel out the
Time Delta(and vice versa). Note the sign (+/-) of the
Time Driftis opposite that of the
Time DeltaFor example, here I had to put a
Time Driftof -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
The first draft of this page was copied over from VE7HZF's site with permission. Please feel free to expend on it.