I upgraded my Linux Mint from version 18.x to 19.x a month or so ago and my WSJTX quit communicating with CQRLOG. Prior to the upgrade, the frequency displayed, mode displayed, etc. Now they don't communicate at all in remote mode. I am new to this forum so forgive me if someone has already solved. Looking for any help.
Thanks
Hi!
When running two or more programs that need to communicate with rig at same time you will create communication collision if you just set correct rig model based parameters to all programs.
When you start cqrlog alone it works. When you start WSJT-X alone it works, too. You can start cqrlog first with normal rig settings and after that WSJT-X but it has to use rig model #2 "Net hamlib rigctld" and "network server" as "localhost:4532" then it should work with both, but needs cqrlog running always first.
More information from this document:
https://github.com/OH1KH/cqrlog/blob/loc_testing/compiled/setting_rigctl...
--
Saku
OH1KH
Thank you for for the quick response. I will try this but I didn't need to do this before when running both on Mint 18.x. I de-selected "run-rigctrl at startup on the TRX page in CQRLOG and then set the obtain Frequency and Mode from WSJTX on the fldigi/wsjt interface page. I launched WSJTX first (it connected to rig via rigctrl) and then I launched CQRLOG and it worked. After moving to Mint 19, no communication is happening between WSJTX and CQRLOG with those same settings. I was wondering if anyone else has experienced the same issue.
I will try your suggestion though, if it supports remote WSJTX mode.
John - KN8L
I fixed it!
I let WSJTX make the rig connection via rigctl. Then, in WSJTX settings, on the reporting screen, I checked secondary UDP server box and matched the port to what was set in CQR log. Then in CQRLOG I set the WSJTX interface to get frequency and mode from WSJTX. Now everything works together! See attachments
File:
John - KN8L
Hi John!
Yes, you can do it also that way that WSJT-X uses rig parameters and drives rig. Then cqrlog TRXcontrol uses rig model #2 (Net Hamlib rigctld).
Then both get frequency display, but WSJT-X must be always running and started before cqrlog.
Your picture has nothing to do with rig cat (and seeing rig frequency in both programs). It affects only for logging.
If you are using "NewQSO/File/remote mode for wsjt" you do not need to check "Secondary UDP server". It is only needed if you do not want to use CQ-monitor, alerts etc. Just move the logged qso to cqrlog.
Then you check "secondary UDP server" set it's adders and port to "preferences/fldigi wsjtx interface/N1MM address" and "N1MM port" and do not use "NewQSO/File/remote mode for wsjt" but use "NewQSO/File/remote mode for N1MM logger" instead.
All this you can see from Help (New QSO top right menu) that opens the help files to your web browser.
But as said, this has no effect to rig cat control and setting rigctld. That makes me wonder was the problem ever with rig CAT control or was question of UDP communication between cqrlog and wsjtx (moving decoded data and loggings from wsjtx to cqrlog).
You were talking about frequency and mode display were not working so I assumed it to be rig CAT problem, not wsjtx<->cqrlog communication problem.
--
Saku
OH1KH
Thanks Saku. Sorry for any confusion I may have caused. The original issue was the two programs not talking to each other after I did the linux update. I could run them both independently. It was probably pilot error on my part. Through trying multiple things, it started working again so I posted what I thought was the fix. You are correct, I did not need to check the secondary UDP server.
I would like to further explore your method of connecting multiple software to rigctl. It would prevent me from changing the settings every time I just want to run CQRLOG standalone. Always more to learn! That is what makes this hobby fun.
Thanks again for your help and all you do for the Ham Radio community!
John - KN8L