Menu ▾ ▴

Hamlib cannot connect to TS-680S on COM1

Help
Pete Howe
2021-02-14
2021-02-15

  • Pete Howe

    Pete Howe - 2021-02-14

    Hello,
    I'm trying to use hamlib to control a Kenwood TS-680S on serial port COM1.
    I've verified that the rig responds directly to Kenwood commands like if; using HyperTerminal and PuTTY on COM1
    However hamlib doesn't enter interactive mode and responds with an error:
    rig.c(972):rig_open return
    rig_open: error = Communication timed out

    I'm using Hamlib 4.1 on Windows 10
    command line is rigctl -m 2024 -r COM1 -s 4800

    I can send debug info if needed.

    Many thanks for any help.
    Pete F5VGH

     

    • Michael Black

      Michael Black - 2021-02-14

      Please send debug.
      And send some screen shots from your hyperterminal too.
      Mike W9MDB

      On Sunday, February 14, 2021, 10:42:11 AM CST, Pete Howe <f5vgh@users.sourceforge.net> wrote:

      Hello,
      I'm trying to use hamlib to control a Kenwood TS-680S on serial port COM1.
      I've verified that the rig responds directly to Kenwood commands like if; using HyperTerminal and PuTTY on COM1
      However hamlib doesn't enter interactive mode and responds with an error:
      rig.c(972):rig_open return
      rig_open: error = Communication timed out

      I'm using Hamlib 4.1 on Windows 10
      command line is rigctl -m 2024 -r COM1 -s 4800

      I can send debug info if needed.

      Many thanks for any help.
      Pete F5VGH

      Hamlib cannot connect to TS-680S on COM1

      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/

       
      alternate

    • Bill Somerville

      Bill Somerville - 2021-02-14

      On 14/02/2021 16:42, Pete Howe wrote:

      Hello,
      I'm trying to use hamlib to control a Kenwood TS-680S on serial port COM1.
      I've verified that the rig responds directly to Kenwood commands like if; using HyperTerminal and PuTTY on COM1
      However hamlib doesn't enter interactive mode and responds with an error:
      rig.c(972):rig_open return
      rig_open: error = Communication timed out

      I'm using Hamlib 4.1 on Windows 10
      command line is rigctl -m 2024 -r COM1 -s 4800

      I can send debug info if needed.

      Many thanks for any help.
      Pete F5VGH

      Hi Pete,

      try adding -Cserial_handshake=Hardware to the command line options.

      73
      Bill
      G4WJS.

       

      • Pete Howe

        Pete Howe - 2021-02-14

        Hi Mike and Bill,
        Many thanks for your replies. I added -C serial_handshake=Hardware to the
        command line and confirm that interactive mode is accessed. The commands f,
        F, t, T and m work as expected.
        M ? returns the list of supported modes, however M LSB doesn't change the
        mode (no response from Rig command:). Are there any other commands that I
        should verify?

        In WSJT-X, when trying to use the Hamlib CAT interface, I selected Hardware
        Handshake but I still got a rig failure IO error message "rig.c(745):rig_open
        return while opening connection to rig". Please let me know how I should
        proceed to enable hamlib to make the rig connection with programs like
        WSJT-X and Log4OM.

        Many thanks,
        Pete

        On Sun, Feb 14, 2021 at 6:06 PM Bill Somerville bsomervi@users.sourceforge.net wrote:

        On 14/02/2021 16:42, Pete Howe wrote:

        Hello,
        I'm trying to use hamlib to control a Kenwood TS-680S on serial port COM1.
        I've verified that the rig responds directly to Kenwood commands like if;
        using HyperTerminal and PuTTY on COM1
        However hamlib doesn't enter interactive mode and responds with an error:
        rig.c(972):rig_open return
        rig_open: error = Communication timed out

        I'm using Hamlib 4.1 on Windows 10
        command line is rigctl -m 2024 -r COM1 -s 4800

        I can send debug info if needed.

        Many thanks for any help.
        Pete F5VGH

        Hi Pete,

        try adding -Cserial_handshake=Hardware to the command line options.

        73
        Bill
        G4WJS.

        Hamlib cannot connect to TS-680S on COM1
        https://sourceforge.net/p/hamlib/discussion/25919/thread/97c65ab073/?limit=25#d12c/2727

        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/

         
        alternate

        • Bill Somerville

          Bill Somerville - 2021-02-14

          Hi Pete,

          make sure only one application is accessing the CAT serial port at any
          one time.

          73
          Bill
          G4WJS.

          On 14/02/2021 20:02, Pete Howe wrote:

          Hi Mike and Bill,
          Many thanks for your replies. I added -C serial_handshake=Hardware to the
          command line and confirm that interactive mode is accessed. The commands f,
          F, t, T and m work as expected.
          M ? returns the list of supported modes, however M LSB doesn't change the
          mode (no response from Rig command:). Are there any other commands that I
          should verify?

          In WSJT-X, when trying to use the Hamlib CAT interface, I selected Hardware
          Handshake but I still got a rig failure IO error message "rig.c(745):rig_open
          return while opening connection to rig". Please let me know how I should
          proceed to enable hamlib to make the rig connection with programs like
          WSJT-X and Log4OM.

          Many thanks,
          Pete

          On Sun, Feb 14, 2021 at 6:06 PM Bill Somerville bsomervi@users.sourceforge.net wrote:

          On 14/02/2021 16:42, Pete Howe wrote:

          Hello,
          I'm trying to use hamlib to control a Kenwood TS-680S on serial port COM1.
          I've verified that the rig responds directly to Kenwood commands like if;
          using HyperTerminal and PuTTY on COM1
          However hamlib doesn't enter interactive mode and responds with an error:
          rig.c(972):rig_open return
          rig_open: error = Communication timed out

          I'm using Hamlib 4.1 on Windows 10
          command line is rigctl -m 2024 -r COM1 -s 4800

          I can send debug info if needed.

          Many thanks for any help.
          Pete F5VGH

          Hi Pete,

          try adding -Cserial_handshake=Hardware to the command line options.

          73
          Bill
          G4WJS.

           
          alternate

        • Michael Black

          Michael Black - 2021-02-14

          Run rigctld and have WSJT-x use "Hamlib NET rigctl".  Log4OM will also connect to rigctld.
          You can test rigctld with "rigctl -m 2"
          If you add "-vvvvv -Z >log.txt 2>&1" to the rigctld line you can send the log.txt to me if you notice any bugs.
          Mike W9MDB

          On Sunday, February 14, 2021, 02:02:55 PM CST, Pete Howe <f5vgh@users.sourceforge.net> wrote:

          Hi Mike and Bill,
          Many thanks for your replies. I added -C serial_handshake=Hardware to the
          command line and confirm that interactive mode is accessed. The commands f,
          F, t, T and m work as expected.
          M ? returns the list of supported modes, however M LSB doesn't change the
          mode (no response from Rig command:). Are there any other commands that I
          should verify?

          In WSJT-X, when trying to use the Hamlib CAT interface, I selected Hardware
          Handshake but I still got a rig failure IO error message "rig.c(745):rig_open
          return while opening connection to rig". Please let me know how I should
          proceed to enable hamlib to make the rig connection with programs like
          WSJT-X and Log4OM.

          Many thanks,
          Pete

          On Sun, Feb 14, 2021 at 6:06 PM Bill Somerville bsomervi@users.sourceforge.net wrote:

          On 14/02/2021 16:42, Pete Howe wrote:

          Hello,
          I'm trying to use hamlib to control a Kenwood TS-680S on serial port COM1.
          I've verified that the rig responds directly to Kenwood commands like if;
          using HyperTerminal and PuTTY on COM1
          However hamlib doesn't enter interactive mode and responds with an error:
          rig.c(972):rig_open return
          rig_open: error = Communication timed out

          I'm using Hamlib 4.1 on Windows 10
          command line is rigctl -m 2024 -r COM1 -s 4800

          I can send debug info if needed.

          Many thanks for any help.
          Pete F5VGH

          Hi Pete,

          try adding -Cserial_handshake=Hardware to the command line options.

          73
          Bill
          G4WJS.

          Hamlib cannot connect to TS-680S on COM1
          https://sourceforge.net/p/hamlib/discussion/25919/thread/97c65ab073/?limit=25#d12c/2727

          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/

          Hamlib cannot connect to TS-680S on COM1

          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/

           
          alternate

          • Pete Howe

            Pete Howe - 2021-02-15

            Many thanks for your replies Mike and Bill. WSJT-x and hamlib are now
            working correctly. I'm going to try running rigctld and will let you know.
            73,
            Pete

            On Sun, Feb 14, 2021 at 11:35 PM Michael Black mdblack98@users.sourceforge.net wrote:

            Run rigctld and have WSJT-x use "Hamlib NET rigctl". Log4OM will also
            connect to rigctld.
            You can test rigctld with "rigctl -m 2"
            If you add "-vvvvv -Z >log.txt 2>&1" to the rigctld line you can send the
            log.txt to me if you notice any bugs.
            Mike W9MDB

            On Sunday, February 14, 2021, 02:02:55 PM CST, Pete Howe f5vgh@users.sourceforge.net wrote:

            Hi Mike and Bill,
            Many thanks for your replies. I added -C serial_handshake=Hardware to the
            command line and confirm that interactive mode is accessed. The commands f,
            F, t, T and m work as expected.
            M ? returns the list of supported modes, however M LSB doesn't change the
            mode (no response from Rig command:). Are there any other commands that I
            should verify?

            In WSJT-X, when trying to use the Hamlib CAT interface, I selected Hardware
            Handshake but I still got a rig failure IO error message
            "rig.c(745):rig_open
            return while opening connection to rig". Please let me know how I should
            proceed to enable hamlib to make the rig connection with programs like
            WSJT-X and Log4OM.

            Many thanks,
            Pete

            On Sun, Feb 14, 2021 at 6:06 PM Bill Somerville
            bsomervi@users.sourceforge.net wrote:

            On 14/02/2021 16:42, Pete Howe wrote:

            Hello,
            I'm trying to use hamlib to control a Kenwood TS-680S on serial port COM1.
            I've verified that the rig responds directly to Kenwood commands like if;
            using HyperTerminal and PuTTY on COM1
            However hamlib doesn't enter interactive mode and responds with an error:
            rig.c(972):rig_open return
            rig_open: error = Communication timed out

            I'm using Hamlib 4.1 on Windows 10
            command line is rigctl -m 2024 -r COM1 -s 4800

            I can send debug info if needed.

            Many thanks for any help.
            Pete F5VGH

            Hi Pete,

            try adding -Cserial_handshake=Hardware to the command line options.

            73
            Bill
            G4WJS.

            Hamlib cannot connect to TS-680S on COM1

            https://sourceforge.net/p/hamlib/discussion/25919/thread/97c65ab073/?limit=25#d12c/2727

            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/

            Hamlib cannot connect to TS-680S on COM1

            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/

            Hamlib cannot connect to TS-680S on COM1
            https://sourceforge.net/p/hamlib/discussion/25919/thread/97c65ab073/?limit=25#d12c/2727/fa14/ddca

            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/

             
            alternate

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.