¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io

callsign lookup in logging program #fldigi #Log4om


 

I am trying to find the link from Fldigi to logging programs that allows them to look up previous calls when a callsign is entered in Fldigi to start a QSO.? When used with DX Keeper as soon as you enter a callsign in Fldigi, DX Keeper and DxView look up the callsign.? When used with N3FJP the same process happens.? I am trying to duplicate this lookup with Log4OMv2 but I cannot find what is sending the data to the other programs.?
?
Does anyone have any idea where I can look, or how to do this set up?
?
Thanks in advance for any ideas.
73
Bill
w1wrh


 

Look for the last adi setting in configuration

sent by ve3wej on samsung s21+


On Sat, Nov 9, 2024, 9:24?p.m. Bill - W1WRH via <w1wrh=[email protected]> wrote:
I am trying to find the link from Fldigi to logging programs that allows them to look up previous calls when a callsign is entered in Fldigi to start a QSO.? When used with DX Keeper as soon as you enter a callsign in Fldigi, DX Keeper and DxView look up the callsign.? When used with N3FJP the same process happens.? I am trying to duplicate this lookup with Log4OMv2 but I cannot find what is sending the data to the other programs.?
?
Does anyone have any idea where I can look, or how to do this set up?
?
Thanks in advance for any ideas.
73
Bill
w1wrh


 

¿ªÔÆÌåÓý

Hi Bill,

Fldigi uses a TCP datagram to communicate with the logging software. The payload is an XMLRPC response and request. My logging software supports the following requests calls:

Log.list_methods - lists the supported methods
Log.add_record - Adds the ADIF data sent as a new record.
Log.get_record - Returns the ADIF record that matches certain fields (call, band, mode)
Log.update_record - merges the current record with the supplied record.
Log.check_dup - returns true, false or possible for the supplied ADIF record.

I can't remember where I got the specifications of these from apart from may be reverse engineering the Fldigi logging interface to fllog. I don't have an instance of fldigi on this machine otherwise I could look to see where the fields you need to enter in its config. There is a menu item to enable connection to the log server (which is what my logging app behaves as). I had a brief scan through the fldigi and fllog manuals but couldn't see anything.

Hope this helps a bit.
Phil GM3ZZA


From: [email protected] <[email protected]> on behalf of Bill - W1WRH via groups.io <w1wrh@...>
Sent: 10 November 2024 2:24 AM
To: [email protected] <[email protected]>
Subject: [winfldigi] callsign lookup in logging program #fldigi #Log4om
?
I am trying to find the link from Fldigi to logging programs that allows them to look up previous calls when a callsign is entered in Fldigi to start a QSO.? When used with DX Keeper as soon as you enter a callsign in Fldigi, DX Keeper and DxView look up the callsign.? When used with N3FJP the same process happens.? I am trying to duplicate this lookup with Log4OMv2 but I cannot find what is sending the data to the other programs.?
?
Does anyone have any idea where I can look, or how to do this set up?
?
Thanks in advance for any ideas.
73
Bill
w1wrh


 

¿ªÔÆÌåÓý

Bill,


The enable switch is in the menu Logbook->Connect to Server.


The port fldigi tries to connect to is 8421.


There is also and interface to broadcast a UDP datagram containing an ADIF record - this can be goot from Configure->Logging->Cloud-UDP. There's also specific configuration for MacLogger and N3FJP loggers.


Phil.


On 10/11/2024 15:36, Philip Rose via groups.io wrote:

Hi Bill,

Fldigi uses a TCP datagram to communicate with the logging software. The payload is an XMLRPC response and request. My logging software supports the following requests calls:

Log.list_methods - lists the supported methods
Log.add_record - Adds the ADIF data sent as a new record.
Log.get_record - Returns the ADIF record that matches certain fields (call, band, mode)
Log.update_record - merges the current record with the supplied record.
Log.check_dup - returns true, false or possible for the supplied ADIF record.

I can't remember where I got the specifications of these from apart from may be reverse engineering the Fldigi logging interface to fllog. I don't have an instance of fldigi on this machine otherwise I could look to see where the fields you need to enter in its config. There is a menu item to enable connection to the log server (which is what my logging app behaves as). I had a brief scan through the fldigi and fllog manuals but couldn't see anything.

Hope this helps a bit.
Phil GM3ZZA

From: [email protected] <[email protected]> on behalf of Bill - W1WRH via groups.io <w1wrh@...>
Sent: 10 November 2024 2:24 AM
To: [email protected] <[email protected]>
Subject: [winfldigi] callsign lookup in logging program #fldigi #Log4om
?
I am trying to find the link from Fldigi to logging programs that allows them to look up previous calls when a callsign is entered in Fldigi to start a QSO.? When used with DX Keeper as soon as you enter a callsign in Fldigi, DX Keeper and DxView look up the callsign.? When used with N3FJP the same process happens.? I am trying to duplicate this lookup with Log4OMv2 but I cannot find what is sending the data to the other programs.?
?
Does anyone have any idea where I can look, or how to do this set up?
?
Thanks in advance for any ideas.
73
Bill
w1wrh


 

Thanks for this help. I was able to get fldigi to log into Log4om2 I just don't get the lookup when you start a qso like wsjt-x does or fldigi does in n3fjp or dxlabs.?
?
I could not connect to server as I didn't understand what to fill in. I am still reading to get ideas.?


 

On Sat, Nov 9, 2024 at 07:24 PM, Bill - W1WRH wrote:
I am trying to duplicate this lookup with Log4OMv2 but I cannot find what is sending the data to the other programs.?
?
Hi Bill, apparently it is a known issue with Log4OM, but I have seen anything mentioned about a fix yet.?
?
?
I can confirm that it also does not work for me with the latest version of Log4OM.
?
Cheers,
Steve K4RVA


Mike Black
 

I think this is a problem with FLDigi and not Log4OM.

I just tested and Log4OM is allowing TCP connections on port 7362 but FLDigi is not attempting to connect to it or any other of the services in that tab.

Mike W9MDB

On Thursday, November 14, 2024 at 11:04:23 AM CST, Steve K4RVA via groups.io <k4rva@...> wrote:





On Sat, Nov 9, 2024 at 07:24 PM, Bill - W1WRH wrote:


I am trying to duplicate this lookup with Log4OMv2 but I cannot find what is sending the data to the other programs.?

?

Hi Bill, apparently it is a known issue with Log4OM, but I have seen anything mentioned about a fix yet.?

?



?

I can confirm that it also does not work for me with the latest version of Log4OM.

?

Cheers,

Steve K4RVA