- Users - lists.chirpmyradio.com

New chirp-next build
by donotreply＠chirpmyradio.com 28 Feb '25

28 Feb '25

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since the last build and may include additional features, bug fixes, etc. Unless you have a reason not to, we recommend using the latest build of CHIRP-next at all times. You can get it from here: https://www.chirpmyradio.com/projects/chirp/wiki/Download A list of changes since the last build are here: f2d7622b Updated Spanish Translation a03a7701 Added Romanian translation de69bb24 Update MURS stock config with power levels 729c075d Add TX-frequency workflow option for memory editor 72cf0709 Move port recall and prompts to per-radio config 8676ff8e Add registered_class() to directory and per-radio config 7b2a50bb tk8180: Use tk280's subdev generator metaclass b5dfe7be tk280: Refactor subdev metaclass generator e8764347 Add TH-888S model alias 90561777 tk8180: Fix Zone Dn, LCD Bright button functions e3163e17 Make memedit copy and paste in TSV format 7972d1ba Add routine for parsing TSV from pasted data f86ce46f csv: Refactor to support TSV read/write Issues addressed in this build: [Bug 11861] US MURS CHANNELS [Feature 11843] Improved copy-and-paste between CHIRP and spreadsheets [Feature 11859] Provide a RX/TX frequency workflow like commercial users expect [New Model 11849] Baofeng TH-888S --

2 1

Can you use CHIRP on a MAC?
by James Henry 28 Feb '25

28 Feb '25

Can you use CHIRP on a MAC? If yes what is the process. If no when will it be available? James Henry James B. Henry 707-255-9393 707-738-4205 cell jimhenry707(a)gmail.com WB6ZZR

4 3

TID H3 Can't Paste
by K0LNY ?? 21 Feb '25

21 Feb '25

Hi, I thought I had done this before in Windows, because I put a lot of memories into my H3 before. So I needed to edit a few fields, and I downloaded from my radio, and exported that to CSV. Then I edited my fields in Open Office Calc and saved that. Then I selected everything in there, and copied it. Then I went to the Chirp that I downloaded and selected all and deleted it, and pasted into the Chirp window, and only Memory #1 will go into the Chirp. I tried a new window in chirp to paste into there, and still, only one line is going in. What am I doing wrong? I hate that we cannot import a CSV any more, like we used to do. Thanks for any help. Glenn Being smart is knowing how to get out of a tough situation. Being wise is not getting into it in the first place. Glenn K0LNY & WSAT439

7 15

New chirp-next build
by donotreply＠chirpmyradio.com 21 Feb '25

21 Feb '25

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since the last build and may include additional features, bug fixes, etc. Unless you have a reason not to, we recommend using the latest build of CHIRP-next at all times. You can get it from here: https://www.chirpmyradio.com/projects/chirp/wiki/Download A list of changes since the last build are here: 0d84388e Try to parse TSV lines from a paste e1d8dd31 new sources mapy73.pl 6fd83334 Fix getting grid cursor on wx 4.0.x 3f19f720 uv17pro: Avoid decode crash on garbage names 306814f8 Fix insert row missing undo action coverage Issues addressed in this build: [Bug 11831] No undo context for action! [Bug 11841] gb2312 codec error accessing Settings [New Model 11840] Baofeng DM-UV32 --

1 0

Yaesu 857d Download from Radio Not Working
by galen.fitzpatrick＠gmail.com 20 Feb '25

20 Feb '25

857d Digirig CHIRP-next 20250214 Ubuntu 24.04 CHIRP sees the USB connection and starts the download. Send on the radio's end finishes with progress bar almost complete on CHIRP. After a few seconds, I get an error message stating: RadioError: Failed to communicate with radio: Unable to read last block. This often happens when the selected model is US but the radio is a non-US one (or widebanded). Please choose the correct model and try again. I have reset the radio. I have unplugged and plugged the Digirig interface back in. I have tried an alternate CAT cable. Both Digirig and the alternate CAT cable have worked with previous versions of the software. As a complicating factor, between the old versions and this one, I reinstalled ubuntu 24.04 Debug Log Follows. I'll admit I never had to look in the debug log before, has the 857 always used the 817 drivers? Galen KC3ZEN [2025-02-19 21:54:53,156] chirp.logger - DEBUG: CHIRP next-20250214 on Linux - Ubuntu 24.04.2 LTS (Python 3.12.3) [2025-02-19 21:54:53,320] chirp.wxui - DEBUG: Using locale: en_US (276) [2025-02-19 21:54:53,328] chirp.wxui - DEBUG: Translation loaded=True for CHIRP: en_US (ja_JP,es,hu,pt_BR,el,uk_UA,nl,tr_TR,de,fr,it,en_US,bg_BG,ru,zh_CN,pl) from /home/kc3zen/.local/share/pipx/venvs/chirp/lib/python3.12/site-packages/chirp/locale [2025-02-19 21:54:53,336] chirp.wxui - DEBUG: Translation loaded=False for wxstd: en (an,vi,eu,pt,ar,zh_TW,uk,ko_KR,gl_ES,hr,ta,cs,ca@valencia,ka,hi,fa_IR,tr,sl,ja,es,hu,pt_BR,el,ca,ne,fi,nl,sr,sv,ms,co,sq,lt,af,de,da,fr,it,ro,ru,zh_CN,pl,sk,nb,id,lv) [2025-02-19 21:54:53,610] main - INFO: Python/3.12.3 // Linux/Linux-6.8.0-52-generic-x86_64-with-glibc2.39 // CHIRP/next-20250214 // wx/4.2.1 gtk3 (phoenix) wxWidgets 3.2.4 [2025-02-19 21:54:53,620] chirp.wxui.main - DEBUG: Recent is now ['/home/kc3zen/Documents/Radios/QRZ1.img', '/home/kc3zen/.local/share/pipx/venvs/chirp/lib/python3.12/site-packages/chirp/stock_configs/US Calling Frequencies.csv'] [2025-02-19 21:54:53,650] chirp.wxui - DEBUG: Desktop file exists [2025-02-19 21:54:53,827] chirp.wxui.main - INFO: Server reports next-20250214 is latest [2025-02-19 21:55:09,588] chirp.wxui.clone - DEBUG: All system ports: [{'device': '/dev/ttyS0', 'name': 'ttyS0', 'description': 'n/a', 'hwid': 'n/a', 'vid': None, 'pid': None, 'serial_number': None, 'location': None, 'manufacturer': None, 'product': None, 'interface': None, 'usb_device_path': None, 'device_path': '/sys/devices/platform/serial8250/serial8250:0/serial8250:0.0', 'subsystem': 'serial-base', 'usb_interface_path': None}, {'device': '/dev/ttyS1', 'name': 'ttyS1', 'description': 'n/a', 'hwid': 'n/a', 'vid': None, 'pid': None, 'serial_number': None, 'location': None, 'manufacturer': None, 'product': None, 'interface': None, 'usb_device_path': None, 'device_path': '/sys/devices/platform/serial8250/serial8250:0/serial8250:0.1', 'subsystem': 'serial-base', 'usb_interface_path': None}, {'device': '/dev/ttyS2', 'name': 'ttyS2', 'description': 'n/a', 'hwid': 'n/a', 'vid': None, 'pid': None, 'serial_number': None, 'location': None, 'manufacturer': None, 'product': None, 'interface': None, 'usb_device_path': None, 'device_path': '/sys/devices/platform/serial8250/serial8250:0/serial8250:0.2', 'subsystem': 'serial-base', 'usb_interface_path': None}, {'device': '/dev/ttyS3', 'name': 'ttyS3', 'description': 'n/a', 'hwid': 'n/a', 'vid': None, 'pid': None, 'serial_number': None, 'location': None, 'manufacturer': None, 'product': None, 'interface': None, 'usb_device_path': None, 'device_path': '/sys/devices/platform/serial8250/serial8250:0/serial8250:0.3', 'subsystem': 'serial-base', 'usb_interface_path': None}, {'device': '/dev/ttyS4', 'name': 'ttyS4', 'description': 'n/a', 'hwid': 'n/a', 'vid': None, 'pid': None, 'serial_number': None, 'location': None, 'manufacturer': None, 'product': None, 'interface': None, 'usb_device_path': None, 'device_path': '/sys/devices/platform/serial8250/serial8250:0/serial8250:0.4', 'subsystem': 'serial-base', 'usb_interface_path': None}, {'device': '/dev/ttyS5', 'name': 'ttyS5', 'description': 'n/a', 'hwid': 'n/a', 'vid': None, 'pid': None, 'serial_number': None, 'location': None, 'manufacturer': None, 'product': None, 'interface': None, 'usb_device_path': None, 'device_path': '/sys/devices/platform/serial8250/serial8250:0/serial8250:0.5', 'subsystem': 'serial-base', 'usb_interface_path': None}, {'device': '/dev/ttyS6', 'name': 'ttyS6', 'description': 'n/a', 'hwid': 'n/a', 'vid': None, 'pid': None, 'serial_number': None, 'location': None, 'manufacturer': None, 'product': None, 'interface': None, 'usb_device_path': None, 'device_path': '/sys/devices/platform/serial8250/serial8250:0/serial8250:0.6', 'subsystem': 'serial-base', 'usb_interface_path': None}, {'device': '/dev/ttyS7', 'name': 'ttyS7', 'description': 'n/a', 'hwid': 'n/a', 'vid': None, 'pid': None, 'serial_number': None, 'location': None, 'manufacturer': None, 'product': None, 'interface': None, 'usb_device_path': None, 'device_path': '/sys/devices/platform/serial8250/serial8250:0/serial8250:0.7', 'subsystem': 'serial-base', 'usb_interface_path': None}, {'device': '/dev/ttyS8', 'name': 'ttyS8', 'description': 'n/a', 'hwid': 'n/a', 'vid': None, 'pid': None, 'serial_number': None, 'location': None, 'manufacturer': None, 'product': None, 'interface': None, 'usb_device_path': None, 'device_path': '/sys/devices/platform/serial8250/serial8250:0/serial8250:0.8', 'subsystem': 'serial-base', 'usb_interface_path': None}, {'device': '/dev/ttyS9', 'name': 'ttyS9', 'description': 'n/a', 'hwid': 'n/a', 'vid': None, 'pid': None, 'serial_number': None, 'location': None, 'manufacturer': None, 'product': None, 'interface': None, 'usb_device_path': None, 'device_path': '/sys/devices/platform/serial8250/serial8250:0/serial8250:0.9', 'subsystem': 'serial-base', 'usb_interface_path': None}, {'device': '/dev/ttyS10', 'name': 'ttyS10', 'description': 'n/a', 'hwid': 'n/a', 'vid': None, 'pid': None, 'serial_number': None, 'location': None, 'manufacturer': None, 'product': None, 'interface': None, 'usb_device_path': None, 'device_path': '/sys/devices/platform/serial8250/serial8250:0/serial8250:0.10', 'subsystem': 'serial-base', 'usb_interface_path': None}, {'device': '/dev/ttyS11', 'name': 'ttyS11', 'description': 'n/a', 'hwid': 'n/a', 'vid': None, 'pid': None, 'serial_number': None, 'location': None, 'manufacturer': None, 'product': None, 'interface': None, 'usb_device_path': None, 'device_path': '/sys/devices/platform/serial8250/serial8250:0/serial8250:0.11', 'subsystem': 'serial-base', 'usb_interface_path': None}, {'device': '/dev/ttyS12', 'name': 'ttyS12', 'description': 'n/a', 'hwid': 'n/a', 'vid': None, 'pid': None, 'serial_number': None, 'location': None, 'manufacturer': None, 'product': None, 'interface': None, 'usb_device_path': None, 'device_path': '/sys/devices/platform/serial8250/serial8250:0/serial8250:0.12', 'subsystem': 'serial-base', 'usb_interface_path': None}, {'device': '/dev/ttyS13', 'name': 'ttyS13', 'description': 'n/a', 'hwid': 'n/a', 'vid': None, 'pid': None, 'serial_number': None, 'location': None, 'manufacturer': None, 'product': None, 'interface': None, 'usb_device_path': None, 'device_path': '/sys/devices/platform/serial8250/serial8250:0/serial8250:0.13', 'subsystem': 'serial-base', 'usb_interface_path': None}, {'device': '/dev/ttyS14', 'name': 'ttyS14', 'description': 'n/a', 'hwid': 'n/a', 'vid': None, 'pid': None, 'serial_number': None, 'location': None, 'manufacturer': None, 'product': None, 'interface': None, 'usb_device_path': None, 'device_path': '/sys/devices/platform/serial8250/serial8250:0/serial8250:0.14', 'subsystem': 'serial-base', 'usb_interface_path': None}, {'device': '/dev/ttyS15', 'name': 'ttyS15', 'description': 'n/a', 'hwid': 'n/a', 'vid': None, 'pid': None, 'serial_number': None, 'location': None, 'manufacturer': None, 'product': None, 'interface': None, 'usb_device_path': None, 'device_path': '/sys/devices/platform/serial8250/serial8250:0/serial8250:0.15', 'subsystem': 'serial-base', 'usb_interface_path': None}, {'device': '/dev/ttyS16', 'name': 'ttyS16', 'description': 'n/a', 'hwid': 'n/a', 'vid': None, 'pid': None, 'serial_number': None, 'location': None, 'manufacturer': None, 'product': None, 'interface': None, 'usb_device_path': None, 'device_path': '/sys/devices/platform/serial8250/serial8250:0/serial8250:0.16', 'subsystem': 'serial-base', 'usb_interface_path': None}, {'device': '/dev/ttyS17', 'name': 'ttyS17', 'description': 'n/a', 'hwid': 'n/a', 'vid': None, 'pid': None, 'serial_number': None, 'location': None, 'manufacturer': None, 'product': None, 'interface': None, 'usb_device_path': None, 'device_path': '/sys/devices/platform/serial8250/serial8250:0/serial8250:0.17', 'subsystem': 'serial-base', 'usb_interface_path': None}, {'device': '/dev/ttyS18', 'name': 'ttyS18', 'description': 'n/a', 'hwid': 'n/a', 'vid': None, 'pid': None, 'serial_number': None, 'location': None, 'manufacturer': None, 'product': None, 'interface': None, 'usb_device_path': None, 'device_path': '/sys/devices/platform/serial8250/serial8250:0/serial8250:0.18', 'subsystem': 'serial-base', 'usb_interface_path': None}, {'device': '/dev/ttyS19', 'name': 'ttyS19', 'description': 'n/a', 'hwid': 'n/a', 'vid': None, 'pid': None, 'serial_number': None, 'location': None, 'manufacturer': None, 'product': None, 'interface': None, 'usb_device_path': None, 'device_path': '/sys/devices/platform/serial8250/serial8250:0/serial8250:0.19', 'subsystem': 'serial-base', 'usb_interface_path': None}, {'device': '/dev/ttyS20', 'name': 'ttyS20', 'description': 'n/a', 'hwid': 'n/a', 'vid': None, 'pid': None, 'serial_number': None, 'location': None, 'manufacturer': None, 'product': None, 'interface': None, 'usb_device_path': None, 'device_path': '/sys/devices/platform/serial8250/serial8250:0/serial8250:0.20', 'subsystem': 'serial-base', 'usb_interface_path': None}, {'device': '/dev/ttyS21', 'name': 'ttyS21', 'description': 'n/a', 'hwid': 'n/a', 'vid': None, 'pid': None, 'serial_number': None, 'location': None, 'manufacturer': None, 'product': None, 'interface': None, 'usb_device_path': None, 'device_path': '/sys/devices/platform/serial8250/serial8250:0/serial8250:0.21', 'subsystem': 'serial-base', 'usb_interface_path': None}, {'device': '/dev/ttyS22', 'name': 'ttyS22', 'description': 'n/a', 'hwid': 'n/a', 'vid': None, 'pid': None, 'serial_number': None, 'location': None, 'manufacturer': None, 'product': None, 'interface': None, 'usb_device_path': None, 'device_path': '/sys/devices/platform/serial8250/serial8250:0/serial8250:0.22', 'subsystem': 'serial-base', 'usb_interface_path': None}, {'device': '/dev/ttyS23', 'name': 'ttyS23', 'description': 'n/a', 'hwid': 'n/a', 'vid': None, 'pid': None, 'serial_number': None, 'location': None, 'manufacturer': None, 'product': None, 'interface': None, 'usb_device_path': None, 'device_path': '/sys/devices/platform/serial8250/serial8250:0/serial8250:0.23', 'subsystem': 'serial-base', 'usb_interface_path': None}, {'device': '/dev/ttyS24', 'name': 'ttyS24', 'description': 'n/a', 'hwid': 'n/a', 'vid': None, 'pid': None, 'serial_number': None, 'location': None, 'manufacturer': None, 'product': None, 'interface': None, 'usb_device_path': None, 'device_path': '/sys/devices/platform/serial8250/serial8250:0/serial8250:0.24', 'subsystem': 'serial-base', 'usb_interface_path': None}, {'device': '/dev/ttyS25', 'name': 'ttyS25', 'description': 'n/a', 'hwid': 'n/a', 'vid': None, 'pid': None, 'serial_number': None, 'location': None, 'manufacturer': None, 'product': None, 'interface': None, 'usb_device_path': None, 'device_path': '/sys/devices/platform/serial8250/serial8250:0/serial8250:0.25', 'subsystem': 'serial-base', 'usb_interface_path': None}, {'device': '/dev/ttyS26', 'name': 'ttyS26', 'description': 'n/a', 'hwid': 'n/a', 'vid': None, 'pid': None, 'serial_number': None, 'location': None, 'manufacturer': None, 'product': None, 'interface': None, 'usb_device_path': None, 'device_path': '/sys/devices/platform/serial8250/serial8250:0/serial8250:0.26', 'subsystem': 'serial-base', 'usb_interface_path': None}, {'device': '/dev/ttyS27', 'name': 'ttyS27', 'description': 'n/a', 'hwid': 'n/a', 'vid': None, 'pid': None, 'serial_number': None, 'location': None, 'manufacturer': None, 'product': None, 'interface': None, 'usb_device_path': None, 'device_path': '/sys/devices/platform/serial8250/serial8250:0/serial8250:0.27', 'subsystem': 'serial-base', 'usb_interface_path': None}, {'device': '/dev/ttyS28', 'name': 'ttyS28', 'description': 'n/a', 'hwid': 'n/a', 'vid': None, 'pid': None, 'serial_number': None, 'location': None, 'manufacturer': None, 'product': None, 'interface': None, 'usb_device_path': None, 'device_path': '/sys/devices/platform/serial8250/serial8250:0/serial8250:0.28', 'subsystem': 'serial-base', 'usb_interface_path': None}, {'device': '/dev/ttyS29', 'name': 'ttyS29', 'description': 'n/a', 'hwid': 'n/a', 'vid': None, 'pid': None, 'serial_number': None, 'location': None, 'manufacturer': None, 'product': None, 'interface': None, 'usb_device_path': None, 'device_path': '/sys/devices/platform/serial8250/serial8250:0/serial8250:0.29', 'subsystem': 'serial-base', 'usb_interface_path': None}, {'device': '/dev/ttyS30', 'name': 'ttyS30', 'description': 'n/a', 'hwid': 'n/a', 'vid': None, 'pid': None, 'serial_number': None, 'location': None, 'manufacturer': None, 'product': None, 'interface': None, 'usb_device_path': None, 'device_path': '/sys/devices/platform/serial8250/serial8250:0/serial8250:0.30', 'subsystem': 'serial-base', 'usb_interface_path': None}, {'device': '/dev/ttyS31', 'name': 'ttyS31', 'description': 'n/a', 'hwid': 'n/a', 'vid': None, 'pid': None, 'serial_number': None, 'location': None, 'manufacturer': None, 'product': None, 'interface': None, 'usb_device_path': None, 'device_path': '/sys/devices/platform/serial8250/serial8250:0/serial8250:0.31', 'subsystem': 'serial-base', 'usb_interface_path': None}, {'device': '/dev/ttyUSB0', 'name': 'ttyUSB0', 'description': 'CP2102N USB to UART Bridge Controller', 'hwid': 'USB VID:PID=10C4:EA60 SER=8a7644e726bded11880a315838a92db5 LOCATION=1-5.1', 'vid': 4292, 'pid': 60000, 'serial_number': '8a7644e726bded11880a315838a92db5', 'location': '1-5.1', 'manufacturer': 'Silicon Labs', 'product': 'CP2102N USB to UART Bridge Controller', 'interface': None, 'usb_device_path': '/sys/devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5.1', 'device_path': '/sys/devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5.1/1-5.1:1.0/ttyUSB0', 'subsystem': 'usb-serial', 'usb_interface_path': '/sys/devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5.1/1-5.1:1.0'}] [2025-02-19 21:55:09,601] chirp.wxui.clone - DEBUG: Automatically chose port /dev/ttyUSB0 as it is last-used for Yaesu:FT-857/897 (US) [2025-02-19 21:55:14,799] chirp.wxui.clone - DEBUG: Using port '/dev/ttyUSB0' [2025-02-19 21:55:14,799] chirp.wxui.clone - DEBUG: Selected <class 'chirp.drivers.ft857.FT857USRadio'> [2025-02-19 21:55:14,804] chirp.wxui.clone - DEBUG: Prompt pre_download disabled for radio [2025-02-19 21:55:14,807] chirp.wxui.clone - DEBUG: Serial opened: Serial<id=0x7851a07572b0, open=True>(port='/dev/ttyUSB0', baudrate=9600, bytesize=8, parity='N', stopbits=1, timeout=0.25, xonxoff=False, rtscts=False, dsrdtr=False) (rts=True dtr=True) [2025-02-19 21:55:14,807] chirp.wxui.clone - DEBUG: Recorded last-used port /dev/ttyUSB0 for Yaesu:FT-857/897 (US) [2025-02-19 21:55:16,001] chirp.drivers.ft817 - DEBUG: Read 2 [2025-02-19 21:55:16,103] chirp.drivers.ft817 - DEBUG: Read 82 [2025-02-19 21:55:16,409] chirp.drivers.ft817 - DEBUG: Read 252 [2025-02-19 21:55:16,647] chirp.drivers.ft817 - DEBUG: Read 196 [2025-02-19 21:55:16,952] chirp.drivers.ft817 - DEBUG: Read 252 [2025-02-19 21:55:17,189] chirp.drivers.ft817 - DEBUG: Read 196 [2025-02-19 21:55:17,447] chirp.drivers.ft817 - DEBUG: Read 212 [2025-02-19 21:55:17,518] chirp.drivers.ft817 - DEBUG: Read 55 [2025-02-19 21:55:17,691] chirp.drivers.ft817 - DEBUG: Read 140 [2025-02-19 21:55:17,864] chirp.drivers.ft817 - DEBUG: Read 140 [2025-02-19 21:55:18,037] chirp.drivers.ft817 - DEBUG: Read 140 [2025-02-19 21:55:18,210] chirp.drivers.ft817 - DEBUG: Read 140 [2025-02-19 21:55:18,383] chirp.drivers.ft817 - DEBUG: Read 140 [2025-02-19 21:55:18,556] chirp.drivers.ft817 - DEBUG: Read 140 [2025-02-19 21:55:18,729] chirp.drivers.ft817 - DEBUG: Read 140 [2025-02-19 21:55:18,903] chirp.drivers.ft817 - DEBUG: Read 140 [2025-02-19 21:55:19,076] chirp.drivers.ft817 - DEBUG: Read 140 [2025-02-19 21:55:19,249] chirp.drivers.ft817 - DEBUG: Read 140 [2025-02-19 21:55:19,422] chirp.drivers.ft817 - DEBUG: Read 140 [2025-02-19 21:55:19,595] chirp.drivers.ft817 - DEBUG: Read 140 [2025-02-19 21:55:19,768] chirp.drivers.ft817 - DEBUG: Read 140 [2025-02-19 21:55:19,941] chirp.drivers.ft817 - DEBUG: Read 140 [2025-02-19 21:55:20,114] chirp.drivers.ft817 - DEBUG: Read 140 [2025-02-19 21:55:20,287] chirp.drivers.ft817 - DEBUG: Read 140 [2025-02-19 21:55:20,460] chirp.drivers.ft817 - DEBUG: Read 140 [2025-02-19 21:55:20,633] chirp.drivers.ft817 - DEBUG: Read 140 [2025-02-19 21:55:20,806] chirp.drivers.ft817 - DEBUG: Read 140 [2025-02-19 21:55:20,979] chirp.drivers.ft817 - DEBUG: Read 140 [2025-02-19 21:55:21,152] chirp.drivers.ft817 - DEBUG: Read 140 [2025-02-19 21:55:21,325] chirp.drivers.ft817 - DEBUG: Read 140 [2025-02-19 21:55:21,498] chirp.drivers.ft817 - DEBUG: Read 140 [2025-02-19 21:55:21,671] chirp.drivers.ft817 - DEBUG: Read 140 [2025-02-19 21:55:21,844] chirp.drivers.ft817 - DEBUG: Read 140 [2025-02-19 21:55:22,017] chirp.drivers.ft817 - DEBUG: Read 140 [2025-02-19 21:55:22,190] chirp.drivers.ft817 - DEBUG: Read 140 [2025-02-19 21:55:22,363] chirp.drivers.ft817 - DEBUG: Read 140 [2025-02-19 21:55:22,536] chirp.drivers.ft817 - DEBUG: Read 140 [2025-02-19 21:55:22,709] chirp.drivers.ft817 - DEBUG: Read 140 [2025-02-19 21:55:22,882] chirp.drivers.ft817 - DEBUG: Read 140 [2025-02-19 21:55:23,055] chirp.drivers.ft817 - DEBUG: Read 140 [2025-02-19 21:55:23,228] chirp.drivers.ft817 - DEBUG: Read 140 [2025-02-19 21:55:23,401] chirp.drivers.ft817 - DEBUG: Read 140 [2025-02-19 21:55:23,574] chirp.drivers.ft817 - DEBUG: Read 140 [2025-02-19 21:55:23,747] chirp.drivers.ft817 - DEBUG: Read 140 [2025-02-19 21:55:23,920] chirp.drivers.ft817 - DEBUG: Read 140 [2025-02-19 21:55:24,093] chirp.drivers.ft817 - DEBUG: Read 140 [2025-02-19 21:55:24,266] chirp.drivers.ft817 - DEBUG: Read 140 [2025-02-19 21:55:24,439] chirp.drivers.ft817 - DEBUG: Read 140 [2025-02-19 21:55:24,612] chirp.drivers.ft817 - DEBUG: Read 140 [2025-02-19 21:55:24,786] chirp.drivers.ft817 - DEBUG: Read 140 [2025-02-19 21:55:24,839] chirp.drivers.ft817 - DEBUG: Read 38 [2025-02-19 21:55:25,055] chirp.drivers.ft817 - DEBUG: Read 176 [2025-02-19 21:55:37,565] chirp.wxui.clone - ERROR: Failed to clone: Failed to communicate with radio: Unable to read last block. This often happens when the selected model is US but the radio is a non-US one (or widebanded). Please choose the correct model and try again. Traceback (most recent call last): File "/home/kc3zen/.local/share/pipx/venvs/chirp/lib/python3.12/site-packages/chirp/drivers/ft817.py", line 416, in sync_in self._mmap = self._clone_in() ^^^^^^^^^^^^^^^^ File "/home/kc3zen/.local/share/pipx/venvs/chirp/lib/python3.12/site-packages/chirp/drivers/ft817.py", line 351, in _clone_in data += self._read(block, blocks, blocks == nblocks - 1) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/kc3zen/.local/share/pipx/venvs/chirp/lib/python3.12/site-packages/chirp/drivers/ft817.py", line 320, in _read raise Exception(_("Unable to read last block. " Exception: Unable to read last block. This often happens when the selected model is US but the radio is a non-US one (or widebanded). Please choose the correct model and try again. During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/home/kc3zen/.local/share/pipx/venvs/chirp/lib/python3.12/site-packages/chirp/wxui/clone.py", line 94, in run self._fn() File "/home/kc3zen/.local/share/pipx/venvs/chirp/lib/python3.12/site-packages/chirp/drivers/ft817.py", line 420, in sync_in raise errors.RadioError("Failed to communicate with radio: %s" % e) chirp.errors.RadioError: Failed to communicate with radio: Unable to read last block. This often happens when the selected model is US but the radio is a non-US one (or widebanded). Please choose the correct model and try again. [2025-02-19 21:55:46,452] chirp.wxui.clone - WARNING: Stopping clone thread

2 1

Radtel RT900
by Milton Garb 20 Feb '25

20 Feb '25

May I ask what Radtel software I can use to program this radio?And is there any special cable required?Tnx,de N6MG

1 0

New chirp-next build
by donotreply＠chirpmyradio.com 14 Feb '25

14 Feb '25

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since the last build and may include additional features, bug fixes, etc. Unless you have a reason not to, we recommend using the latest build of CHIRP-next at all times. You can get it from here: https://www.chirpmyradio.com/projects/chirp/wiki/Download A list of changes since the last build are here: 32167019 Make UI avoid re-deleting memories for cut/paste ba282a76 tk481: Fix re-deleting memory corrupting data structures 894d9347 tk481: Properly strip non-space padding 9e433523 rh5rv2: Convert to py3 a62f2b31 icf.py: Replace numeric literals where names have already been defined 0d4d665a chore: remove last use of future a64a53a5 Updated Italian Translation 2eeb3db0 Add Baofeng P15UV alias a7d05a48 Prevent reporting to closed bugs 7606aa5a Add undo/redo support for memory editor 2115a41c Avoid showing temporary and hidden stock files 1c55830e Updated Italian Translation Issues addressed in this build: [Bug 11810] Rugged Radio RH5R-V2 in Chirp-next? [Bug 11826] Priority channel [New Model 11814] Baofeng P15UV --

4 4

MUTERA TM 1000 - 16 CHANNEL
by mamasdigital＠gmail.com 14 Feb '25

14 Feb '25

I have Mutera TM 1000. I hope, can get the CHIRP modul of this seri of radio. I want to change the frequencies of this radio

1 0

New chirp-next build
by donotreply＠chirpmyradio.com 07 Feb '25

07 Feb '25

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since the last build and may include additional features, bug fixes, etc. Unless you have a reason not to, we recommend using the latest build of CHIRP-next at all times. You can get it from here: https://www.chirpmyradio.com/projects/chirp/wiki/Download A list of changes since the last build are here: 3082a03e tk280: Factor out some things to enable v1 support 1b65b2ac tk280: Fix scan/skip setting 336210b3 tk280: Fix DAT file detection when extension is capitalized 8c42811e Updated Spanish Translation c4d1ec32 Enable validate_all_steps test for all, except some failing drivers b0c2988d uv5r: Remove invalid 1kHz step channels from sample image 83231261 ga510: Remove obviously-invalid channel from sample image 03c5597e tk690: Expose proper PLL steps for 690,790,890 c1e88001 ft450: Mark as nostep_tuning because 1Hz tuning 05efb58b icx90: Fix missing tuning steps for TV memories d7dafa0b Clean up yaesu_clone transmit echo munching 69862679 vx7: Fix sample image with invalid frequencies b8a20b09 Add test to validate_memory() all channels in test images fcc6491f Add "include cached" toggle for RepeaterBook query b9fa31fa Add accelerator key for RepeaterBook query a243702e tk481: Add call flag to mem.extra 77c75527 Reload dynamic-subdev editors when volatile settings change 70113221 Add dynamic subdevices feature flag df4ed4a1 Add string hex editing in browser 6802d670 Flatten browser UI and add addresses to elements d506feb4 icf520: Add tuning steps 7cd2503b icf520: Clarify display inhibit and tx inhibit 270b3d88 anytone: Add PTTID setting a5d508a1 Fix bitwise BCD int/float error febde821 fix retevis rb626 support b73f8ad7 Added Icom IC-7410 Issues addressed in this build: [Bug 11811] Unable To Paste Valid Frequency [Feature 11798] Add ability to program DTMF PTT-ID [Feature 11803] RepeaterBook proximity query unable to return multi-state results [New Model 11795] ICOM IC-7410 --

1 0

P15UV
by Massimo Nespolo 06 Feb '25

06 Feb '25

Greetings, In the list of supported radio, I do not see the Baofeng/Pofung P15UV https://www.chirpmyradio.com/projects/chirp/wiki/Home https://www.manualslib.com/manual/2389725/Pofung-P15uv.html https://www.anyradios.com/product/baofeng-p15uv-radio/ According to Miklor, it should use the same factory software as the UV-17 Pro or UV-13 / UV-22 https://www.miklor.com/COM/UV_Software.php I wonder if choosing these models in CHIRP will also work. I haven't received the radio and I see in the archives a thread from a few months ago, without a definite answer: https://lists.chirpmyradio.com/hyperkitty/list/users@lists.chirpmyradio.com… Maybe in the meanwhile others have found which alternative model works best? Thank you in advance for your suggestions. Massimo Nespolo, from France.

1 1

Yaesu FT1500m Programming
by Drake Rebar 01 Feb '25

01 Feb '25

I have the cable and can get the radio into programming mode, and I'm running the latest CHIRP software on my computer. I've got the right port selected but when I hit transmit to clone the radio over to the CHIRP software, I get an error on the radio and a no response from the radio on the software. There is not much documentation on this that I am able to find. Is there a fix for this or something I have missed? Thank you in advance!

2 1

RB17P Programming Error
by Chris Hosman 01 Feb '25

01 Feb '25

I have a new RB-17P GMRS radio that I'm trying to program. When I try to download from the radio I get a "Radio refused to enter programming mode" error message. Any suggestions? - Chris <>< KC4F Note: if you receive an attachment from me titled "winmail.dat" please ignore it. This is Microsoft email formatting information and not relevant to my message. [sent from the web]

2 1

New chirp-next build
by donotreply＠chirpmyradio.com 31 Jan '25

31 Jan '25

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since the last build and may include additional features, bug fixes, etc. Unless you have a reason not to, we recommend using the latest build of CHIRP-next at all times. You can get it from here: https://archive.chirpmyradio.com/chirp_next/next-20250131 A list of changes since the last build are here: 5f667291 Add support for Icom IC-F621 76af7922 Add Kenwood TK-981 679b5325 tk280: Fix padding ponmsg with 0xFF instead of spaces 62b277ea Encourage user to actually fill out bug reports 4845706c Add some missing-element tests for bitwise bea921ce Updated Spanish Translation e3e6994f tk481: Add Kenwood TK-481 radio 13463c38 Fix bitwise hex count values and array of zero d5ce1f9c tk280: Refactor internals to work with tk481 a1dfb3f4 tk8180: Remove hackaround bitwise array-of-one bug 39a30a90 Fix long-standing bitwise array-of-one bug aa6e7ff8 Fix always choosing mode FM even if unsupported 4ba46b50 Fix reloading driver keeping the same UI tab 02b5e297 Remember last-used port by model b3d5df84 Allow changing setting/group display names 4e5de794 Fixed a typo ccdd7588 Updated Italian Translation d00cdfa5 Fix sorting columns on linux Issues addressed in this build: [Bug 11793] error message when sorting [Feature 11797] Remember COM port in Recent [New Model 11490] Icom IC-F521 [New Model 11802] Kenwood TK-981 [New Model 6505] Icom IC-F621-2 --

1 0

Airport Freqs
by CN7 30 Jan '25

30 Jan '25

How does one imput freqs for an airport? Rockhampton QLD Aussie Tower freq is 118.1Mhz - BUT I do NOT want it to accidently tx on it. So, how does one, block TX mode? rgrds n 73

3 11

Chirp 20250124 ==> Yaesu FT-70D fail to communicate with the radio
by Stéphane BOUTEILLER 28 Jan '25

28 Jan '25

Hello I got this error on a mac since the last update of shirp, any ideas ? [2025-01-28 19:39:01,364] chirp.wxui.main - DEBUG: Recent is now [] [2025-01-28 19:39:01,713] chirp.wxui.main - INFO: Server reports next-20250124 is latest [2025-01-28 19:39:56,450] chirp.wxui.clone - DEBUG: All system ports: [{'device': '/dev/cu.Bluetooth-Incoming-Port', 'name': 'cu.Bluetooth-Incoming-Port', 'description': 'n/a', 'hwid': 'n/a', 'vid': None, 'pid': None, 'serial_number': None, 'location': None, 'manufacturer': None, 'product': None, 'interface': None}, {'device': '/dev/cu.usbmodem0000000000001', 'name': 'cu.usbmodem0000000000001', 'description': 'IOUSBHostDevice', 'hwid': 'USB VID:PID=26AA:001B SER=000000000000 LOCATION=1-1', 'vid': 9898, 'pid': 27, 'serial_number': '000000000000', 'location': '1-1', 'manufacturer': None, 'product': 'IOUSBHostDevice', 'interface': None}] [2025-01-28 19:39:58,766] chirp.wxui.clone - DEBUG: Using port '/dev/cu.usbmodem0000000000001' [2025-01-28 19:39:58,766] chirp.wxui.clone - DEBUG: Selected <class 'chirp.drivers.ft70.FT70Radio'> [2025-01-28 19:39:58,771] chirp.wxui.clone - DEBUG: Showing pre_download prompt [2025-01-28 19:40:01,542] chirp.wxui.clone - DEBUG: Setting flag for prompt pre_download [2025-01-28 19:40:01,590] chirp.wxui.clone - DEBUG: Serial opened: Serial<id=0x10f0a8fa0, open=True>(port='/dev/cu.usbmodem0000000000001', baudrate=38400, bytesize=8, parity='N', stopbits=1, timeout=0.25, xonxoff=False, rtscts=False, dsrdtr=False) (rts=True dtr=True) [2025-01-28 19:40:16,814] chirp.drivers.yaesu_clone - DEBUG: [2025-01-28 19:40:16,815] chirp.wxui.clone - ERROR: Failed to clone: Failed to communicate with the radio: No response from radio Traceback (most recent call last): File "chirp/drivers/yaesu_clone.py", line 109, in _clone_in File "chirp/drivers/yaesu_clone.py", line 91, in __clone_in chirp.errors.RadioError: No response from radio During handling of the above exception, another exception occurred: Traceback (most recent call last): File "chirp/wxui/clone.py", line 94, in run File "chirp/drivers/yaesu_clone.py", line 268, in sync_in File "chirp/drivers/yaesu_clone.py", line 111, in _clone_in chirp.errors.RadioError: Failed to communicate with the radio: No response from radio [2025-01-28 19:40:20,212] chirp.wxui.clone - WARNING: Stopping clone thread

1 0

Yaesu VX-8G
by dorn＠hetzel.org 27 Jan '25

27 Jan '25

I see several Yaesu VX-8? models in the supported list, but not the VX-8G. Should I expect it will probably work, or no?

2 1

Program ANI or PTT ID?
by John Oliver 26 Jan '25

26 Jan '25

I'm having a devil of a time figuring out how to do this... I'm looking through all sorts of fields and functions looking for anything that looks relevant. All I can find is length (3, 4, or 5) and PTT-ID that isn't a way to set the code, but just when it's transmitted. I was given a 4 digit code that is now a requirement on one of the repeaters I use, but no info on how to apply it.

2 2

Re: Users Digest, Vol 186, Issue 1
by Dave B 25 Jan '25

25 Jan '25

Re:- On 01/06/2024 21:38, users-request(a)lists.chirpmyradio.com wrote: > I don't want to specify a specific version here because it's specified in the package and mentioned when you install (see above). Putting it here is just asking for it to be stale if it doesn't get updated the next time we bump. However, I'll be glad to add to the page that if you see something like the above error message it means your python is too old if you think it's necessary for clarity. > >> (Sorry to shout, but...) > Yeah, but please don't do that again. Your responses here have already been quite rude and I'm sure the other volunteers who work on this (and the docs, thanks Jeff!) will join me in appreciating you being a lot more respectful. Thanks! > > --Dan OK Dan. Apologies for "shouting", but things could be somewhat easier for us (the less experience Python users out here) than your good self, who only get involved with installs and updates when needed. Just having something on the download page (and in the archive) that states what the minimum Python version (and wxPython perhaps) is needed for any particular version of Chirp, would save "A Lot" of user time (+ cost for those on a $-per-kByte connection) and confusion re Chirp, when they find after waiting (and or paying for) the download, that it won't install. I see you updated the download info page some hours ago now, at least your name is at the bottom of the page, not Jeff's. (Sorry, I don't know who Jeff is in this respect.) As to "needing" to update my distro (LMDE 5 just now) that is still in full support for nearly another 80 days, it keeps telling me. I don't doubt that things move on over time, that's the nature of stuff, but some appreciation for us the users would help us a lot. As for what pipx is telling us when it fails, that's rather cryptic and embedded in a lot of other text, and looks at first, to be something that was spat out as some code crashed and burnt. OK. For now, I've installed one of the 2024 January 11th version, as that still works with Python 3.9.x So I have the use of Chirp again, for now. FYI: There are several LTS versions of Linux, that last a lot longer than the 2 to 2 1/5 years of the mainstream distro's. Many are popular with Radio Amateurs, just because they /*do not*/ keep messing messing with utility version changes and such. "Stability" is preferable to many of us, rather than living on the bleeding edge of development. If a distro (as mine is) still receives security patches, that for the most part, is all we need. However... For those who would like to know if it's viable to try to install a CHIRP update, before doing so. First, in a terminal command line session. (Ctrl + Alt + T will launch a fresh terminal/command line session.) These commands will show you what you are running. (The '$' indicates the command line prompt, you do not need to enter it.) The result is shown on the next line. Find out the currently installed Python version. $ python3 --version Python 3.9.2 (https://devguide.python.org/versions/ is good to view, in relation to what you discover above. 3.9.x doesn't die, until October 2025, nearly a year and a half away, just for info...) To find out the installed version of wxpython... $ python3 -c "import wx;print(wx.__version__)" 4.0.7 Both as discovered on my present system. In a downloaded .whl file, using an archive browser, look for the folder 'chirp-yyymmdd.dist-info' (Where yyyymmdd equals the date part of whatever file you downloaded.) In that folder, look in the file METADATA and you'll find a string (it is a plain text file) like:- 'Requires-Python: >=3.7,<4' That (in this case) indicates that a Python version between 3.7 and 4 is needed. (Greater or equal to v3.7 and less than v4 That example comes from the 20240111 dated .whl file.) If you download the .tar.gz file instead, look for the file 'requirements.txt' Again, that has some minimum version info re wxpython, but not python itself, that can be found in the file PKG-INFO Again, both are plain text files. Sadly, you do have to download an entire file first to discover that info in either case.. Frankly, I'd suggest doing that first, */before/* uninstalling an existing working version of Chirp! Oh, I'd also keep a local copy of the downloaded file, especially when you do install it successfully. You may need it to repair things if something else goes bad, or to revert to a known working state if a future install goes bad. Perhaps without i'net access at that time. FYI: The immediate past day-job (thankfully I'm retired now!) I used to be the customer support and service guru, in-house and on-site, both hardware and software. I learnt very early on, that making as much information available to users, /before/ they commit themselves, saves a lot of time, effort (and cost) and greatly increases a customers likelihood to come back for more of whatever we were doing at the time, and giving us more of their money! That is with hardware, and especially software! Yes, Chirp is largely free to us the users, other than the cost of time and effort to install and learn. For that we are all grateful indeed. But wasting even "free" time does not go down well with many of us. Retired I might be now, but I'm as busy as ever, just working for other "managers". (Domestic and/or feline!) 73. Dave G8KBV. -- Created on and sent from a Unix like PC running and using free and open source software:

9 14

Programmazione del Polmar DB10 MK II
by Ivano 25 Jan '25

25 Jan '25

Salve, fra gli apparati programmabili con Chirp non vedo la radio in oggetto. Esiste un prodotto similare, che non sono riuscito a trovare tra le varie possibilita' nel menu del programma? Grazie in anticipo Ivano

2 3

Running chirp on a tablet with windows 10
by Gary Chesshir 24 Jan '25

24 Jan '25

Has anyone tried using chirp on a tablet running windows 10? Did it work ok or what if any issues did you encounter? Gary Sent from my T-Mobile 5G Device Get Outlook for Android<https://aka.ms/AAb9ysg>

2 1

Programming the Polmar DB10 MK II.....
by Ivano 24 Jan '25

24 Jan '25

Hi, among the devices programmable with Chirp I don't see the radio in question. Is there a similar product that I couldn't find among the various possibilities in the program menu? Thanks in advance Ivan

1 0

Help uninstalling legacy version of chirp in ubuntu
by vafred＠gmail.com 24 Jan '25

24 Jan '25

I installed (CHIRP daily-20220604) a while ago and cannot find it. I'm running Ubuntu 24.04 and can't find the program to delete it. I want to install the new build but the documentation say's uninstall older versions. any help would be appreciated. I have tried searching anywhere I could think of to no avail. I tried grep and searched my complete drive with file explorer. Thanks, Fred

4 8

New chirp-next build
by donotreply＠chirpmyradio.com 24 Jan '25

24 Jan '25

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since the last build and may include additional features, bug fixes, etc. Unless you have a reason not to, we recommend using the latest build of CHIRP-next at all times. You can get it from here: https://archive.chirpmyradio.com/chirp_next/next-20250124 A list of changes since the last build are here: 470a8a0a TK690: Add test frequencies to settings, fix power level handling, and fix k3 band limits 993b281b tk280: Clean up setting names and structure cbf38f63 tk280: remove some leftover comments and debug 45e90cc2 tk280: Add mobile-only key definitions 0f0e609d kguv920p: Fix initializing new memories e22fbedd tk280: Fix some spelling errors from previous author ca5761fd Add TK-880 and TK-780 support 9bda8b30 Hide more not-a-radio ports on macos da6d48af tk8180: Support key assignments ee07f6e2 tk8180: Add battery save, warning, pttid settings 0aa7f9eb Allow RSVBoolean to record different mem values abac23c7 Remember last tab for cross-tab raw diff 1154a705 tk8180: Fix loading settings with multiple zones 095e4bfd tk280: Add OST backup and direct settings e1befe5a Update Turkish language 13ef1f73 Update locale after previous patch 416e50a1 [ft2d] Remove leading space, unify strings a bit f5324c8a Update Bulgarian translation 7479fc19 Updated Italian Translation 4c4c1422 Updated Spanish Translation Issues addressed in this build: [Bug 11786] Wouxun KG-UV920P-A - Incorrect settings from uninitialized channel memory [New Model 3475] Kenwood TK-x80, TK-x81 [New Model 5249] Kenwood TK-880 / TK-880H --

1 0

New model #8087 Revevis RT27 loan offer?
by kz4jc＠radiobursts.org 22 Jan '25

22 Jan '25

About 8 days ago I added a comment to issue #8087. I am interested in loaning a USA version. The issue was originally for a EU version. Should there be a separate issue for a US version? How to change issue status to show loan offered: Yes? The new model backlog is long. Any guess how long for this one? Thanks for this software. It is great!

1 0

UV25 Programming question
by Gary Chesshir 17 Jan '25

17 Jan '25

I have a uv25 and am trying to enter frequencies around 240mhz, AM, airband. I can enter the frequency but it won't let me enter the mode as AM. It reports that the frequency must be FM. The frequency is used by aircraft and in the AM mode. I have entered the frequency in other radios and can set them to AM. But not the uv25. Also chirp has uv25 listed under baofeng but it won't accept any airband frequencies. Using uv17pro will let me enter the frequency but only in FM. Does anyone have a work around for this? Thanks. Regards Gary Sent from my T-Mobile 5G Device Get Outlook for Android<https://aka.ms/AAb9ysg>

4 5

GMRS Programming using CHIRP
by Dave 17 Jan '25

17 Jan '25

i am very new to this, I am trying to program using CHIRP to the Baofeng UV-5R, as I am licensed to use GMRS, CHIRP, when I programmed in the frequency, put in DTSC in the tone mode column, which prevented me from hearing anyone, I changed it to tone, now I can hear other users, the tone is set at 88.5, channels that have a repeater are set to + 5.000000, FM at high power. As I am not sure if any of the settings are correct, as I am not able to contact anyone, is there anyone who can help me with the settings I need in all the columns? I appreciate any assistance you can give me in this!

4 14

Re: Retevis H777 Unable to Connect
by Joshua Morin 17 Jan '25

17 Jan '25

Hi Jim, Saw the latest build includes support for H777H_FRS model. Tried it this morning and it does not work. Windows machine gives error "No response from radio". Confirmed I am still able to read/write with OEM software. Josh

1 0

Fw: Uv25 programming
by Gary Chesshir 17 Jan '25

17 Jan '25

Sent from my T-Mobile 5G Device Get Outlook for Android<https://aka.ms/AAb9ysg> ________________________________ From: Gary Chesshir <gary_chesshir(a)hotmail.com> Sent: Friday, January 17, 2025 3:21:26 AM To: Gary Chesshir <gary_chesshir(a)hotmail.com> Subject: Fw: Uv25 programming Sent from my T-Mobile 5G Device Get Outlook for Android<https://aka.ms/AAb9ysg> ________________________________ From: postmaster(a)outlook.com <postmaster(a)outlook.com> Sent: Friday, January 17, 2025 3:14:06 AM To: users(a)listschirpmyradio.com <users(a)listschirpmyradio.com> Subject: Undeliverable: Uv25 programming Delivery has failed to these recipients or groups: users(a)listschirpmyradio.com (users(a)listschirpmyradio.com)<mailto:users@listschirpmyradio.com> Your message couldn't be delivered. The Domain Name System (DNS) reported that the recipient's domain does not exist. Contact the recipient by some other means (by phone, for example) and ask them to tell their email admin that it appears that their domain isn't properly registered at their domain registrar. Give them the error details shown below. It's likely that the recipient's email admin is the only one who can fix this problem. For more information and tips to fix this issue see this article: https://go.microsoft.com/fwlink/?LinkId=389361. Diagnostic information for administrators: Generating server: MN2PR11MB4550.namprd11.prod.outlook.com users(a)listschirpmyradio.com Remote server returned '550 5.4.310 DNS domain listschirpmyradio.com does not exist [Message=InfoDomainNonexistent] [LastAttemptedServerName=listschirpmyradio.com] [MW2NAM12FT088.eop-nam12.prod.protection.outlook.com 2025-01-17T13:14:06.782Z 08DD36B93286D12E]' Original message headers: ARC-Seal: i=1; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=none; b=HQ9cEvIATPlFFCwy/qrX2BL4oOzVLTPO2dJCgkHeAVY4xWcq2e+vdLT7N2dgUnVUqtpNESN5o3UX/56z1eSgkIj/mPSCoosTPyEPVH1Dq4Pg/Be6GUEYSuOvNU5ggofplObuRxYppodyOPGqB2TWf7JU4a7HUkyaY1Yr5xrNnF3SLNOA52xK+t2CyaUnsCMyhXTkURpawbsHYvRC/QsZkOVK2ZknmuSpXr0H5d6OMnFswVTUY6S/RsJD1vFtlFT1c0LJbnPnRAVH59MHAqStoE17mEDe6SxIQRVddC6RYp2hPQR80e8W5tpoIS/eKMV5Vu3hKyAwdNqg7A6diMGisA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector10001; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=6qLNscIihaI5QA5AuENHV8j1RTNEU9AnzWAPQfhPCYA=; b=Vwg6DDCLH7PSYHal3nJEAlm/yDOQfSGzEkQ0lWb2+fRoAAwbXk5UJ6HfVNg6JvkrOqcFOkDMbSs2Jd1pIlqd7z+fWU6gT5aCM5Zd9KTd38VnbHS8GBuG7zSSYtn26sHQHYpG944y6mK8ymoZSs+uI66bybBRIEW4jrBVYVMgFUfi7toYVbCR/ggjdY2qp44RHS/F8YlFVkpsm8A0r58cqhK6G7/n/+TDET6K7BGKW524ugbLVO+1DQlLnqWt/6g2ZP3Gukjm8RKq52KMtI6RQZYBvziaQ05O17p4qg2SqkqR5H7jrLnqGItErUYzQoLVIJg2R1wk3nhejgGcXcluog== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=none; dmarc=none; dkim=none; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hotmail.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=6qLNscIihaI5QA5AuENHV8j1RTNEU9AnzWAPQfhPCYA=; b=u5mOcD3RvfAYnLiceWFYKaYklVtF7DPY3L/Sc8Erl+LBXFNcCiQIXoo6beIWeiJsuFiiloPQdMGRp6oHjCBtlj6nPu/Aok05rxyaS2bu3O0RtYpReUaJoxP9YYXviOLEmzkBqKgBC8oqBmeEkltGy4QBRishAWiMbRXkJkZzZZrLkaBbz1rDO/YJZkU/NxJhd7jdXzQ7V+bizBkCekEl16UdaA/i1CT8LNkBWoFc9COLeRk4ZOmwczDgVMQO2aAvGTkkk5R8mF/6ZrftNtHyxIJ00gxWohoptcOhuJUqW84gynEQwIkHG2qQy4w7BbbI6lmekB+JgivtSA/nmCiFDw== Received: from MN0PR11MB6135.namprd11.prod.outlook.com (2603:10b6:208:3c9::9) by MN2PR11MB4550.namprd11.prod.outlook.com (2603:10b6:208:267::7) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.8356.17; Fri, 17 Jan 2025 13:14:05 +0000 Received: from MN0PR11MB6135.namprd11.prod.outlook.com ([fe80::3225:d4ad:74a:6d7a]) by MN0PR11MB6135.namprd11.prod.outlook.com ([fe80::3225:d4ad:74a:6d7a%3]) with mapi id 15.20.8356.010; Fri, 17 Jan 2025 13:14:05 +0000 From: Gary Chesshir <gary_chesshir(a)hotmail.com> To: "users(a)listschirpmyradio.com" <users(a)listschirpmyradio.com> Subject: Uv25 programming Thread-Topic: Uv25 programming Thread-Index: AQHbaODHxWK7ClOxSEGPqDiwQC1PIA== Date: Fri, 17 Jan 2025 13:14:05 +0000 Message-ID: <MN0PR11MB6135AFE7A4D8255F649C0C17801B2(a)MN0PR11MB6135.namprd11.prod.outlook.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-reactions: allow x-ms-exchange-messagesentrepresentingtype: 1 x-ms-publictraffictype: Email x-ms-traffictypediagnostic: MN0PR11MB6135:EE_|MN2PR11MB4550:EE_ x-ms-office365-filtering-correlation-id: a3cc224b-de2a-4458-e979-08dd36f8d1f8 x-microsoft-antispam: BCL:0;ARA:14566002|9400799030|461199028|14030799003|15080799006|8062599003|12050799009|7092599003|8060799006|19110799003|102099032|1602099012|440099028|10035399004|3412199025|4302099013; x-microsoft-antispam-message-info: =?us-ascii?Q?oHLpmA2/AU1CnZlNITaReAUuONWOPMA0PFNuF5nOUrsmF6gmjMMEkXgZt+mt?= =?us-ascii?Q?KG/NQhAX3S4s7N6R/N13SodaLn3nXdixEmP9QgrayWcuxD2Kpen++5M+siCE?= =?us-ascii?Q?1C27dxx4kVONb8QIj9NFh+Rp59PLvZb5dXqbIihb4b9vII1e8i4sqHKZq25u?= =?us-ascii?Q?sfJ0lzaCCuw3I1nitpExAq8mB5xgIemg5ieuCeg5pVPhexorVqeaoPunRa0P?= =?us-ascii?Q?v4LaJ7EYDKQ6eSbOQ2rV6JjGtUZ6UPWDrtz8ic3cBG+90d5/dzIZgW7oOUII?= =?us-ascii?Q?1ocRdNxUNwpizLMtVZf0npJ31vHD5g1jml8GXOp/b/aDdb+miq01Tu7OOS6Q?= =?us-ascii?Q?ZyeeTUUHj3f51Gvmpv2T3AWJO8K0YOsXDhO28elEXu5J+AZTJSFJOxjF6MPz?= =?us-ascii?Q?AFqGlO8MYMJkLzIYTYn1G+Nh/cYpzMfQy/CWFVWPaDwoZiZKnAbhSHuzW5nJ?= =?us-ascii?Q?JQxUtuLb5JZEETTssF71CDtvTYuzCkO98WO6bLJ1hGzB3C+hJZ4ejb59ebQ9?= =?us-ascii?Q?tjsdqM61zY/CytTd8Df81bzEpSPIZc8kT1EmHYbDT8Ut5TZ0RBqhJuEJTucm?= =?us-ascii?Q?T0HlTWs9Ty2pB3nD6g2sK+Mt5UVydwtgWqSPVsGydjizioC+CBHoa9cAfAlU?= =?us-ascii?Q?URcHy4VeNj7OlLfEvszrOpcWvkeQv614KnStNDWCcH1Z0JXZZsJTLQ3+Yt0h?= =?us-ascii?Q?PoTluW5IgQPwnXl9c/Rxg68NOHpU0mk8awbKcrNQUlcf3gqUA9BeS7FNj96r?= =?us-ascii?Q?fTDgoBMc+R+MV5olcAcDBX7QWcB9QY00e6TqSA4TpO8QKe31NWgqiOZpAATi?= =?us-ascii?Q?7C/lGTzY/xYtxu50nzxnSRjMuV+dQ9sAiMN+Gs2Qf0DhPVqgWJNZi42J73Qs?= =?us-ascii?Q?37EW8FjX1zhastE0W74FC4HtizZBNYHc/pJJdO5OLoH0Q/QGTILlesLpKSo8?= =?us-ascii?Q?Av3YmaMzcHvmrxpp2LTLP3W89eJqYymq6WJdUHONxH4dkD+HvuzC/fJFIy3t?= =?us-ascii?Q?taAsPUqgb0+nf32M6D8tnUDcJCTXp53kO8nkG6fcAjAd7ju6/ea8uzvHuXrJ?= =?us-ascii?Q?7WhiwMhZSfVYZ7z+DY76mw76qvd6JQ2KV6NykFnl6X7SqDNxMGew6V8tN21j?= =?us-ascii?Q?Nh8nxZX6GD+yknSkzgcM4OKte7MkB0aW41Nb3UkDXl5wuVA8KZegevlUu8bg?= =?us-ascii?Q?DM9OBuxagCLtQUCE4A05+qXCtcIW+ivqmT6UUJqfu3cMkhLsp9ojl76gxtY+?= =?us-ascii?Q?OuCgWMEdC5/jGAQCtQ5UP+lli6hB+dqXSnoBDdT8Zw=3D=3D?= x-ms-exchange-antispam-messagedata-chunkcount: 1 x-ms-exchange-antispam-messagedata-0: =?us-ascii?Q?nToopkVDDdXjZHbomWRDbtcIJPh/9oFKoKo0+D4s4KcwAb+/Yd1anKqqv0QV?= =?us-ascii?Q?du5dy7IBILONOpWzRsGMqfMMTcACOHzKw90cb5twibBXS154D48AXW+LRAco?= =?us-ascii?Q?jzBoy3EhMzRGmrjfNcHjaWbM8Qt5aRcdYs8QKyiTQIy55aXmBSWP83EA4RkB?= =?us-ascii?Q?GFon0dWiQm/FGMLSpauge151qpXYOX7dI5fuo47ufJji+WnQa6QVltQGKKHH?= =?us-ascii?Q?4+3onsFA+s0yGpylAvQKuMixv2I9xbhaB/nKsOmf5s0CgymugUN5rm0nbuL6?= =?us-ascii?Q?kTD8h6a0Kp8F0GvGPf+yQhfXxoGfeqpqTEqQbM1UzvNwYBaVhwZcFUsmR0sn?= =?us-ascii?Q?xLThuNhoB8oYh3WEjpTjT6gr3tCMhNIrqBvK502KiEEcVQeHkyBTTU/JkRbm?= =?us-ascii?Q?Kr8XXmiqWor0CddpUPHXrJjsvb+6wzy4KwW4PcBOo1kNtrf+SSEs5LLJSSRh?= =?us-ascii?Q?kmOOyvRnqEtnM8hZb2tGUD/xaQBY25KOOicZkJe922LFMEgB4DLlL8DYBifa?= =?us-ascii?Q?xLCMWIJiZpOVR6ddpCy7ioURLGrHaQ6sIadCKnEzt7DxaxtNDONkuhigvU/1?= =?us-ascii?Q?pYQNf9+l+FMBDEa5vaj4on07lRB+Cwz5cz2Q0enltLqq+DmYuEL5pJ6exira?= =?us-ascii?Q?w4TcPn4yoGjPfTnnG3nWN3+FQpQQZr8h6MZmhWsWgKSU8P1Ugjy9XTi1B/+a?= =?us-ascii?Q?LH7CQyHhK8Sct6aSax+7S17TFJY6gjVBz1oavKbIVBv0VEeJtyTMsQ3wIUfB?= =?us-ascii?Q?heTuSi5fs45vDGXwZDxEaUu/YSedUDbfGdJSdtwuFYOke8BJYNSVHr6A4gnn?= =?us-ascii?Q?AUmw/cojVr3vo/f1Q8BhVl2Ls6Piksumq/7ZsGpioy67wWNp0hkhgLOg6StM?= =?us-ascii?Q?jH4dNXWe506CccDSUTO2Ra6e3Rmu+Hw1tRyBQESHk0w7Ow+PM6D1cT2lK7hQ?= =?us-ascii?Q?92ZHZ+cV/irYk84NJo6YFpTICP7HbMeNBU9iEyqKMEj2ZwDB7Hk7zEHTOWpT?= =?us-ascii?Q?CrTIMWg4LPMiiJ9MDCephG+G7PiXRTiZF5qf9b1oUOuxHozjkq5G2YG0lrBZ?= =?us-ascii?Q?C0e2Y4mqY7qAeQxC8OHXTaDH062xFKoGeAXUITmZy8y9PjZw5X6UZvmuJaZP?= =?us-ascii?Q?QIwmzwCGyUmn5mXZmE+9Z3v2LWPe4NX8gMc40zsO7eTumGbvstVg9oPCxjaz?= =?us-ascii?Q?YHCDkNBOW1eYq0VuCYnmMuPKG178VH6mWAcsmI+Bpa1m6HPcf4NxxabJtQR/?= =?us-ascii?Q?hSoKJyQ1PqDHJFAA/qZD?= Content-Type: multipart/alternative; boundary="_000_MN0PR11MB6135AFE7A4D8255F649C0C17801B2MN0PR11MB6135namp_" MIME-Version: 1.0 X-OriginatorOrg: sct-15-20-7719-20-msonline-outlook-d1079.templateTenant X-MS-Exchange-CrossTenant-AuthAs: Internal X-MS-Exchange-CrossTenant-AuthSource: MN0PR11MB6135.namprd11.prod.outlook.com X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: 00000000-0000-0000-0000-000000000000 X-MS-Exchange-CrossTenant-Network-Message-Id: a3cc224b-de2a-4458-e979-08dd36f8d1f8 X-MS-Exchange-CrossTenant-originalarrivaltime: 17 Jan 2025 13:14:05.8571 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: 00000000-0000-0000-0000-000000000000 X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB4550

1 0

New chirp-next build
by donotreply＠chirpmyradio.com 17 Jan '25

17 Jan '25

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since the last build and may include additional features, bug fixes, etc. Unless you have a reason not to, we recommend using the latest build of CHIRP-next at all times. You can get it from here: https://archive.chirpmyradio.com/chirp_next/next-20250117 A list of changes since the last build are here: c97ccc75 Add diff-between-tabs developer function 5b178d50 tk8180: Fix tuning step encoding 229c8218 tk280: Fix tuning step encoding 497a9f44 tk280: Fix supporting duplex=split abf21c0c Improve keyboard navigation from setting group to editor fa75ee23 tk280: Fix saving radio version in metadata ed01c80c tk280: Improve performance by caching mappings a0339278 tk280: Fix battery save setting 4d9ba57e tk280: Fix memory format deprecated behaviors 2aedd6d1 Fix memory dragging off-by-N rows issue 3075cd43 tk280: Implement OST settings 0863e4e3 Add Kenwood TK-280,380 support d47b210e Improved keyboard navigation for settings editor 3ea12b3b Add MemSetting to streamline set_settings() in many cases c2ff1b04 Improve reporting of settings failures in tests a7b805ab radtel_t18: add Retevis H777H PMR version - fixes #11775 79fefdcb radtel_t18.py: add support for Radtel H777H FRS version - related to #11775 fc94f148 uv17pro: Fix exposing static banks on some models dc48c8a1 snapcraft: Install wheel instead of tarball 837aef0d Improve keyboard navigation and editing Issues addressed in this build: [Bug 11642] zone/bank assignments [Bug 4935] Radio not seen in Linux Mint [New Model 11775] Add support for Retevis H777H series radios --

1 0

Alternate Programmng Methods
by ebills＠ncsmiths.com 14 Jan '25

14 Jan '25

I'm playing around with a TIDradioH3 which has both bluetooth programming and a dedicated usbc connection for programming. Curious if Chirp has usb to usb programming capability or bluetooth capability. Dick W4RS

5 4

Re: Trouble with Linux USB port (Dave B)
by Dave B 13 Jan '25

13 Jan '25

Hi again. You need to... sudo apt purge brltty If you've not already done so in the past... "brltty" is (I think) a Braile input device, for partially sighted users, often installed and active by default. It would appear the devices probably use a CH340 USB/Serial bridge chipset, hence the confusion. Also, if you've not already made yourself a member of the "dialout group"... sudo adduser $USER dialout. That will add "you" (the logged in user) to the "dialout" group, giving you permission to use serial ports, among other things. ("$USER" is a system variable that holds the logged in username.) Then, at least logout and log back in again for that change to take effect. If you wish, do a full restart just to be sure that brltty has gone. There is also often another background daemon "modem manager" that can cause similar issues. That can be disabled too, plenty on the web about that. Hope the above helps. Dave B.

1 0

Re: Trouble with Linux USB port
by Dave B 13 Jan '25

13 Jan '25

Hi. With recent Linux's, you can use... dmesg -WH in a command line session... Where nothing appears to happen but if you plug something in, you'll see what the OS does with it. If -WH errors, try -wH.. An initial splurge of info, then silence, untill you change what's plugged in. (Ctrl+C exits the dmesg thing, Ctrl+D will close the terminal session.) If you have a FTDI based adapter, you can create a udev rule, so it always shows up under a more easily recognizable device name, such as... /dev/ttyMyAdapter! Or other creative name, regardless of were you connect it. Lesser chipsets without a unique serial number, you can do similar tricks, but you have to decypher the "path" to the device, and as I've recently found, with some OS/PC Hardware combinations, that can change at each boot! Most application software these days will accept that sort of thing, CHIRP used to, but I've yet to try the latest incarnation. 73. Dave G0WBX.

3 4

Re: Trouble with Linux USB port
by Dave Baxter 13 Jan '25

13 Jan '25

Disable and remove BRLTTY. It's a not uncommon issue for that to mess with serial ports. Plenty online about that, and other pre-installed software that comes with the OS's these days. It doesn't affect many, but when it does, mayhem ensues! Hope that helps. Dave.

1 0

Re: Trouble with Linux USB port
by Gregory Beyer 13 Jan '25

13 Jan '25

> Yes I did follow the instructions, as stated in my OP. There is no > difference between running ls /dev/tty* before and after cable > plugin. No new device is added. I have no ttyACM device. Ran usermod > command, then rebooted. No joy. running ls against all of /dev, I do > find a usb directory (not ttyUSB) -- IDK if it relates to this problem. > > ls -la usb > total 0 > drwxr-xr-x 2 root root 60 Jan 12 12:03 . > drwxr-xr-x 21 root root 4880 Jan 12 12:15 .. > crw------- 1 root root 180, 0 Jan 12 12:04 hiddev0 > > "In some cases it may be necessary to enter the device (port) name > manually before chirp can see it." How would I do that? > > Thanks, > *________________________* > > *Greg Beyer > greg(a)beyerusa.net* > > > KQ4AVZ > > > ------------------------------------------------------------------------ > *From:* Jeffrey Vian via Users <users(a)lists.chirpmyradio.com> > *Sent:* Sunday, January 12, 2025 at 12:39 AM > *To:* CHIRP users list > *Cc:* Jeffrey Vian > *Subject:* [users] Re: Trouble with Linux USB port > >> Did you follow the instructions on this page? Especially steps 1 and 2. >> >> Are you certain that the port is getting the name you expected?. >> >> It may get a name ttyUSB0 or it may get something like ttyACM0. On >> some of >> my radios it gets USB and on others it gets ACM. I think that is >> related >> to the specific chipset in the programming cable (or maybe the linux >> distro >> used could be a factor) >> You may be able to run `ls /dev/tty*` before plugging in the cable and >> again after plugging it in to identify the name it actually is assigned. >> >> In some cases it may be necessary to enter the device (port) name >> manually >> before chirp can see it. >> It also may be necessary to add your user to the `dialout` group for >> access >> to the device. If you have not already done so the command `sudo >> usermod >> -a -G dialout <username>` should add the user to that group. Then a >> logout >> and back in will be required before the group assignment becomes active. >> >> Jeff >> KI7GJG >> >> >> >> On Sat, Jan 11, 2025 at 10:23 PM Gregory Beyer via Users < >> users(a)lists.chirpmyradio.com> wrote: >> >>> Hi, I'm having trouble with CHIRP not recognizing any USB ports. I'm >>> running LinuxMint 21, Mate. I've installed >>> chirp-20250110-py3-none-any.whl per the instructions at >>> /wiki/ChirpOnLinux. Other than needing to install python3-yattag, it >>> went smoothly. Love how fast chirp loads over the flatpak I used to >>> use >>> a long time ago! >>> >>> When I run chirp, and scroll through the ports, there are no USB ports >>> listed. Tried "Help me" and got "Unable to determine a port for your >>> cable. Check your drivers and connections." Under Mate System >>> Reports/System Information, I see the cable listed under USB hub 1: >>> Device-2: 1-2:40 info: QinHeng CH340 serial converter type: <vendor >>> specific> driver: usbfs rev: 1.1 speed: 12 Mb/s chip-ID: 1a86:7523. >>> I plugged my cable into a different USB port, cable appears under hub 2 >>> in the report. So, my OS is recognizing the cable, on either USB >>> port, but CHIRP does not. >>> >>> Even tho I'm not getting a permission denied error, I tried "sudo >>> usermod -a -G $(stat -c %G /dev/ttyUSB0) $USER" anyway, and got "stat: >>> cannot statx '/dev/ttyUSB0': No such file or directory." Same error >>> when I tried command for USB1 and USB2. >>> >>> Any suggestions on how I can resolve? >>> >>> Thanks much, >>> >>> *________________________* >>> >>> *Greg Beyer >>> greg(a)beyerusa.net* >>> >>> >>> KQ4AVZ >>> _______________________________________________ >>> Users mailing list >>> users(a)lists.chirpmyradio.com >>> https://lists.chirpmyradio.com/postorius/lists/users.lists.chirpmyradio.com >>> >>> To unsubscribe, send an email to users-leave(a)lists.chirpmyradio.com >>> To report this email as off-topic, please email >>> users-owner(a)lists.chirpmyradio.com >>> List archives: >>> https://lists.chirpmyradio.com/hyperkitty/list/users@lists.chirpmyradio.com/ >>> >> _______________________________________________ >> Users mailing list >> users(a)lists.chirpmyradio.com >> https://lists.chirpmyradio.com/postorius/lists/users.lists.chirpmyradio.com >> >> To unsubscribe, send an email to users-leave(a)lists.chirpmyradio.com >> To report this email as off-topic, please email >> users-owner(a)lists.chirpmyradio.com >> List archives: >> https://lists.chirpmyradio.com/hyperkitty/list/users@lists.chirpmyradio.com/

2 1

Trouble with Linux USB port
by Gregory Beyer 12 Jan '25

12 Jan '25

Hi, I'm having trouble with CHIRP not recognizing any USB ports. I'm running LinuxMint 21, Mate. I've installed chirp-20250110-py3-none-any.whl per the instructions at /wiki/ChirpOnLinux. Other than needing to install python3-yattag, it went smoothly. Love how fast chirp loads over the flatpak I used to use a long time ago! When I run chirp, and scroll through the ports, there are no USB ports listed. Tried "Help me" and got "Unable to determine a port for your cable. Check your drivers and connections." Under Mate System Reports/System Information, I see the cable listed under USB hub 1: Device-2: 1-2:40 info: QinHeng CH340 serial converter type: <vendor specific> driver: usbfs rev: 1.1 speed: 12 Mb/s chip-ID: 1a86:7523. I plugged my cable into a different USB port, cable appears under hub 2 in the report. So, my OS is recognizing the cable, on either USB port, but CHIRP does not. Even tho I'm not getting a permission denied error, I tried "sudo usermod -a -G $(stat -c %G /dev/ttyUSB0) $USER" anyway, and got "stat: cannot statx '/dev/ttyUSB0': No such file or directory." Same error when I tried command for USB1 and USB2. Any suggestions on how I can resolve? Thanks much, *________________________* *Greg Beyer greg(a)beyerusa.net* KQ4AVZ

4 4

Retevis H777 Unable to Connect
by jmorin06＠gmail.com 11 Jan '25

11 Jan '25

Greetings! New CHIRP user here. I ordered (4) Retevis H777 radios and am trying to program them. Two radios are the "newer" version (with usb-c charging) while the other two are an "older" version. I am able to connect, download, and upload to the older version radios, but not the newer version radios. When I try, I get the error message "Error communicating with radio, no response from radio". Tried with all three of the H777 profiles (H777, H777 Plus, H777S). The first two profiles give the same error message already described. The third is a different error message "The radio did not accept program mode after five tries...". Radio is on, tried different computers (Mac and windows) also made sure I was using latest CHIRP build (10-Jan-2025). Nothing works... I am able to program with the Retevis CPS. The "newer" version does have some different features so maybe it needs a new profile/model in CHIRP? Before I submit a bug/new model request, I wanted to check here to see if anyone has advice or experience working with this "newer" H777 model. Thanks!

2 2

Icom IC-2710
by Ken Gordon 10 Jan '25

10 Jan '25

Is Chirp able to program the subject radio? Ken W7EKB -- This email has been checked for viruses by Avast antivirus software. www.avast.com

3 2

UV-5R receive issues using CHIRP
by Dave 10 Jan '25

10 Jan '25

I downloaded the CHIRP software I received with the radio, I used updated software to program the radio, it transmits fine, the problem is that I am not receiving anyone, the color on the radio changes as there are people talking, I have a scanner that also confirms that people are talking, but no audio from the radio, with the exception of the National Weather Service that is programmed in. I have some ham radio, FRS, GMRS Freq's programmed in. Since the updated software puts all the information in for us when you enter the frequency, I am not sure what is going on, any solutions?

3 5

Re: UV-5R receive issues using CHIRP
by Joe Pizzi 10 Jan '25

10 Jan '25

My guess is that you put the ctcss tones as receive tones instead of transmit tones. Joe Pizzi KI5LST

1 0

New chirp-next build
by donotreply＠chirpmyradio.com 10 Jan '25

10 Jan '25

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since the last build and may include additional features, bug fixes, etc. Unless you have a reason not to, we recommend using the latest build of CHIRP-next at all times. You can get it from here: https://archive.chirpmyradio.com/chirp_next/next-20250110 A list of changes since the last build are here: cd69e1b9 Add Baofeng BFT20D radio c4273f95 rt21: Fix DTCS decoding when stored in hex 83b5c06b tdh3: Fix incorrect ponmsg and step list values 3d03ae13 Update bg_BG.po 48e8354a Disable filtering on Linux 12082ade Update UV-5GPlus model alias ccf0a655 Added support for Kenwood TS-790E. Possibly fixes #10215 3e66222c kenwood_live: Refresh memory after setting 927ba36c Avoiding globals in kenwood_live.py Issues addressed in this build: [Bug 11749] Some memory fields empty, message "some memories are incompatible with this radio" [Bug 11760] Chirp Freezes when I click in the Filter Field [Bug 11761] Tidradio TD-H3 : Power on message and step values incorrect [New Model 10215] Kenwood TS-790A & TS-790E [New Model 11742] Add support for Baofeng BF-T20D --

1 0

"Round-trip" processing with Chirp
by lgadallah＠gmail.com 08 Jan '25

08 Jan '25

Hi all: I have used 'chirpc' to connect to my radio and download the memory map. It is my understanding that entries can be added to a .csv file and these can be added to such a memory map file, allowing updating or adding new entries to the memory map. However, I wonder if there is a way to convert the memory map file to a .csv file, allowing the contents to be managed there? This would allow a "round-trip" capability as mentioned in the title: Configuration could be downloaded from a radio, converted into a .csv file, edited as needed, and then inserted into a memory map file and uploaded to the radio. Note: I may be missing some obvious functionality as I am using 'chirpc' rather than the GUI, as I am remote from the PC and radio. 73, Larry NM7A/VE6VQ

3 2

New chirp-next build
by donotreply＠chirpmyradio.com 27 Dec '24

27 Dec '24

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since the last build and may include additional features, bug fixes, etc. Unless you have a reason not to, we recommend using the latest build of CHIRP-next at all times. You can get it from here: https://archive.chirpmyradio.com/chirp_next/next-20241227 A list of changes since the last build are here: 43449629 Add basic support for Baofeng W31D and BF-T20D - closes #11671 and #11742 67d51a73 Updated Italian Translation d9949018 Fix marking some untranslated strings aba99276 ga510v2: Fix reading memory block list 855276b7 TK690: Additional Settings options added group names, setting basic/full control head, setting welcome message, setting channel/group name lengths, and compander enable/disable per channel 7db6b122 Fix reloading volatile settings 204f4f78 chore: Bump gh action versions Issues addressed in this build: [Bug 11209] seems some strings, for example "Name" and "Skip" columns are missing from translations. [Bug 11739] Radioddity GA-510

1 0

Question
by Thomas Bain 22 Dec '24

22 Dec '24

Hello. I have a simple question. Is CHIRP software compatible with Windows systems that use the new Qualcomm ARM-based processors? Thank you, Tom

3 4

New chirp-next build
by donotreply＠chirpmyradio.com 20 Dec '24

20 Dec '24

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since the last build and may include additional features, bug fixes, etc. Unless you have a reason not to, we recommend using the latest build of CHIRP-next at all times. You can get it from here: https://archive.chirpmyradio.com/chirp_next/next-20241220 A list of changes since the last build are here: 605037de bankedit.py: remove redundant memory_changed function, now that _cell_changing handles both cases 48c33155 handle spacebar selection of cells properly ef723140 fix style issues in alinco_dr735t.py to resolve tox -e style failing tests 9deeb0e1 Make RadioSettingValueMap support lazy init 7e5be48c tk690: Remove stray print() debug 81f6e5da Fix RadioSettingValueMap deprecated current-value ef3502e1 Fix missing EOL in FRS/GMRS stock config 58664d97 Add driver for Kenwood TK690, TK790, and TK890. d8bb14bb uv5r: Expose rich "K1 connection" error c58ef444 Updated Italian Translation 0b5af16d Updated Spanish Translation Issues addressed in this build: [Bug 11738] Upload from Radio [New Model 1093] Kenwood TK-690/790/890 [New Model 3363] Kenwood TK-790 Single Head --

1 0

New chirp-next build
by donotreply＠chirpmyradio.com 13 Dec '24

13 Dec '24

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since the last build and may include additional features, bug fixes, etc. Unless you have a reason not to, we recommend using the latest build of CHIRP-next at all times. You can get it from here: https://archive.chirpmyradio.com/chirp_next/next-20241213 A list of changes since the last build are here: 3991158d fix typo in CSV column name, fixing TStep c7d02403 add legal power limits for US FRS and GMRS, replacing chirp's auto-populated 50W on all channels 409312fe Add MaxTalker P15 301c2fea Add filtering capability to the memory editor ded11074 repeaterbook: Fix memory number sequence 22e3642f baofeng_uv17Pro.py: support BF-F8HP-PRO firmware v0.33 - fixes #11729 68d2fc9b Fix reporting bugs with UTF-8 in debug.log 78ad1411 radtel_rt490: Fix deprecations 3f65fa40 radtel_rt490: Add language toggle cc5db82a rt490: Fix channel names in chinese characters Issues addressed in this build: [Bug 11722] Is it possible to display the channel name in Chinese? [Bug 11724] Language toggle for radtel_rt490 and related [Bug 11725] Log upload with UTF-8 chars fails on Windows [Bug 11729] Update support for Baofeng BF-F8HP-PRO to include changes brought about by firmware version 0.33 [Feature 11731] Add filter querying ability to the memory editor --

1 0

Settings content problem
by Lofgren, Charles 08 Dec '24

08 Dec '24

I'm trying to fix the missing 222 mHz band problem with my Radioddity UV-5rx3, and I've gotten these directions from Chirps' Issues section: Without a copy of an original image (or at least one that wasn't blanked, the best I can offer for you is to do the following... 1. Save the Radioddity_UV-5RX3_20230722(factory).img file that I just attached to a convenient location on your computer 2. Start CHIRP 3. Load the image file that was saved in step 1 into CHIRP 4. Click Settings -> Advanced Settings 5. Click in the field for the bottom Range Override Parameter setting 6. Type CTRL + A to highlight the whole field 7. Type the Delete key to empty the field 8. Manually type in UseAtOwnRisk (do not copy-and-paste from your browser) 9. Upload to your radio 10. Restart CHIRP My problem is that when I go to the Advanced Settings tab, I don't find the indicated Range Override Parameter. The Settings tab itself is at the top of a column on the left side of the screen. I've seen several YouTube videos where the Chriip Settings tab appears about the middle of the screen after some preliminary material. The Settings option on my screen seems to have different content. How do I get to the right version of Settings? Thanks, Charlie

2 2

New chirp-next build
by donotreply＠chirpmyradio.com 06 Dec '24

06 Dec '24

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since the last build and may include additional features, bug fixes, etc. Unless you have a reason not to, we recommend using the latest build of CHIRP-next at all times. You can get it from here: https://archive.chirpmyradio.com/chirp_next/next-20241206 A list of changes since the last build are here: c233a006 Fix GDK_BACKEND hack on Linux 581819f7 ftlx1011: Preliminary py3 conversion ec34595c Update repeaterbook tests for more coverage 39a1b12b Make repeaterbook errors more verbose 351b31df wouxun: Initialize bands after mmap parse a1268a0e Add TYT TH-350US version 44d6ad76 Updated Italian Translation 2560148f Initial support for Radtel RT-620 (GPS) radio, based on UV17 Fixes: #11699 8f0d16ba uv17: Fix missing setting warning message Issues addressed in this build: [Bug 10887] TYT TH-350 Jumbled Names column from Download [Bug 11487] channel names all scrambled [Bug 11715] KG-UV6D rejects 6M frequencies with KG-UV7D [Bug 11721] Glitchy scroll on Ubuntu [New Model 11699] New Model Radtel RT-620 (Ruyage UV6D) GPS --

1 0

Vertex FTL-1011 on Next
by Mark Phillips 05 Dec '24

05 Dec '24

I'm guessing someone already knows this but I tried programming a recently received Vertex FTL-1011 using the latest build of Next and it did not work. I tried on both Linux and Windows to no avail. The initial read crapped out instantly with an error message. Trying it with Legacy worked just fine on both platforms. Should I report this to the developers list? Mark NI2O

2 1

New chirp-next build
by donotreply＠chirpmyradio.com 29 Nov '24

29 Nov '24

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since the last build and may include additional features, bug fixes, etc. Unless you have a reason not to, we recommend using the latest build of CHIRP-next at all times. You can get it from here: https://archive.chirpmyradio.com/chirp_next/next-20241129 A list of changes since the last build are here: 7fef7cca Updated Spanish Translation 626586c0 Fix opening the languages list when running from the sources tree 924c5696 Do a case insensitive sort of languages 6c2cffeb Make offset column hint at TX freq for split-capable radios 85cfb944 Catch driver errors during save and show a dialog d76634dd ft70: Some bank assignment fixes d7827323 Initial ICOM IC-M710 driver 1c38b735 icf: Allow drivers to skip clone result f2b00534 Make test_icom_clone honor radio _ranges 2f48001e Move STEPS in baofeng_uv17Pro to UV17Pro class, fixes #11716 d1f8504e uv17: Allow separate block list to be read 7703a97c Add Radtel RT-470X Plus BT signature, separate class and test file b2ff882d query sources: add przemienniki.eu 8276b581 Fix typos 5b41e67d Add developer serial-open-error test fixture 518cbb66 Fix clone dialog hang if serial open error Issues addressed in this build: [Bug 11700] Hanging when communicating with radio [Bug 11702] Yaesu FT-70D Memory Bank issues [Bug 11717] After introduction of banks in UV17Pro driver, UV17 driver reports multiple errors for banks [Feature 11430] SP Repaters Database - przemienniki.eu [Feature 11716] Improvement of Baofeng uv17Pro to make step lists part of class [New Model 1067] Icom IC-M710 [New Model 11695] Radtel RT-470X Plus Bluetooth --

1 0

New chirp-next build
by donotreply＠chirpmyradio.com 22 Nov '24

22 Nov '24

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since the last build and may include additional features, bug fixes, etc. Unless you have a reason not to, we recommend using the latest build of CHIRP-next at all times. You can get it from here: https://archive.chirpmyradio.com/chirp_next/next-20241122 A list of changes since the last build are here: 99bf4ccc Added zh_CN welcome screen e01d36e1 Remove last remaining usage of python3-six b33595c6 icv80: Fix txinhibit as duplex=off 53235e50 ft70: Fix tuning steps 5.0 and 6.25 4b030553 Improve error message for tuning step failure Issues addressed in this build: [Bug 11336] v80e duplex is missing OFF [Bug 11681] Yaesu FT-70D Wrong tuning steps --

1 0