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)
That's because PC005; does not return anything and it's waiting for an answer.
Here's the best (fastest) solution with the W command where you tell it to expect 0 bytes
rigctl -m 2 -vvv --skipinit W PC005; 0
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)
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.
Using the "W" command just didn't work.
When using the "W" command, I also tried all manner of variations to pass the "PC" command - "PC015;",0 , PC015;0, PC015; ,0 - everything was either exactly same behavior and the rig never got the PC015; command.
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.
Using the "W" command just didn't work.
When using the "W" command, I also tried all manner of variations to pass the "PC" command - "PC015;",0 , PC015;0, PC015; ,0 - everything was either exactly same behavior and the rig never got the PC015; command.
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
That's because PC005; does not return anything and it's waiting for an answer.
Here's the best (fastest) solution with the W command where you tell it to expect 0 bytes
rigctl -m 2 -vvv --skipinit W PC005; 0
Mike W9MDB
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
20 second delay during command execution/response
Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/hamlib/discussion/25919/
To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/
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.
Using the "W" command just didn't work.
When using the "W" command, I also tried all manner of variations to pass the "PC" command - "PC015;",0 , PC015;0, PC015; ,0 - everything was either exactly same behavior and the rig never got the PC015; command.
Once again - thank you
There's a space after the semicolon
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.
Using the "W" command just didn't work.
When using the "W" command, I also tried all manner of variations to pass the "PC" command - "PC015;",0 , PC015;0, PC015; ,0 - everything was either exactly same behavior and the rig never got the PC015; command.
Once again - thank you
Attachments:
20 second delay during command execution/response
Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/hamlib/discussion/25919/
To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/
Sorry I missed that - all working now, thank you.