Log4OM

You have wsjt set up incorrectly

In wsjt select Omnirig - NOT YOUR RADIO

in wsjt-x I chose well:
radio tab = OMNIRIG, party CAT control com6 and 4800 bauds , and PTT = CAT.
tnx
Berty

This is how WSJT should be set up, if it still does not work then you have failed to install Log4OM, Omnirig and WSJT to 'RUN AS AN ADMINISTRATOR' page 1 of our quick start guide

Ok I test this evening! Because on car control Ihave com6 !!!! I test with nothing
Tnx
See you this evening

hello!!!
don't working !!
see pictures

it's ok :
https://i62.servimg.com/u/f62/18/51/01/93/20180317.jpg

but after transmit:



the config






tnx

Hi Berty,

do me a favour and read the manuals. Check the Communicator settings for UDP Port to handle
JTAlert and check the Settings for FlDigi. All is working fine for me and i can run FLdigi and WSJT-X
and JTalertX and some more and all have complete CAT ... With 3 instances of differents Callsigns.

We don´t have a "Install and be Happy" Software. Each setup is different. But if you RTFM it would
be easier to got it to work ...

Last try to give a Tip ... JTAlert must be 2236. Log4OM Communicator must be 2236 .... WSJT-X and
or JTDX can be stay on the 223x as it has ... UDP must be enabled in WSJT-X/JTDX or no function is availible ...

For FlDigi XML-RCP must be enabled and FLdigi you must start first ...

Good night ...

DF5WW wrote: ↑06 Mar 2018, 18:14 Hi Berty,

do me a favour and read the manuals. Check the Communicator settings for UDP Port to handle
JTAlert and check the Settings for FlDigi. All is working fine for me and i can run FLdigi and WSJT-X
and JTalertX and some more and all have complete CAT ... With 3 instances of differents Callsigns.

We don´t have a "Install and be Happy" Software. Each setup is different. But if you RTFM it would
be easier to got it to work ...

Last try to give a Tip ... JTAlert must be 2236. Log4OM Communicator must be 2236 .... WSJT-X and
or JTDX can be stay on the 223x as it has ... UDP must be enabled in WSJT-X/JTDX or no function is availible ...

For FlDigi XML-RCP must be enabled and FLdigi you must start first ...

Good night ...

sorry but I don't understand verry good english ! and I don't undertstand when you tell: "Check the Communicator settings for UDP Port to handle JTAlert and check the Settings for FlDigi"... "UDP must be enabled in WSJT-X/JTDX"

sorry
for wsjt-x:

for communicator log4om:

Hi berty,

see another problem in your setup. If you like to log via JTalert from WSJT-X to Log4OM you have to
check the Box "Accept UDP Requests" in the WSJT-X settings. B.t.w in JTalert logging to Log4OM must
be enabled and there must be a route to your SQlite database ...

I don´t know you know it or not but we have an excellent french manual to download. Maybe we are
talking on different ways ... Try to download the french manual. Maybe that will be helpful.

ok yes route to your SQlite database =>this is ok!

for fldigi all is ok !!!

but not for wsjt-x

Hi Berty,

from time to time i have 3 different WSJT-X and/or JTDX instances running and alo 3 instances of JTalert.
Please check the Box "Allow UDP Requests" in WSJT-X/Settings/Reporting .... Enable logging to Log4OM
in JTalert Settings ...

What i see is that we have a problem with the languages ... I don´t understand french, my english isn´t perfect
and you don´t know german ...

Fact is that it works perfectly on my side. I can start Fldigi with XML-RPC, followed by Log4OM which has CAT
control to Omnirig and followed by different instances of WSJT-X/JTDX via JTalert. All instances of WSJT-X and
JTDX have CAT control via Omnirig and Log4OM changes the frequency if you change the bands in WS/JT ....

Your problem is simply a problem by the user and not by Log4OM.