Menu

20 second delay during command execution/response

Help
2024-09-17
2024-09-20
  • Mark Sheffield

    Mark Sheffield - 2024-09-17

    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

     
    • Michael Black

      Michael Black - 2024-09-17

      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

      On Tuesday, September 17, 2024 at 03:55:07 PM CDT, Mark Sheffield <markat@users.sourceforge.net> wrote:
      

      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/

       
      • Mark Sheffield

        Mark Sheffield - 2024-09-19

        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

         
        • Michael Black

          Michael Black - 2024-09-19

          There's a space after the semicolon

          On Thursday, September 19, 2024 at 03:40:14 PM CDT, Mark Sheffield <markat@users.sourceforge.net> wrote:
          

          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:

          • Rigctl_debug_output_using_CAPITAL_W.txt (45.3 kB; text/plain)
          • Rigctl_debug_output_using_little_w.txt (47.0 kB; text/plain)

          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/

           
          • Mark Sheffield

            Mark Sheffield - 2024-09-20

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

             

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.