thank you Terry
I will make a detailed report when I return home next week.
UDP connection problem
Re: UDP connection problem
Dan - F6FLU
Log4OM V2.35.1.0 - Windows 11 - i9-11900K - SSD 512Go - 32 Go
FTdx101D - Hexbeam - Wire dipole 40-30M
https://F6FLU.org
Log4OM V2.35.1.0 - Windows 11 - i9-11900K - SSD 512Go - 32 Go
FTdx101D - Hexbeam - Wire dipole 40-30M
https://F6FLU.org
Re: UDP connection problem
Hello Terry
Here I am back at the QRA
Some precisions :
1) My requests are to help radio amateurs who have problems
2) as far as I'm concerned it works very well for me
3) as it works at home, I try to do the same at my friends
4) it does not work for example with my friend F8NHF
5) the only thing I see is that I'm using a Broadcast address for JTDX instead of using the Localhost, but since it works fine I concluded that can't be the problem
here are the screenshots requested, I will make 2 posts to show all the screenshots:
Here I am back at the QRA
Some precisions :
1) My requests are to help radio amateurs who have problems
2) as far as I'm concerned it works very well for me
3) as it works at home, I try to do the same at my friends
4) it does not work for example with my friend F8NHF
5) the only thing I see is that I'm using a Broadcast address for JTDX instead of using the Localhost, but since it works fine I concluded that can't be the problem
here are the screenshots requested, I will make 2 posts to show all the screenshots:
Dan - F6FLU
Log4OM V2.35.1.0 - Windows 11 - i9-11900K - SSD 512Go - 32 Go
FTdx101D - Hexbeam - Wire dipole 40-30M
https://F6FLU.org
Log4OM V2.35.1.0 - Windows 11 - i9-11900K - SSD 512Go - 32 Go
FTdx101D - Hexbeam - Wire dipole 40-30M
https://F6FLU.org
Re: UDP connection problem
following screenshots :
In JTAlert we have a setting of Resend WSJT-X UDP packets (received only) (In Settings/Applications/WSJT-X/JTDX) with 127.0.0.1 and UDP port: 1240
And
in Log4OM there is no connection with this port 1240?
Would that mean that port 1240 is useless?
Thank you very much Terry if you can look at all this and guide me, it will help a lot of friends
The other question I get asked that I don't know how to answer is:In JTAlert we have a setting of Resend WSJT-X UDP packets (received only) (In Settings/Applications/WSJT-X/JTDX) with 127.0.0.1 and UDP port: 1240
And
in Log4OM there is no connection with this port 1240?
Would that mean that port 1240 is useless?
Thank you very much Terry if you can look at all this and guide me, it will help a lot of friends
Dan - F6FLU
Log4OM V2.35.1.0 - Windows 11 - i9-11900K - SSD 512Go - 32 Go
FTdx101D - Hexbeam - Wire dipole 40-30M
https://F6FLU.org
Log4OM V2.35.1.0 - Windows 11 - i9-11900K - SSD 512Go - 32 Go
FTdx101D - Hexbeam - Wire dipole 40-30M
https://F6FLU.org
Re: UDP connection problem
From my research that is so JTAlert can resend UDP packets from WSJT-X to other programs. But it appears that JTAlert is already setup for Log4OM; so I don't think you would need to have the packets repeated. If you do...it should just be a matter of setting it up as another Inbound Connection.
- G4POP
- Log4OM Alpha Team
- Posts: 11606
- Joined: 21 Jan 2013, 14:55
- Location: Burnham on Crouch, Essex UK
Re: UDP connection problem
Dan,
If you recall I posted the JTDX and LOG4OM set up windows earlier in this thread which you found worked fine for your friend.
Firstly I prefer the UDP connection to JTDX to be the JT Message instead of the ADIF_Message and you found that worked OK
By introducing JTAlert you have started to duplicate logging so you should either dissable the JTAlert logging to Log4om or dispense with the UDP connection to JTDX - Dont use both
I understand that JTAlert is a great program to alert you to required contacts and it does maintain its own internal log I beleieve so ther eis no reason to stop using it just dont double up on sending the QSO's to Log4OM
If you recall I posted the JTDX and LOG4OM set up windows earlier in this thread which you found worked fine for your friend.
Firstly I prefer the UDP connection to JTDX to be the JT Message instead of the ADIF_Message and you found that worked OK
By introducing JTAlert you have started to duplicate logging so you should either dissable the JTAlert logging to Log4om or dispense with the UDP connection to JTDX - Dont use both
I understand that JTAlert is a great program to alert you to required contacts and it does maintain its own internal log I beleieve so ther eis no reason to stop using it just dont double up on sending the QSO's to Log4OM
73 Terry G4POP
Re: UDP connection problem
Yes Terry for the first friend it's OK with the screenshots you gave me, it was the case with JTDX connected directly with Log4OMG4POP wrote: 11 Apr 2023, 17:10 Dan,
If you recall I posted the JTDX and LOG4OM set up windows earlier in this thread which you found worked fine for your friend.
For these screenshots that I just sent it's for another OM

I will follow your advice
If I understood :
1) I change the JTAlet-Log4OM connection from Adif Message to UDP
2) I delete in JTAlert the resend with port #1240
3) For ADIF Monitor in Log4OM should it be ticked or not validated?
thanks again
Dan - F6FLU
Log4OM V2.35.1.0 - Windows 11 - i9-11900K - SSD 512Go - 32 Go
FTdx101D - Hexbeam - Wire dipole 40-30M
https://F6FLU.org
Log4OM V2.35.1.0 - Windows 11 - i9-11900K - SSD 512Go - 32 Go
FTdx101D - Hexbeam - Wire dipole 40-30M
https://F6FLU.org
- G4POP
- Log4OM Alpha Team
- Posts: 11606
- Joined: 21 Jan 2013, 14:55
- Location: Burnham on Crouch, Essex UK
Re: UDP connection problem
F6FLU wrote: 11 Apr 2023, 21:21Yes Terry for the first friend it's OK with the screenshots you gave me, it was the case with JTDX connected directly with Log4OMG4POP wrote: 11 Apr 2023, 17:10 Dan,
If you recall I posted the JTDX and LOG4OM set up windows earlier in this thread which you found worked fine for your friend.
For these screenshots that I just sent it's for another OM
I will follow your advice
If I understood :
1) I change the JTAlet-Log4OM connection from Adif Message to UDP
2) I delete in JTAlert the resend with port #1240
3) For ADIF Monitor in Log4OM should it be ticked or not validated?
thanks again
Correct except number 2
Just dissable Log4OM V2 Logging to SQLite file but leave port 1240 enabled
73 Terry G4POP
Re: UDP connection problem
Thank you Terry
2-1) this means that in the Log4OM preferences (User Configuration / Station Information / Database
I don't select my SQLite file?
2-2) This means that in JTAlert I leave "Resend WSJT-X UDP packets (received only ) validated with port 1240 (JTALERT Settings/Logging/WSJT-X/JTDX)?
2-3) and that means that Log4OM will receive the ADIF frame via this port 1240?
2-4) and that this QSO will be written in the SQLite file?
2-5) so Log4OM automatically monitors this port 1240?
2-6) Is that right or is it more complicated?
I would like to understand this process
3) 3) ADIF Monitor in Log4OM must not validated?
Thanks and thanks again
73
Dan - F6FLU
Log4OM V2.35.1.0 - Windows 11 - i9-11900K - SSD 512Go - 32 Go
FTdx101D - Hexbeam - Wire dipole 40-30M
https://F6FLU.org
Log4OM V2.35.1.0 - Windows 11 - i9-11900K - SSD 512Go - 32 Go
FTdx101D - Hexbeam - Wire dipole 40-30M
https://F6FLU.org
- G4POP
- Log4OM Alpha Team
- Posts: 11606
- Joined: 21 Jan 2013, 14:55
- Location: Burnham on Crouch, Essex UK
Re: UDP connection problem
2-1 Yes no selectionF6FLU wrote: 12 Apr 2023, 07:35Thank you Terry
2-1) this means that in the Log4OM preferences (User Configuration / Station Information / Database
I don't select my SQLite file?
2023-04-12 09_26_28.jpg
2-2) This means that in JTAlert I leave "Resend WSJT-X UDP packets (received only ) validated with port 1240 (JTALERT Settings/Logging/WSJT-X/JTDX)?
2-3) and that means that Log4OM will receive the ADIF frame via this port 1240?
2-4) and that this QSO will be written in the SQLite file?
2-5) so Log4OM automatically monitors this port 1240?
2-6) Is that right or is it more complicated?
I would like to understand this process
3) 3) ADIF Monitor in Log4OM must not validated?
2-2 Yes
2-3 Inmaterial the port is used for other things
2-4 No
2-5 Please ignore
2-6 No answer required
3-3 I reccomend that you deleter that connection and create another using JT_MESSAGE not ADIF
Logging route will then be same as your friend JTDX direct vis UDP (JT_MESSAGE) to Log4OM
JTAlert will monitor what goes on in WSJT and ALERT you of required stations etc
There are many alternative ways to connect these programs to Log4OM you might find one that you prefer on Youtube but that is my take on it.
As a personal statement re Joe Taylor WSJT and similar cloned programes, they are causing us so much extra work integrating and changing things due to changes in these external programs that it has virtually stopped development of Log4OM!
73 Terry G4POP
Re: UDP connection problem
Thank you TerrY
but i'm having trouble understanding how it works
1) If I don't select the SQLite file in Log4OM how will the QSO be saved in this SQLite file?
according to all your answers that you kindly gave, I will try to make a synoptic of the connections
but here I admit that I do not understand how the QSO will be recorded in Log4OM
but i'm having trouble understanding how it works
1) If I don't select the SQLite file in Log4OM how will the QSO be saved in this SQLite file?
according to all your answers that you kindly gave, I will try to make a synoptic of the connections
but here I admit that I do not understand how the QSO will be recorded in Log4OM
Dan - F6FLU
Log4OM V2.35.1.0 - Windows 11 - i9-11900K - SSD 512Go - 32 Go
FTdx101D - Hexbeam - Wire dipole 40-30M
https://F6FLU.org
Log4OM V2.35.1.0 - Windows 11 - i9-11900K - SSD 512Go - 32 Go
FTdx101D - Hexbeam - Wire dipole 40-30M
https://F6FLU.org