a-d.s

CHIRP

personal settings for the chirp software

🚧🏗️🚚HTML WORK AHEAD (i) play pause stop 🚧

"CHIRP" on https://aligot-death.space, available at https://aligot-death.space/wiki/chirp-en


Content

Personal settings#

These are settings for the radios and setup I use. It's probably not very useful to anyone else.

Finding which port (Arch Linux)#

To find on which port the radio is connected, open a terminal and type journalctl -f -n 50, to see system log as they happen. Connect the cable, and look at the logs. You should have something like this:

1 Jun 13 01:35:41 niflheim kernel: usb 1-1: new full-speed USB device number 16 using xhci_hcd
2 Jun 13 01:35:42 niflheim kernel: usb 1-1: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice= 2.64
3 Jun 13 01:35:42 niflheim kernel: usb 1-1: New USB device strings: Mfr=0, Product=2, SerialNumber=0
4 Jun 13 01:35:42 niflheim kernel: usb 1-1: Product: USB Serial
5 Jun 13 01:35:42 niflheim kernel: ch341 1-1:1.0: ch341-uart converter detected
6 Jun 13 01:35:42 niflheim kernel: usb 1-1: ch341-uart converter now attached to ttyUSB0

This last line [...] attached to ttyUSB0 is what you're looking for. Either select that option in "port", or select "custom" and enter /dev/ttyUSB0

"Radio did not respond"#

Aside from typical troubleshooting (e.g. cable not seated properly, as it requires way more force than you may think), wrong selection of port can also trigger a Radio did not respond error.

contact

contact

Support

Ko-fi