As others have noted, /dev/ttyUSB0 is a serial port user for rig control via CAT, and has nothing to do with audio. You clearly have the correct audio device, since you get RX audio, so that should al

#txaudio #AudioIssues #TechnicalHelpQuestion #linux

That's tramsmit audio - I believe he was talking about receive . . .

#AudioIssues

Sorry, read it as radio's MIC jack . . . Gotta look more closely! :-) :-) - Tim

#AudioIssues

What happens if you select a different sound card? Can you get it to zero in any way, shape, or form?

#AudioIssues

NTP initiates from the inside, going out. Typically firewalls only restrict inbound traffic . . .

#Timesync

Which still won't prevent syncing! I do that as well, but the port 123 traffic is *OUTBOUND*, which (if properly implemented) will only affect inbound connections to your ntp server originated externa

#Timesync

This must vary based on rig. On my FT1000MP, MK-V, when Wsjtx comes up and initiates CAT in split, it sets VFO A for RX, VFO B for TX, and activates split. Freq is set when the station is selected or

#frequency #TechnicalHelpQuestion

I have an FT-847 as well, and have no recollection of ever seeing that specific setting. A I recall, the -847 decides which jnput to use based on which mode you are in, and if in "Data" mode, it will

#AudioIssues #txaudio

Yes, but using CAT PTT for timing (but that is irrelevant here). Don't clip the initial tones that way, as would be the case with the Signallink VOX PTT . . . Other than that, thanks for confirming wh

#AudioIssues #txaudio

Not being certain on detailed internals of wsjtx (yet), this may be off the mark, but the timing of this seems almost like a DNS or network timeoout. Do you have any external sites, psklocator, etc. c

#linux

What are the permissions (ls -lia /dev/ttyUSB0) specifically, and is that device available by any other name? Second, might there be a getty runming on that port, and lastly, is the lock directory pre

#WSJTX_config #linux

I can't imagine why a process usig ttyUSB1 would affect ttyUSB0, but can't argue with success . . .

#WSJTX_config #linux

Ah, yes! If you have a device in place and open, simply unplugging does not drop the process holding it open, and it steps the device, as you noted. (I had thought that both your devices had been plug

#WSJTX_config #linux

I assume that is has been verified on tigertronics.com that you have the correct internal jumpers in place in the Signallink for that radio and cable? - Tim

#Icom

Perhaps this is my doing something incorrectly, but I have been unable to get calibration to work on my WSJTX 2.5.4 deployment. This is a source build on Linux with a Yaesu FT1000MPV-Field behind it,

#Yaesu

I think you missed my point . . . when I set "F Tol" to 1 I calibrated withing .4 Hz . . . the issue isk't that the TCXO was off, it is that F Tol skews the values seen in fmt.all . . . . Changing not

#Yaesu

(Added missing #Calibration tag)

#Yaesu

I get data in fmt.all no matter what F Too is. The issue is that the reported error in for.all is .4 Hz with F Too set to 1, but simply changing F Tol to 50 causes the exact same data points to show e

#Yaesu

I'm out at the moment, but will pull together an example of this a bit later.

#Yaesu

It's the contents of fmt.all that changes, not the output of the calculation (andso far that thecalc fails)

#Yaesu