FLdigi integration

[dawkagaming]

Hello,

would I be possible to add a fldigi integration like that one from Log4OM? That it can automatically take log file from fldigi or it can get info by TCP/UDP.

It is really useful to have everything centered at logging program and send all data to it automatically. Log4OM works great with it, but it is not available for Linux.

Thank you for maintaining this program!

[aa5sh]

Take a look here: https://github.com/foldynl/QLog/wiki/Fldigi Fldigi github.com

…

On Sep 4, 2025, at 11:51 AM, Dawid Kulas ***@***.***> wrote: Hello, would I be possible to add a fldigi integration like that one from Log4OM? That it can automatically take log file from fldigi or it can get info by TCP/UDP. It is really useful to have everything centered at logging program and send all data to it automatically. Log4OM works great with it, but it is not available for Linux. Thank you for maintaining this program! — Reply to this email directly, view it on GitHub <#745>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AUEEMXQAQKKELXY3BP46X233RBUZJAVCNFSM6AAAAACFUS6HNCVHI2DSMVQWIX3LMV43ERDJONRXK43TNFXW4OZYHA2DCMRQGU>. You are receiving this because you are subscribed to this thread.

[dawkagaming]

Ah, I was sure I read everything.

Thanks!

[dawkagaming]

Hello again,

QLog can't connect to flrig.
It says:
"Rig Error: Network Error
Error Detail: Host not found"

[dawkagaming]

I managed to get it to work, not by using default flrig option, but with hamlib -> flrig

[foldynl]

hamlib->flrig does not work very well - flrig is not very well implemented in hamlib.

Host not found means that you have not entered the correct hostname. I would prefer the classic 127.0.0.1 on the loopback interface.

[dawkagaming]

@foldynl Got it, it is working now with default flrig settings and it seems to actually be faster in terms of response times.

But I got the problem which was already described in #485
I have the same version as described in the tread (4.2.06), downloaded from Debian repository.

What can I do about this?

[aa5sh]

This is a problem with FLrig sending the frequency in the wrong format. You may want to inquire with Dave or on that list serv about if there is a way to make it compliant. Michael, AA5SH

…

On Fri, Sep 5, 2025 at 5:43 PM Dawid Kulas ***@***.***> wrote: @foldynl <https://github.com/foldynl> Got it, it is working now with default flrig settings and it seems to actually be faster in terms of response times. But I got the problem which was already described in #485 <#485> I have the same version as described in the tread (4.2.06), downloaded from Debian repository. What can I do about this? — Reply to this email directly, view it on GitHub <#745 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AUEEMXUS3ZHXNZG57AX4VKT3RIG2BAVCNFSM6AAAAACFUS6HNCVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTIMZSGQZTOMQ> . You are receiving this because you commented.Message ID: ***@***.***>

[aa5sh]

Looks like it may have been added in FLDigi in your version or the one after, it is hard skimming their readme of changes on my phone. Could you try the newest version of FLDigi looks like they’re up to 4.2.08.

[dawkagaming]

@aa5sh https://salsa.debian.org/search?search=comma2period&nav_source=navbar&project_id=28119&group_id=2635&search_code=true&repository_ref=debian%2F4.2.06-1

It is already in the version I am using as shown here.

As I was testing on Debian Sid, this also happens on 4.2.07

[foldynl]

Instead of emailing back and forth, wouldn’t it be better to send us the debug log I mentioned in the issue #485 ? I think that would speed things up a lot and save everyone time.

[dawkagaming]

@foldynl Sorry for that!

Here is the part with QSO being send to Qlog:

"<QSO_DATE:8>20250907<QSO_DATE_OFF:8>20250907<TIME_ON:4>1315<TIME_OFF:6>131526<CALL:4>WW8A<FREQ:9>14,071585<MODE:4>RTTY<RST_SENT:3>599<RST_RCVD:3>599<TX_PWR:1>0<NAME:0><QTH:0><STATE:0><VE_PROV:0><COUNTRY:3>USA<CNTY:0><GRIDSQUARE:0><STX:3>000<SRX:0><SRX_STRING:0><STX_STRING:0><NOTES:0><CLASS:0><ARRL_SECT:0><CQZ:1>5<IOTA:0><DXCC:0><QSL_VIA:0><QSLRDATE:0><QSLSDATE:0><CWSS_CHK:0><CWSS_SECTION:0><CWSS_SERNO:0><CWSS_PREC:0><AGE:0><TEN_TEN:0><CHECK:0><TROOPS:0><TROOPR:0><SCOUTS:0><SCOUTR:0><OPERATOR:6><STATION_CALLSIGN:6><MY_CITY:11><MY_STATE:0><MY_GRIDSQUARE:6><eor>" [QByteArray FldigiTCPServer::addRecord(QString):core/FldigiTCPServer.cpp:153]

Looks like it is still sending the frequency with a comma.

[dawkagaming]

@foldynl
I think we got the issue.

Fldigi when set to Polish language, uses commas instead of dots.

[foldynl]

This should rather be directed to the fldigi forum.

[dawkagaming]

@foldynl I will try to get it fixed, thank you.