Hi Philip,
the messages that normally have grids are CQ calls, replies to CQ calls,
and QRZ messages. That accounts for roughly 33% of all messages. If we
sent spots for all of those instead of just those with grid squares then
the overall increase would be quite small as most of them already
Hi Al and all,
On 5/18/2018 11:21 AM, Al Pawlowski K6AVP wrote:
Why not make the FT/JT messages a bit longer to accommodate the compound calls?
If a longer tx/rx cycle time would be needed for FT8 - up to 30s would be fine
by me. It would be nice to have enough time to manually initiate a
Why not make the FT/JT messages a bit longer to accommodate the compound calls?
If a longer tx/rx cycle time would be needed for FT8 - up to 30s would be fine
by me. It would be nice to have enough time to manually initiate a decodable CQ
answer.
If a longer cycle time or message improved
I already get a bunch of spots (from other modes) without locators. This
will just encourage me to allow people to enter grids on pskreporter.
I'm already think that I have to deal with the /B calls and just use the
locator of the base callsign.
Do you really think that this would be a big
I don't think it's the location that is important but the "who's seeing me"
which doesn't care about your location. You just can't draw the traces without
it.This should only be done for CQ messages so very little traffic
increase.Philip probably maintains the last grid reported for a call
On 18/05/2018 03:43, Philip Gladstone wrote:
I've been contacted by a few people with compound callsigns whose
transmissions are never reported to PSKReporter. I took a quick look
at the WSJT-X code and it appears that the CQ is only reported if
there is both a callsign *and* a grid. I suspect
I've been contacted by a few people with compound callsigns whose
transmissions are never reported to PSKReporter. I took a quick look at
the WSJT-X code and it appears that the CQ is only reported if there is
both a callsign *and* a grid. I suspect that these compound callsigns
are not being
