Alan: I've never tried using different profiles for different rigs but I can't see why there would be a problem with my approach - if each profile creates a new folder in or under the default location

#install #Windows10

You can install the WSJT-X app wherever you want - I've put mine onto the E: drive which is a separate logical partition on the same physical disk as the C: drive - but by default the installer always

#install #Windows10

Which band(s) were you on, Ken? I decided to operate on only 15m and there were oodles of FT4 sigs on there (21080kHz) on both Sturday evening and for much of Sunday; out of my total of 337 QSOs on 15

#ContestMode

Hi Reino (and all), one factor that shouldn't be overlooked when deciding which time-sync'ing app to use on a PC is the effect of using an app such as D4 (and also NetTime?) that is based on the SNTP

#Timesync

Hi Mike, I'm running WSJT-X v2.5.4 on a 64-bit WIn 10 PC; the rig is an IC-7610 and the PC-to-rig connection for WSJT-X's CAT is CI-V using a USB-to-CI-V adaptor. I haven't tried Rig Split with the la

#hamlib

[Snipped[ Steve: In recent years I've got into the regular habit of renaming my ALL.TXT file, using a format of 'ALL-TXT for 2022-April.txt', at the end of each month so that a new file is automatical

#logging

Hi Robert, you're looking at the wrong file. If you want to delete your entire log then you need to find 'wsjtx_log.adi' and delete it (or delete whichever QSOs you want to get rid of); this is the fi

#logging #NewUser #macOS

Bill: Are you sure you're looking at the correct file, namely wsjtx_log.adi? There's another file - wsjtx.log - in the same directory but this isn't the ADIF file that gets read by the software; my un

#adiFiles

Glen: The advantage of using the 'split' mode with either 'Rig' or 'Fake It' selected is that the software ensures that the audio signal that's fed to the Tx is maintained within the 'sweet spot' rang

#WSJTX_config #windows11 #Windows10

Are you sure the left-hand Band Activity window pane is wide enough to display either the country name or the prefix? Have you tried moving the divider between the left-hand and right-hand panes sligh

#raspberryPi #WSJTX_config

Sam: Take a look at the 'SetSystemTimeAdjustment' function in Windows; you'll find it via: https://docs.microsoft.com/en-us/windows/win32/api/sysinfoapi/nf-sysinfoapi-setsystemtimeadjustment As you'll

#Timesync

It's also important to remember that the time step-changes made by a time syncing program that uses SNTP (eg. D4 and NetTime) rather than the full NTP protocol can and probably will cause discontinuit

#Timesync

Are you seeing any signals on the waterfall? If you are but you're not getting any decodes then check that your PC's clock is sufficiently close to 'real time'. The best way to ensure the clock is acc

#decode #windows11

Simply upgrading to the latest version won't correct the error in the wsjtx_log.adi file's header unless the file is deleted so that the software creates a new file with the correct header. If you wan

#adiFiles

https://wsjtx.groups.io/g/main/message/18574

#adiFiles

Hello Mark, what drivers do you feel are necessary for your set-up? The SignaLink-USB is solely an audio device and I would have expected that Windows 11 will already have the necessary drivers for a

#AudioIssues #Windows10

You can untick the 'Call 1st' option and that will leave the choice of which caller to answer entirely in the hands of you, the operator.

#EnhancementReqest #QSO_practices

Hi again Reino, thanks for the clarification. I took the information about using 'CATEGORY-MODE: FT4' from a Cabrillo log template that the RSGB has produced for its FT4 contest series and just assume

#logging

As Reino has said, the only modes that Cabrillo recognises in the record for each QSO are those listed in his posting above. However, in the first part of the Cabrillo file you can include the followi

#logging

Anyone using a time sync program that uses the SNTP protocol instead of the full NTP protocol, as used by the Meinberg NTP app, should bear the following comment made by the late, much-missed Bill G4W

#windows11