![]() ![]() ![]() I can now make Mode / Filter / Frequency changes using FLDigi or FLRig, and they are smooth - with only single-beeps from the radio, and no weird VFO changes. subsequent CQRLOG read/updates from rig show VFO B, 14.255MHz, USB a lot of rig-beeping happens, then the rig has been changed to VFO B! I click a DX Spot, and CQRLOG sends correct data: 14.019 / CW CQRLOG receives the Mode and Frequncy properly.īut, as DXCluster spots arrive, I click on one of those, and CQRLOG issues a lot of commands which make my rig beep far too much, and the result includes an undesired change to VFO B!! So now, I start CQRLOG, and attach it to Model 2 (hamlib NET) on port 4532. seemingly faster and more-robustly than hamlib. I wish it did, because I find that FLRig is super-responsive, and supports rig- control. I find that CQRLOG cannot talk XML-RPC to FLRig. So, I use FLDigi and verify that BOTH methods of rig-access work - they do! FLDigi is happy to use either XML-RPC or hamlib. I test and verify this part interactively, from the command-line.Īt this point, my rig is accessbile 2x: via XML-RPC on port 12345, and also via hamlib on port 4532. I can then start rigctld with model 4, and it re-serves my rig using hamlib, port 4532. I test and verify this with rigctl, interactively, from the command-line. Then, FRLig shares the rig over XML-RPC, port 12345. I have this connection - FLRig talks to my TS-850. "rigctld will talk to flrig via localhost address 127.0.0.1, port 12345, but for cqrlog config defaults 127.0.0.1 (or localhost) and port 4532 should be set for cqrlog to talk to rigctld as before (no change there)" ![]() Flrig must be running when cqrlog (and rigctld) are started.įeel free to test and report how it works ! So answer is YES, but settings needs further investigation. So it works in basic, but needs some setting to fix still. It seems to work ok, but only a while then frequency disappears and comes momentary back if TRXContol is reset. I made a quick setup for ic7300 to flrig (that I do not normally use for anything). Rigctld will talk to flrig via localhost address 127.0.0.1, port 12345, but for cqrlog config defaults 127.0.0.1 (or localhost) and port 4532 should be set for cqrlog to talk to rigctld as before (no change there). The command has extension "-wsjtx" and that must added in cqrlog "preferences/TRXcontol/Path to rigctld binary" string to get v3.3 in use. Warranty not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. This is free software see the source for copying conditions. If you have installed latest wsjt-x (v2.0rc4 at the moment) it will install also hamlib-wsjtx.įrom command line you should be able to ~]$ rigctld-wsjtx -version How ever it might be that your linux does not have hamlib 3.3 as package. In hamlib version 3.3 it has rig called "flrig". ![]()
0 Comments
Leave a Reply. |