Barry, not sure of the point of your comments if you don't use WSJT-X, but unchecking "Settings->General->Disable Tx after sending 73" would meet your requirement. 73 Bill G4WJS.

Kevin, WSJT-X is not a replacement for the operator, it has aids that help with the quick turnaround of QSOs where there is very little thinking time between decoding a signal and transmitting your re

Hi Roger, both applications are expecting to talk to a serial device, not another application, the only way you can connect them back-to-back is to loop pair of serial devices. Com0Com emulates a pair

Hi Carl, it's not that simple. The technology used to implement DX Lab Suite does not support multicast IP, nor is it possible to patch it up by calling the necessary lower level Windows functionality

Hi Paul, the contents of a DX Cluster spot do not include any mode field, either the notes must contain an unambiguous reference to the mode, or in the case of SpotCollector you must have a sub-bands

Hi Dave and David, when logging a QSO in WSJT-X the date and times of the start and end of the QSO are presented to the user to check and can be modified before committing the QSO details to the log.

Hi Ed, the buttons and other widgets in that panel are dependent on the QSL mode selected at the top of the window.

Hi Mark, a standard ADIF export from DXKeeper is fine. WSJT-X expects the CALL, MODE, SUBMODE, GRIDSQUARE, and BAND fields in each QSO ADIF record. CALL is the only required field, SUBMODE is only use

Steve, if you had that setting unchecked JTAlert would have been truncating the seconds from logged QSO start and end times. That's fine but when you import a WSJT-X ADIF log with seconds included in

Paul, I believe the message you mention says JTAlert could not confirm the QSO was logged, the QSO may have been logged but not in tome for when JTAlert checked for it. You first need to conform if th

Hi Steve, sri, inline attachment was too large. It's "Settings->Manage Settings->Logging->Logging Options->Log seconds in time_on and time_off values.

Hi Steve, you probably have the JTAlert option to not log seconds checked. Assuming you imported with the Select field set to 'Y' and cleared all Select fields before import; you can delete all the im

Hi Dave, yes, I use "Config->Rotator Control->Model->Prosistel" with 9600 baud 8N1 serial port. 73 Bill G4WJS.

Hi Dave, I can't help you with those rotators but if you ever consider adding queries to the Pro.sis.tel models I can test with a model D controller. Let me know if you wish to consider this, I can he

Hi Andy, that depends on what you define as acceptable. If you have complex sequencing requirements and want to avoid any hot switching of relays then the timings of those circuits has to be included.

Hi Dave, it will if the Tx frequency needs to change. If an op double-clicks a decode without "Hold Tx Frequency" checked and the Rx offset of the message being clicked is in a different 500 Hz segmen

Hi Dave, because the user may have inadvertently changed the mode. I could reply with why is Commander not ignoring a mode set command if it thinks it knows the mode is already set that way on the rig

Hi Andy, note that 580 ms is too slow for FT4 mode.

Hi Andy, please try the WSJT-X option "Settings->Radio->Mode->None". You will then have to set USB-DATA mode manually on your rig, but there may be enough reduction in the delay to make it worthwhile.