I am finally getting around Fldigi working with CQRLog. Everything is working except the logging piece.
I followed the directions in the CQRLog help (port 7362 address 127.0.0.1) and the Use XMLPC is checked. Everything is running on a Pi4 so nothing fancy. I have set up the fldigi/wsjt interface just like the help. I have started fldigi from a terminal prompt using fldigi --xmlrpc-server-port 7362. When I start Fldigi remote from CQRLOG, the "fldigi xmlrpc" window appears showing in the Comment QSO "Socket error check fldigi!". For the life of what is there to check since I did start fldigi with --xmlrpc-server-port 7362 and saved the configuration. Is there something else to check?
Thanks.
73,
Kevin, KX4KU
I figured out something that fixed it. I needed to set Load QSO from fldigi every to 2 and change Drop after Sync Err to 5 it fixed it.
73,
Kevin
W4RKU
Hi Kevin!
"Load QSO from fldigi every" affects only when XmlRpc is not used.
Instead "Drop after Sync Err" is mandatory with XmlRpc and may cause problmes if it is too small value.
It is told at "Help/Operation/Digital modes(fldigi XmlRpc)":
"Parameter "Drop after SyncErr >" automates remote mode closing when fldigi is closed. But as it may affect also (in slow PCs) fldigi started by cqrlog it can be changed. 0 disables, 1-20 means timer rounds until drop. When closing happens it leaves text "Socket error, check fldigi!" to NewQSO field "Comment QSO".
Maybe that is a bit unclear explanation (I do not understand it by myself either when reading now some years later).
I put that sentence to fix list.
--
Saku
OH1KH
Saku,
Yes, I read that and printed it. I think when a read it I didn't think a Pi4 with 8G was a "slow" PC.
Maybe in the sentence that ends with "socket error in the comment" means the timer "expires" - something like that. Frankly the phrase "timer rounds" is a bit ambiguous because what is a "round". Number of times it tries to send the data. Now that it is set up right, it does work well and having used Fldigi on the PC for a long time, I never really knew about this feature so it was a learning opportunity.
Thanks for the explaination.
73,
Kevin
73,
Kevin
W4RKU
Hi Kevin!
Main thing is that it works now !
The "timer expires" ...
Because I am thinking it from programmers side it may look different for user.
We do a request to fldigi, then timer starts to count and when it has done one "round" (think about old mechanical mile counter of a car) we increase "failed poll"-counter by one and do all again. Once "failed poll"-counter gets bigger than set value in "Drop after Sync Err >" (Drop fldigi remote after Sync error count is bigger than) we give up and close fldigi remote.
What is really needed is a rewriting of whole cqrlog help by a native English speaking person.
The Finnish way of thinking differs quite a lot from English/US way, and for example while there are prepositions like to,at,in,on, ... etc. in use we do use one or few letter suffixes (postpositions) instead for words in Finnish language that makes a selection of right preposition for foreign language harder.
So it is no wonder that some sentences are unclear, even for the writer himself after few years :-)
--
Saku
OH1KH