Log4OM

Log4OM is now refusing to recognize the DB SQLite when working with JT Alert. It was working just fine and now it's gone all wonky.
Any ideas why?

K7QH wrote: 30 Jul 2021, 19:45 Log4OM is now refusing to recognize the DB SQLite when working with JT Alert. It was working just fine and now it's gone all wonky.
Any ideas why?

Dana,

Need more information ...

What version of Log4OM V2 are you using? It is noted at top left title bar on the Main UI or by tapping: Help / About

Have you tried to simply run Log4OM V2 by itself without any other APPs connected to it? If so it should be finding your SQLite database. If the stand-a-lone operation of Log4OM V2 can't find the SQLite d/b then you have to start there first.

What APPs are you using as part of your FTxx operation? WSJTx or JTDX and you have noted JTAlert.

Have you configured your FTxx operation per the steps we have outlined in our current User Guide starting on Page 201?

Any Microsoft O/S updates in recent days?

During your initial Log4OM V2 installation did you let the installation choose the default directory/file paths or did you pick/choose them?

Just need to peel the onion one layer at a time to get to the hiccup and then resolve.

Nolan,
I finally got the database issue solved; but the program won't connect to radio. Using V2.16.0 rig is IC-7410 to a log periodic. Computer interface is laptop running Windows 10. I have tried nothing and Omnirig for CAT control without success.
Dana

Hi Dana,

did you run other software (WSJT-x or JTDX) with Omirig ? If yes all programs must be run as
administrator to use the multithreading of Omnirig. Are you using original Icom drivers for
USB connection (if it is connected via USB), the baud rate for the virtual COM the same as
in the radio menu ?