Log4OM

Good morning
this weekend I'm traveling to a radio amateur friend to install Log4om latest version, we installed the Beta version 2.27.1.2
The use is simple JTDX direct to Log4OM
We followed the usual guidelines, deletion of old connections, reboot, creation of a new ADIF MESSAGE connection (port 2237 here), backup and PC reboot. if we validate a QSO from JTDX it is well logged in Log4OM
BUT
the call is not transmitted in Log4OM, that is to say that when the in clicks on a call in JTDX normally the call is transmitted in Log4OM and we can for example see if we have already made QSO or not (with the window worked before) but there the call is not transmitted
In the documentation it is shown that it is necessary to validate in second UDP the port 2333 (for example) what I did but that does not change anything

If you could guide us
Thank you for your help I have to leave tomorrow and I would like to solve this Pb you can even take control of this PC if necessary
Thanks and 73

Dan,
Start again and use the WSJT/JTDX UDP connection not the ADIF one


This worked fine on my test set up although I dont use those modes myself

thank you Terry I did exactly as you showed me on your screenshots with the same port numbers and it works fine now
really, thank you..
73

Good morning
Terry can you guide me to do exactly the same thing but incorporating JTAlert between JTdx and Log4Om
THANKS

Dan there is a preset at the bottom for JTDX. Use that and make sure the port matches whatever your JTDX program is using. You will have to do that on your own because Terry would have to assume those things.

The programs need to be talking on the same port. Its a simple setup and outlined in the User manual.

Good morning
if it were as simple as that we wouldn't bother you with all that and so I would like, as Terry did, that you tell us exactly what to do as a connection in Log4OM for a use of JTdx- JTAlert-Log4OM
THANKS

Please read the manual.

We dont know what port you are using for your 3rd party program. You will have to figure that out yourself and make sure when you use the preset in Log4om that that port matches.

Its never been easier than with the new updates.

Dan and Others ...

Look starting on Page 221 of the Current User Guide dated: 23/03/2023 9:15 PM. It is all laid out very clearly there.

Again ... as Rich noted ... y'all have to ID your own ports being used in the various APPs.

Thanks a lot it is sure that it will help us enormously

F6FLU wrote: 08 Apr 2023, 18:06 Thanks a lot it is sure that it will help us enormously

Dan,
It really is detailed as Nolan suggested in the user guide so it has to be a missmatch of ports

Perhaps you can post screen shots of the following, as I said before I dont use these modes and it would require me to install all of the software again and do a fresh set up

1. Log4OM UDP outbound connections window
2. JTDX reporting window
3. JTALert/logging/Log4OM V2 window
4. JTALert/Applications/WSJT-JTDX window

We should then be able to spot your issue