And if CAT PTT still fails I need to see debug info -- add ">log.txt 2>&1" to
the rigctld line.
rigctld --model=3011 --rig-file=/dev/ttyUSB0 --serial-speed=4800 --port=4532
--set-conf=stop_bits=1,dtr_state=ON,rts_state=ON --ptt-file=/dev/ttyUSB1
--ptt-type=RTS -Z >log.txt 2>&1
Then send me the log file.
Mike W9MDB
On Thursday, June 23, 2022 at 08:19:19 AM CDT, Hrafnkell Eiriksson via
wsjt-devel <wsjt-devel@lists.sourceforge.net> wrote:
It works fine when I'm running WSJT-X on the same computer as hamlib rigctld
and I can set it to access the serial port directly for PTT.But in this case
I'm running WSJT-X on Windows but running hamlib rigctld on a Raspberry Pi.
WSJT-X does not have access to the /dev/ttyUSB* on the raspberry pi.The
communication between WSJT-X and hamlib happens over a network. So I'm
expecting the hamlib code in WSJT-X to delegate the PTT to hamlib as a
rig_set_ptt command that then turns into a network message and the rigctld
backend then performs a PTT.
Browsing the code shows that there HamlibTranceiver::do_ptt() does indeed call
rig_set_ptt.
Is it possible that WSJT-X is trying to open a local COM port on windows when
setting up the communication to hamlib even though it is not set to use DTR or
RTS PTT?Could it be that the code still tries to open a local COM port even
though the rig control is set to a network server and PTT is selected as CAT?
Thanks for your help Hrafnkell TF3HR
On Thu, Jun 23, 2022 at 12:06 PM Black Michael via wsjt-devel
<wsjt-devel@lists.sourceforge.net> wrote:
WSJT-X has to be set up to use the same RTS keying and the the /dev/ttyUSB1
port.
Just tested it here and it uses it correctly (though I tested on Windows).
Mike W9MDB
On Thursday, June 23, 2022 at 03:53:35 AM CDT, Hrafnkell Eiriksson via
wsjt-devel <wsjt-devel@lists.sourceforge.net> wrote:
> Why do you have rst_state=ON? That conflicts with ptt-type=RTS and might be
>why it's not working.I have rts_state and dts_state ON to power the CAT
>cable. The --set_conf option only seems to apply to the rig-file device, not
>the ptt device. I can remove the rts_state=ON, it has no effect on PTT
PTT over hamlib is working, it's just WSJT-X that is not using it. I can use
e.g. a voice keyer in Log4OM and it does PTT properly through hamlib.
73 de Hrafnkell TF3HR
On Wed, Jun 22, 2022 at 11:07 PM Black Michael via wsjt-devel
<wsjt-devel@lists.sourceforge.net> wrote:
The 706MKIIG does not do CAT PTT per se but the ptt-type=RTS should work.
Why do you have rst_state=ON? That conflicts with ptt-type=RTS and might be
why it's not working.
And dtr_state=ON would only be needed if your CAT cable needs power from the
computer to work.
Mike W9MDB
On Wednesday, June 22, 2022 at 11:35:27 AM CDT, Hrafnkell Eiriksson via
wsjt-devel <wsjt-devel@lists.sourceforge.net> wrote:
Hi
I'm running WSJT-X v2.5.4 on a Win10 computer.I've set up hamlib rigctld
(version 4.4) on a Raspberry Pi and connected it to my Icom706mk2g.I'm using
two com ports from the RPi, one for CAT control and one for PTT.I've set
WSJT-X to use hamlib for rig control and pointed it to the ip:port of my RPi.
Test CAT works fine and WSJT-X can set and read the frequency if I have PTT
method set to Vox.If I set PTT method to CAT then Test CAT fails with the
error:Rig failureHamlib error: IO errornetwork.c(441):network_close
return(0)iofunc.c(361):port_close return(0)rig.c(1047):rig_open return(-6) IO
errornetwork.c(441):network_close return(0)iofunc.c(361):port_close
return(0)iofunc.c(361):port_close return(0) while opening connection to rig
I can use the hamlib CAT PTT from other software such as Log4OM without
issues.I would expect CAT PTT with hamlib rigcontrol in WSJT-X to behave the
same, that is use hamlib calls to do PTT.
My rigctld command line isrigctld --model=3011 --rig-file=/dev/ttyUSB0
--serial-speed=4800 --port=4532
--set-conf=stop_bits=1,dtr_state=ON,rts_state=ON --ptt-file=/dev/ttyUSB1
--ptt-type=RTS -Z
Am I setting something wrong or misunderstanding something?
Thanks Hrafnkell TF3HR_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
