Mark Sheffield

Sorry I missed that - all working now, thank you.

Posted this originally as a reply to the original comment.... Thanks for the reply, Mike.... Same behavior with "0"mreturn characters, attached is debug file with timestamps (using "w" command).... when I use "W" command, it just fails (debug file also attached) --skipinit doesn't seem to be doing much. debug files for: rigctl -m 2 -Z -vvvvv --skipinit W PC015;0 rigctl -m 2 -Z -vvvvv --skipinit w PC015;0 No matter what I did using the "w" command, the power changed correctly but delayed for 20 seconds....

I am running Log4OM to my Kenwood TS-570 using the rigctld daemon. This works fabulously. When running a command from the cmd window through the daemon to the rig, the command executes but immediately pauses for 20 full seconds for a complaint. The command executed is: >rigctl -m 2 -vvv w "PC005;" which changes the power of the rig to 5W. I have attached the debug file and annotated where the command "PC005;" completes and the 20 second delay occurs (relative to the screen output) Thank you

Hello - I have my TS-570 hooked up on COM3, can access my radio with this port using omni-rig (Log4OM) and python with no problem. I can't get rigctl to access the radio using a clean COM3 connection with the simplest of commands: rigctl -m2004 -s38400 -rCOM3 f (or any rigctl command, for that matter). The result is always C:\Users\MarkS>rigctl -m 2004 -s 38400 -r COM3 f rig_open: error = COM3 No such file or directory I set verbose mode high and captured the results of the following command and...