Thanks so much, Joe! VY 73, Lance
On 3/19/2022 18:54:54, Joe Taylor wrote:
TO7GJ is perfectly acceptable as a standard callsign.
As described in the User Guide, the list of acceptable prefixes and suffixes
applies only to the case of a Type 1 add-on prefix or suffix, which Lance will not
be u
TO7GJ is perfectly acceptable as a standard callsign.
As described in the User Guide, the list of acceptable prefixes and
suffixes applies only to the case of a Type 1 add-on prefix or suffix,
which Lance will not be using.
-- Joe, K1JT
On 3/19/2022 2:29 PM, Lance Collister, W7GJ via
On 3/19/2022 9:39 AM, DX Jami via wsjt-devel wrote:
My call is AH6FX and I am in Virginia now. For WSJT-X purposes I
configure or set-up WSJT-X for W4/AH6FX.
Totally unnecessary -- calling CQ or answering with your grid tells
others all they need to know.
73, Jim K9YC (in California since 2
Hi Rick,
Yes, I THINK I will be OK using the callsign of TO7GJ for both FT8 and Q65-60A modes,
but it sure will be interesting to hear definitively from Joe as to whether I will
suffer in any way by not having "TO" in the list of official "Type 1" prefixes.
MNI TNX and VY 73, Lance
On 3/19/2
Lance,
Good luck on your DXpedition. I will be looking for you.
I share your frustration with "non-standard" call signs. Actually they are
standard in the ham radio world, even per Part 97 ... but non-standard for
WSJT-X. That is another issue for another day.
My call is AH6FX and I am in Vir
Hi Charlie!
MNI TNX for your email! I made sure to get a dedicated Type 1 callsign because Joe
told me that it is always better than using a compound callsign such as FH/W7GJ. But
you raise a very interesting question. I no longer see the ability to enter
non-standard prefixes in WSJT-X the wa
