I don't think you can do that. What you can do is connect JTDX to Logger32 and turn on one of the UDP repeaters in Logger32 and configure it to send logging messages to another logging program. With that configuration, the other logging program can only?'listen' to the UDP messages and not reply. See section 15.7 (page 378) of the help file.
?
Or you could configure one (or both) logging programs to log by TCP. Use your imagination.
?
The ultimate configuration option would be to remove Logger32 completely. Sure would reduce the reflector bandwidth. SeventyThree(s).?
On 11/21/2024 1:23 PM EST Paul F6EXV via groups.io <f6exv@...> wrote:
?
?
I must be more precise...
This message pops up only when I have Log4OM already open. If I open L32 first, then I do not get that error message, BUT then, when I open Log4OM second, Log4OM does not import the QSO info ...
It's either one , or the other.
How must I configure these things so that JTDX sends QSO to both L32 and L4OM ?
?
TU + 73
Paul
?
Bob
That error message pops up when I open L32....
The UDP "numbers" are correct as you say.
?
So ?
73
Paul F6EXV
?
It doesn't sound like a Logger32 error to me. Look at the JTDX settings on the REPORTING tab. What is the UDP server address? It should be 127.0.0.1 SeventyThree(s).
On 11/21/2024 11:18 AM EST Paul F6EXV via groups.io <f6exv@...> wrote:
?
?
Hi all
"Can't open the UDP socket. Error : the requested address is a broadcast address, but flag is not set"...
How do I deal with that, as my JTDX QSO do not get ipmported automatically ?
?
TU + 73
Paul F6EXV
