Hi Alex,

it seems we need some diagnostics from the Hamlib rig control server to see why it cannot access your rig's CAT port or you PTT serial port. Try this command to start the server:

C:\WSJT\wsjtx\bin>rigctld-wsjtx -m 3081 -r COM4 -s 19200 -p COM2 -P RTS 
-Cptt_share=1 -vvvvv

This will provide a lot of diagnostic output, you can redirect the output to a file by modifying the command like this:

C:\WSJT\wsjtx\bin>rigctld-wsjtx -m 3081 -r COM4 -s 19200 -p COM2 -P RTS -Cptt_share=1 
-vvvvv 1> rigctld.log 2>&1

that will create a log file in your current working directory called rigctld.log, send that file for analysis please?

73
Bill
G4WJS.

On 18/02/2021 06:16, Alex Artieda, HB9DRI wrote:

Hello Bill

I reboot the computer to avoid other application take control of any com port, same error.

73 de Alex, HB9DRI

*From:* Bill Somerville <g4...@classdesign.com>
*Sent:* Thursday, February 18, 2021 12:43 AM
*To:* wsjt-devel@lists.sourceforge.net
*Subject:* Re: [wsjt-devel] FW: BUG in WSJT-X 2.3 and 2.4rc1 COM port

Hi Alex,

one of the two serial ports is probably opened by another application.

73
Bill
G4WJS.

On 17/02/2021 17:38, Alex Artieda, HB9DRI wrote:

    Hello Bill

    This is the answer after execute the command:

    C:\WSJT\wsjtx\bin>rigctld-wsjtx -m 3081 -r COM4 -s 19200 -p COM2
    -P RTS -Cptt_share=1

    Recommend using --vfo switch for rigctld if client supports it

    rigctl and netrigctl will automatically detect vfo mode

    rig_open: error = IO error

    Alex, HB9DRI

    *From:* Bill Somerville <g4...@classdesign.com>
    <mailto:g4...@classdesign.com>
    *Sent:* Thursday, February 18, 2021 12:16 AM
    *To:* wsjt-devel@lists.sourceforge.net
    <mailto:wsjt-devel@lists.sourceforge.net>
    *Subject:* Re: [wsjt-devel] FW: BUG in WSJT-X 2.3 and 2.4rc1 COM port

    Hi Alex,

    yes it will work exactly as you require.

    73
    Bill
    G4WJS.

    On 17/02/2021 16:29, Alex Artieda, HB9DRI wrote:

        Hello Bill

        I must PTT a external sequencer via a COM port, I cannot use
        PTT via CAT because that will trigger the Radio 1^st , I must
        trigger the external sequencer via a COM port 1st, then the
        sequencer has 4 events to manage antenna relays, preamps, bias
        in the SSPA and for last PTT the radio, if I use PTT via CAT
        that will destroy my preamplifiers.

        Your proposal will works?

        Alex, HB9DRI

        *From:* Bill Somerville <g4...@classdesign.com>
        <mailto:g4...@classdesign.com>
        *Sent:* Wednesday, February 17, 2021 10:05 PM
        *To:* wsjt-devel@lists.sourceforge.net
        <mailto:wsjt-devel@lists.sourceforge.net>
        *Subject:* Re: [wsjt-devel] FW: BUG in WSJT-X 2.3 and 2.4rc1
        COM port

        Hi Alex,

        OK, try this. Change "Settings->Radio->Rig" to "Hamlib NET
        rigctl" and "Settings->Radio->PTT Method" to "CAT" for each
        WSJT-X instance you run.

        Open a CMD prompt window and type the following command:

        C:\WSJT\wsjtx\bin\rigctld-wsjtx -m 3081 -r COMx -s y -p COMz -P RTS 
-Cptt_share=1

        where 'x' is the CAT serial port number of your IC-9700, 'y'
        is the CAT baud rate, and 'z' is the PTT serial port number.

        The above command starts a Hamlib rig control server to serve
        your IC-9700 with Hamlib clients over a network connection.
        The adjustment to WSJT-X radio settings tells WSJT-X to
        communicate with the rig control server you have started, and
        also to do PTT via that server. You may get a message from
        your firewall application to asking to allow rigctld-wsjtx to
        accept network connections, which you should allow.

        Do not start Omni-Rig, you do not need it.

        This will do exactly what you need, you can make a short batch
        script containing the above command to start the Hamlib rig
        control server.

        If you are only using a single instance of WSJT-X the next
        release of WSJT-X will allow you to configure that instance to
        talk directly to your for CAT control while allowing other
        applications to access the PTT port when WSJT-X is not
        asserting PTT. For now, or if you use multiple WSJT-X
        instances; the approach above will work.

        73
        Bill
        G4WJS.

        On 17/02/2021 14:45, Alex Artieda, HB9DRI wrote:

            Hello Bill

            Yes I use only 1 CAT controller transmitter, the IC-9700,
            I don’t have any other CAT application accessing my
            Transceiver.

            73 de Alex, HB9DRI

            *From:* Bill Somerville <g4...@classdesign.com>
            <mailto:g4...@classdesign.com>
            *Sent:* Wednesday, February 17, 2021 9:39 PM
            *To:* wsjt-devel@lists.sourceforge.net
            <mailto:wsjt-devel@lists.sourceforge.net>
            *Subject:* Re: [wsjt-devel] FW: BUG in WSJT-X 2.3 and
            2.4rc1 COM port

            Alex,

            let me try again as you have not answered my question. I
            will qualify it a bit which may help.

            Are you only using one CAT controlled transmitter and is
            that your IC-7900?

            Do you have any other applications that require CAT access
            to your transceiver(s)?

            Note by CAT control I do not mean simple PTT control using
            a serial port control line like RTS or DTR alone.

            73
            Bill
            G4WJS.


_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Reply via email to