Log4OM

Hello
Just one question :
Does Log4OM accept the Broadcast sytem ?

I tried to read the contributions here, I watched a lot of video, but obviously nobody talks about Broadcast, so I guess doesn't (yet) support Brodcast

I'm wrong ?
Thanks and 73
Dan

What did you mean with "broadcast system" ? Do you mean the different reporting systems like
RST for hamradio and SINPO for broadcast ? If yes we dont have this so Log4OM is a logging
software for hamradio based on strict ADIF rules ...

Hello
No
I use 2 computers and Log4OM and Gridtracker and JTDX
JTDX and Log4OM are on the same computer
Gridtracker is running on an another computer
These 2 computers are on the same network
JTDX and Gridtracker use the brodcast address (255.x.x.x)
When I click on a call from the Gridtracker, Gridtracker send to JTDX , I made QSO with JTDX and I log to Log4OM from JTDX with the second JTDX UDP port
If I click directly from JTDX I made a QSO and log into Log4OM
All works fine...
But
When I click on a call (from GT or from JTDX) this call is not transferred into Log4OM ( into the Log4OM CALL field)
I’m talking about when I click not when I valid this QSO...
My question is
How can I do transfert a call to Log4OM when I click on GT or JTDX ?
Sorry for my English
I hope you understand
Thanks and 73

Why not use a common sqlite database stored in the cloud, like Dropbox or Google drive?

Then with Log4OM, JT whatever and Gridtracker installed on both computers but using the common Log4OM sqlite database whatever PC you have a qso with it will log to the same logbook and be visible in both installations of Log4OM

Hi Terry
I'm not looking for Log4OM, Gridtracker and JTDX , to use the same Log.
I'm looking for how to make sure that when I click on a call (either in JTDX or GT), this call is sent to the "CALL" Field of Log4OM.
In fact I would like to check IN Log4om is I have already worked this call.
But it might not be a good idea
Dan

We already have that with WSJT but I am not sure if JTDX provides the same facility

It's not a case of Log4om 're broadcasting it's the external software that sends the data for Log4om to use

Ah OK Terry
maybe JTDX doesn't allow it, I don't know...
but JTDX does allow sending data to log in Log4OM so I think it should work?
Thanks again
73

Did you read our user guide 're JTDX set up?

Hello

G4POP wrote: 10 Nov 2020, 15:55 Did you read our user guide 're JTDX set up?

Yes I read and read again ...
But I don't use the same environment
On the manual you only use a local address (127.0.0.1 : 2237)
Here I use a broadcast address (239.255.0.0 : 2334)
BUT
I don't test with the
WSJT-X/JTDX, check the box 'Import QSO's from JT Message #12

Perhaps it's the problem ?

In fact I use :
in JTDX : Main UDP Server : 239.255.0.0 : 2334 AND second UDP Port as : 127.0.0.1 : 2236
Gridtracker use the same broadcast address : 239.255.0.0 : 2334
And JTDX sent to Log4OM via the second local address port 127.0.0.1 : 2237

On Log4OM I configured with UDP_Inbound ADIF_MESSAGE 2236 as JTDX Log

I don't know How can I send the call from JTDX to Log4OM perhaps via the JT Message #12 ?

Many thanks Terry but I don't sure that one solution exist
73

we actually don't read broadcast messages from other applications. That feature will be probably added in the future for GT.