- Users - lists.chirpmyradio.com

New chirp-next build
by donotreply＠chirpmyradio.com 30 May '25

30 May '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://chirpmyradio.com/projects/chirp/wiki/Download A list of changes since the last build are here: 8575ead0 Update french translations de741e93 Add pr check for print() d7b5b384 rt470: Add v1.27A firmware version 4ca102ec Fix tox CHIRP_TESTIMG option d74423a2 Make check_commit look for modified images b97057d3 Fixes #12005 TD-H8 SHORT_KEY_TOP not saving fc56ae08 Related to #11996 Inverted FM Allow Receive setting a50213c9 Fixes #11996 Inverted FM VFO/CH setting Issues addressed in this build: [Bug 11996] FM VFO/CH inverted [Bug 12005] SHORT_KEY_TOP not saving [Bug 12007] Radtel RT-470 10W (old PCB) with firmware 1.27A failed to load in Chirp (Radio returned unknown identification string) --

1 0

Baofeng 5RH PRO radio
by Chris Hart 29 May '25

29 May '25

Hi there, I have this model radio and wish to program it. Unfortunately as an Apple Mac user I cannot run the manufacturers software written for MS Windows. I am hoping that CHIRP can be my answer but this model radio does not appear to, as yet be compliant. Would you please add Baofeng 5RH PRO to CHIRP? Can you give a rough idea when this might happen? CHIRP works well with my Baofeng UV 5R - thank you. Good wishes, Chris

3 2

Anytone AT-778UV II
by Ricardo Duran 27 May '25

27 May '25

Hello Which of the two listed models do I use to program the Anytone AT-778UV II mobile radio? Thank you in advance, Ric Duran WD7U

1 0

KG-UV980P.
by Daniel Smith 26 May '25

26 May '25

Hello everyone, I have a KG-UV980P that i need to transmit on the VHF range of 66-88MHZ. Is there a way to unblock that range and do I do that on the 50M or 150M section Any assistance would be greatly appreciated Regards, Daniel.

1 0

Chirp with Yaesu radios
by howard＠small.au 26 May '25

26 May '25

I have an FT817ND and an FTM7250DR, both of which are listed as supported radios. However, I have seen a number of posts on the internet from Yaesu stating that using Chirp with Yaesu radios may damage them. On the 7250, Chirp uses the clone mode of the radio which, to my mind, is a very safe way to go. I am not sure how it works with the 817. I would like to use Chirp with both but I am, of course, worried by the Yaesu statements. Are these statements still valid? Or have they been invalidated by progress within Chirp? Or were they not valid in the first instance but a reflection of some other issue? Thanks for any information on this. Howard, VK4BS

8 10

Re: 5RH, 5RH Pro comments
by Terri Kennedy 25 May '25

25 May '25

> Date: Fri, 23 May 2025 05:25:14 +0000 > From: Massimo Nespolo <massimo.nespolo(a)orange.fr> > Subject: [users] Re: Baofeng K67 Pro > > On 23 May 2025 05:37:15 (+02:00), Terri Kennedy via Users wrote: > > If the radio is similar to the 5RH Pro, you might not want it even > if > > you could program it with CHIRP. My 1-sentence review of the 5RH Pro > was > > "Straight into the parts bin". > > I dare to disagree. I have or have had 5RH, 5RH Pro (before it became > "GPS") and 5RH Pro Max and I'm pretty satisfied. I am not an advanced > user, > but for my purpose there radios are perfect - if you forgive a slightly > bigger size. The modern UV-5RH (internal designation 5RHL) and UV-5RM (internal designation 5RHBK) are good, basic radios in line with other recent full-color-screen Baofeng models, with the 5RH not having air band or 350-390, while the 5RM does. The related UV-5G Plus (also internal designation 5RHL) is a 5RH that is locked to Tx only on the GMRS channels. My dislike is for the 5RH Pro (internal designation 5RH- 501-NRF). In addition to the usability problems with the radio (with firmware 2.0.9 when the keypad backlight comes on, the screen goes off, not to mention the many APRS issues), the one big show-stopper is: All of the software for the 5RH Pro is absolutely infested with viruses / malware. A representative sampling: 5RH_Font_tool.exe - https://www.virustotal.com/gui/file/2ed67337eddb0d23dd7edcda00654c75f4f634d… 5RH_V1_19_CPS.exe - https://www.virustotal.com/gui/file/3fc1efe231e026d96e8277343a29dd01c7ea49f… 501_Update_115200_v1_2.exe - https://www.virustotal.com/gui/file/8d247719a1ccc2e9381ee5bd0a8b3eb3a50f81b… BF501_Update 240118(1).exe - https://www.virustotal.com/gui/file/459880c46ebecd7ab1ea0f1c845283e81efc2fd… This isn't just me - you can read about other user's ex- periences with viruses on the radio's Amazon page reviews: https://www.amazon.com/dp/B0DKNHG7DF "Moreover, the software update aspect is negative, with customers noting that CHIRP software is unavailable and the software is infected with viruses." If you download the programming software from TIDRADIO, the "5RH Pro programming software.zip" file contains a file named "1.------READ IT FIRST------.txt" which says (as its only contents): "Note：If the software is installed on drive C, please run it as an administrator. !!! Please close the anti-virus program first to avoid the program being deleted. Please don't worry. The program is safe." It has been infested with various viruses/malware since at least the 1.0.56 release, with different payloads all the way up to the current 2.0.9 release. Both the firmware updating software and the CPS obfuscate what they're doing in order to hide their true purpose. As this has been going on since these radios first went on sale (I have serial #111), Baofeng is either oblivious to the fact that they're shipping malware, or an active participant. This is the only analog Baofeng that I've seen this issue on (although I certainly haven't tried every model). The usual Baofeng CPS is rather poorly written, uses a pirated copy of a discontinued library from a company that went out of business, and suffers from a bunch of annoyances (crashing on radio read or write, not allowing the entry of air band frequencies, etc.) but nothing that I would categorize as intentionally bad.

1 0

Re: Baofeng K67 Pro
by Terri Kennedy 22 May '25

22 May '25

> From: hugh(a)hughjmilsom.co.uk > Subject: [users] Re: Baofeng K67 Pro > To: CHIRP users list <users(a)lists.chirpmyradio.com> > Message-ID: <26cb19f5-3799-40b8-ac9b-5f76a9598c2e@Spark> > Content-Type: text/plain; charset="utf-8" > > I’m sure you all know that the Baofeng UV-5RH Pro software does work > with the K67 Pro? > > TBH that s/w is so complex that I returned the K67 to the seller; I’m > waiting for CHIRP or a more user-friendly CPS before I try again. If the radio is similar to the 5RH Pro, you might not want it even if you could program it with CHIRP. My 1-sentence review of the 5RH Pro was "Straight into the parts bin". > From: ken hartmann <115irons(a)gmail.com> > Subject: [users] Re: Baofeng K67 Pro > To: CHIRP users list <users(a)lists.chirpmyradio.com> > Message-ID: > <CACev5_4wLXdKJjfGGEk8RFavLsEj6htAdKaxFy1UwfeY8sxW5A(a)mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" > > Cant get uv-5rm to connect to chirp.... tried all the different uv5r > options.. any suggeations Baofeng is known for "the model of the week" which is often an older radio re-packaged in a new case, and using one of the other model def- initions in CHIRP will work. OTOH, the 5RH and 5RM model designations have been re-used many times for completely different models. If your 5RM has a full-color screen, it is one of the newer ones. Try the UV-17 or UV-17 Pro and see if either of those will talk to it. The problem is that many Baofeng models use the same "wake up" com- mand and display the "Program" icon on their screens but time out be- cause the "code word" doesn't match what the radio expects. So the radio times out, the user thinks there is a cable / driver / CHIRP issue when in fact it's the wrong code word.

2 1

Baofeng K67 Pro
by Massimo Nespolo 22 May '25

22 May '25

Greetings, I have recently acquired a Baofeng K67 Pro, which is not (yet) supported by CHIRP. I have tried to read from the radio by choosing another model, but failed despite several tests. I have contacted Baofeng support asking whether there is a CPS for this model, here is their answer. ******************************** Please kindly notice that the K67 Pro is customized by other distributors, and we just sell the standard models on our website:https://www.baofengradio.com/. Please kindly note that different distributors may have varying requirements for the model's functionality depending on their clients' needs. As a result, the instructions for the product's functions may also differ. We only sell the K63 radio, you can check if the programming software can help you: https://baofeng.s3.amazonaws.com/BAOFENG_K6_CPS_1.1.2_20240913.zip To avoid confusion, dealers save all information regarding the models they have customized and provide after-sales service and custom model information to their own customers. Therefore, please contact the seller directly for further assistance. Hope you can solve the problem as soon as possible. ******************************** Unfortunately, the seller does not provide a programming software. I wonder if I can in some way help adding support to this model in CHIRP. I am willing to lend, or even give my radio to the developers, but I live in France and shipping to US would certainly be more expensive than the radio itself (which I got pretty cheap on the occasion of a sale). I guess that nothing can be done remotely, but if instead something is possible, I could give remote access to a PC connected to the radio (unsure whether this may be of some help....) Let me know if I can help in some way. Massimo

5 6

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

17 May '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://chirpmyradio.com/projects/chirp/wiki/Download A list of changes since the last build are here: eb4e4547 Correct P15UV model alias to UV-13Pro 293ee664 Remove a bunch of overly verbose yaesu_clone logging a4b3cf61 Fix hardware flow flag for TH-K2,TM-271/281, etc 68c78eb5 Updated Italian Translation 69a96dc0 Updated Spanish Translation Issues addressed in this build: [Bug 11973] TM-281 read/write failure [Bug 11980] Baofeng P15UV incorrectly listed as UV-17Pro --

3 3

TM-281 read/write failure
by nicheath＠gmail.com 11 May '25

11 May '25

Hello, I see the TM-281 is listed as supported and in the code comments it shows it is identical to the TM-271. Indeed if I connect to the radio using putty and send the ID command it returns TM-271. I am able to connect to the radio and read using Kenwoods MCP-1A software and I see the TX/RX lights on my serial adapter flash accordingly. Unfortunately this software is no longer being maintained. So I really would like to use CHIRP. I have proved out my cable connection by using the MCP-1A software. In CHIRP it doesn't seem even try sending data as my LEDs for TX/RX never light up when I hit connect. I noticed in the MCP1-A software that there is setting read from the radio with the name of "Data Speed" with two options: 1200bps and 9600bps. I have tried setting it to 9600bps and writing that to the radio and connecting with CHIRP and still no connection and not TX/RX lights. But I don't think this is the ultimate problem as I don't even see the TX light flash with CHIRP trying to send ID at the different speeds. I did notice in the debug log that it never tries 1200bps. It seems like CHIRP just isn't actually opening the serial port and writing to it. Also I noticed rts/cts is set to true but that should be false, I think. I'm not sure how to change that in chirp in the UI. Here is the debug log. ------------------------------------------------------------------------------------------------------------------ [2025-05-11 20:29:59,543] chirp.logger - DEBUG: CHIRP next-20250509 on Win32 (Unknown 10.0:22000) (Python 3.10.8) [2025-05-11 20:29:59,623] chirp.wxui - DEBUG: Using locale: en_US (276) [2025-05-11 20:29:59,631] chirp.wxui - DEBUG: Translation loaded=True for CHIRP: en_US (bg_BG,de,el,en_US,es,fr,hu,it,ja_JP,nl,pl,pt_BR,ro_RO,ru,tr_TR,uk_UA,zh_CN) from C:\bin\chirp-next-20250509-win64\chirp\locale [2025-05-11 20:29:59,639] chirp.wxui - DEBUG: Translation loaded=False for wxstd: en_US (af,an,ar,ca,ca@valencia,co,cs,da,de,el,es,eu,fa_IR,fi,fr,gl_ES,hi,hr,hu,id,it,ja,ka,ko_KR,lt,lv,ms,nb,ne,nl,pl,pt,pt_BR,ro,ru,sk,sl,sq,sv,ta,tr,uk,vi,zh_CN,zh_TW) [2025-05-11 20:30:00,177] main - INFO: Python/3.10.8 // Windows/Windows-10-10.0.22000-SP0 // CHIRP/next-20250509 // wx/4.2.0 msw (phoenix) wxWidgets 3.2.0 [2025-05-11 20:30:00,228] chirp.wxui.main - DEBUG: Recent is now ['Z:\\Ham\\Yaesu_VX-6_20220831.img', 'Z:\\Ham\\Anysecu_WP-9900_20231119.img', 'Z:\\Ham\\Anysecu_WP-9900_20230529.img', 'Z:\\Ham\\Anysecu_WP-9900_20230529.img', 'Z:\\Ham\\Anysecu_WP-9900_20230529.img', 'Z:\\Ham\\Anysecu_WP-9900_20230529.img', 'Untitled.csv'] [2025-05-11 20:30:00,492] chirp.wxui.main - INFO: Server reports next-20250509 is latest [2025-05-11 20:30:03,506] chirp.wxui.clone - DEBUG: All system ports: [{'device': 'COM1', 'name': 'COM1', 'description': 'Communications Port (COM1)', 'hwid': 'ACPI\\PNP0501\\1', 'vid': None, 'pid': None, 'serial_number': None, 'location': None, 'manufacturer': '(Standard port types)', 'product': None, 'interface': None}, {'device': 'COM9', 'name': 'COM9', 'description': 'USB Serial Port (COM9)', 'hwid': 'USB VID:PID=0403:6001 SER=A9SFJXJGA', 'vid': 1027, 'pid': 24577, 'serial_number': 'A9SFJXJGA', 'location': None, 'manufacturer': 'FTDI', 'product': None, 'interface': None}, {'device': 'COM4', 'name': 'COM4', 'description': 'com0com - serial port emulator (COM4)', 'hwid': 'COM0COM\\PORT\\CNCA1', 'vid': None, 'pid': None, 'serial_number': None, 'location': None, 'manufacturer': 'Vyacheslav Frolov', 'product': None, 'interface': None}, {'device': 'COM3', 'name': 'COM3', 'description': 'com0com - serial port emulator (COM3)', 'hwid': 'COM0COM\\PORT\\CNCB1', 'vid': None, 'pid': None, 'serial_number': None, 'location': None, 'manufacturer': 'Vyacheslav Frolov', 'product': None, 'interface': None}, {'device': 'COM6', 'name': 'COM6', 'description': 'USB-SERIAL CH340 (COM6)', 'hwid': 'USB VID:PID=1A86:7523 SER= LOCATION=1-1', 'vid': 6790, 'pid': 29987, 'serial_number': '', 'location': '1-1', 'manufacturer': 'wch.cn', 'product': None, 'interface': None}, {'device': 'COM13', 'name': 'COM13', 'description': 'USB Serial Port (COM13)', 'hwid': 'USB VID:PID=0403:6001 SER=AB0LC5EGA', 'vid': 1027, 'pid': 24577, 'serial_number': 'AB0LC5EGA', 'location': None, 'manufacturer': 'FTDI', 'product': None, 'interface': None}] [2025-05-11 20:30:03,717] chirp.wxui.clone - DEBUG: Selected <class 'chirp.drivers.kenwood_live.TM281Radio'> [2025-05-11 20:30:03,718] chirp.wxui.clone - DEBUG: Automatically chose last-used port COM13 for Kenwood TM-281 [2025-05-11 20:30:05,448] chirp.wxui.clone - DEBUG: Using port 'COM13' [2025-05-11 20:30:05,448] chirp.wxui.clone - DEBUG: Selected <class 'chirp.drivers.kenwood_live.TM281Radio'> [2025-05-11 20:30:05,455] chirp.wxui.clone - DEBUG: Serial opened: Serial<id=0x1a9ae406230, open=True>(port='COM13', baudrate=9600, bytesize=8, parity='N', stopbits=1, timeout=0.25, xonxoff=False, rtscts=True, dsrdtr=False) (rts=True dtr=True) [2025-05-11 20:30:05,455] chirp.wxui.clone - DEBUG: Selected <class 'chirp.drivers.kenwood_live.TM281Radio'> [2025-05-11 20:30:05,455] chirp.wxui.clone - DEBUG: Recorded last-used port COM13 for Kenwood TM-281 [2025-05-11 20:30:05,456] chirp.drivers.kenwood_live - INFO: Trying ID at baud 4800 with delimiter "('\r', ' ')" [2025-05-11 20:30:05,571] chirp.drivers.kenwood_live - DEBUG: PC->RADIO: ID [2025-05-11 20:30:06,649] chirp.drivers.kenwood_live - ERROR: Timeout waiting for data [2025-05-11 20:30:06,649] chirp.drivers.kenwood_live - ERROR: Giving up [2025-05-11 20:30:06,649] chirp.drivers.kenwood_live - INFO: Trying ID at baud 115200 with delimiter "('\r', ' ')" [2025-05-11 20:30:06,756] chirp.drivers.kenwood_live - DEBUG: PC->RADIO: ID [2025-05-11 20:30:07,839] chirp.drivers.kenwood_live - ERROR: Timeout waiting for data [2025-05-11 20:30:07,839] chirp.drivers.kenwood_live - ERROR: Giving up [2025-05-11 20:30:07,839] chirp.drivers.kenwood_live - INFO: Trying ID at baud 57600 with delimiter "('\r', ' ')" [2025-05-11 20:30:07,947] chirp.drivers.kenwood_live - DEBUG: PC->RADIO: ID [2025-05-11 20:30:09,027] chirp.drivers.kenwood_live - ERROR: Timeout waiting for data [2025-05-11 20:30:09,027] chirp.drivers.kenwood_live - ERROR: Giving up [2025-05-11 20:30:09,027] chirp.drivers.kenwood_live - INFO: Trying ID at baud 38400 with delimiter "('\r', ' ')" [2025-05-11 20:30:09,134] chirp.drivers.kenwood_live - DEBUG: PC->RADIO: ID [2025-05-11 20:30:10,216] chirp.drivers.kenwood_live - ERROR: Timeout waiting for data [2025-05-11 20:30:10,216] chirp.drivers.kenwood_live - ERROR: Giving up [2025-05-11 20:30:10,216] chirp.drivers.kenwood_live - INFO: Trying ID at baud 19200 with delimiter "('\r', ' ')" [2025-05-11 20:30:10,324] chirp.drivers.kenwood_live - DEBUG: PC->RADIO: ID [2025-05-11 20:30:11,400] chirp.drivers.kenwood_live - ERROR: Timeout waiting for data [2025-05-11 20:30:11,400] chirp.drivers.kenwood_live - ERROR: Giving up [2025-05-11 20:30:11,400] chirp.drivers.kenwood_live - INFO: Trying ID at baud 9600 with delimiter "('\r', ' ')" [2025-05-11 20:30:11,508] chirp.drivers.kenwood_live - DEBUG: PC->RADIO: ID [2025-05-11 20:30:12,591] chirp.drivers.kenwood_live - ERROR: Timeout waiting for data [2025-05-11 20:30:12,591] chirp.drivers.kenwood_live - ERROR: Giving up [2025-05-11 20:30:12,591] chirp.drivers.kenwood_live - INFO: Trying ID at baud 4800 with delimiter "(';', '')" [2025-05-11 20:30:12,700] chirp.drivers.kenwood_live - DEBUG: PC->RADIO: ID; [2025-05-11 20:30:13,775] chirp.drivers.kenwood_live - ERROR: Timeout waiting for data [2025-05-11 20:30:13,775] chirp.drivers.kenwood_live - ERROR: Giving up [2025-05-11 20:30:13,775] chirp.drivers.kenwood_live - INFO: Trying ID at baud 115200 with delimiter "(';', '')" [2025-05-11 20:30:13,883] chirp.drivers.kenwood_live - DEBUG: PC->RADIO: ID; [2025-05-11 20:30:14,956] chirp.drivers.kenwood_live - ERROR: Timeout waiting for data [2025-05-11 20:30:14,956] chirp.drivers.kenwood_live - ERROR: Giving up [2025-05-11 20:30:14,956] chirp.drivers.kenwood_live - INFO: Trying ID at baud 57600 with delimiter "(';', '')" [2025-05-11 20:30:15,063] chirp.drivers.kenwood_live - DEBUG: PC->RADIO: ID; [2025-05-11 20:30:16,140] chirp.drivers.kenwood_live - ERROR: Timeout waiting for data [2025-05-11 20:30:16,140] chirp.drivers.kenwood_live - ERROR: Giving up [2025-05-11 20:30:16,140] chirp.drivers.kenwood_live - INFO: Trying ID at baud 38400 with delimiter "(';', '')" [2025-05-11 20:30:16,248] chirp.drivers.kenwood_live - DEBUG: PC->RADIO: ID; [2025-05-11 20:30:17,328] chirp.drivers.kenwood_live - ERROR: Timeout waiting for data [2025-05-11 20:30:17,328] chirp.drivers.kenwood_live - ERROR: Giving up [2025-05-11 20:30:17,328] chirp.drivers.kenwood_live - INFO: Trying ID at baud 19200 with delimiter "(';', '')" [2025-05-11 20:30:17,436] chirp.drivers.kenwood_live - DEBUG: PC->RADIO: ID; [2025-05-11 20:30:18,511] chirp.drivers.kenwood_live - ERROR: Timeout waiting for data [2025-05-11 20:30:18,511] chirp.drivers.kenwood_live - ERROR: Giving up [2025-05-11 20:30:18,511] chirp.drivers.kenwood_live - INFO: Trying ID at baud 9600 with delimiter "(';', '')" [2025-05-11 20:30:18,619] chirp.drivers.kenwood_live - DEBUG: PC->RADIO: ID; [2025-05-11 20:30:19,697] chirp.drivers.kenwood_live - ERROR: Timeout waiting for data [2025-05-11 20:30:19,697] chirp.drivers.kenwood_live - ERROR: Giving up [2025-05-11 20:30:19,697] chirp.wxui.clone - ERROR: Failed to open serial: No response from radio Traceback (most recent call last): File "chirp\wxui\clone.py", line 808, in _actual_action File "chirp\drivers\kenwood_live.py", line 101, in __init__ File "chirp\drivers\kenwood_live.py", line 157, in get_id chirp.errors.RadioError: No response from radio [2025-05-11 20:30:26,285] chirp.wxui.bugreport - DEBUG: Created page start [2025-05-11 20:30:26,292] chirp.wxui.bugreport - DEBUG: Created page creds [2025-05-11 20:30:26,316] chirp.wxui.bugreport - DEBUG: Created page existbug [2025-05-11 20:30:26,326] chirp.wxui.bugreport - DEBUG: Created page update [2025-05-11 20:30:31,384] chirp.wxui.bugreport - DEBUG: Created page newbug [2025-05-11 20:40:50,755] chirp.wxui.clone - DEBUG: All system ports: [{'device': 'COM1', 'name': 'COM1', 'description': 'Communications Port (COM1)', 'hwid': 'ACPI\\PNP0501\\1', 'vid': None, 'pid': None, 'serial_number': None, 'location': None, 'manufacturer': '(Standard port types)', 'product': None, 'interface': None}, {'device': 'COM9', 'name': 'COM9', 'description': 'USB Serial Port (COM9)', 'hwid': 'USB VID:PID=0403:6001 SER=A9SFJXJGA', 'vid': 1027, 'pid': 24577, 'serial_number': 'A9SFJXJGA', 'location': None, 'manufacturer': 'FTDI', 'product': None, 'interface': None}, {'device': 'COM4', 'name': 'COM4', 'description': 'com0com - serial port emulator (COM4)', 'hwid': 'COM0COM\\PORT\\CNCA1', 'vid': None, 'pid': None, 'serial_number': None, 'location': None, 'manufacturer': 'Vyacheslav Frolov', 'product': None, 'interface': None}, {'device': 'COM3', 'name': 'COM3', 'description': 'com0com - serial port emulator (COM3)', 'hwid': 'COM0COM\\PORT\\CNCB1', 'vid': None, 'pid': None, 'serial_number': None, 'location': None, 'manufacturer': 'Vyacheslav Frolov', 'product': None, 'interface': None}, {'device': 'COM6', 'name': 'COM6', 'description': 'USB-SERIAL CH340 (COM6)', 'hwid': 'USB VID:PID=1A86:7523 SER= LOCATION=1-1', 'vid': 6790, 'pid': 29987, 'serial_number': '', 'location': '1-1', 'manufacturer': 'wch.cn', 'product': None, 'interface': None}, {'device': 'COM13', 'name': 'COM13', 'description': 'USB Serial Port (COM13)', 'hwid': 'USB VID:PID=0403:6001 SER=AB0LC5EGA', 'vid': 1027, 'pid': 24577, 'serial_number': 'AB0LC5EGA', 'location': None, 'manufacturer': 'FTDI', 'product': None, 'interface': None}] [2025-05-11 20:40:50,974] chirp.wxui.clone - DEBUG: Selected <class 'chirp.drivers.kenwood_live.TM281Radio'> [2025-05-11 20:40:50,974] chirp.wxui.clone - DEBUG: Automatically chose last-used port COM13 for Kenwood TM-281 [2025-05-11 20:40:58,620] chirp.wxui.clone - DEBUG: Using port 'COM13' [2025-05-11 20:40:58,620] chirp.wxui.clone - DEBUG: Selected <class 'chirp.drivers.kenwood_live.TM281Radio'> [2025-05-11 20:40:58,620] chirp.wxui.clone - DEBUG: Serial opened: Serial<id=0x1a9ae761750, open=True>(port='COM13', baudrate=9600, bytesize=8, parity='N', stopbits=1, timeout=0.25, xonxoff=False, rtscts=True, dsrdtr=False) (rts=True dtr=True) [2025-05-11 20:40:58,620] chirp.wxui.clone - DEBUG: Selected <class 'chirp.drivers.kenwood_live.TM281Radio'> [2025-05-11 20:40:58,620] chirp.wxui.clone - DEBUG: Recorded last-used port COM13 for Kenwood TM-281 [2025-05-11 20:40:58,620] chirp.drivers.kenwood_live - INFO: Trying ID at baud 4800 with delimiter "('\r', ' ')" [2025-05-11 20:40:58,730] chirp.drivers.kenwood_live - DEBUG: PC->RADIO: ID [2025-05-11 20:40:59,828] chirp.drivers.kenwood_live - ERROR: Timeout waiting for data [2025-05-11 20:40:59,828] chirp.drivers.kenwood_live - ERROR: Giving up [2025-05-11 20:40:59,828] chirp.drivers.kenwood_live - INFO: Trying ID at baud 115200 with delimiter "('\r', ' ')" [2025-05-11 20:40:59,938] chirp.drivers.kenwood_live - DEBUG: PC->RADIO: ID [2025-05-11 20:41:01,036] chirp.drivers.kenwood_live - ERROR: Timeout waiting for data [2025-05-11 20:41:01,036] chirp.drivers.kenwood_live - ERROR: Giving up [2025-05-11 20:41:01,036] chirp.drivers.kenwood_live - INFO: Trying ID at baud 57600 with delimiter "('\r', ' ')" [2025-05-11 20:41:01,146] chirp.drivers.kenwood_live - DEBUG: PC->RADIO: ID [2025-05-11 20:41:02,245] chirp.drivers.kenwood_live - ERROR: Timeout waiting for data [2025-05-11 20:41:02,245] chirp.drivers.kenwood_live - ERROR: Giving up [2025-05-11 20:41:02,245] chirp.drivers.kenwood_live - INFO: Trying ID at baud 38400 with delimiter "('\r', ' ')" [2025-05-11 20:41:02,355] chirp.drivers.kenwood_live - DEBUG: PC->RADIO: ID [2025-05-11 20:41:03,439] chirp.drivers.kenwood_live - ERROR: Timeout waiting for data [2025-05-11 20:41:03,439] chirp.drivers.kenwood_live - ERROR: Giving up [2025-05-11 20:41:03,439] chirp.drivers.kenwood_live - INFO: Trying ID at baud 19200 with delimiter "('\r', ' ')" [2025-05-11 20:41:03,549] chirp.drivers.kenwood_live - DEBUG: PC->RADIO: ID [2025-05-11 20:41:04,584] chirp.drivers.kenwood_live - ERROR: Timeout waiting for data [2025-05-11 20:41:04,584] chirp.drivers.kenwood_live - ERROR: Giving up [2025-05-11 20:41:04,584] chirp.drivers.kenwood_live - INFO: Trying ID at baud 9600 with delimiter "('\r', ' ')" [2025-05-11 20:41:04,691] chirp.drivers.kenwood_live - DEBUG: PC->RADIO: ID [2025-05-11 20:41:05,723] chirp.drivers.kenwood_live - ERROR: Timeout waiting for data [2025-05-11 20:41:05,723] chirp.drivers.kenwood_live - ERROR: Giving up [2025-05-11 20:41:05,723] chirp.drivers.kenwood_live - INFO: Trying ID at baud 4800 with delimiter "(';', '')" [2025-05-11 20:41:05,826] chirp.drivers.kenwood_live - DEBUG: PC->RADIO: ID; [2025-05-11 20:41:06,900] chirp.drivers.kenwood_live - ERROR: Timeout waiting for data [2025-05-11 20:41:06,900] chirp.drivers.kenwood_live - ERROR: Giving up [2025-05-11 20:41:06,900] chirp.drivers.kenwood_live - INFO: Trying ID at baud 115200 with delimiter "(';', '')" [2025-05-11 20:41:07,010] chirp.drivers.kenwood_live - DEBUG: PC->RADIO: ID; [2025-05-11 20:41:08,017] chirp.drivers.kenwood_live - ERROR: Timeout waiting for data [2025-05-11 20:41:08,017] chirp.drivers.kenwood_live - ERROR: Giving up [2025-05-11 20:41:08,017] chirp.drivers.kenwood_live - INFO: Trying ID at baud 57600 with delimiter "(';', '')" [2025-05-11 20:41:08,127] chirp.drivers.kenwood_live - DEBUG: PC->RADIO: ID; [2025-05-11 20:41:09,185] chirp.drivers.kenwood_live - ERROR: Timeout waiting for data [2025-05-11 20:41:09,185] chirp.drivers.kenwood_live - ERROR: Giving up [2025-05-11 20:41:09,185] chirp.drivers.kenwood_live - INFO: Trying ID at baud 38400 with delimiter "(';', '')" [2025-05-11 20:41:09,295] chirp.drivers.kenwood_live - DEBUG: PC->RADIO: ID; [2025-05-11 20:41:10,337] chirp.drivers.kenwood_live - ERROR: Timeout waiting for data [2025-05-11 20:41:10,337] chirp.drivers.kenwood_live - ERROR: Giving up [2025-05-11 20:41:10,337] chirp.drivers.kenwood_live - INFO: Trying ID at baud 19200 with delimiter "(';', '')" [2025-05-11 20:41:10,447] chirp.drivers.kenwood_live - DEBUG: PC->RADIO: ID; [2025-05-11 20:41:11,528] chirp.drivers.kenwood_live - ERROR: Timeout waiting for data [2025-05-11 20:41:11,528] chirp.drivers.kenwood_live - ERROR: Giving up [2025-05-11 20:41:11,528] chirp.drivers.kenwood_live - INFO: Trying ID at baud 9600 with delimiter "(';', '')" [2025-05-11 20:41:11,637] chirp.drivers.kenwood_live - DEBUG: PC->RADIO: ID; [2025-05-11 20:41:12,711] chirp.drivers.kenwood_live - ERROR: Timeout waiting for data [2025-05-11 20:41:12,711] chirp.drivers.kenwood_live - ERROR: Giving up [2025-05-11 20:41:12,711] chirp.wxui.clone - ERROR: Failed to open serial: No response from radio Traceback (most recent call last): File "chirp\wxui\clone.py", line 808, in _actual_action File "chirp\drivers\kenwood_live.py", line 101, in __init__ File "chirp\drivers\kenwood_live.py", line 157, in get_id chirp.errors.RadioError: No response from radio

4 4