Where is the location of the qsos you made in WSJT-X? After a lot of trial and error I made several qsos that I logged. I want to export the list of qsos onto XMLog. Evan KB2AMY Windows

Thanks Mike, I will give it a try tomorrow. I have downloaded the file, which went just fine. 73 de Phil GU0SUP

Success. When I had version 2.5.4 installed although I couldn't get it to connect to my rig I was able to get the schedule window up briefly and enter what I wanted - 40m and 20m simultaneously on

Yes, 1x1 call signs, such as the one I am currently working with, N1D. I have several queries about this posted on WSPR-related forums, and I surmise it may simply turn out to be a flaw in the

The WSJT-X_RigControl.log file is an empty text file I created. I also gave the wsjtx_log_config.ini file the chance to create the log file. I tried both ways. WSJT-X_RigControl.log that I

I guess I should have added - are you talking about special event 1x1 callsigns? Ron - KJ5XX

That file would go in AppData/Local/WSJT-X Mike W9MDB

Placed the wsjx_log_config.ini file from downloaded from drop box into both folders. It did not generate the log file or fill the log file I then created myself and placed in the ~<me>/appdat/local

I kinda thought he was talking about N1D, as per the first line of his original missive... 73, Willie N1JBJ

What do you mean by a "three letter callsign". Are you talking about a 1 by three or a two by three such as: K5OXM or KL7ETX? An example would be helpful. Ron - KJ5XX

Actually, according to https://www.codeproject.com/Articles/1200310/Creating-WSPR-Message-in-Cplusplus you can prepend a space, noting that the third character must be numeric. I hope that's not just

"gareth.pale" <gareth.paley@...> wrote: Which hamlib version are you using Gareth? The 4.5~git version has had a lot of changes, so if you can try the current git version in place of whatever

I'm trying to operate a WSPR beacon for a special event station (N1D). It appears that the decoder in WSJT-x does not accept the use of a three letter call sign. The only spots I am getting are from

I started afresh with a new Raspberry Buster image. Then I followed the instructions at: https://physics.princeton.edu/pulsar/k1jt/wsjtx-doc/wsjtx-main-2.5.4.html#INSTALL_LINUX executing the

Try the latest hamlib...I made a change Nov 2021 where the rig's bandwidth is not supposed to change from what the user selects for Icom rigs. New hamlib for Windows installation directions #1 Shut

Hi all, New to this group, and as you would expect, I have a weird issue which I need help with... Let me see if I can explain it - I have been using WSJTx & JTAlert for ages now, and when I changed

Will do. Probably early evening today. Thank you for your help. yahoo.com@groups.io> wrote:

Did what you said. USB AUdio CODEC is listed as default device under recording tab, but no bars are lit up. Got there by using the mmsys.cpl in CMD window. Frustrating. Neal Aguillard

yes WSJTX is listed as allowed under security settings Neal

I just upgraded to a i7 processor with 12 GB of RAM and a SSD, running Windows 11. Windows did some strange things with Com Ports. Mike W9MDB, had to fix it, by remote log in. Buddy WB4OMG