Checking the WSJT Yahoogroup, there is discussion on how the features in WSJT-x could be used for SOTA and it seems someone has worked it out.
This is from the list - so in reverse sequence - newest at the top.
Black Michael Feb 15 9:14 AM
I’ve got macro expansions working. Starting list is this…suggestions welcomed. I’ll note that using “FD” was discussed before and discounted as few would know what it means and I wonder how many would be trying to figure out a state that beings with “F”
The restriction on these macros is it needs to be after your callsign otherwise the other side can’t quite handle the format. On older versions they will just see the short macro instead of the expansion.
So like this:
CQ W9MDB /1
msg.replace(" /0"," 1010");
msg.replace(" /1"," SPLIT UP");
msg.replace(" /2"," SPLIT DOWN");
msg.replace(" /C"," CONTEST");
msg.replace(" /E"," EMAILME");
msg.replace(" /F"," FIELDDAY");
msg.replace(" /S"," SOTA");
msg.replace(" /T"," TEST");
msg.replace(" /X"," DXPEDITION");
de Mike W9MDB
Show message history
As I understand it, you can already send 2 letter directional CQ’s, so this is already possible:
CQ FD W9MDB EM49, or CQ SS W9MDB EM49
We would only need the macro codes for things longer than 2 characters (perhaps such as SOTA, CONTEST, 1010, QRP, EME*, DXPED MODE, VHF TEST MODE, etc.) Being able to have 36 potential macros sounds like it could really cover a lot of potential phrases! It almost sounds too good to be true!
I am not that familiar with the way WSJT-X is structured, but if the macro file could be accessed as a text file stored in the default WSJT-X folder, then it would be easy for users to download updated macro files as they became available.
You also might be able to use such a macro to identify something like the length of the sequence being used, provided there was a compatibility in the decoding between 15 second and other longer (but potentially more sensitive sequences). However, there may be easier ways to determine this automatically.
Very interesting possibilities VY 73, Lance
- I know FT8 was not developed as an EME mode, so I initially added this to the list sort of tougue-in-cheek. However, now that I think about it, most of my recent 2m EME contacts have been stronger than -22 dB, so I wonder if maybe there would be some interest in using FT8 on EME I don’t know that the stability would be good enough for most stations to use such a narrow bandwidth mode on EME, though. I know on 6m EME, it often seems like JT65A in Deep Search mode often could still stand another dB or two of sensitivity…
On 2/14/2018 16:49, Black Michael wrote:
I wonder if we could implement some 2-char macros for that kind of thing?
/S - SOTA
/0 - TEST
/F - FIELD DAY
If first char of token is “/” then it’s a macro that gets expanded.
Sounds pretty simple…old versions would see the macro…current ones the expansion. Could have 36 macros.
So you could do
CQ W9MDB /F
de Mike W9MDB
On Wednesday, February 14, 2018, 10:41:33 AM CST, ‘Lance Collister, W7GJ’ w7gj@… [wsjtgroup] email@example.com wrote:
I understand the required protocol, but it sure would be nice to be able to use some
of the extra characters in the message to add something like “SOTA” (or possibly some
other standard acronyms like “TEST” or “CQWW”) onto the end of the CQ message… VY