Bug #8657
closedrtsystems cable not recognized in Debian 10
0%
Description
Debian 10
CHIRP daily-20201221
GTK 2.24.32
PyGTK 2.24.0
Python 2.7.16
Other USB cables create e.g. /dev/ttyUSB0 device to specify in chirp when downloading from a radio. This has never been a problem when programming Baofeng and Yaesu FT-60R radios.
An expensive rtsystems cable was recently acquired to program a Yaesu FT2DR which is supported in chirp, but the /dev/ttyUSB* device is not created:
$ ls /dev/ttyUSB*
ls: cannot access '/dev/ttyUSB*': No such file or directory
When the USB cable is inserted, a /dev/sdb block device is created:
@$ ls -l /dev/sdb
brw-rw---- 1 root disk 8, 16 Jan 6 10:59 /dev/sdb
@
... but chirp generates an error as shown in the attached png images.
Are rtsystems cables simply non-functional in Linux? It was difficult to find an ordinary USB cable to fit this radio.
Files
| chirp_dev_error.png (14.3 KB) chirp_dev_error.png | Linux /dev/ttyUSB* not created with rtsystems cabling | ||
| chirp_radio_dev.png (9.94 KB) chirp_radio_dev.png |
Updated by Bernhard Hailer over 3 years ago
- Status changed from New to Closed
- Priority changed from Immediate to Normal
Sorry, this isn't a Chirp issue - you may want to contact RTSystems. They have a habit of making their cables proprietary and often incompatible with non-RTSystems software.