Log4OM

I have followed the instructions in the user manual for Log40M version 2

WSJT-X V 2.2.2 and Log40mV2 2.11.0.0 both using Omnirig
WSJTX; Omnirig 1 (in my case)
Data/Packet, Fake It, Rear

JT-Alert;
UDP Connections 127.0.0.1
ADIF Message Port 2235
Cnntrol Port 2241
Resend WSJT-X UDP Packets
IP Address 127.0.0.1
UDP Port 1240

Log40MV2; Run as Administrator
UDP_INBOUND ADIF_MESSAGE 2235 JT Alert QSO
UDP_INBOUND JT_MESSAGE 1240 JT ALERT REBROADCAST

Omnirig allows for CAT Control for the software(s)
I am using JT-Alert 2.16.15.
Yes, I am aware that there is an upgrade version.

When I click on a callsign in FT8 mode, the radio changes from USB to FSR (Never saw this before).
The FT8 waterfall then shows no signal.

Radio transmits, but FT8 nothing shows in waerfall or in JT-Alert.
Also, does not log to Log40M V2
Radio is not using Data Mode.

Any ideas?

search this forum I beleive there is an issue with the Omnirig ini for your radio, another user contacted omnirig and they provided a replacement ini if I recall

Nothing wrong with ini file of the 590sg, using it al the time

In WSJT-x do not choose Data/Packet, choose USB
On your transceiver activate the DATA function when in USB mode

Hi Marcel,

it could be only a problem with WSJT-X and/or with Omnirig and it´s .ini file. Log4OM does not
switch anything. It only uses those softwares as 3rd party implementations. If the CAT commands
set your transceiver to digital instead of USB there must be something wrong at the Omnirig side.

My transceiver (ALT-512) is using the TS-2000 protocol for CAT and i don´t have this problem that
CAT changes my TRX to a different USB instead of Digi and/or vice versa.

It never bothered me, but i looked into the TS590SG.ini located in C:\Program Files (x86)\Afreet\OmniRig\rigs

Made the changes marked in BOLD in the set mode part:

;-------------------------------------------------------------------------------
; set mode
;-------------------------------------------------------------------------------
[pmCW_U]
Command=(MD3;)
ReplyLength=0

[pmCW_L]
Command=(MD7;)
ReplyLength=0

[pmSSB_U]
Command=(MD2;DA0;)
ReplyLength=0

[pmSSB_L]
Command=(MD1;DA0;)
ReplyLength=0

[pmDIG_U]
Command=(MD2;DA1;)
ReplyLength=0

[pmDIG_L]
Command=(MD1;DA1;)
ReplyLength=0

[pmAM]
Command=(MD5;)
ReplyLength=0

[pmFM]
Command=(MD4;)
ReplyLength=0

;-------------------------------------------------------------------------------

Now you can use Data/Pkt in WSJT-X and the 590SG will switch to USB-DATA mode, and switches DATA back off when USB/LSB is selected

Thanks to all who replied.

I figured out tha FSR on the radio display is actually FSK.

The radio is using FSK mode.
To me, should not be happening

I really do not care if Log4om is in sync with the radio as I am using it as a log only for FT8.
I used to have radio set to TS590SG not Omnirig.
JT-Alert sent logging to Log40M V2 and everything worked fine.

When I get out of FT8, Log40mV2 synced with Radio

Will see if I can do it that way.

Again,

Thanks for the info.

Just make the changes as described above in TS590SG.ini and Omnirig will no longer select FSK for digitalmode but it switches the 590S(G) to USB-DATA mode.

If you don't thrust yourself make a copy of the file before you edit it.

PE5TT,

It works!
Set WSJT-X Radio to Omnirig Kenwood TS 590.ini filed that I modified.
Yes, I made a copy so I always have original to go by.
Log40M to Omnirig.

That is, FT8 and Log40M V2 both show radio frequency, and logs to Log40M.

JT Alert however shows
Logging Warning
ERROR Message : LOG40M V2 SQLite: Unable to confirm QSO Logged
NOTE: The QSO is still saved to the WSJT-X Log File.

Need to get this fixed

You have to follow the Log4OM manual exactly and it works (page 158 and on)

From your post i don't see you have

In log4om in Connections:
enabled remote control port 2241

In WSJT-x in Reporting:
UDP Server 127.0.0.1
UDP port 2333
enable Accept UDP requests
enable notify on accepted UDP requests
enable Accepted UDP request restores window

In JTAlert in Logging -> Log4OM v2
Did you point JTAlert to the location of your Log4OM database
Did you test database connection with the TEST button

PE5TT

Thank you for all your help.

You were correct in that it was not referencing the database file.

That solved the issue.

Thanks to all who posted on this thread.

Live is good again.