Hi Gary, it enables the reception of Location UDP messages (https://sourceforge.net/p/wsjt/wsjtx/ci/master/tree/NetworkMessage.hpp#l359) to change the station grid locator. The intent is that a

Recently after a software fix with WSJT--x for 60 meter operation, I noticed a change in the power slider control. It has become somewhat erratic in that it is simulating a real life dirty

Could someone please explain the Auto Grid function available on the General Settings tab? The tool tip says "Check to allow grid changes from external programs." What external programs? When

Bill, excellent call; problem solved. I performed a CPU Reset on the Icom yesterday trying to resolve another, unrelated issue, and I guess I missed that parameter change. I have been changing a lot

On 26/05/2019 01:42, Matt Thomas W5MT via Groups.Io wrote: Hi Matt, turn off "CI-V Transceive Mode" in your rig's menu. 73 Bill G4WJS.

Using WSJT-X 2.0.1, Navigator interface, Icom 756ProII. This config has been working greatly for many many months. Just in the last couple of days whenever I tune the VFO manually, the WSJT program

An updated TQSL configuration file was released this morning and LoTW now accepts FT4 as a submode of MFSK.

I use JTAlert to log FT4 QSO's to HRD v5.0 JTAlert records the MODE as FT4. I have been uploading these log entries to eQSL with no problem and have received many confirmations. eQSL is

It wasn't quite unanimous. But the new spec 3.0.10 (?) hasn't been published yet. A: MODE field value of FT4. 1 Vote. B: SUBMODE field value of FT4 with MODE field value MFSK. 12 Votes de Mike

Is LOTW accepting FT4 yet? Do I need to resubmit as MFSK? Tnx 73, Herb WB8ASI

Wonderful Bill and thank you for taking the time to experiment for me. I take particular satisfaction by reading "it also shows what would be transmitted and decoded by another station" That was my

What mode/submode is FT4? My confidant Julian Assange assures me that the ADIF keepers unanimously agreed (at least a week ago) that FT4 is an MFSK submode. For some unknown reason, this has been kept

Ah okay. Now I understand. Bonne chance et bon DX des États Unis. Mike G7TWC

In the CQ at 200200 I see you sent CQ F2YS FN31 not CQ W2/F2YS. This is why I asked. Mike G7TWC

On 17/05/2019 23:16, Jacques Pecourt wrote: Hi Jacques, it works for me. Here are two invocations: c:\WSJT\wsjtx\bin>ft8code "CQ W2/F2YS FN31" Message

Bill, Interesting comment you made in a previous post ( I strongly recommend anyone using a non-standard call try out the possible messages using the ft8code tool we provide in the WSJT-X install

Mike, I do use the prefix (W2) / before the F2YS as the proper ID procedure. May be you misunderstood what I was trying to say. Forcing the grid square after the CQ (in TX6), the W2/ disapears once

Thanks for explaining the hash/space constraints, Bill. The next question here is why does Jacques use CQ F2... in his CQ and not W2/F2...? That is very confusing. Surely the accuracu of the

John, that is not possible unless QSOs with non-standard calls are sacrificed. Clearly you have not understood what messages are allowed and what is required for a valid two-way QSO. See my last post

Hi Mike and Jacques, check the WSJT-X User Guide https://physics.princeton.edu/pulsar/k1jt/wsjtx-doc/wsjtx-main-2.0.1.html#COMP-CALL Note that the only opportunity, for a station working another