While working this last weekend’s JS8Call QSOs I noticed some heavy QSB (fade) on signals on the waterfall.
Turns out they were XYL induced!
While working this last weekend’s JS8Call QSOs I noticed some heavy QSB (fade) on signals on the waterfall.
Turns out they were XYL induced!
Wanted to give JS8Call, the more PSK31 variant of FT8, a whirl.
Loaded up quickly on my WI-001L Washington Island station computer and quickly got the hang of things.
At our new QTH we’ve been hard at work – actually a whole team has been hard at work – getting the site ready for the first tower.
First a tower site had to be selected. Topography, trees, and access were special considerations. Vern K9EME has been hard at work cutting down unneeded trees once the site was picked, and processing the felled trees into firewood.
When a QSO is pretty impersonal, fleeting in time, and distilled down to the absolute basics to qualify as a QSO, what level of courtesy does that QSO deserve in memorializing the communication in a QSL Card?
Many operators log their FT8 QSOs using Log Book of the World, eQSL, QRZ Log, and others, but a few take the time to send out proper QSL cards.
Some operators request return QSL cards as well.
Does an FT8 QSO deserve a QSL card?
At the FlexRadio Community folks were discussing whether SmartSDR Version 1.x was going to see any feature additions (think not) and if you had to have an internet connection to run a FlexRadio (which is “no” other than upgrades or doing remote by SmartLink).
Here are my comments:
Andy KU7T had asked in reference to my write up on background FT8 QSOs:
“How do you combine your QSOs with your master log? Or do you just import the ADIF later? Then how do you know what is an ATNO?”
Breaking his questions down: