I still can't start FLDigi remote from latest cqrlog.
If I try, I got a Error Box from cqrlog with "No timers available" and Abort and Okay Buttons.
Abort kills cqrlog, and OK does nothing.
I can start FLDigi and the TRX Connection is working, changing Freq in FLDigi changes Freq in cqrlog, both ways are working.
No Mode change in cqrlog in New QSO Window. Stays at SSB.
But there is no logging from FLDigi to cqrlog.
Path to the FLDigi Binary is correct, Port in cqrlog is 7362, Adress is 127.0.0.1
Both Programs are build from the latest Source and used as normal User.
I can live with the Remote Startup Error (any Idea what causes this Error?) but logging to cqrlog would be fine.
I see a UDP Cloud Logging Function in FLDigi and a Broadcast UDP ADIF record with Port 9876 and the Local Host IP 127.0.0.1.
Not active yet. Could the "Broadcast UDP ADIF record" Function be used to Log to cqrlog?
Heinz-Juergen DO1YHJ
Hi Heinz-Juergen!
Latest version means CqrlogAlpha 140 ?
I have not used fldigi, but just tested that it starts when remote mode is seleced and correct path to fldigi is set and "run fldigi----" is cheked.
fldigi XML rpc was used and it brings all information from fldigi to Cqrlog.
my fldigi version is 4.2.03
Then I made a quick update from Fedora repository and got version 4.2.10
With that version I found UDP Cloud logging and tested it. It has some non standard adif fields but logging seems to work when using Cqrlog's ADIF remote.
The UDP is datagram is found as "rmt ADIF hdless" (see Cqrlog Help/Operation/ADIF remote)
Then main information seems to be logged but more testing is needed if you use eQSL or LoTW updates via fldigi. Then it must be checked that eQSL/LoTW dates and received dates are transferred ok to Cqrlog.
But if you do eQSL/LoTW update via Cqrlog then there is nothing to worry with those.
How ever when you use ADIF remote you do not get call information to Cqrlog while qso like you get with fldigi xml remote.
On the other hand fldigi can access call information from it's connections to callbooks, so that does not matter.
--
Saku
OH1KH
Yes, latest Versions.
But I think it's a Problem with my Log, Database or INI.
Just tested the Remote Connection with a other Log and no Errors appear.
Will do some Tests.
It's something with my regular Preference INI. New Log, imported the ini from my regular Log - Error.
Same new Log with the ini from my Contest Log - no Error.
Let's check the Difference now.
Couldn't find it. Must be one Setting that causes this Error.
Here are the two INI Files, renamed to .txt because of the Upload Limitations. Passwords and Login Names are deleted.
The contest.ini starts fldigi without any Problem and Logging did work.
The do1yhj.ini causes the Error.
If I merge the Diff from the do1yhj.ini to the contest.ini, the Error appears.
Heinz-Juergen DO1YHJ
No File Upload at replay?
Okay, then the other Way.
do1yhj.ini with the Error
File:
And the contest.ini without the Error
File: