QLog activates PTT whenever Yaesu FT-450D is connected

[jaymot123]

Rig: Yaesu FT-450D
OS: Linux Mint 21 Wilma
Rig to computer interface: Digirig Mobile RS-232 version with Digirig's TS-480 cables which are also for the FT-450 series radios, also Digirig's coiled, shielded and choked USB A to C cable.
Hamlib version: 4.7-git.2025-09-18T16:08:14Z SHA-D44011 64-bit
QLog version: 0.46.1 built and installed from GitHub
Problem: whenever I connect QLog to the rig, PTT activates. WSJT-X is working normally and only transmits when I tell it to by clicking tune or calling or answering a CQ. Flrig also connects to the radio without activating PTT as QLog does.

I followed the example in the Wiki's Tips & Tricks section for connecting an IC-7300 except selecting Yaesu FT-450D as the rig, selecting the port that appears in /dev/serial/by-id when I plug the USB cable into my computer, and selecting the CAT baud rate that my radio is optioned for (38400.) QLog connects to the rig, but when I look at the radio's display I see that it's transmitting.

My QLog settings for the rig are: interface=Hamlib; enabled rig fearures=mode, freq, power, CS keyer speed, VFO, QSY wiping; port type=serial; port= /dev/serial/by=id/usb-Silicon_Labs_CP2102N_USB_to_UART_Bridge_Controller (and some gobbledegook at the end) which is what appears in /dev when I connect the Digirig's USB cable to the computer; baudrate: 38400; data bits 8; stop bits 1; flow control none; parity no; PTT type CAT (I've also tried setting PTT to none.)

Radio settings are CAT RTS none, CAT TOT 3000, CATRATE 38400.

Originally posted by @jaymot123 in #796

[aa5sh]

as a work around you could launch rigctld and connect to it in QLog. Positive thing also you could connect to it in WSJT at the same time a command similar to this:
rigctld -m 3073 -r /dev/serial/by-id/usb-Silicon_Labs_CP2102N_USB_to_UART_Bridge_Controller -s 38400 --set-conf=rts_state=0,dtr_state=0,serial_handshake=None

In QLog/WSJT you would use something similar to this:

Michael, AA5SH

[jaymot123]

I'm using flrig as middleware as my work-around. I'd just prefer not needing to and just connecting directly to the rig in QLog using hamlib, one less thing to fail that way.

I don't think it's a hamlib issue or it would also happen in WSJT-X, so it must be something in QLog v0.46.1 and it seems to be specific to this rig as QLog (same version and installation) worked seamlessly with my (now-dead) Yaesu FTDX10.

[aa5sh]

I agree it is another option that would need to be exposed in QLog at some point.

…

On Oct 21, 2025, at 9:28 PM, jaymot123 ***@***.***> wrote: jaymot123 left a comment (foldynl/QLog#797) <#797 (comment)> I'm using flrig as middleware as my work-around. I'd just prefer not needing to and just connect directly to the rig in QLog, one less thing to fail that way. I don't think it's a hamlib issue or it would also happen in WSJT-X, so it must be something in QLog v0.46.1 and it seems to be specific to this rig as QLog (same version and installation) worked seamlessly with my (now-dead) Yaesu FTDX10. — Reply to this email directly, view it on GitHub <#797 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AUEEMXWANQ6CNPAZIAIMUM33Y3TT3AVCNFSM6AAAAACJ3ANCYKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTIMZQGI3DAOBWGU>. You are receiving this because you commented.