Lo4OM and JT65-HF

[VK3AWG]

Hi guys and girls. I am new to the forum (first post). I am hoping someone maybe able to help me with a software issue. I run Log4OM, OmniRig, JT65-HF and JTAlert. Now when I hit the Log QSO button in JT65-HF it logs the contact fine but within a few seconds the Comm Services button at the bottom of Log4OM goes red. I then have to click on the arrow and reconnect TCP- IP and also re-start communicator. This is a bit of a pain. Hopefully there is a simple answer.

Thanks
Chris
VK3AWG

[G4POP]

Chris,
Follow the instructions here for generating a support request and send it by email to either Daniele or me

http://www.log4om.com/log4om-support/

[VK7XX]

Hi guys and girls. I am new to the forum (first post). I am hoping someone maybe able to help me with a software issue. I run Log4OM, OmniRig, JT65-HF and JTAlert. Now when I hit the Log QSO button in JT65-HF it logs the contact fine but within a few seconds the Comm Services button at the bottom of Log4OM goes red. I then have to click on the arrow and reconnect TCP- IP and also re-start communicator. This is a bit of a pain. Hopefully there is a simple answer.

Thanks
Chris
VK3AWG

Chris, nothing to do with your current problem, however, as you are probably aware, JT65-HF is quite dated now with no updates for a very long time. Currently there are several other pieces of software available that have been updated and have far more sensitive decoders than JT65-HF. Admittedly, they don't have as pretty an user interface, but they don't take long to get used to. Perhaps you might like to try WSJT-X. The release version has both JT65 and JT9 ability or, you could try one of the almost daily beta versions which has even more modes. Both release and beta's available from here >>> http://jt65-dx.com/download/wsjt-x.html

73
John

PS, JTAlert also works with WSJT-X

[VK3AWG]

Thank you Terry for the fix. Works fine now.

[G4POP]

Thank you Terry for the fix. Works fine now.

For everyone's benefit the problem was caused by the path in the communicator 'ADIF file polling' field which had been pointed to the SQLite database not to an ADIF file