- Users - lists.chirpmyradio.com

cli can't connect to my baofeng uv25
by joeri.cochuyt＠gmail.com 29 Apr '25

29 Apr '25

Hi, I'm trying to download an img file from my radio trough chirpc but with no luck. It keeps telling me that the radio is not connected. I tested this in the gui and everything worked fine so it's not a bad cable. I'm on windows python 3.10 and using the latest build from github. Listing radios does work trough chirpc --list-radios. DELAY = 5.0 MAX_RETRIES = 5 RETRY_BACKOFF = 2 def download_image(radio_model, com_port, mmap_file="backupimage.img"): """ Attempts to download the image from the radio with retry logic. """ delay = DELAY for attempt in range(1, MAX_RETRIES + 1): try: cmd = [ sys.executable, str(CHIRPPATH), '-r', radio_model, f'--serial={com_port}', f'--mmap={mmap_file}', '--download-mmap' ] pprint(cmd) print(f"Attempt {attempt}: Running command: {' '.join(cmd)}") time.sleep(delay) result = subprocess.run(cmd, capture_output=True, text=True, check=True) print("Success:", result.stdout) return True except subprocess.CalledProcessError as e: print(f"Attempt {attempt} failed with code {e.returncode}: {e.stderr.strip()}") if attempt < MAX_RETRIES: print(f"Retrying after {delay} seconds...") delay *= RETRY_BACKOFF # Exponential backoff else: print("Max retries reached. Giving up.") return False radio_driver_id = 'Baofeng_UV-25' com_port = 'COM4' # double checked this! print(f"\nDownloading image from radio '{radio_driver_id}' on port '{com_port}'...") download_image(radio_driver_id, com_port) ------------------------------------------------------------------------------------------- Attempt 4: Running command: C:\Users\...\Desktop\chirptest\venv\Scripts\python.exe C:\Users\joeri\Desktop\chirptest\chirp\chirpc -r Baofeng_UV-25 --serial=COM4 --mmap=backupimage.img --download-mmap Attempt 4 failed with code 1: ERROR: No response from radio. Check connector and cabling! Traceback (most recent call last): File "C:\Users\...\Desktop\chirptest\chirp\chirp\cli\main.py", line 380, in main radio.sync_in() File "C:\Users\...\Desktop\chirptest\chirp\chirp\drivers\baofeng_uv17Pro.py", line 1166, in sync_in data = self.download_function() File "C:\Users\...\Desktop\chirptest\chirp\chirp\drivers\baofeng_uv17Pro.py", line 132, in _download _do_ident(radio) File "C:\Users\...\Desktop\chirptest\chirp\chirp\drivers\baofeng_uv17Pro.py", line 115, in _do_ident ack = _sendmagic(radio, radio._magic, len(radio._fingerprint)) File "C:\Users\...\Desktop\chirptest\chirp\chirp\drivers\baofeng_uv17Pro.py", line 107, in _sendmagic return bfc._rawrecv(radio, response_len) File "C:\Users\...\Desktop\chirptest\chirp\chirp\drivers\baofeng_common.py", line 55, in _rawrecv raise errors.RadioNoContactLikelyK1() chirp.errors.RadioNoContactLikelyK1: No response from radio. Check connector and cabling! Retrying after 40.0 seconds... ------------------------------------------------------------------------------------------- Has anyone successfully used chirpc with a UV-25 radio?" or "What am I missing in my script?

4 4

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

25 Apr '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: 52536959 th350: Fix FM preset failure in settings on US version 72a881a0 dr735: Fix handling out-of-range extra settings 6498adf5 Update bg_BG.po a96c6df2 New settings for Wouxun KG-805g Issues addressed in this build: [Bug 11947] list index out of range error [Bug 11948] TYT TH-350 US Settings - No attribute fm_presets --

1 0

UV-5R+Plus
by sentinelwolf70＠gmail.com 22 Apr '25

22 Apr '25

If this has been discussed before, I apologize for adding to the discussion. I have a UV-5R+Plus that isn't accepting my image when I upload it (cloned) to the radio. I've been successful with my old UV5R and new AR-5RM. I don't see the UV-5R+Plus in the radio drop-down. I've attempted the UV-5R, UV-5RH, UV-5X, and UV-5XP without success. Can anyone point me in the correct direction? Thank you so much for your assistance. Shawn

2 1

BF-F9 v2
by Ricardo Duran 18 Apr '25

18 Apr '25

Hello, Don’t see the Baofeng BF-F9 v2 listed. What model should I use to program my radio? Thanks, Ric

3 3

QYT KT-8900D
by abqmules＠gmail.com 15 Apr '25

15 Apr '25

Can't connect with radio no matter what driver I use....tried 3 different dates. Does work with the Chinese app but that is quirky and cumbersome software to use. CHIRP make some kind of initial contact and then shuts off with a beep.

4 3

New chirp-next build
by donotreply＠chirpmyradio.com 04 Apr '25

04 Apr '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: bc27f665 TH9000: Add programmable buttons to settings. 8ca56d44 tk280: Fix choosing highest applicable tuning step bb857b11 Change lower bound valid_bands acceptance test 45ea1202 Simplify required_step() to honor the allow list 389b27c9 Fix two unused globals for new flake8 cec1d4b3 ic9700: Decode cross tone modes 66c3d7d4 KG805G fix: Duplex field calculated wrong 6a9dec97 tk8180: Fix choosing max step f0d7807f tk8180: Fix 12.5kHz-required step frequencies Issues addressed in this build: [Bug 11911] IC-9700: Unable to set Cross tone modes --

1 0

Can not get Chirp Linux or Windows to work with Yaesu VX5R, FT60R, VX150 or TYT UV8000D
by David Marshall 04 Apr '25

04 Apr '25

I can not get Chirp to work with anything. I have a RT Systems USB-57A cable and the TYT cable that came with the radio. I am aware of the problem with bootleg Prolific hips for the TYT cable, and have installed the appropriate driver from: https://www.miklor.com/COM/UV_Drivers.php#install I am using a computer with an Asus ROG Strix B365F motherboard that dual boots Windows 10 and PCLinuxOS Debian Edition. I have tried known working USB ports on both the back and front of the computer. I have also tried an HP laptop running Windows 11 with the FT60R. Just for the record, I have also tried an extremely old copy or RT Systems ADMS-1E in Windows with the VX5R, and FT60 Commander, and the free TYT software for the UV8000D. On the FT60R and VX5R, after trying to read from the radios, I get a "Clone Error" on the radio display. When trying to read from the UV8000D, it appears to start, but the progress bar never goes beyond 0%. My primary need is getting the TYT UV8000D programmed because that thing is impossible to program with the keypad. Knowing that my problem is not just with Chirp on Windows 10, 11 and Linux, but also with other software, does anyone have some ideas to try other that buying RT Systems software and cables? Thank you, 73 de N8OAY

1 0

220 BAND
by Ricardo Duran 29 Mar '25

29 Mar '25

hI I read somewhere that the CHIRP program for Baofeng Radios such as the UV-5R III model drops the capability of programming in the 220 input/output frequencies. This model is supposed to operate on the three bands. Everything else seems to work just fine as far as programming the radio. Your program is wonderful. I am using the latest version of CHIRP. Am I not doing something correctly?. Or is this simply a limitation to the program? Thank you in advance for whatever help you can provide, 73, de Ric WD7U

2 2

Re: Retevis H777 Unable to Connect
by Joshua Morin 28 Mar '25

28 Mar '25

Confirming factory software works.

3 2

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

28 Mar '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: 906aa970 Wouxun KG-805g: Add new radio driver cb06abfd Updated Italian Translation de4bdc44 Initial support of QYT KT-5000. 7f63cf04 Updated Spanish Translation 74d862ef kg816/818: Fix query string processing 3cae2992 add UV21ProV2 and UV21ProGPS f3d71bf8 Disable immutable mem.extra in expanded memory editor 1ea297cf update upper frequency limit that is displayed in validation error message Issues addressed in this build: [Bug 11208] Having Problem Downloading [Bug 11904] Name column gets disabled (not reflected in UI) if extra is added to immutable [New Model 10530] QYT KT-5000 [New Model 11214] Wouxun KG-805G [New Model 7781] Wouxun KG-805 --

1 0

Possible Bug In TD H3 In Chirp
by K0LNY ?? 25 Mar '25

25 Mar '25

Hello All, I don't know if this is a bug in Chirp or what, but I am using the open firmware on the Tid TD H3, which is the Ham version of that radio, and for the life of me, I could not get a GMRS repeater in my area to work from a programmed channel that I put in with Chirp. So last night I put a channel in by hand, and set it to a number, and that works. So, it isn't the radio, with this issue. Glenn You're never too old to learn something stupid. Glenn K0LNY & WSAT439

1 0

TID TD H3 Channels That Chirp Complains About
by K0LNY ?? 24 Mar '25

24 Mar '25

Hello, Well last night I finally got my 64 channels into the radio with Chirp. The newest Chirp I grabbed yesterday may have done the trick, but even that didn't work at first. Anyway, there are still two channels that I may have the lines wrong on, and one imports to the radio with Chirp, but does not work, and the other errors with Chirp, and I am wondering if there is something with these lines that need fixing. One is for my FM transmitter in my house, it transmits at 86.99 mhz. I can pick it up with my H3 by toggling to FM with the bottom side key and entering the frequency. The other problem channel is an AM airband frequency, and this radio is supposed to receive AM airband. Chirp says it should not use duplex, and I either have zero or nothing in that field, so I don't know why Chirp complains about that. I'll paste the lines below in case anyone cares to make suggestions for changes. Thanks. Glenn 64 HomeFM 87 FM 63 AIRPRT 122.7 5 88.5 88.5 23 NN 23 Tone->Tone AM 5 Glenn K0LNY & WSAT439

1 0

import errors on a tidradio H3
by K0LNY ?? 23 Mar '25

23 Mar '25

Hello folks, I'm struggling with trying to import a CSV into Chirp. I download from my radio, and save to CSV, and then edit the CSV, and Chirp gives me an error message, which I'll paste below. After that error message is okayed, I get the error, invalid file format. Thanks for any ideas. I've had others look at it, and they can't tell what is wrong here. Glenn Import messages Line 2: [cross_mode] Invalid cross mode 'Tone+AC0APg-Tone' Line 3: [cross_mode] Invalid cross mode 'Tone+AC0APg-Tone' Line 4: [cross_mode] Invalid cross mode 'Tone+AC0APg-Tone' Line 5: [cross_mode] Invalid cross mode 'Tone+AC0APg-Tone' Line 6: [cross_mode] Invalid cross mode 'Tone+AC0APg-Tone' Line 7: [cross_mode] Invalid cross mode 'Tone+AC0APg-Tone' Line 8: [duplex] `+AC0-' is not in valid list: ['', '+', '-', 'split', 'off'] Line 9: [duplex] `+AC0-' is not in valid list: ['', '+', '-', 'split', 'off'] Line 10: [cross_mode] Invalid cross mode 'Tone+AC0APg-Tone' Line 11: [cross_mode] Invalid cross mode 'Tone+AC0APg-Tone' Line 12: [cross_mode] Invalid cross mode 'Tone+AC0APg-Tone' Line 13: [cross_mode] Invalid cross mode 'Tone+AC0APg-Tone' Line 14: [cross_mode] Invalid cross mode 'Tone+AC0APg-Tone' Line 15: [cross_mode] Invalid cross mode 'Tone+AC0APg-Tone' Line 16: [cross_mode] Invalid cross mode 'Tone+AC0APg-Tone' Line 17: [cross_mode] Invalid cross mode 'Tone+AC0APg-Tone' Line 18: [cross_mode] Invalid cross mode 'Tone+AC0APg-Tone' Line 19: [cross_mode] Invalid cross mode 'Tone+AC0APg-Tone' Line 20: [cross_mode] Invalid cross mode 'Tone+AC0APg-Tone' Line 21: [cross_mode] Invalid cross mode 'Tone+AC0APg-Tone' Line 22: [cross_mode] Invalid cross mode 'Tone+AC0APg-Tone' Line 23: [cross_mode] Invalid cross mode 'Tone+AC0APg-Tone' Line 24: [cross_mode] Invalid cross mode 'Tone+AC0APg-Tone' Line 25: [cross_mode] Invalid cross mode 'Tone+AC0APg-Tone' OK Glenn K0LNY & WSAT439

2 1

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

21 Mar '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: 01cf01ca Fix radio prompt disable flag checking 0b63fe2d Fix scrolling in "info" tab 936229ab fix "cloning from" to cloning to" message 5788e55a IC-T10: Adding Icom IC-T10 driver. Fixes #10181 07381a94 Add Baofeng K61 model alias 798e6ead Compress F8HP Pro and BFK6 memory maps 735513cb baofeng_uv17Pro.py: add Baofeng_K6 - for #11507 a8333736 baofeng_uv17Pro.py: address 'DeprecationWarning' issues - prep for #11507 12a6f646 baofeng_uv17Pro.py: address 'FutureWarning' issues - prep for #11507 9057aa4b RT-470X: Adds NAM mode ba9ef5ce mml_jc8810: Enables Scramble and Encryption feature 7d0a609a Fix Baofeng K5-Plus marked as unconfirmed for py3 176ae17e Fix FM-converted D-STAR repeaterbook entries 0cc95c5d baofeng_uv17Pro.py: correct DTMF mapping - fixes #11894 205342f0 Related to #11882 Add roger beep list for TD-H3 e387509a Add Support for Wouxun KG-935H 3bb24886 Fix GMRS negative offset in band plan Issues addressed in this build: [Bug 11396] Tidradio TD-H8 Chirp driver allows only repeaters in memory channels [Bug 11882] Options to choose from in "Battery Save" [Bug 11892] multi-mode repeaters rejected when they have valid analog config [Bug 11894] baofeng_uv17Pro driver has incorrect DTMF mapping for *, #, A, B, C, D [Bug 11896] Works on the Baofeng k5 plus [Bug 11898] Developer Mode - Unable to scroll all items under "Info" [Bug 11901] Yaseu VX3 no longer showing prompts [Feature 11899] Add Scrambler to RT-470X [New Model 10181] Icom IC-T10 [New Model 11507] Baofeng K6 and K61 [New Model 11779] KG-935H --

1 0

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

17 Mar '25

Ticket was created as suggested. https://chirpmyradio.com/issues/11787 I believe the debug file has errors using all available options. Let me know if I am missing something. Josh

2 1

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

14 Mar '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: 975593d8 tdh8: Eliminate duplex requirement on mems 31-52 5627ebef Revert "Clean up yaesu_clone transmit echo munching" 64fd07cf Related to #11882 Code cleanup in tdh8.py 39b5cc63 Fixes bug #11882 in tdh8.py d78318fe Remove TH-350 from the unsupported list 7ba82c4f Fix TSV paste bringing in a ghost memory e09ae4d9 Add "copy portable" to memedit right-click menu 33c87234 Revert "th_uv88: Add Dual Wait settings for RA89,P2,etc" Issues addressed in this build: [Bug 10473] Newest version of ChirpNext resets Yaesu-FT70D when trying to upload data [Bug 11396] Tidradio TD-H8 Chirp driver allows only repeaters in memory channels [Bug 11882] Options to choose from in "Battery Save" [Feature 11843] Improved copy-and-paste between CHIRP and spreadsheets [Feature 11864] Please add Dual Watch to Retevis P2 / Retevis 62 / TYT TC-29 --

1 0

Re: Retevis H777 Unable to Connect
by Joshua Morin 12 Mar '25

12 Mar '25

I looked at the release notes for the latest build and saw the new model ticket number (11775) for the H777H_FRS shows an SKU of A9104J for the FRS version. The SKU for the radios I am trying to connect is A9294C. Is this a different H777 model that also needs support developed?

3 3

Weircom FT7800
by jack.bvlgari＠gmail.com 08 Mar '25

08 Mar '25

Hi There! I just bought new radio, weircom FT7800 and used chirp to program because i thought it can be used with yaesu FT7800 system by CHIRP, but it cannot. Is there by any change Developer can build the program for weircom FT7800? Thank you for your time. Good Luck! 73

1 0

TYT th-9800 plus quad band radio
by stephen wahl 08 Mar '25

08 Mar '25

The 9800 has two vfo sides. Usually referred to by users as right side and kept side. The left side encompasses all four bands and receives other non-amateur radio bands. The right side only handles the 2-meter and 70-cm bands. My question, how program each side separately? I have a list of 2-meter and 70-cm repeaters that I would like to program to the right side of the radio. Leaving the left side for 25, 50 and non transmit frequencies. Thanks Stephen Wahl KI7TKR

2 1

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

07 Mar '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: 3e663d36 th_uv88: Add Dual Wait settings for RA89,P2,etc 1219bee0 Fix Cut/Paste active in right-click for query source d29ee641 Un-flatten int settings in browser view 2834441c Updated Italian Translation Issues addressed in this build: [Bug 11871] Query Result right-click edit operations are not disabled [Feature 11864] Please add Dual Watch to Retevis P2 / Retevis 62 / TYT TC-29 --

1 0

Can CHIRP files be preloaded before connecting to radio?
by loumickie＠msn.com 01 Mar '25

01 Mar '25

All, I'm new to using CHIRP. I have an ICOM 2730A which has the base unit mounted in the trunk of my car. Can I setup all of my repeater info into the various memories before I connect the programming cable from the computer to the radio? Hope that makes sense, Lou

3 3

New chirp-next build
by donotreply＠chirpmyradio.com 01 Mar '25

01 Mar '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: edd9a9c3 Fix repeaterbook query loading Issues addressed in this build: [Bug 11863] No access to Repeater Book --

1 0

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 21 Feb '25

21 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 21 Feb '25

21 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 02 Feb '25

02 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 25 Jan '25

25 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