I'm looking to work with some ft8 messages using command line programs and was able to find both ft8code and jt9 in my /usr/bin. I cannot find ft8sim, however.

In this mailing list message, Steve Franke says that "the ft8sim executable should be found in your build directory, assuming that you are building the development versions yourself."

I've attempted to build from source a couple of times and have gotten errors both times on different machines. I will attempt again, but in the mean time, thought I would try here.

Is anyone that has built from source willing to share the ft8sim executable file for Linux? Assuming that is a complete program and doesn't need to be built and access other installed programs on the same machine.

Thanks in advance for any help or replies.

I recently reinstalled wsjtx after a few years away from the radio and thought I'd try setting up a 22m beacon. I'm getting OOB and it's not allowing me to transmit on 13.5539. Is there a way to get around this? I did add the freq in the freq list, is there anything else I need to do?

I had the standard messages and was making contacts, now I guess I've done something, and pressing the "generate standard messages" button does nothing and they are all blank except the last one. What am I missing?

https://preview.redd.it/lo0v5wh0hqrd1.jpg?width=1388&format=pjpg&auto=webp&s=e8f8b1f768d34c850e3d13f213029df6117ed8fa

WSI Alarms have the options to send notifications via Email, Text to speech, and lightpole. Does anyone know what the lightpole is and how to configure it. My experience with lightpole is in the labs where I worked. There was a series of colored light on the ceiling with 5 different colors that would indicate the state of the lab.

I have used wsjt-x for a while on 10m. I just got my general ticket and want to hop in the 20m playground, but for the life of me, I cannot figure out how to add /ag or <ag> to my callsign.

I tried under settings and it just kills the app if I respond to a qso. I do not see it under suffixes in the help file and the manual only states that you can to it, but not how to do it.

Is this even possible?

003130 -2 0.1 711 ~ KA8MMI RR73; KC1NXT <KD5USA> -12

What is the above line supposed to mean ? (I'm KC1NXT) This was followed 70 seconds later by the more typical

003130 -2 0.1 711 ~ KA8MMI RR73; KC1NXT <KD5USA> -12

Alas, the exchange wasn't completed.

WSJT-X v2.6.1 using an x6100

Still setting up new laptop, previously l had set up CQ as green, if l had logged them already it was red. I have everything set up the same but it doesn’t work right. Everything is one color.

Setting up new computer, comparing with previous laptop. Things are working good so far but l cannot seem to figure out how to get a WSJTX contact out in my HRD logbook like l could before. It has to be one little thing.

Setting up new laptop. My old relic used a SignaLink and works great. I hear l might be able to not use a SignaLink with my new laptop. How would l find this out and if you know the settings that would be helpful. If not l will continue on with the SignaLink.

Thank you

I've had this problem off and on for a year. Updates mess things up... Win11 doesn't provide the audio needed to generate power out of my FT-991... are there some applicable settings in Win11? The rig settings are fine, CAT works, cannot get power out. Fixed it once before by defaulting the mic, that is defaulted currently and still no power out.

Has anyone gotten Hamclock to work with WSJTX?

I'm trying to setup my Kenwood TS-450S with Digirig mobile and WSJT-X. I've got the digirig installed and I can monitor the band. All good. However, I noticed that my monitor bar was red and measuring like 88-89dB! I went into my audio settings in Windows 11 to try and turn down the mic level for the digirig. It was already set to 1 so I can't go any lower. However, I did turn off AGC in Windows Audio Properties and this dropped it down to about 74-78dB, just teetering on the edge of red/green.

Is there anything else I can do? Any idea if I can control the volume of the output of the radio?

Has anybody used a IC-9100 rig on weak signal modes?

Can anyone help on how to increase the decoded signal font size of WSJT-x for Mac, it's not on any of the dropdown menu.

Don't forget to add yourself to the dialout group. Also, could only get the Flathub to load.

Has anyone resolved the pskreporter tls initialisation failure issue?

Thanks

I posted this over on r/amateurradio then realized it might be more appropriate here. Sorry for the double posting.

There's an option under "View" for "PSKReporter". I was thinking that this might display some information about current band conditions based on the information available on pskreporter.info. However, when I open that window, I receive the message "TLS Initialization Failed".

Searching for this issue, there are several pages talking about installing OpenSSL, and occasionally the MS Visual C 2013 runtime. I have all of that installed.

There a number of pages reporting a similar error, and some references to read the OpenSSL section in the WSJT-X 2.5.4 documentation, but there are no references in the documentation I see for View PSKReporter. There is documentation for sending reports to PSKReporter.info, and that's working fine for me.

My question is: do you know what this window is for? Does it work for you? Did you do anything special to make it work?

​

Im working on getting my G90 with a DigiRig to work. I cant get FLRig to work so I am using WSJT-X direct with G90 selected. I keep getting the following error.

Hamlib error: rig_set_cache_freq(122): vfo=VFOA, current_vfo=VFOA

rig_get_freq(2116): freqMainA=14074000, modeMainA=USB, widthMainA=2400

rig_get_freq(2116): freqMainB=14166000, modeMainB=, widthMainB=0

rig_get_freq(2179): freqMainA=14074000, modeMainA=USB, widthMainA=2400

rig_get_freq(2179): freqMainB=14166000, modeMainB=, widthMainB=0

rig_set_cache_freq(122): vfo=VFOA, current_vfo=VFOA

rig_get_freq(2186): freqMainA=14074000, modeMainA=USB, widthMainA=2400

rig_get_freq(2186): freqMainB=14166000, modeMainB=, widthMainB=0

8:rig_get_freq: elapsed=34ms

icom_band_changing: lastfreq=0, thisfreq=0

icom_band_changing: Band change not detected

icom.c(1264):icom_band_changing returning2(0)

Protocol error

icom.c(1431):icom_set_freq returning2(-8) Protocol error

8:rig.c(1814):rig_set_freq returning(-8) Protocol error

Protocol error

Protocol error

while setting frequency

Timestamp: 2023-06-20T23:23:54.110Z

Dear WSJT-X Users,

We are pleased to announce that Release Candidate WSJT-X 2.7.0-rc1 is ready for download by beta testers.

WSJT-X 2.7.0 Release Candidate 1 introduces a new program called "QMAP", a new Special Operating Activity known as "Q65 Pileup", and a number of other program enhancements and bug fixes. A full list of enhancements can be found in the Release Notes:

https://wsjt.sourceforge.io/wsjtx-doc/Release_Notes_2.7.0-rc1.txt

Release Candidates are intended for Beta testers. If you download and use WSJT-X 2.7.0-rc1, please remember to provide feedback to us on its new features -- and on anything that does not seem to work properly.

Direct links to installation packages for Windows, Linux, and macOS can be found on the WSJT-X page https://wsjt.sourceforge.io/wsjtx.html Scroll down to the heading "Candidate release: WSJT-X 2.7.0-rc1".

For those who like to compile from source, a complete source-code tarball is available at the WSJT-X page. Public access to the git repository for the WSJT project is also available on the "Git" tab here:

https://sourceforge.net/projects/wsjt/ It may take a short time for the code to be updated on SourceForge.

​

WSJT-X is licensed under the terms of Version 3 of the GNU General Public License (GPL). Development of this software is a cooperative project to which many amateur radio operators have contributed. If you use our code, please have the courtesy to let us know about it. If you find bugs or make improvements to the code, please report them to us in a timely fashion.

The authors and Copyright holders of WSJT-X request that derivative works should not publish programs based on features in WSJT-X before those features are made available in a General Availability (GA) release of WSJT-X. We will cease making public Release Candidate (RC) pre-releases for testing and user early access purposes if this request is ignored.

Feedback should be sent to this email list or one of the of the others mentioned here in the User Guide:

https://wsjt.sourceforge.io/wsjtx-doc/wsjtx-main-2.7.0-rc1.html#SUPPORT

We hope you will enjoy using WSJT-X 2.7.0-rc1, and that you help us to create a GA release of this version very soon.

-- 73 from Joe, K1JT; Steve, K9AN; Nico, IV3NWV; Uwe, DG3YCB;

Brian, N9ADG; and John, G4KLA

While watching a WWII documentary on Amazon Prime, "As it Happened - Tarawa". I glanced over at the WSJT-X window and noticed T30UN calling CQ. Gridtracker had him in Kiribati. Thinking to myself it was yet another Caribbean Island on 12 meters, I reached over and casually worked him. Logged the QSO. Went over to QRZ to check on the entry and about hit the floor. It was North Tarawa Island. It's also a rare DX entity. I love 12 meters for DX.

Dear WSJT-X Users,

The overwhelming success of the temporary WSJT-XY forum has brought us close to the limit of 100 users within one day. The good news is that a permanent solution has now been found: wsjtgroup@groups.io. This forum has no limit on the number of members. I think this is an opportunity we should not miss! Thanks to everyone who made this possible!

Unfortunately, this means that we have to move one more time. I am very sorry about that, but I think you will understand the reason. Once everyone has moved, I plan to close our temporary WSJT-XY forum.

Note: For technical reasons, groups.io requires messages from new members to be approved once. After that, posts are possible without further hurdles.

73 de Uwe, DG2YCB

Dear WSJT-X Users,

Unfortunately, complaints about the WSJTX.group.io forum have been piling up lately. Therefore, the following should be clarified at this point:

1. WSJTX.group.io is a private forum and is NOT operated by the Core WSJT Development Group!

2. It is NOT our intention to ban users on WSJTX.group.io anywhere else just because they use certain keywords in a technical-scientific discussion, which the owner of WSJTX.group.io obviously does not like.

3. We point out that only the wsjt-devel mailing list is our official communication channel. Please use this list if you want to report bugs or discuss with us developers.

4. With immediate effect, I have therefore disabled the mention of the WSJTX.group.io forum on the official WSJT-X homepage.

73 de Uwe, DG2YCB
Core WSJT Development Group

P.S.: As a temporary solution, I just created a new private forum (WSJTXY.groups.io), where you can discuss technical issues and help each other with problems. I hope that one day the moderator of WSJTX.group.io will realize that his behavior was not good, will change it accordingly and that we as WSJT core development group will be able to recommend the WSJTX.group.io forum again. At present, unfortunately, this is no longer the case!

Hi All,

So far, I've been an ssb only operator since getting licensed a few years ago. I've been interested in digital modes in a general sort of way all along, but am finally getting my ducks in a row to get on with it.

New g90, digirig and usb gps dongle are all en route and should get here early next week.

I have two weeks off work coming up to recuperate from a surgery, so I figure that's plenty of time to figure out wspr, winlink email and ft8, all via my microcenter evolve iii pc.

I would imagine that I'll post here if I get really stumped, but hopefully the next time I post is to relate tales of adventure and success in getting on digital modes for the first time.

Thanks and 73!

Below is the link to the community web server. If you have files that you would like to post, please feel free to contact the moderators to make arrangements.

http://kb6ibb-15.ham-radio-op.net/Ham-Radio/

Welcome to the WSJT-X community. Post away!