When you say "TX still failed" what does that mean?  No power out?  Or power out but nobody answering you? I show you being spotted 18 hours ago so you apparently got TX working for a while. Mike

Tim, I haven't set the radio in split mode.  For a test I tried setting it to split and made sure both VFO's were set to the same frequency.  WSJT-X still decoded and in fact would decode even as I

Willie, N1JBJ To my knowledge Linux Mint does not inject any eq, echo, etc in the standard install and I haven't installed anything like that.  I was dead wrong when I said the software volume

What I meant was that a lot of companies only provide Whinderp drivers, leaving Linux users out in the cold. (I have no idea what Yaesu did, since I don't own a radio with native USB . . .) Signallink

Never said it was wrong, Tim.  Just not the optimal solution.  And, not sure what you meant by the Linux comment....I'm using Uubntu, Mint, Raspian, and Windoze.  All of these work well with the

But then again, if it works, it's not wrong . . . and not every mfg. supports advanced platforms like Linux . . . -- Sent from my Android device with K-9 Mail. Please excuse my brevity.

For what it's worth, I agree. Using a SignaLink to use an FT991A is like driving a Tesla a la Fred Flintstone. If you're having issues sorting out multiple sound cards, suggest Pulse Audio Volume

Unless I am mixing messages in my head, the Hamlib error looked like you were using split? If so, is the *second* VFO also set for USB? If not, you may be transmitting LSB, or ??? which will not be

If you add the "ntpdate . . ." commands I posted to the start and restart batch files (in c:\Prog..x86..\NTP\bin\...) then it will instantly set at boot, and you won't need to do anything. I'm not at

Mike I think at this point you need to verify that you are actually transmitting an FT8 signal. You have a nearby buddy that can get on and verify your signal? Or a second radio that will tune to

From Section 12.1 "AP decoding" of the rc1 local help file.... "Type|a7|, used only in FT8 mode, uses information from the previous Rx sequence." AL, K0VM

Hmm, lots of info here, not sure how much I can help, but a few observations: Sounds like it, so (and if your ALC is set as below, it sounds like you are doing the right thing there. Unless your

Tim, I appreciate what you just wrote. Not at all sure what all the details are all about, since I'm a newbie and all, but hv a general understanding. And so, if you are suggesting a modification

Not sure why this is being so difficult. https://physics.princeton.edu/pulsar/k1jt/wsjtx-doc/wsjtx-main-2.6.0-rc1.html#_ap_decoding

with the 'web' page open, use CTRL-F to open up a search box (works for me on Chrome) WDG

New 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 -- hopefully your browser doesn't block it but

Click on Help, then click on Local User Guide and search for a7. 73 Stan KM4HQE

I noted that A7 is not in Table 1.  This might have been a recent addition to FT4/FT8. It's in Table 2. A7 indicates that all 3 tokens here were hypothesized and the resulting decode had high

Yes, I carefully set the mic adjustment to show the flickering 5th bar. I had a look at wsjtx_syslog.log and set the following errors which appear to be logged once a minute. [RIGCTRL][2022-06-18

Can you be a little more specific as my users guide has not search function and I have looked every place I can think of and can not find it tnx AH0U