So what would stop someone from determining the key, trivially adding it to the source, and recompiling? It's not like compiling WSJTX is even minimally difficult . . .

#EnhancementReqest

Yeah, I reealize that . . . It just seems that with a request to test, an appropriate source tarball ought to be dropped as well, since that will run on anything, as opposed to the limited scope of th

#hamlib

For those of us who never use prebuilt packages, is there a link to source for this? Or is the *4.6*git.tar.gz close? Thanks, - Tim

#hamlib

FWiW, the Signallink makes no difference, sinceit handles audio only. Rig control setup will be the same with or without it.

#Icom #WSJTX_config

Allow me to correct that . . . *WINDOWS* audio is ridiculously complicated and fragile. More advanced platforms have no such issues . . . - Tim

#AudioIssues

. . . . via the VOX capability in the SignalLink . . . (IE, it requires an adequate audio level to key . . . )

#NewUser

Signalink is an audio interface, so as long as you have a suitable cable, it should be impossible for it to *NOT* work. Check Tigertronics to verify your hookup . . .

#NewUser

Signalink for audio, and WSJT-X with Hamlib (native) for rig control (freq, etc. as well as PTT for most, if desired). The SignaLink is a nice unit, but it is audio only . . . If you are running PTT v

#Kenwood

Find and remove the lock file! (It is, as you have found, *NOT* part of the installation).

#stopped_working

You might try running ldd against the binary giving the error . . . if there are missing libraries, it should tell you (although I would not expect your build to have completed linking if anything was

#hamlib

You might consider posting the issues here . . . Hamlib gets a lotmof attention here as well.

#hamlib

That indicates that the audio device is fine (and I assume by "band activity" you mean the waterfall? It also runs soley from rx audio). Freq, key, band select, etc. are all done via the CAT device, i

#hamlib

Hamlib is used for frequency control and keying . . . it has no involvement in the audio path. So, I am a bit unclear on your specific problem (and it seems like there may be more than one).

#hamlib

So make sure that that path exists, and that you can write/mkdir in it . . .

#linux

Never used it anyhow, myself . . . if I need to step, I use ntpdate (part of the ntpd package) to step before ntpd starts . . . . (More than one way to skin that cat). For that matter, if ntpd is work

#AudioIssues

GPS or WWV/WWVB receiver . . . . both work well . . . (Just GPS generally does not work well indoors . . .)

#AudioIssues

With full ntp, the drift correction factor calculated for you clock will allow it to stay in sync far, far, longer that it could umcorrected. For long term issues, eithe GPS or a WWV/WWVB based time s

#AudioIssues

There is a *LOT* wrong with sntp! It is a crude bastardization of ntp, which is incapable of smoothly managing a clock (which is why those using it likely have problems! Real ntp rarely (if ever) does

#AudioIssues

One other thing to note (and the original message has been lost) was someone had mentioned an ntp client taking CPU resources away from WSJTX . . . . Not sure where the idea came from that time servic

#AudioIssues

If you are referring to configuring multiple/additional servers in ntpd (or the Meinberg package thereof) it is simply a matter of adding more server lines in the config file - ntp.conf. Yank, paste,

#AudioIssues