If I log a QSO using FT4, only the first time I log a QSO is broadcast out the ADIF logging port. In order for each additional log entry to go out, I have to restart WSJT. There's no problem at all

Interestingly, I have not seen a thread specifically associated with this issue on the FLEX Radio Community site. Bob - N7RJN

I am anxiously awaiting a resolution as well. But I haven't seen anyone from Flex say that they are working on it. Noticeably quiet on the subject actually. Or maybe I am just looking in the wrong

Good questions but my computer is a relatively new (a year old) Dell XPS with 64MB Ram, i7 6 core processor running at a base speed of 3.7Ghz. It never shows much more than 10% utilization while

Are you perhaps using the the USB or data/pkt option in the WSJTX rig settings? Try None and see if that works. I am working in a fix for the flrig interface right now. De Mike W9MDB Sent from Yahoo

I upgraded to the new version of WSJTX last week and it's not longer working. I wondered if anyone else has run into the problems I'm having. I start up WSJTX via a script that starts

I am running WSJT-X v2.1.0 on a Mac computer with MacOS Mojave with 8GB of Ram. When I run FT4 and I am in a QSO sometimes I will miss the next cycle,(ie) I send a report

Bill, Many thanks for the follow-up. After reading Steve's analysis, I contemplated what OS operations might cause the SmartSDR DAX stream to become corrupted from time to time. I considered the

It’s not just him. It’s a lot of Flex users. I suspect it’s a Windows 10 update vs Flex software audio chain issue. Mine is fine in Windows 7, thankfully. I suspect there will be teething

Hi. I'm guessing, that you're intending to run all the Flex software, and WSJTx etc, on the same (now Win10) PC, right? If so, what is the typical CPU load when you're running the Flex

With help from Tim at Flex, I am now updated (W10 build 1903) and running more or less like normal. Windows decided to corrupt the names of the DAX devices and TIm straightened that out. So now I am

Hello all, I've been tinkering with the newest version and FT-4 and I have noticed something odd. While signals on JT65 are consistently solid, I am seeing a lot of fragmented signals on FT-4 at the

That did the trick Bill! No error & verified the download in the WSJT-X folder. Tnx es 73! Dave - KB3MOW

Hi Dave, see this message on the wsjtgroup Yahoo forum: https://groups.yahoo.com/neo/groups/wsjtgroup/conversations/messages/38467 73 Bill G4WJS.

I must be missing something about the installation of these two support apps. Installed both 32 and 64 bit OpenSSL v 1.02 Light and install was uneventful. Still getting the error message in WSJT-X

Hi All Windows 10 latest release Ft 450D signal link. Every thing works fine. I’ve experienced no problems Randy WI9D

This happens at all power levels, but as mentioned, the symptoms involve the radio going in to transmit but the tones generated by the computer end up going to a different sound port than the one

On 18/07/2019 16:54, Peter Dougherty wrote: Hi Peter, I know this seems a glib and unthought out response, but your issue could be due to RFI. The mechanism is that a USB

I am on WSJTX 2.1 and SmartSDR 2.4.9 on Win7. Seems fine here. So it’s either Win10 or SSDR 2.5.1/v3.x. Someone mentioned Windows 10 updates and a DAX issue. Not sure what the issue was there but

Hi all, Got a serious problem here with the 64 bit version of v2.1.0. After upgrading from version 2.0.1 everything appeared to be normal. I could send and receive (after correcting levels), DX Lab