I and others reported this same situation after the FT Roundup, although
nothing ever came of it. It seems to happen randomly, and it's always
the received report that doesn't get captured. Fixing it ruins any run
you might have going.
73
Dave AB7E
On 1/4/2020 4:47 PM, John Pelham wro
On 04/01/2020 23:47, John Pelham wrote:
Hello all,
Today in the RTTY Roundup I’ve been operating only FT8 and only S&P. I
followed Joe’s article in January QST, in that I set the Special
Operating Activity to RTTY Roundup, entered my state MA, made sure
Auto Seq is checked, renamed wsjt_log.
Hello all,
Today in the RTTY Roundup I’ve been operating only FT8 and only S&P. I followed
Joe’s article in January QST, in that I set the Special Operating Activity to
RTTY Roundup, entered my state MA, made sure Auto Seq is checked, renamed
wsjt_log.adi to wsjt_log.bak, and erased Cabrillo
Indeed, pskreporter of course can not do anything with something it doesn't
get. The dependency is of course on the client software and what it does.
I did some more testing prompted by Reino's postings.
FN25 VE3GHM does not get sent to pskreporter by WSJT-X, likewise nor does
VE3GHM FN25.
CQ VE
I don't know what others are seeing, but for me the theoretical rate on FT4
is blown away by constant and pervasive QRM. I am constantly getting busted
Q's, and then when I stop TXing I discover that someone else is now TXing
on my slot.
Is this just inexperienced operators? Does nobody listen bef
Whether PSK reporter gets to see some particular signal depends on the
decoding software. It is easy enough to experiment with various
transmissions and see which get reported. Use different callsigns
(suffixes) so that you can tell which signals get through.
On Sat, Jan 4, 2020 at 10:26 AM Reino
It seems that many, if not all messages, where the call sign is in the
'sender' position are reported to pskreporter.info. So 'DE VE3GHM FN25'
would be fine, if non-standard call sign were supported with a locator. No
need to use CQ, if broadcasting and not needing a response at that time.
73, Rei
This morning I found wide graph and input level frozen but Decode not lit.
That was caused by "Error in Sound Input" and was fixed by cycling the
Soundcard Input to a different source then back to TS-590 audio CODEC.
The WSJT-X error window was not visible until the sound card input was cycle
I may have done 2 steps in the wrong order. The JTSDK io group had 5
messages since August 2019 and 3 of them said they had new jobs and were
going QRT.
All i want to do is swap the 2 cpp lines and compile for windows.
... wonder whats on 20M today ...
Al Gerheim
Horribly mistyped on my droid.
