Hamlib PTT issue seems to be a regression in Hamlib.
I was running Hamlib built from github master. When I built hamlib from the
4.4 release instead of master, PTT works fine over hamlib network
connection.
It was my mistake to oversee that github master was not the latest released
version.
> On the Pi, or any Linux based system, you have to be a member of the
dialout group in order to have access to the serial port. So if all of the
software is being denied access to the serial port, most likely, your not a
member of group dialout.
Thank you for the suggestion Jeff. This is not
When pressing Test CAT a connection is opened from WSJT-X to rigctld and
closed very quickly as WSJT-X displays the error message in my original
email
This is the part of the log after I press Test CAT. I'll send you the log
directly as I do not think the mailing list allows them.
On the Pi, or any Linux based system, you have to be a member of the
dialout group in order to have access to the serial port. So if all of
the software is being denied access to the serial port, most likely,
your not a member of group dialout.
sudo -a -G dialout
Reboot to be safe, but
All 5-v
On Thursday, June 23, 2022 at 09:18:14 AM CDT, Hrafnkell Eiriksson via
wsjt-devel wrote:
I'll get you that log later today. What verbose level do you need on rigctld
(how many v)?
Thanks Hrafnkell TF3HR
On Thu, Jun 23, 2022 at 1:44 PM Black Michael via wsjt-devel
I'll get you that log later today. What verbose level do you need on
rigctld (how many v)?
Thanks
Hrafnkell TF3HR
On Thu, Jun 23, 2022 at 1:44 PM Black Michael via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:
> And if CAT PTT still fails I need to see debug info -- add ">log.txt
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
Then PTT CAT should work. WSJTX should send the "T" command to rigctld and
rigctld then uses the RTS keying.
I just confirmed that works.
2022-06-23T08:37:29.191879-0600: rigctl(d): T 'currVFO' '3' ''
''2022-06-23T08:37:29.191879-0600: rigctl_parse:
vfo_opt=02022-06-23T08:37:29.191879-0600:
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
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 wrote:
> Why do you have
> 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
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
12 matches
Mail list logo
