The message announced an FT8 QSO party this weekend (16-17/12/17) to promote EURAO, which seems like a perfectly good idea.
Unfortunately, things quickly started to unravel when EURAO realised a lot of its announcement made absolutely no sense at all.
Oh dear! |
In what appeared to be a 'copy and paste' failure, EURAO advised operators that this wasn't a competition, and that we could talk about anything we liked on air.
For those who are not familiar with FT8 - which seems to include EURAO - FT8 is not a ragchew mode and, due to its sheer speed, is only suited to standardised CQ, report and 73 messages. It's also impossible to even call CQ in the way prescribed, because, whilst you can type the message in full on-screen, on transmitting there is no room left in the protocol to send it in full, let alone that plus the callsign. It actually comes out as 'CQ EURAO PART'!
This is how the wording went (accessed 13:42 12/12/2017):
'Call: "CQ EURAO Party".
Exchange: because this is a QSO event, not a contest, you can talk about
So, a big set of mistakes that leaves EURAO looking like a big, fat lemon.
Update, after the EURAO QSO Party weekend:
I didn't see a single station calling the prescribed CQ call.
3 comments:
L.O.L. ;-) 73, Bas
I would hardly say that is a big mess, or they look like a lemon. Either 1, someone forgot to take out the lined out parts, or 2 they left them in on purpose to be quasi facetious. Either way your headline is misleading and your conclusion mislead
Quite a convoluted explanation, on your part.
Clearly it is a mess when an FT8 message is suggested that doesn't actually fit the protocol.
Post a Comment