Log4OM

Isn't that an error on pg 215 of the docs???
It has 2233 instead of 2235

I'm going crazy setting up my buddy and just read that omnirig and the program MUST be run as admin.
Is there a 'shortcut' to bypass the 'authorization clicks?

It refuses to fill the callsign box when a call is selected by wsjtx. I'm assuming the change will fix it.

We both had problems with omnirig & Win4Icom (which recommends its use) and switched to using the rig (IC-7610)
Then today switching back works. Windows upgrade magic?

I wish more details on the magic omnirig program was available.

He has an ending program problem. His database has 40k Q's in it. I changed the 'log size' from 5000 down to 100 to see if that helps.
Checking for a TQSL delay is next.

We both have not responding errors, but just have to deal with them. Cutting down background helps may help.
Its a perfectly fast Win10 computer.

Suggestions appreciated

73, Bo W4GHV since '54

W4GHV wrote: 04 Jun 2022, 23:57 Isn't that an error on pg 215 of the docs???
It has 2233 instead of 2235

Will check

I'm going crazy setting up my buddy and just read that omnirig and the program MUST be run as admin.
Is there a 'shortcut' to bypass the 'authorization clicks?

Page 14 describes how to set programs to 'run as an administrator' once done you dont need to do it again

It refuses to fill the callsign box when a call is selected by wsjtx. I'm assuming the change will fix it.

Seems that you have not completely followed the instructions, please revisit and re try

He has an ending program problem. His database has 40k Q's in it. I changed the 'log size' from 5000 down to 100 to see if that helps.

Changing the value to 100 only effects the number of QSO's displayed in the grid it does not change functionality

Surely your not trying to upload 40K QSO's to LOTW when the program is closed, LOTW would not cope with that.

Try turning off the upload to LOTW on program closing and see if it closes OK, if it does your issue is the upload not the software.

Problems persist.
One went away NOT EXITING when we turned off LOTW update on exit. We will deal with that later.

Following is my setup guide, based upon the docs to the best of my knowledge.

The setup works perfectly for ME, but his is still disabled.

Callsign entry in WSJTX does not transform to the logger, nor does the 'log this qso' transfer to the log. Our setups, rigs, software are the SAME
Windows 10 PC, 16gb memory, fast CPU, latest Log4OM (admin mode), Omnirig (admin mode), Win4Icom latest version, WSJTX & JTalert latest versions, & IC-7610.
-------------------------------------------------------------------------
Win4Icom, IC-7610, Log4OM, WSJTX, JTAlert setup guide 6/6/22

Win4Icom
CI-V COM 6 115200
Virtual COMM ports 16,14,13,10,18,20 all 38400
Omnirig COMM 10
Auto Launch Omnirig, Log4OM

Omnirig
Set to run as admin
COMM 10, 38400,8,N,1,low, low,100,100

Log4OM
Set to run as admin
Config, connections
UDP_INBOUND ADIF_MESSAGE 2235
UDP_INBOUND JT_MESSAGE 1240
UDP_INBOUND N1MM_MESSAGE 12060
Note, the Outbound message (in the docs) is not set since it said V1

Applications UN-click Import

External services LOTW
My call 1st, 2nd, 4th clicked
Upload flag REQUESTED (also in Confirmations)

JTAlert
Logging - unclicked Last QSO, unclicked standard adif file
Log4OM Enable,Send, 127.0.0.1, 2235, 2241
Applications, WSJTX Resend WSJTX UDP packets, 127.0.0.1, 1240

WSJTX
Settings, reporting, Enable PSK reporting, 127.0.0.1, 2237, 3 clicks to the right
----------------------------------------------------------------------------------------------------
Comments greatly appreciated.
Bo W4GHV since '54

Please email me his support request from the help menu