Bob VK2YQA

Hi Mike Would be fine if it toggles VFOB>VFOA>VFOB, but it does an extra >VFOA VFOA>VFOB>VFOA works fine. Rig was set to; VFOB 14071 USB F1 VFOA 14066 USB F1 then left on VFOA After the following (before ctrl-c) rig was on VFOB Cheers Bob VK2YQA rigctld.c(641) Startup: /usr/local/bin/rigctld -m 3068 -c 0x7c -s 19200 -vvvvv -r /dev/icom9100a rigctld Hamlib 4.7~git 2024-12-25T05:19:02Z SHA=e0a805 64-bit Report bugs to hamlib-developer@lists.sourceforge.net Max# of rigctld client services=32 rig_test_2038:...

Tnxs Mike The patch has resolved the rigctl toggles. I would ask that some others with Icom's test the rigctld initialise "problem". I understand the need to test for the "other" VFO's, but the whilst VFOA is showing on the rig display, it toggles VFOB, VFOA then back to VFOB is likely to cause some irritation/confusion. I would expect the active frequency to be the same before and after launching rigctld. This may be IC-9100 specific so pls advise if you'd like a vvvvv dump. Cheers Bob VK2YQA On...

Thanks Mike That solved the problem. Thought it worth a mention though that --skipinit is not in the man page, but skip_init is and fails as follows $ rigctl -m 2 skip_init f rigctld: Hamlib 4.7~git 2024-12-22T21:48:56Z SHA=8589d5 64-bit 14066000 Command '' not found! and to verify the syntax $ rigctl -m 2 get_rig_info f rigctld: Hamlib 4.7~git 2024-12-22T21:48:56Z SHA=8589d5 64-bit VFO=VFOA Freq=14066000 Mode=PKTUSB Width=2500 RX=1 TX=1 VFO=VFOB Freq=14071030 Mode=None Width=0 RX=0 TX=0 Split=0...

Have had an interesting problem with rigctld (-m 3068) and launching rigctl (-m 2) from a bash script that I thought worth a mention. I have actually found a workaround so not a big disaster. Using the latest source from github. I have a Icom 9100 connected via USB (with a udev name function) and launch a fairly standard rigctld as; /usr/local/bin/rigctld -m 3068 -x 2 -c 0x7c -s 19200 -r /dev/icom9100a & Whenever I launch something like; /usr/local/bin/rigctl -m 2 T 0 or set VFO frequency etc, the...