I have just upgraded hamlib from the fedora 28 repo. This upgraded hamlib from 3.1-11 to 3.3-1. Unfortunately the PTT stopped working. I rolled back to recover the PTT. Here are the symptoms:
I am using primarily wsjt-x but also flrig. The rig is a Kenwood TS570, and I use one USB port for CAT, and another for PTT via RTS, both via identical USB serial converters. I do this because I am a bit cautious and use a physical switch on the rig adapter to allow me to prevent TX unless I really want it! The PTT adapter has an LED showing the RTS state. It does not light when I test the PTT. The serial adapters are FTDI.
[root@localhost ~]# lsusb
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 002: ID 04d9:1702 Holtek Semiconductor, Inc. Keyboard LKS02
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 004: ID 1c4f:0003 SiGma Micro HID controller Bus 003 Device 005: ID 0403:6001 Future Technology Devices International, Ltd FT232 Serial (UART) IC
Bus 003 Device 006: ID 041e:30d3 Creative Technology, Ltd Sound Blaster Play!
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 009 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 008 Device 004: ID 1df7:3000
Bus 008 Device 005: ID 0403:6001 Future Technology Devices International, Ltd FT232 Serial (UART) IC
Bus 008 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 008 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
In wsjt-x, if I set the CAT port to be the serial port connected to the PTT, the RTS light comes on, showing that all the physical connections are good. It just doesn't work when setting it to the PTT function. The CAT port still connects as usual when configured properly.
There were no obvious errors in the logs, and re-installing wsjt-x after removing all its config files didn't help. The hamlib downgrade resolved the issue for now, but presumably it will keep trying to update when I update fedora.
Any thoughts, or logs I can get?
Rgds
Keith
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
can you explain how you switched between versions of Hamlib please? I ask because Hamlib is statically linked into WSJT-X so changing the Hamlib package installed on your system will npt necessarily change the version of Hamlib use by WSJT-X.
73
Bill
G4WJS.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The update was just done through "dnf update" as a regular system update
I'm slightly confused by the symptoms, which is why I looked for some help. I have /dev/ttyUSB1 for CAT and /dev/ttyUSB0 for the PTT, where I use RTS to trigger the PTT via data mode adapter which opto-couples to the back PTT connector on the TS-570. So this doesn't look like a hamlib issue until you look at the symptoms. After the general software update I did, which I do regularly, I lost the PTT. Uninstalling WSJT-X, deleting all its config files and re-installing didn't help. Flrig has lost the PTT too, but I didn't do much work on that because I don't use that regularly. I found that even setting the PTT for CAT in wsjt-x does not work, so no PTT method was available. At this point CAT is up and synching frequency etc. Just for certainty, I even factory defaulted the TS-570 and re-configured the CAT port - no improvement. It was only when out of any other options, I noticed that hamlib was upgraded as part of the software update that I tried downgrading hamlib to the previous version. This is where it all started working again.
Given that the PTT did not work either through CAT or RTS, it was not clear to me whether something was causing wsjt-x to not trigger PTT properly itself, although it thought it was in TX mode by the look of the GUI. And given that it was the hamlib downgrade that fixed this, maybe it was hamlib that provided some influence on the way wsjt-x and flrig were behaving?
Rgds
Keith
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I got a little time on this and determined that the problem only occured with wsjtx if I upgraded hamlib to 3.3-1. Other apps such as flrig could be made to work with hamlib 3-.3-1. Today I updated Fedora again, and this time it installed a new version of wsjtx as well as hamlib 3.3-1. I now have wsjtx 1.9.1-2.fc28 and it now works. So this must be an incompatibility with older wsjtx versions.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have just upgraded hamlib from the fedora 28 repo. This upgraded hamlib from 3.1-11 to 3.3-1. Unfortunately the PTT stopped working. I rolled back to recover the PTT. Here are the symptoms:
I am using primarily wsjt-x but also flrig. The rig is a Kenwood TS570, and I use one USB port for CAT, and another for PTT via RTS, both via identical USB serial converters. I do this because I am a bit cautious and use a physical switch on the rig adapter to allow me to prevent TX unless I really want it! The PTT adapter has an LED showing the RTS state. It does not light when I test the PTT. The serial adapters are FTDI.
[root@localhost ~]# lsusb
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 002: ID 04d9:1702 Holtek Semiconductor, Inc. Keyboard LKS02
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 004: ID 1c4f:0003 SiGma Micro HID controller
Bus 003 Device 005: ID 0403:6001 Future Technology Devices International, Ltd FT232 Serial (UART) IC
Bus 003 Device 006: ID 041e:30d3 Creative Technology, Ltd Sound Blaster Play!
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 009 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 008 Device 004: ID 1df7:3000
Bus 008 Device 005: ID 0403:6001 Future Technology Devices International, Ltd FT232 Serial (UART) IC
Bus 008 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 008 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
In wsjt-x, if I set the CAT port to be the serial port connected to the PTT, the RTS light comes on, showing that all the physical connections are good. It just doesn't work when setting it to the PTT function. The CAT port still connects as usual when configured properly.
There were no obvious errors in the logs, and re-installing wsjt-x after removing all its config files didn't help. The hamlib downgrade resolved the issue for now, but presumably it will keep trying to update when I update fedora.
Any thoughts, or logs I can get?
Rgds
Keith
Hi Keith,
can you explain how you switched between versions of Hamlib please? I ask because Hamlib is statically linked into WSJT-X so changing the Hamlib package installed on your system will npt necessarily change the version of Hamlib use by WSJT-X.
73
Bill
G4WJS.
The update was just done through "dnf update" as a regular system update
I'm slightly confused by the symptoms, which is why I looked for some help. I have /dev/ttyUSB1 for CAT and /dev/ttyUSB0 for the PTT, where I use RTS to trigger the PTT via data mode adapter which opto-couples to the back PTT connector on the TS-570. So this doesn't look like a hamlib issue until you look at the symptoms. After the general software update I did, which I do regularly, I lost the PTT. Uninstalling WSJT-X, deleting all its config files and re-installing didn't help. Flrig has lost the PTT too, but I didn't do much work on that because I don't use that regularly. I found that even setting the PTT for CAT in wsjt-x does not work, so no PTT method was available. At this point CAT is up and synching frequency etc. Just for certainty, I even factory defaulted the TS-570 and re-configured the CAT port - no improvement. It was only when out of any other options, I noticed that hamlib was upgraded as part of the software update that I tried downgrading hamlib to the previous version. This is where it all started working again.
Given that the PTT did not work either through CAT or RTS, it was not clear to me whether something was causing wsjt-x to not trigger PTT properly itself, although it thought it was in TX mode by the look of the GUI. And given that it was the hamlib downgrade that fixed this, maybe it was hamlib that provided some influence on the way wsjt-x and flrig were behaving?
Rgds
Keith
I got a little time on this and determined that the problem only occured with wsjtx if I upgraded hamlib to 3.3-1. Other apps such as flrig could be made to work with hamlib 3-.3-1. Today I updated Fedora again, and this time it installed a new version of wsjtx as well as hamlib 3.3-1. I now have wsjtx 1.9.1-2.fc28 and it now works. So this must be an incompatibility with older wsjtx versions.