[SJDXA] T22T

[Bob Schenck N2OO]

SJDXA members,

It seems that the T22T ops are not always sending the RR73 after initially
sending out a report. Most of these are probably getting logged by T22T.

Here is what I did that worked. 

Beth and I each had a QSO like this on 12 meter FT8. No RR73 seen, and few
RR73's noticed with others.

Although this is not right really, what we did was "write down the log data
on a piece of paper" instead of entering it into our log. The reason is that
I don't like uploading bogus log entries to LoTW or ClubLog. It just causes
confusion later. T22T is uploading their log to Club Log when they have a
reliable internet connection. So we waited until the next day and we found
both of our QSO's in the log on Club Log. We then added our QSO's manually
into our master log (we use AC Log/N3FJP) carefully to make sure all fields
were properly entered (band mode sent/rec reports/frequency/start and end
time of QSO) etc. Then uploaded that to Club Log. Waited a couple of minutes
and then went into clublog looking for a MATCH by doing a LOG SEARCH. It
SHOULD match up. Ours actually showed double QSO's at the time logged. 

These guys don't always follow all of the rules, but not going there. This
is just for you to not miss any QSOs. You sent them a report and you
received a report from them. That should be enough.

Or.. there is another DXpedition going to Tuvalu October 10-23 by a German
team https://t2c.mydx.de

They will probably use better operating techniques and also probably have an
easier QSL method.

 

 

73!

de Bob Schenck, N2OO

President SJDXA!

GO SJDXA!

www.sjdxa.org <http://www.sjdxa.org> 

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.qth.net/pipermail/sjdxa/attachments/20230922/e1531027/attachment.html>