Hi is anyone willing to share some vb.net code which will decode WSJT-X messages? Thanks Clive G4NAQ

Hi Randy, To put this on the right rails may I refer to an excellent paper https://physics.princeton.edu/pulsar/k1jt/FT4_FT8_QEX.pdf It describes how the messages are constructed and source coded. The

I have no idea what your problem might be ... using WSJX 2.6.0-rc1, select Settings (F2) -> Colors and click on the Fetch Now button. When I did that, WSJTX reached out to LotW and downloaded the

Well I did find the file on the computer. "FETCH" did not work even after installing all the files suggested to do a "FETCH". I went to the web page as just got a blank page with nothing

I love the idea of the F/H quick switch button on the main screen. It is actually seldom needed if you are chasing a DXPedition, one usually stays in Hound until you can finally make the contact.

Found the best workaround so far, and it's very simple: Cancel using the Esc key rather than the mouse. Just gotta remember to do it that way. I generally do use the keyboard rather than mouse clicks;

You'll have to convince logger32 to add multicast. Mike W9MDB

Upgrade to the latest Hamlib -- and if you still have problems do the debug stuff too. New hamlib for installation directions #1 Shut down WSJTX/JTDX #2 Download either the 32-bit or 64-bit DLL

Normally it works fine. But if I start to "play" with the radio, IC-7300 WSJT-X "complains after a while (loosing the connection). It's not any new thing. Always been like that. But before it was just

I discovered an irritating program behavior that I did not see discussed as I browsed the #logging topics. I usually log QSOs at the first opportunity; when I've sent 73, then as far as I'm concerned

A separate topic brought to light the fact that, with good signals, a surprisingly short transmission (either started late or ended early) can be decoded. This raises an interesting question in my

@ Alex DH2ID But it is NOT working with logger32. -- 73 de Daniel, HB9DDS

What rig? First off let's try the latest hamlibNew hamlib for installation directions #1 Shut down WSJTX/JTDX #2 Download either the 32-bit or 64-bit DLL matching the 32/64-bit version of WSJTX/JTDX

Hi Al, Yes it is. I just downloaded a new file. Do you have the OpenSSL libraries correctly installed? Or perhaps it's an issue wit N1MM? AFAIK no. 73's de Kari, oh2gqc

Is this file being produced anymore. It seems that this is missing when trying to fetch the LOTW users and also shows as an error in the startup of WSJT when using FT8 with N1MM. If not there how

If only a restart fixes it then it sounds like something with the serial port driver. I assume you have a USB serial adapter?  What rig is this? Uninstall the serial port in the Device Manager (I'm

Kurt - if you send me your email (it's not in QRZ.com and I can't get the full email address from this thread) I'll send you my configuration screenshots. BTW I am using the ELAD FDM-DUO selection in

Hi Upgraded and I have CAT issue now from time to time. Hamlib error and it doesn't help to do "retry" which worked before. The frequency setting is 0.000. The only fix is to restart the PC. Very

Wow, thought it was only me. I have a slow Acer with a cheap AMD CPU, $150 laptop from Walmart bought 7 years ago and all this time it worked fine with my K3 and KPA500. After the W10 update last

To add to this, DXLabs SpotCollector can connect to WSJT-X, color highlight callsigns that you need based on your DXKeeper log in real time, and display spots from your WSJT-X of needed DX that you