Charlie here is the US a call sign is no longer a indicator of location. Bob - wd6dod

Not exactly easy in the 2 second gap. I actually do this but the calling station often repeats the reply (not exactly saving time) and the whole rigmarole starts again. You can also close the program,

Sorry, but I don’t care, my request stands in that I want a way to ignore responses which are not of the standard format and do not include a grid square. It’s called choice, they choose not to

Charlie, You can choose to ignore them, by disabling TX before you have a chance to reply, or double-clicking on the call you do want to answer. The choice is all yours. 73 Phil GM3ZZA

Charlie, you are either putting word into my mouth I did not say, or you are misunderstanding. A Tx1 message does not always contain a gridsquare. A user can choose not to

Bill No I'm not, you are talking semantics here. I am referring to the sequence messaging and as it's a prescribed order it is in itself a protocol, albeit not a data one. It is I and others it seems

Hi Dave, we don't really expect users to read them, but at least we can point them out when they do happen cover the issue being asked about, hi. 73 Bill G4WJS.

Thanks Bill Guess I should read the incuded documents... 73 Dave W4WLC

Hi Dave, instructions to configure shared memory parameters for your system are included in the ReadMe.txt file on the installer DMG. 73 Bill G4WJS.

Bill Trying to install WSJTX 2.5 on the Mac laptop. It has never had the WSJTX program on it. The topic should have said 2.5 not 2.4. Dave W4WLC

<snipped part answered separately> Hi Ralf, you can't send 0 or 1 for the report & serial word, it's not that flexible. The report part must be one of 52, 53, 54, 55, 56, 57, 58, 59. A token in

Or to 73. Ralf -- Dr. Ralf Schlatterbeck Tel: +43/2243/26465-16 Open Source Consulting www: www.runtux.com Reichergasse 131, A-3411 Weidling email:

Hi Ralph, that is already implemented - see the Location(11) message in the WSJT-X UDP Message Protocol: https://sourceforge.net/p/wsjt/wsjtx/ci/master/tree/Network/NetworkMessage.hpp#l406 You must

[..] Cool. I'd set the 590000 to 0 or 1 if possible to at least reduce the confusion a bit .-) But a mechanism to update the first call <G4WJS> in your example with the qso partner of the last call

I agree it is unfair to ignore non-standard calls. On the other hand I consider it quite acceptable for standard calls. 73 Roger GW4HZA

Hi Ralph, there is nothing stopping you from entering a message like the following into the Tx5 field: <G4WJS> <DL/OE3RSU> 590000 JN75mm It will be transmitted, and if the

Charlie, you are confusing the message protocols and the order of messages exchanged in QSOs, they are very different things. No changes were needed to the protocols to

I opened a can of worms what I posted this issue a few days back. It seems that the developers ignoring the protocol in the official documentation succumbed to pressure from the users to allow the

Hi Bill No sorry never ignored your comments - definitely not on purpose would I. Yes I know there are issues with Special event calls, did mention that - impossible to send grid in CQ and needs to

Sorry for chiming into the middle of this, but wouldn't it be possible for the non-standard call to send an EU-VHF message (i3=5) with two hashes for the callsigns and a locator with length 6 (and