- Users - lists.chirpmyradio.com

[chirp_users] help
by Craig 03 Mar '23

03 Mar '23

I am a newbie to the radio programming world. I have the newest version of CHIRP. I have several questions. I live in north central Nevada in a very rural area and I want to program my Baofeng UV-R5 pro to the most common freq. for this area so if STHTF. CHIRP has several openstock configurations was which ones to use? Also how do you export then to the radio once you choose? I tried to to click on the upload to radio and it is "grayed" out. Any help is appreciated Thanks C Sent with [Proton Mail](https://proton.me/) secure email.

3 3

[chirp_users] New chirp-next build
by donotreply＠chirp.danplanet.com 03 Mar '23

03 Mar '23

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since yesterday and may include additional features, bug fixes, etc. As a reminder, this is different from the "daily" CHIRP builds in that new development and features are happening here. It is the latest and greatest, but also may be less stable than the "daily" builds at this time. If it works for you, we recommend using CHIRP-next, but if your radio is not yet working on it, then you may prefer to use the "daily" builds for the time being. You can get it from here: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: Changes for Build #81 [3046399+kk7ds] Add BTECH MURS-V2 - fixes #10409 [3046399+kk7ds] Provide some warnings about developer mode [3046399+kk7ds] Add "Load module from issue" helper --

1 0

[chirp_users] Prolific Chip On Windows 11
by Anthony (N2KI) 02 Mar '23

02 Mar '23

I plugged a Baofeng programming cable into a laptop running Windows 11 but Win11 does not have the drivers to support it. Anyone have a programming cable that works on both Windows 10 and 11? Regards, Anthony (N2KI)

6 6

[chirp_users] New chirp-next build
by donotreply＠chirp.danplanet.com 02 Mar '23

02 Mar '23

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since yesterday and may include additional features, bug fixes, etc. As a reminder, this is different from the "daily" CHIRP builds in that new development and features are happening here. It is the latest and greatest, but also may be less stable than the "daily" builds at this time. If it works for you, we recommend using CHIRP-next, but if your radio is not yet working on it, then you may prefer to use the "daily" builds for the time being. You can get it from here: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: Changes for Build #80 [3046399+kk7ds] Adds IC-V86 test image and fix failing tests. [3046399+kk7ds] Ensure browser panels are re-fit on selection [3046399+kk7ds] Allow loaded modules to be reloaded [3046399+kk7ds] Disable dev radio menu items when appropriate [3046399+kk7ds] Remove MUNCH_CLONE_RESP from icf [3046399+kk7ds] GMRS-50V2: tolerate factory out-of-band vfo frequencies - fixes #10408 [3046399+kk7ds] lt725uv.py: expand UHF band limits to match radios limits - fixes #10396 [3046399+kk7ds] uv5r.py: Add support for 3rd FM frequency storage method - fixes #10406 --

1 0

[chirp_users] New chirp-next build
by donotreply＠chirp.danplanet.com 01 Mar '23

01 Mar '23

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since yesterday and may include additional features, bug fixes, etc. As a reminder, this is different from the "daily" CHIRP builds in that new development and features are happening here. It is the latest and greatest, but also may be less stable than the "daily" builds at this time. If it works for you, we recommend using CHIRP-next, but if your radio is not yet working on it, then you may prefer to use the "daily" builds for the time being. You can get it from here: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: Changes for Build #79 [3046399+kk7ds] baofeng_wp970i.py: limit check the VFO A/B TXP settings - fixes #10403 [3046399+kk7ds] Fix typo in FT-60 settings menu [3046399+kk7ds] Make directory honor metadata VARIANT on load [3046399+kk7ds] Fix VX-6 220 power handling [3046399+kk7ds] Fix Quansheng TG-UV2 for Python3 [3046399+kk7ds] baofeng_wp970i: Fix bug when no fm chip is present --

1 0

[chirp_users] uv5r plus corrupt img file
by Adrian Norcross 25 Feb '23

25 Feb '23

Hello, I'm new to programming radios so please bear with me. I have downloaded some frequencies from my radio through Chirp to a folder on my computer. When I try to open the folder I get a message saying that the "disk image file is corrupted" . I have downloaded a uv5r image file from the internet and I get the same message. Could anyone advise me as to a fix. Many thanks Adrian.

4 9

[chirp_users] New chirp-next build
by donotreply＠chirp.danplanet.com 24 Feb '23

24 Feb '23

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since yesterday and may include additional features, bug fixes, etc. As a reminder, this is different from the "daily" CHIRP builds in that new development and features are happening here. It is the latest and greatest, but also may be less stable than the "daily" builds at this time. If it works for you, we recommend using CHIRP-next, but if your radio is not yet working on it, then you may prefer to use the "daily" builds for the time being. You can get it from here: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: Changes for Build #78 [3046399+kk7ds] Updates to check-patch job [3046399+kk7ds] Remove debug sleep left in ft90 [3046399+kk7ds] Improve TS480 tuning_step fix [3046399+kk7ds] Improve skip test to catch more things --

1 0

[chirp_users] New chirp-next build
by donotreply＠chirp.danplanet.com 23 Feb '23

23 Feb '23

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since yesterday and may include additional features, bug fixes, etc. As a reminder, this is different from the "daily" CHIRP builds in that new development and features are happening here. It is the latest and greatest, but also may be less stable than the "daily" builds at this time. If it works for you, we recommend using CHIRP-next, but if your radio is not yet working on it, then you may prefer to use the "daily" builds for the time being. You can get it from here: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: Changes for Build #77 [3046399+kk7ds] Remove legacy platform serial enumeration [3046399+kk7ds] Migrate old mox-based tests to mock [3046399+kk7ds] Remove legacy X11 compat hack for Unix/macOS [3046399+kk7ds] Remove legacy platform file dialog helpers [3046399+kk7ds] Stop using mock from external packages [3046399+kk7ds] Log the SHA256 of module files when loading [3046399+kk7ds] Fix support for radios that need port open early [3046399+kk7ds] Fix Yaesu FT-90 for python3 [3046399+kk7ds] Make required_step find 10kHz before 5kHz [3046399+kk7ds] Add Yaesu FT-90 test image and fix bugs --

1 0

[chirp_users] Kenwood TK 2000
by Bennie Potgieter 21 Feb '23

21 Feb '23

Gooday Can anyone assist me with this,kan the TK 2000 be programmed with chirp? Thank you

3 10

[chirp_users] Moving Columns
by Paul G7BHE 19 Feb '23

19 Feb '23

Hi everyone I may have missed this in the chat. Is it possible to rearrange the columns? I’ve tried several methods and can’t move anything. If not then I would be very grateful if this could be considered for future builds. Many thanks Paul G7BHE Sent from my iPhone

3 3

[chirp_users] Changing data Baofeng UV5
by Julian Macassey 18 Feb '23

18 Feb '23

I gave up trying to programme my Baofeng UV-5RV2+ using the previous CHIRP release. When CHIRP next came out, I thought maybe I could get it to programme my radio. I went through the steps to grab an *img file and load it into the radio. Then I saved it with modifications then downloaded, with a window saying "cloning". Exiting CHIRP, turning the radio off and on does NOT change the file. Am I doing something wrong? Yours Julian Macassey, GM8LUK -- The modern web is a crumbling edifice of unspeakable horror - Jamie Zawinski <jwz(a)jwz.org>

4 6

Re: [chirp_users] Changing data Baofeng UV5
by Rich NE1EE 18 Feb '23

18 Feb '23

This is a great explanation of why and how...I wish that all newbies (like me, at one time ;-) could read this... On 2023-02-18 08:27:-0500, you wrote: >What most people do is set one display line to FREQuency and the other >display line to NAME. That way when you set both display lines to the >same channel number (they have to be synced manually because each >display line is independent and the radio has no ability to >automatically sync them), the channel name and frequency can be seen >at the same time. This is really the hot tip here... ~R~ 72/73 de Rich NE1EE The Dusty Key On the banks of the Piscataqua

2 1

[chirp_users] New chirp-next build
by donotreply＠chirp.danplanet.com 18 Feb '23

18 Feb '23

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since yesterday and may include additional features, bug fixes, etc. As a reminder, this is different from the "daily" CHIRP builds in that new development and features are happening here. It is the latest and greatest, but also may be less stable than the "daily" builds at this time. If it works for you, we recommend using CHIRP-next, but if your radio is not yet working on it, then you may prefer to use the "daily" builds for the time being. You can get it from here: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: Changes for Build #75 [3046399+kk7ds] Add Retevis RT86 - fixes #10377 [3046399+kk7ds] Update Upload/Download menu items [3046399+kk7ds] Try a test frequency from each valid band [3046399+kk7ds] Keep the radio mmap from setup in clone tests [3046399+kk7ds] Ensure we return integers in some bitwise funcs [3046399+kk7ds] Use python 3 print() syntax in check_parameters.py --

1 0

Re: [chirp_users] The meaning of CHIRP...
by Rich NE1EE 17 Feb '23

17 Feb '23

On 2023-02-17 10:43:-0500, you wrote: >I'm not sure if my screenshot went through. I got a message saying my message was blocked by moderator or something like that. The ai software basically derived its name from the chirp sound a radio makes when communicating. I recall that when I was a new engineer, my manager told me that I needed to have "projects for score" each year to increase the likelihood of a raise or promotion (or both ;-), AND that the more clever the name of the project, the more likely it was to stick in everyone's mind, and that, too, was taken into account as part of the success of the project. I have followed his advice over the years, even when I started my own consulting company. CHIRP is so much more memorable than 'repidr', so I think it qualifies. I was on the MMS engineering development and post-launch data analysis team, and always thought that PhDs needed to hire some slug to name their projects. MMS is /so/ forgettable ;-) CHIRP is so memorable :-) ~R~ 72/73 de Rich NE1EE The Dusty Key On the banks of the Piscataqua

1 0

Re: [chirp_users] The meaning of CHIRP...
by Rich NE1EE 17 Feb '23

17 Feb '23

On 2023-02-17 08:36:-0500, you wrote: >> � There is an excellent open source program called CHIRP which stands >> for CHInese Radio Project." > >Which has no basis in fact. The oldest CHIRP build <snip> > >Jim KC9HI I have often wondered about the name. I sent a message to that web page developer. I appreciate Jim being able to post. I am still left wondering why it was named that...I continue to hope that someone will step up with real history, as trivial as this subject is...if Jim's stuff goes back to 2008, it is not likely that we will find the original reason for the name, unless some original developers are lurking about. ~R~ 72/73 de Rich NE1EE The Dusty Key On the banks of the Piscataqua

3 3

[chirp_users] The meaning of CHIRP...
by Dave Turnmire 17 Feb '23

17 Feb '23

I am a long time user of CHIRP and I just realized there is a key bit of knowledge I lack... and unless I'm missing it... it is also missing from the web site's FAQ. Where did the name come from? Does CHIRP stand for something? Did Dan's first radio keep chirping at him every time he pressed the wrong button? 😉 Inquiring minds want to know... (and I'm preparing to teach a class on CHIRP...) Dave

3 2

[chirp_users] New chirp-next build
by donotreply＠chirp.danplanet.com 17 Feb '23

17 Feb '23

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since yesterday and may include additional features, bug fixes, etc. As a reminder, this is different from the "daily" CHIRP builds in that new development and features are happening here. It is the latest and greatest, but also may be less stable than the "daily" builds at this time. If it works for you, we recommend using CHIRP-next, but if your radio is not yet working on it, then you may prefer to use the "daily" builds for the time being. You can get it from here: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: Changes for Build #74 [3046399+kk7ds] Initial commit of ICOM IC-V80 driver. Fixes #174 [3046399+kk7ds] Subsequent support for skip memories in IC-V80 driver. Fixes #174 [3046399+kk7ds] Settings support added to IC-V80 driver. Fixes #174 [3046399+kk7ds] Fix IC-V80 style issues [3046399+kk7ds] Add IC-V80 test image and fix tests [3046399+kk7ds] Add IC-V80 clone ranges and endframe [3046399+kk7ds] Add IC-7100 as reported working [3046399+kk7ds] uv5r.py: relocate validate_memory() to subclasses that need to use it [3046399+kk7ds] retevis_rb17p.py: relocate validate_memory to subclass, update syntax [3046399+kk7ds] Add Baojie BJ-218 to Python3 Driver Testing matrix --

1 0

[chirp_users] IC-7100 programming
by Mike W 16 Feb '23

16 Feb '23

I understand the LIVE reminder when reading the IC-7100 memory banks into Chirp, but how do I load a data file to program the damn thing?. Either I'm thick or I'm missing something, or both ! 73 Mike G8NXD

2 3

[chirp_users] New chirp-next build
by donotreply＠chirp.danplanet.com 16 Feb '23

16 Feb '23

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since yesterday and may include additional features, bug fixes, etc. As a reminder, this is different from the "daily" CHIRP builds in that new development and features are happening here. It is the latest and greatest, but also may be less stable than the "daily" builds at this time. If it works for you, we recommend using CHIRP-next, but if your radio is not yet working on it, then you may prefer to use the "daily" builds for the time being. You can get it from here: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: Changes for Build #73 [3046399+kk7ds] Add BTech GMRS-50V2 - fixes #10374 [3046399+kk7ds] Add support for KPG-89D .dat files for TK-x180 [3046399+kk7ds] Add Tail Eliminate setting for TH-UVF8D [3046399+kk7ds] Translate en/disabled string for developer mode [3046399+kk7ds] Remove old chirp XML schema definition files --

1 0

[chirp_users] Python3 Branch
by James Keener 15 Feb '23

15 Feb '23

I have a Kenwood TM-V7 and a Baofeng UV-5R, along with the appropriate programming cables. I'm running Linux, and write python, php, and rust for my day job. Are there any tasks or features I can help build or test? Thank you, Jim Keener KC3NPJ

1 0

[chirp_users] New chirp-next build
by donotreply＠chirp.danplanet.com 15 Feb '23

15 Feb '23

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since yesterday and may include additional features, bug fixes, etc. As a reminder, this is different from the "daily" CHIRP builds in that new development and features are happening here. It is the latest and greatest, but also may be less stable than the "daily" builds at this time. If it works for you, we recommend using CHIRP-next, but if your radio is not yet working on it, then you may prefer to use the "daily" builds for the time being. You can get it from here: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: Changes for Build #72 [3046399+kk7ds] btech.py: move validate_memory to subclasses that use it --

1 0

[chirp_users] New chirp-next build
by donotreply＠chirp.danplanet.com 14 Feb '23

14 Feb '23

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since yesterday and may include additional features, bug fixes, etc. As a reminder, this is different from the "daily" CHIRP builds in that new development and features are happening here. It is the latest and greatest, but also may be less stable than the "daily" builds at this time. If it works for you, we recommend using CHIRP-next, but if your radio is not yet working on it, then you may prefer to use the "daily" builds for the time being. You can get it from here: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: Changes for Build #71 [3046399+kk7ds] Move validate_memory() to special subclasses that need to use it [3046399+kk7ds] bf_t8.py: relocate validate_memory() to subclass - fixes #10371 --

1 0

[chirp_users] New chirp-next build
by donotreply＠chirp.danplanet.com 13 Feb '23

13 Feb '23

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since yesterday and may include additional features, bug fixes, etc. As a reminder, this is different from the "daily" CHIRP builds in that new development and features are happening here. It is the latest and greatest, but also may be less stable than the "daily" builds at this time. If it works for you, we recommend using CHIRP-next, but if your radio is not yet working on it, then you may prefer to use the "daily" builds for the time being. You can get it from here: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: Changes for Build #70 [3046399+kk7ds] baofeng_common.py: relocate validate_memory() - fixes 10367 --

3 2

Re: [chirp_users] chirp_users Digest, Vol 170, Issue 12
by v44kf.dx 12 Feb '23

12 Feb '23

Cannot update On Sun, Feb 12, 2023 at 4:01 PM <chirp_users-request(a)intrepid.danplanet.com> wrote: > Send chirp_users mailing list submissions to > chirp_users(a)intrepid.danplanet.com > > To subscribe or unsubscribe via the World Wide Web, visit > http://intrepid.danplanet.com/mailman/listinfo/chirp_users > or, via email, send a message with subject or body 'help' to > chirp_users-request(a)intrepid.danplanet.com > > You can reach the person managing the list at > chirp_users-owner(a)intrepid.danplanet.com > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of chirp_users digest..." > > > Today's Topics: > > 1. New chirp-next build (donotreply(a)chirp.danplanet.com) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 12 Feb 2023 02:09:21 -0800 (PST) > From: donotreply(a)chirp.danplanet.com > Subject: [chirp_users] New chirp-next build > To: chirp_users(a)intrepid.danplanet.com > Message-ID: <202039202.139.1676196561759(a)eagle.danplanet.com> > Content-Type: text/plain; charset="utf-8" > > Greetings, > > A new build of CHIRP-next is available. This includes changes made > directly to the tree since yesterday and may include additional features, > bug fixes, etc. As a reminder, this is different from the "daily" CHIRP > builds in that new development and features are happening here. It is the > latest and greatest, but also may be less stable than the "daily" builds at > this time. If it works for you, we recommend using CHIRP-next, but if your > radio is not yet working on it, then you may prefer to use the "daily" > builds for the time being. > > You can get it from here: > > http://trac.chirp.danplanet.com/chirp_next/ > > A list of changes since the last build are here: > > Changes for Build #69 > [3046399+kk7ds] Greek translation added > > > > > -- > > ------------------------------ > > _______________________________________________ > chirp_users mailing list > chirp_users(a)intrepid.danplanet.com > http://intrepid.danplanet.com/mailman/listinfo/chirp_users > To unsubscribe, send an email to > chirp_users-unsubscribe(a)intrepid.danplanet.com > > End of chirp_users Digest, Vol 170, Issue 12 > ******************************************** >

2 1

[chirp_users] New chirp-next build
by donotreply＠chirp.danplanet.com 12 Feb '23

12 Feb '23

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since yesterday and may include additional features, bug fixes, etc. As a reminder, this is different from the "daily" CHIRP builds in that new development and features are happening here. It is the latest and greatest, but also may be less stable than the "daily" builds at this time. If it works for you, we recommend using CHIRP-next, but if your radio is not yet working on it, then you may prefer to use the "daily" builds for the time being. You can get it from here: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: Changes for Build #69 [3046399+kk7ds] Greek translation added --

1 0

[chirp_users] New chirp-next build
by donotreply＠chirp.danplanet.com 11 Feb '23

11 Feb '23

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since yesterday and may include additional features, bug fixes, etc. As a reminder, this is different from the "daily" CHIRP builds in that new development and features are happening here. It is the latest and greatest, but also may be less stable than the "daily" builds at this time. If it works for you, we recommend using CHIRP-next, but if your radio is not yet working on it, then you may prefer to use the "daily" builds for the time being. You can get it from here: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: Changes for Build #68 [3046399+kk7ds] Add Retevis RB628 - fixes #10325 [3046399+kk7ds] Make common master lists immutable [3046399+kk7ds] Populate Tone and DTCS lists from RadioFeatures [3046399+kk7ds] Fix logging errors in anytone778uv [3046399+kk7ds] Fix scan/skip bit in TH-UVF8D --

1 0

[chirp_users] Ubuntu Launcher
by K0LNY_Glenn 10 Feb '23

10 Feb '23

Hi, I have chirp in Ubuntu-Mate, 18.04. I installed an older Chirp because it works with my screenreader. But the installed launcher, but if I run chirpw in a terminal, it runs. Or I can type in the terminal: /usr/bin/chirpw and it runs fine. I have been trying to make a desktop launcher to do this, so I don't have to launch it in a terminal. But the desktop launcher attempts I try do nothing, no errors, and no launching of chirp. Any ideas why I can launch it in a terminal, but not in a desktop launcher? Thanks. Glenn

4 6

[chirp_users] Kenwood TH-D72, glitches
by Rich NE1EE 10 Feb '23

10 Feb '23

Been a while since I used chirp. Picked up a Yaesu FT-70D, and wanted to copy my Kenwood settings. 1. Tried Kenwood clone mode, but got an error. 2. Used LIVE mode, but then could not save the img. Still wondering why CHIRP doesn't permit what MCP does. I never have found that live mode is required, but maybe I need to revisit why I think there is a difference. At any rate, I downloaded successfully from the FT-70 and the TH-D72 using chirp 20230209. Copied the D72 data to the memory cells for the FT-70, uploaded, and voila! found that mysteriously all my names got "encrypted". Took me a few minutes to remember that some of my radios use upper and lower case, and some don't. 3. That brought me to another surprise. No simple way to UC the names in chirp. I figured there'd be a menu item for that. The only way I can think of is to edit the csv. I'd then want to paste only the names...in the end, I used EditPad Pro, and ran a regex on the names. Imported the csv back into chirp. 4. As a test, I connected the D72 and downloaded in LIVE mode. Success. Then tried to download in clone mode. "Could not open port 'COM6': Permission error(13, Access denied, none,5) 5. Wait! I then disconnected from the D72, thinking that the COM port was still owned by another process (live download), reconnected, and successfully downloaded a clone copy of the D72. Oops. Nothing is displayed. Because I had not used clone mode before, I looked in CHIRP help and browsed the web. Nothing found. I immediately tried live mode, and it worked. Immediately tried clone mode. Access denied. Disconnect/reconnect D72. Cloning ran, but as before, no display. Is there anything here I should file a bug report on, or am I just experiencing growing pains ? ;-) ~R~ 72/73 de Rich NE1EE The Dusty Key On the banks of the Piscataqua

2 1

[chirp_users] New chirp-next build
by donotreply＠chirp.danplanet.com 10 Feb '23

10 Feb '23

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since yesterday and may include additional features, bug fixes, etc. As a reminder, this is different from the "daily" CHIRP builds in that new development and features are happening here. It is the latest and greatest, but also may be less stable than the "daily" builds at this time. If it works for you, we recommend using CHIRP-next, but if your radio is not yet working on it, then you may prefer to use the "daily" builds for the time being. You can get it from here: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: Changes for Build #67 [3046399+kk7ds] Fix translating name-inherited column headers [3046399+kk7ds] Fix transposed TK-3140 key definitions. [3046399+kk7ds] Fix frozen check for win32 driver import [3046399+kk7ds] Add Retevis RB28 - fixes #10324 --

1 0

[chirp_users] New chirp-next build
by donotreply＠chirp.danplanet.com 09 Feb '23

09 Feb '23

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since yesterday and may include additional features, bug fixes, etc. As a reminder, this is different from the "daily" CHIRP builds in that new development and features are happening here. It is the latest and greatest, but also may be less stable than the "daily" builds at this time. If it works for you, we recommend using CHIRP-next, but if your radio is not yet working on it, then you may prefer to use the "daily" builds for the time being. You can get it from here: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: Changes for Build #66 [3046399+kk7ds] Rename es_ES translation to es [3046399+kk7ds] Add PMR446 frequency table to bandplan_iaru_r1 - fixes #10357 --

1 0

[chirp_users] New chirp-next build
by donotreply＠chirp.danplanet.com 08 Feb '23

08 Feb '23

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since yesterday and may include additional features, bug fixes, etc. As a reminder, this is different from the "daily" CHIRP builds in that new development and features are happening here. It is the latest and greatest, but also may be less stable than the "daily" builds at this time. If it works for you, we recommend using CHIRP-next, but if your radio is not yet working on it, then you may prefer to use the "daily" builds for the time being. You can get it from here: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: Changes for Build #65 [3046399+kk7ds] Use wx.Locale instead of gettext [3046399+kk7ds] Fix untranslated menu names [3046399+kk7ds] Refresh locale files [3046399+kk7ds] New Model Support- Wouxun KG-935G Plus [3046399+kk7ds] UV-9R Pro: Allow 7 character channel names - fixes #9932 [3046399+kk7ds] Update es_ES.po --

3 3

[chirp_users] Chirp installation under Ubuntu error messages
by Phil 08 Feb '23

08 Feb '23

I believe that I have all of the required dependencies installed but perhaps I've missed something. :~/.local/bin$ ./chirp Traceback (most recent call last): File "/home/phil/.local/bin/./chirp", line 33, in <module> sys.exit(load_entry_point('chirp===py3-20221124', 'console_scripts', 'chirp')()) File "/home/phil/.local/bin/./chirp", line 25, in importlib_load_entry_point return next(matches).load() File "/usr/lib/python3.10/importlib/metadata/__init__.py", line 171, in load module = import_module(match.group('module')) File "/usr/lib/python3.10/importlib/__init__.py", line 126, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "<frozen importlib._bootstrap>", line 1050, in _gcd_import File "<frozen importlib._bootstrap>", line 1027, in _find_and_load File "<frozen importlib._bootstrap>", line 1006, in _find_and_load_unlocked File "<frozen importlib._bootstrap>", line 688, in _load_unlocked File "<frozen importlib._bootstrap_external>", line 883, in exec_module File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed File "/home/phil/.local/lib/python3.10/site-packages/chirp/wxui/__init__.py", line 6, in <module> from chirp import directory File "/home/phil/.local/lib/python3.10/site-packages/chirp/directory.py", line 26, in <module> from chirp.drivers import icf # , rfinder File "/home/phil/.local/lib/python3.10/site-packages/chirp/drivers/__init__.py", line 1, in <module> from chirp.drivers import vx5 File "/home/phil/.local/lib/python3.10/site-packages/chirp/drivers/vx5.py", line 164, in <module> @directory.register AttributeError: partially initialized module 'chirp.directory' has no attribute 'register' (most likely due to a circular import) -- Regards, Phil

3 9

[chirp_users] New chirp-next build
by donotreply＠chirp.danplanet.com 07 Feb '23

07 Feb '23

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since yesterday and may include additional features, bug fixes, etc. As a reminder, this is different from the "daily" CHIRP builds in that new development and features are happening here. It is the latest and greatest, but also may be less stable than the "daily" builds at this time. If it works for you, we recommend using CHIRP-next, but if your radio is not yet working on it, then you may prefer to use the "daily" builds for the time being. You can get it from here: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: Changes for Build #64 [3046399+kk7ds] Set setup.py version to zero [3046399+kk7ds] Enable Baofeng BF-V8A TX CTCSS Tones - fixes #9784 [3046399+kk7ds] UV-6R: Allow 7 character channel names - fixes #6891 fixes #10351 [3046399+kk7ds] Tolerate null fields in repeaterbook responses --

1 0

[chirp_users] New chirp-next build
by donotreply＠chirp.danplanet.com 06 Feb '23

06 Feb '23

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since yesterday and may include additional features, bug fixes, etc. As a reminder, this is different from the "daily" CHIRP builds in that new development and features are happening here. It is the latest and greatest, but also may be less stable than the "daily" builds at this time. If it works for you, we recommend using CHIRP-next, but if your radio is not yet working on it, then you may prefer to use the "daily" builds for the time being. You can get it from here: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: Changes for Build #63 [3046399+kk7ds] GMRS-V2 update/streamline driver - fixes #10350 --

1 0

[chirp_users] New chirp-next build
by donotreply＠chirp.danplanet.com 05 Feb '23

05 Feb '23

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since yesterday and may include additional features, bug fixes, etc. As a reminder, this is different from the "daily" CHIRP builds in that new development and features are happening here. It is the latest and greatest, but also may be less stable than the "daily" builds at this time. If it works for you, we recommend using CHIRP-next, but if your radio is not yet working on it, then you may prefer to use the "daily" builds for the time being. You can get it from here: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: Changes for Build #62 [3046399+kk7ds] Update baofeng_wp970i.py driver to use mem.immutable - #10288 [3046399+kk7ds] Update py3_driver_testers.txt [3046399+kk7ds] Update GMRS bandplan in bandplan_na.py - fixes #10347 --

1 0

[chirp_users] New chirp-next build
by donotreply＠chirp.danplanet.com 04 Feb '23

04 Feb '23

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since yesterday and may include additional features, bug fixes, etc. As a reminder, this is different from the "daily" CHIRP builds in that new development and features are happening here. It is the latest and greatest, but also may be less stable than the "daily" builds at this time. If it works for you, we recommend using CHIRP-next, but if your radio is not yet working on it, then you may prefer to use the "daily" builds for the time being. You can get it from here: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: Changes for Build #61 [3046399+kk7ds] Update es_ES.po [3046399+kk7ds] Fix CHARSET_1252 skipping the space character [3046399+kk7ds] Settings for keys on TKx140 and TKx160 [3046399+kk7ds] Fix TYT UVF8 for Python 3 [3046399+kk7ds] Fix up tests.base.get_mem() for some radios [3046399+kk7ds] Update bf_t8.py driver to use mem.immutable (revisited) - #10288 [3046399+kk7ds] Mark IC-746 as tested --

1 0

[chirp_users] New chirp-next build
by donotreply＠chirp.danplanet.com 03 Feb '23

03 Feb '23

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since yesterday and may include additional features, bug fixes, etc. As a reminder, this is different from the "daily" CHIRP builds in that new development and features are happening here. It is the latest and greatest, but also may be less stable than the "daily" builds at this time. If it works for you, we recommend using CHIRP-next, but if your radio is not yet working on it, then you may prefer to use the "daily" builds for the time being. You can get it from here: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: Changes for Build #60 [3046399+kk7ds] Use legacy branch for legacy builds [3046399+kk7ds] Build snap using chirp-next release tarball [3046399+kk7ds] Allow registering multiple formats with same ext [3046399+kk7ds] Expand repeaterbook tests to another state [3046399+kk7ds] Fix truncated multiword names in properties box [3046399+kk7ds] Add Kenwood TK-2140/3140 support [3046399+kk7ds] Fix some TK-8160 issues --

1 0

[chirp_users] New chirp-next build
by donotreply＠chirp.danplanet.com 02 Feb '23

02 Feb '23

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since yesterday and may include additional features, bug fixes, etc. As a reminder, this is different from the "daily" CHIRP builds in that new development and features are happening here. It is the latest and greatest, but also may be less stable than the "daily" builds at this time. If it works for you, we recommend using CHIRP-next, but if your radio is not yet working on it, then you may prefer to use the "daily" builds for the time being. You can get it from here: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: Changes for Build #58 [3046399+kk7ds] Update uv5r.py driver to use mem.immutable - #10288 [3046399+kk7ds] add menu items before enabling/disabling Changes for Build #59 No changes

1 0

[chirp_users] Bricked UV82HP & BF-F8HP
by Jeff Gallaway 01 Feb '23

01 Feb '23

I was using a tidradio bluetooth programming adaptor and after programming the scan feature stopped working and the programmed channels wouldn't program and a lot of other issues that I assume come with a bricked radio. I tried resetting both radios from the menu but it didn't help. I'm assuming the firmware is messed up somehow. UV82HP - Hold down #3 and power on- US2S35 Hold down #6 & power on- 150602N BF-F8HP - Hold down #3 and power on- F8HP-1 Hold down #6 & power on6- 160102 I'm not sure if there's a way to do a hard reset in chirp to get everything back to factory settings or if I have to do something with the firmware? Any help would be appreciated. I'm better at seeing how it's done on video rather than following steps but anything is worth a try right now. Thanks, Jeff

3 2

[chirp_users] UV82HP & BF-F8HP
by Jeff Gallaway 01 Feb '23

01 Feb '23

I was using a tidradio bluetooth programming adaptor and after programming the scan feature stopped working and the programmed channels wouldn't program and a lot of other issues that I assume come with a bricked radio. I tried resetting both radios from the menu but it didn't help. I'm assuming the firmware is messed up somehow. UV82HP - Hold down #3 and power on- US2S35 Hold down #6 & power on- 150602N BF-F8HP - Hold down #3 and power on- F8HP-1 Hold down #6 & power on6- 160102 I'm not sure if there's a way to do a hard reset in chirp to get everything back to factory settings or if I have to do something with the firmware? Any help would be appreciated. I'm better at seeing how it's done on video rather than following steps but anything is worth a try right now. Thanks, Jeff

1 0

[chirp_users] New chirp-next build
by donotreply＠chirp.danplanet.com 01 Feb '23

01 Feb '23

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since yesterday and may include additional features, bug fixes, etc. As a reminder, this is different from the "daily" CHIRP builds in that new development and features are happening here. It is the latest and greatest, but also may be less stable than the "daily" builds at this time. If it works for you, we recommend using CHIRP-next, but if your radio is not yet working on it, then you may prefer to use the "daily" builds for the time being. You can get it from here: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: Changes for Build #57 [3046399+kk7ds] Update ga510.py driver to use mem.immutable - #10288

1 0

[chirp_users] New chirp-next build
by donotreply＠chirp.danplanet.com 31 Jan '23

31 Jan '23

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since yesterday and may include additional features, bug fixes, etc. As a reminder, this is different from the "daily" CHIRP builds in that new development and features are happening here. It is the latest and greatest, but also may be less stable than the "daily" builds at this time. If it works for you, we recommend using CHIRP-next, but if your radio is not yet working on it, then you may prefer to use the "daily" builds for the time being. You can get it from here: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: Changes for Build #56 [noreply] Wouxun KG-935G Call Code fix (#458) [3046399+kk7ds] Add the SVG logo to sdist, bdist_whl [3046399+kk7ds] Fix bank index test [3046399+kk7ds] Update btech.py to use mem.immutable - #10288

1 0

[chirp_users] kenwood tk-768 (N)
by Paul Pohl 30 Jan '23

30 Jan '23

Good day I have kenwood tk-768(n) and I use ch340 module (Prolific USB to Serial, Driver details; ser2pl64 (version 3.6.81.357) serenum.sys (version 10.0.22621.1)) I use chirp (daily-20221217) but doesn't read from radio. On the lcd appear -pc- and than it stays there. On the PC an error; "radio refuse to enter into program mode after a few tries" pops up Please help me, what am I doing wrong? Kind Regards, Paul

3 4

[chirp_users] New chirp-next build
by donotreply＠chirp.danplanet.com 30 Jan '23

30 Jan '23

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since yesterday and may include additional features, bug fixes, etc. As a reminder, this is different from the "daily" CHIRP builds in that new development and features are happening here. It is the latest and greatest, but also may be less stable than the "daily" builds at this time. If it works for you, we recommend using CHIRP-next, but if your radio is not yet working on it, then you may prefer to use the "daily" builds for the time being. You can get it from here: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: Changes for Build #55 [3046399+kk7ds] Fix actually returning status from fast-driver [3046399+kk7ds] fix UV-9R Pro FM preset bug - fixes #10318 [3046399+kk7ds] Fix setting duplex=split on TK-8160 [3046399+kk7ds] Fix can_odd_split flag in FRS-A1 and RB27 [3046399+kk7ds] Treat ValidationWarnings as non-fatal in the UI [3046399+kk7ds] Upgrade gmrsv2 and rb17p use mem.immutable [3046399+kk7ds] Fix brute force duplex test [3046399+kk7ds] Fix ID-80H mode and band limits

1 0

Re: [chirp_users] chirp-next for NixOS
by Tim Lavoie 29 Jan '23

29 Jan '23

Thanks Graham, that works! Now I have to go look for a cable... > From: Graham Christensen <graham(a)grahamc.com> > Hi Tim, > > I think if you use Chirp from nixpkgs-unstable / nixos-unstable, > you'll get chirp-next with python3 (from 2022-12-07.) > > Try this: > > nix run nixpkgs#chirp

2 1

[chirp_users] Should I file a bug report - can't program a frequency in chirp that I can from keypad
by Doug Scoda 29 Jan '23

29 Jan '23

Please advise if this is an easy fix and I will generate a bug report. I am able to program into the IC-80AD (ID-80H) FM broadcast band frequencies such as 97.1. I can do so from the keypad or the Icom software. After a successful download and a test, the radio scans and receives the monitoring frequencies as expected. When I download the clone into Chirp, on the entries for the FM stations are errored out in RED in the memory number column. On right clicking and checking properties of the memory entry, I get the following text message box: `?2' is not in valid list: ['WFM', 'FM', 'NFM', 'AM', 'NAM', 'DV', 'USB', 'LSB', 'CW', 'RTTY', 'DIG', 'PKT', 'NCW', 'NCWR', 'CWR', 'P25', 'Auto', 'RTTYR', 'FSK', 'FSKR', 'DMR', 'DN', 'FSK-R', 'CW-R', 'Data+LSB', 'Data+USB', 'Data+FM', 'USER-L', 'USER-U', 'LSB+CW', 'USB+CW', 'RTTY-L', 'RTTY-U', 'N/A'] If I try to program via chirp 97.1 FM into a memory I get the following error even though it is in the valid frequency range of the receiver. Invalid edit: Frequency 97.100000 is out of supported range I get the same error when programming CB frequencies with chirp even though the radio is capable of monitoring that AM band.

2 1

[chirp_users] Can anyone help me identify a radio
by g7jiq1 29 Jan '23

29 Jan '23

Can anyone Identify this radio so I may reprogram it with chirp. It is badged on the front as Vitesse Rugged Under the battery it is marked as TEKK Model XU-1000 It is a 16 channel uhf Any help would be greatly received

2 2

[chirp_users] New chirp-next build
by donotreply＠chirp.danplanet.com 29 Jan '23

29 Jan '23

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since yesterday and may include additional features, bug fixes, etc. As a reminder, this is different from the "daily" CHIRP builds in that new development and features are happening here. It is the latest and greatest, but also may be less stable than the "daily" builds at this time. If it works for you, we recommend using CHIRP-next, but if your radio is not yet working on it, then you may prefer to use the "daily" builds for the time being. You can get it from here: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: Changes for Build #54 [3046399+kk7ds] Check for merge commits in PRs [3046399+kk7ds] Add fast-driver tox target [3046399+kk7ds] Run fast-driver for CI [3046399+kk7ds] Fix TK-8180 duplex=off setting [3046399+kk7ds] Add Retevis RB628B - fixes #10325 [3046399+kk7ds] Fix Brute Force mode test [3046399+kk7ds] Fix Icom ID-880 obscure tone modes [3046399+kk7ds] Fix radioddity_r2 frs16 immutable mode

1 0

[chirp_users] chirp-next for NixOS
by Tim Lavoie 28 Jan '23

28 Jan '23

Hello, There is a version of chirp-daily (20220823) packaged up as a Nix package for NixOS Linux. It does install fine, along with python 2, but fails since there is a third element when it splits the version number. I thought I'd prefer to try out chirp-next anyway, and then not need python 2. Has anyone tried wrapping it up as a Nix package yet? (There isn't one in the nix repo.) Cheers, Tim

2 1

[chirp_users] Icom IC-80AD HT - Assigning Channel Bank
by Doug Scoda 28 Jan '23

28 Jan '23

------------------------------ >>* Am I missing something on how to edit the index numbers? * >Yes, you're missing the step where you click on the index in the GUI and change it to something sensible. However, your query made me realize that this was broken back in December and nobody noticed until now! I imagine maybe you clicked a couple (thousand) times on the index thinking maybe you could change it, and assumed you were missing something else. My apologies :) >Can you file a bug? I'll get a fix cooked up for tomorrow's build. >Thanks! >--Dan Thank you Dan, the fix works exactly as expected. -ds

2 1

[chirp_users] New chirp-next build
by donotreply＠chirp.danplanet.com 28 Jan '23

28 Jan '23

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since yesterday and may include additional features, bug fixes, etc. As a reminder, this is different from the "daily" CHIRP builds in that new development and features are happening here. It is the latest and greatest, but also may be less stable than the "daily" builds at this time. If it works for you, we recommend using CHIRP-next, but if your radio is not yet working on it, then you may prefer to use the "daily" builds for the time being. You can get it from here: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: Changes for Build #53 [3046399+kk7ds] Record Yaesu FT-65E as working [3046399+kk7ds] Fix inability to edit bank index [3046399+kk7ds] Fix test infrastructure for radios with subdevs [3046399+kk7ds] Make editorset use a Treebook for many subdevs [3046399+kk7ds] Add Kenwood TK-7160, 8160 support [3046399+kk7ds] Add Retevis RB28B - fixes #10324

1 0

[chirp_users] Wouxun 980p 950p
by max＠m-u-m.info 27 Jan '23

27 Jan '23

Hello, fist great that the wouxun 980p is now supported, i will test it the next days (it is in my car an at the moment its a little bit cold outside to play with notebook and chirp next) but if have 950p inside and i can download from radio but the every informations are very crippy it would be nice to have these radio also thx max

1 0

[chirp_users] Icom IC-80AD HT - Assigning Channel Banks
by Doug Scoda 27 Jan '23

27 Jan '23

Hello all, >From the best I can figure, the IC-80AD is similar D-Star version of the ID-80H. I can use the ID-80H profile to download and upload memory channels to my IC-80AD. I see the Memories Group, Bank Group and Settings Group. All channel memories, Banks and Settings match the radio. >From the radio keypad I am able to create Banks in the IC-80AD and add memory channels to those banks. The bank entries get populated with an index number. When I scan in bank mode, all is well and it works as intended In Chirp, when I try to assign a memory location to a check box in the Banks tab, the bank check box is assigned, but the bank index number is defaulted to zero. I can't figure out how to edit the bank index numbers on those entries. If an unindexed bank is uploaded to the radio, the banks do not scan, Am I missing something on how to edit the index numbers? -ds

2 1

[chirp_users] RFG-8100
by Don Breazile 27 Jan '23

27 Jan '23

RFG-8100 Is there any plans to support this radio?

1 0

[chirp_users] New chirp-next build
by donotreply＠chirp.danplanet.com 27 Jan '23

27 Jan '23

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since yesterday and may include additional features, bug fixes, etc. As a reminder, this is different from the "daily" CHIRP builds in that new development and features are happening here. It is the latest and greatest, but also may be less stable than the "daily" builds at this time. If it works for you, we recommend using CHIRP-next, but if your radio is not yet working on it, then you may prefer to use the "daily" builds for the time being. You can get it from here: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: Changes for Build #52 [3046399+kk7ds] Use cp1252 codec for kenwood_live comms [3046399+kk7ds] Add CHARSET_1252 and make TH-D7 use it [3046399+kk7ds] Add a fake TH-F7 serial fixture for testing [3046399+kk7ds] Expand the CSV character set to include cp1252

1 0

[chirp_users] New chirp-next build
by donotreply＠chirp.danplanet.com 26 Jan '23

26 Jan '23

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since yesterday and may include additional features, bug fixes, etc. As a reminder, this is different from the "daily" CHIRP builds in that new development and features are happening here. It is the latest and greatest, but also may be less stable than the "daily" builds at this time. If it works for you, we recommend using CHIRP-next, but if your radio is not yet working on it, then you may prefer to use the "daily" builds for the time being. You can get it from here: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: Changes for Build #51 [3046399+kk7ds] Fix Icom IC-E90 special memory editing [3046399+kk7ds] Fix editing specials with negative indexes [3046399+kk7ds] Add special memories test and fix issues [3046399+kk7ds] Add a test to check for memory name whitespace [3046399+kk7ds] Add a test and fixes for trailing name whitespace [3046399+kk7ds] Make FloatProperty honor precision [3046399+kk7ds] Fix radioreference dialog crash on passwords [3046399+kk7ds] Fix requiring Canadians to conform to the USPS [3046399+kk7ds] Start conversion of icx8x driver to bitwise [3046399+kk7ds] Finish icx8x conversion to bitwise [3046399+kk7ds] Fix icx8x driver upload [3046399+kk7ds] Update radioddity_r2.py to use mem.immutable - #10288 [3046399+kk7ds] New Model support Wouxun KG-UV980P, KG-1000G, KG-1000G Plus

1 0

[chirp_users] New chirp-next build
by donotreply＠chirp.danplanet.com 25 Jan '23

25 Jan '23

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since yesterday and may include additional features, bug fixes, etc. As a reminder, this is different from the "daily" CHIRP builds in that new development and features are happening here. It is the latest and greatest, but also may be less stable than the "daily" builds at this time. If it works for you, we recommend using CHIRP-next, but if your radio is not yet working on it, then you may prefer to use the "daily" builds for the time being. You can get it from here: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: Changes for Build #50 [3046399+kk7ds] Remove accidental debug [3046399+kk7ds] Decorate driver tests with the module name [3046399+kk7ds] Add missing Icom IC-E90 test image [3046399+kk7ds] Update retevis_rb15.py driver to use mem.immutable - #10288

1 0

[chirp_users] New chirp-next build
by donotreply＠chirp.danplanet.com 24 Jan '23

24 Jan '23

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since yesterday and may include additional features, bug fixes, etc. As a reminder, this is different from the "daily" CHIRP builds in that new development and features are happening here. It is the latest and greatest, but also may be less stable than the "daily" builds at this time. If it works for you, we recommend using CHIRP-next, but if your radio is not yet working on it, then you may prefer to use the "daily" builds for the time being. You can get it from here: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: Changes for Build #49 [3046399+kk7ds] Update mursv1.py driver to use mem.immutable - #10288 [3046399+kk7ds] Remove MUNCH_CLONE_RESP from IC-x90 [3046399+kk7ds] Fix bankedit when sub devices differ in has_bank [3046399+kk7ds] Allow KG-UV9D Plus driver to open other radio revisions [3046399+kk7ds] Add some more settings to TK-8102 (and friends) [3046399+kk7ds] Make TK-8102 retry program mode once [3046399+kk7ds] Fix memedit for yaesu-style cross-tone modes [3046399+kk7ds] Add cross-tone support for Yaesu FT-60 [3046399+kk7ds] Fix gmrsuv1.py driver - #10309

1 0

[chirp_users] New chirp-next build
by donotreply＠chirp.danplanet.com 23 Jan '23

23 Jan '23

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since yesterday and may include additional features, bug fixes, etc. As a reminder, this is different from the "daily" CHIRP builds in that new development and features are happening here. It is the latest and greatest, but also may be less stable than the "daily" builds at this time. If it works for you, we recommend using CHIRP-next, but if your radio is not yet working on it, then you may prefer to use the "daily" builds for the time being. You can get it from here: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: Changes for Build #48 [3046399+kk7ds] Add MURS channels to bandplan_na - fixes #10307 [3046399+kk7ds] Upgrade radtel_t18.py to use mem.immutable (revisited) - #10288 [3046399+kk7ds] Update retevis_rt21.py driver to use mem.immutable - #10288 [3046399+kk7ds] Fix opening command line images when no restore [3046399+kk7ds] Add Cross tone support for VX-6

1 0

[chirp_users] What's next for CHIRP
by Dan Smith 22 Jan '23

22 Jan '23

Hi all, I'd like to announce the availability of what I'm calling the "CHIRP-next" build for the new year. If you're not aware, some of the libraries that CHIRP depends on have been orphaned such that CHIRP was a bit stuck in time for many years. Overcoming this obstacle required a lot of changes to CHIRP's core, drivers, and the GUI has had to be completely rewritten as a result. This has been a ton of work, and we still have a lot left to do. However, it's time to rope you, the users and power users, into the effort. Several of us have tested hundreds of radios over the last few months getting ready for this, but we need your help to flesh things out. Over 90% of the radios that get used most often with CHIRP have been tested, but there are still plenty left that need to be confirmed (or fixed). Similarly, the GUI has been tested fairly well amongst the developers at this point, but there are surely still plenty of bugs to find and fix. Ultimately, this new build will become what is today the "daily" builds, and the current version of chirp will be renamed "legacy". As of now, all new development is being done on the "next" builds and only critical bug fixes will be considered for legacy. If CHIRP-next works for you and your radios, we want you running it as soon as possible. I've put together a page that describes in more detail why we're having to do this, how you can help, and what to look for and report: https://chirp.danplanet.com/projects/chirp/wiki/ChirpNextBuild Also, here's a page that describes some of the changes you can expect in the new version: https://chirp.danplanet.com/projects/chirp/wiki/ChirpNextBuildChanges While we're not doing this specifically to add features, the "opportunity" to redesign some things has allowed us to add some improvements. Further, being on newer dependent libraries has allowed us to add some features we never had before. If you're on MacOS or Linux, you will almost certainly want to be running the new build immediately. It uses modern dependencies and also behaves much more like a native application on all platforms. We really need your help testing and vetting this new version, so if you feel comfortable, please consider giving it a try and letting us know what you run into. I'm getting the word out here to the users groups a little early, before we start offering it on the download page specifically. Feel free to forward this to your own groups, facebook pages, etc to get more visibility than just the users here. You can find the CHIRP-next builds here: https://trac.chirp.danplanet.com/download?stream=next As always, you'll want to stay up-to-date with these, as things have been moving fast! --Dan

13 14

[chirp_users] New chirp-next build
by donotreply＠chirp.danplanet.com 22 Jan '23

22 Jan '23

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since yesterday and may include additional features, bug fixes, etc. As a reminder, this is different from the "daily" CHIRP builds in that new development and features are happening here. It is the latest and greatest, but also may be less stable than the "daily" builds at this time. If it works for you, we recommend using CHIRP-next, but if your radio is not yet working on it, then you may prefer to use the "daily" builds for the time being. You can get it from here: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: Changes for Build #47 [3046399+kk7ds] Add radio override for set_memory() policy [3046399+kk7ds] Fix pasting memories over top of immutable fields [3046399+kk7ds] Make tests more tolerant of highly immutable mems [3046399+kk7ds] Add GMRS channels to bandplan_na [3046399+kk7ds] Adjust GMRS-V2 set_memory immutable policy

1 0

[chirp_users] New chirp-next build
by donotreply＠chirp.danplanet.com 21 Jan '23

21 Jan '23

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since yesterday and may include additional features, bug fixes, etc. As a reminder, this is different from the "daily" CHIRP builds in that new development and features are happening here. It is the latest and greatest, but also may be less stable than the "daily" builds at this time. If it works for you, we recommend using CHIRP-next, but if your radio is not yet working on it, then you may prefer to use the "daily" builds for the time being. You can get it from here: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: Changes for Build #46 [noreply] GridSelectNone not available before 4.2.0 (#418) [3046399+kk7ds] New Model Support for Wouxun KG-UV9PX [3046399+kk7ds] Update kguv9dplus driver settings text [3046399+kk7ds] Fix use of hasattr [3046399+kk7ds] Verify VX-2

1 0

[chirp_users] Bullseye 64 Chirp-next build
by Jerry Rector - K4OAM 20 Jan '23

20 Jan '23

After a seemingly successful Buster 64 buil and install, all seems OK, but I have the following in the terminal window: *(chirp:9399): Gtk-CRITICAL **: 14:30:16.961: gtk_distribute_natural_allocation: assertion 'extra_space >= 0' failed* Is this a concern? If yes, how to fix it? Jerry - K4OAM ReplyForward Compose: Bullseye 64 Chirp-next build [image: Minimize][image: Pop-out][image: Close] chirp_users(a)intrepid.danplanet.com

2 4

[chirp_users] New chirp-next build
by donotreply＠chirp.danplanet.com 20 Jan '23

20 Jan '23

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since yesterday and may include additional features, bug fixes, etc. As a reminder, this is different from the "daily" CHIRP builds in that new development and features are happening here. It is the latest and greatest, but also may be less stable than the "daily" builds at this time. If it works for you, we recommend using CHIRP-next, but if your radio is not yet working on it, then you may prefer to use the "daily" builds for the time being. You can get it from here: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: Changes for Build #45 [3046399+kk7ds] Fix 817ND US variant 60m channels [3046399+kk7ds] Fix FT-817/857/897 immutable comment [3046399+kk7ds] Fix proxying get_memory() exceptions [3046399+kk7ds] Clean up extreme chattiness in match_model() [3046399+kk7ds] Reduce log noise about registrations [3046399+kk7ds] Tweak button box padding in radio prompt dialog [3046399+kk7ds] Add Restore Tabs to recent menu [3046399+kk7ds] Do not show Cross Mode column if not supported [3046399+kk7ds] Fix DTCS validations not being exposed [3046399+kk7ds] Fix metadata merge on Python 3.8 [3046399+kk7ds] Fix D710 unsupported tones [3046399+kk7ds] Stop running duplicate tests on push [3046399+kk7ds] Fix ID-5100 Cross Mode handling [3046399+kk7ds] Small tweak to tab restores

1 0

[chirp_users] Problem on Linux Mint with Mate desktop
by Angelo Marcone 19 Jan '23

19 Jan '23

Hi, using 'Linux Mint 21.1 (Vera)' with mate desktop, after downloading from radio no channel grid windows is showed. In the terminal (where I run chirp) there is this: --------------------------------------------------------------------------------------------------------- angelo@ham:~$ chirp WARNING: Did not find localedir: /usr/local/lib/python3.10/dist-packages/chirp-next_20230115-py3.10.egg/chirp/locale Traceback (most recent call last): File "/usr/local/lib/python3.10/dist-packages/chirp-next_20230115-py3.10.egg/chirp/wxui/main.py", line 1109, in _menu_download editorset = ChirpEditorSet(radio, None, self._editors) File "/usr/local/lib/python3.10/dist-packages/chirp-next_20230115-py3.10.egg/chirp/wxui/main.py", line 119, in __init__ edit = self.MEMEDIT_CLS(radio, self._editors) File "/usr/local/lib/python3.10/dist-packages/chirp-next_20230115-py3.10.egg/chirp/wxui/memedit.py", line 465, in __init__ self.set_cell_attrs() File "/usr/local/lib/python3.10/dist-packages/chirp-next_20230115-py3.10.egg/chirp/wxui/memedit.py", line 482, in set_cell_attrs attr.SetFitMode(wx.grid.GridFitMode.Ellipsize()) AttributeError: 'GridCellAttr' object has no attribute 'SetFitMode' ------------------------------------------------------------------------------------------ Chirp about info is: CHIRP-next-20230115 on Python 3.10.6 wxPython 4.0.7 gtk3 (phoenix) Wxwidget 3.0.5 Any help? Thank you, 73. Angelo IK8VRQ/KG6DPO

4 4

[chirp_users] New chirp-next build
by donotreply＠chirp.danplanet.com 19 Jan '23

19 Jan '23

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since yesterday and may include additional features, bug fixes, etc. As a reminder, this is different from the "daily" CHIRP builds in that new development and features are happening here. It is the latest and greatest, but also may be less stable than the "daily" builds at this time. If it works for you, we recommend using CHIRP-next, but if your radio is not yet working on it, then you may prefer to use the "daily" builds for the time being. You can get it from here: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: Changes for Build #44 [3046399+kk7ds] Fix (again) power conversions [3046399+kk7ds] Add generic power level parsing and a helper [3046399+kk7ds] Add a has_variable_power feature flag [3046399+kk7ds] Make CSVRadio support variable power [3046399+kk7ds] Fix CSV reference sharing bug [3046399+kk7ds] Pretty up the memedit and print headers [3046399+kk7ds] Update gmrsv2.py driver to use mem.immutable - #10288 [3046399+kk7ds] Update gmrsuv1.py driver to use mem.immutable - #10288 [3046399+kk7ds] Update bf_t8.py driver to use mem.immutable - #10288 [3046399+kk7ds] Fix MURS frequency table in radtel_t18.py driver - #10290 [3046399+kk7ds] Update radtel_t18.py driver to use mem.immutable - #10288

1 0

[chirp_users] New chirp-next build
by donotreply＠chirp.danplanet.com 18 Jan '23

18 Jan '23

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since yesterday and may include additional features, bug fixes, etc. As a reminder, this is different from the "daily" CHIRP builds in that new development and features are happening here. It is the latest and greatest, but also may be less stable than the "daily" builds at this time. If it works for you, we recommend using CHIRP-next, but if your radio is not yet working on it, then you may prefer to use the "daily" builds for the time being. You can get it from here: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: Changes for Build #23 [3046399+kk7ds] Fix ft857/897 get_memory() of special channels

31 85

[chirp_users] error reading from radio
by K0LNY_Glenn 18 Jan '23

18 Jan '23

Hi, I've tried this with Chirp Next and with an older chirp as well, with a Btech UV3r. The error says: graphic 213 graphic 798 An error has occurredgraphic 289 Error reading data from radio: not the amount of data we want. OK Thanks for any ideas. Glenn

3 3

[chirp_users] New chirp-next build
by donotreply＠chirp.danplanet.com 18 Jan '23

18 Jan '23

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since yesterday and may include additional features, bug fixes, etc. As a reminder, this is different from the "daily" CHIRP builds in that new development and features are happening here. It is the latest and greatest, but also may be less stable than the "daily" builds at this time. If it works for you, we recommend using CHIRP-next, but if your radio is not yet working on it, then you may prefer to use the "daily" builds for the time being. You can get it from here: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: Changes for Build #43 [3046399+kk7ds] Update kguv9dplus.py for TOA Bug #8947 [3046399+kk7ds] Update kguv9dplus working channel size [3046399+kk7ds] Fix kguv9dplus memory download issue [3046399+kk7ds] Set tuning_step on RepeaterBook results [3046399+kk7ds] Allow pip caching for tox environments [3046399+kk7ds] Run CSV export through import_logic [3046399+kk7ds] Fix a bug in choosing the closest power level [3046399+kk7ds] More protection against invalid power levels [3046399+kk7ds] Move mmap and metadata code to CloneModeRadio [3046399+kk7ds] Refactor get, set, erase memory ops in memedit [3046399+kk7ds] Add interface for storing extra memory fields [3046399+kk7ds] Make wxui support ExternalMemoryProperties [3046399+kk7ds] Limit comment input to 256 characters [3046399+kk7ds] Remove FT-450's abuse of the comment field

1 0

[chirp_users] New chirp-next build
by donotreply＠chirp.danplanet.com 17 Jan '23

17 Jan '23

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since yesterday and may include additional features, bug fixes, etc. As a reminder, this is different from the "daily" CHIRP builds in that new development and features are happening here. It is the latest and greatest, but also may be less stable than the "daily" builds at this time. If it works for you, we recommend using CHIRP-next, but if your radio is not yet working on it, then you may prefer to use the "daily" builds for the time being. You can get it from here: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: Changes for Build #41 [3046399+kk7ds] Remove legacy test_utils.py [3046399+kk7ds] Make import_logic pick the actual highest power [3046399+kk7ds] Make our power levels support fractional watts [3046399+kk7ds] Make CSV driver support power levels [3046399+kk7ds] Add AU/NZ UHF CB Radio Stock Config Changes for Build #42 No changes

1 0

[chirp_users] Query RepeaterBook - Limit Band option only lists 10m band
by Nicolas Pike 16 Jan '23

16 Jan '23

Latest (16.01.2023) Chirp-next build on Linux Mint 20.2 Query RepeaterBook - Limit Band option only lists the 10m band. Am I missing something obvious? If not I can investigate further. Limit modes appears to work as expected. Freq Step is always 5KHZ - I have raised this with Garrett. Really great to see Chirp moving on Python3 and I will be doing all I can to assist. Thanks Nicolas > [image: image.png] >

2 2

[chirp_users] New chirp-next build
by donotreply＠chirp.danplanet.com 16 Jan '23

16 Jan '23

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since yesterday and may include additional features, bug fixes, etc. As a reminder, this is different from the "daily" CHIRP builds in that new development and features are happening here. It is the latest and greatest, but also may be less stable than the "daily" builds at this time. If it works for you, we recommend using CHIRP-next, but if your radio is not yet working on it, then you may prefer to use the "daily" builds for the time being. You can get it from here: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: Changes for Build #40 [3046399+kk7ds] Fix str / bytes error on python 3 [3046399+kk7ds] Fix RadioReference not showing comments [3046399+kk7ds] Avoid using SetFitMode on older wxPython [3046399+kk7ds] Fix ft450d.py line endings [3046399+kk7ds] Make check_commit detect CRLF files [3046399+kk7ds] Make UI honor empty in mem.immutable [3046399+kk7ds] Make use of empty in immutable for some radios [3046399+kk7ds] Fix check-patch CRLF detection [3046399+kk7ds] Force UTF-8 encoding for CSV on windows

2 2

[chirp_users] help running chirp-next on RPI
by Robert Cartier 15 Jan '23

15 Jan '23

I have no luck trying to find the base program ..on the latest builds tarball for chirp-next I have had no issue running chirp and running chirpw Must be missing something very basic but I dont see any docs to guide me THanks in advance Robert Cartier kd1jg(a)icloud.com <mailto:kd1jg@icloud.com>

5 10

[chirp_users] RepeaterBook Worldwide
by Dan Smith 15 Jan '23

15 Jan '23

Hi all, In continuing this weekend's RepeaterBook theme, I wanted to point out that today's build contains support for RepeaterBook's worldwide directory, That means the list of countries in the drop-down box has gone from three to over a hundred, with hundreds of repeaters listed for many countries. Again this is a volunteer-maintained database, so it's only as good as you make it, but if you've never had the ability to query sources in CHIRP, give it a try! https://www.repeaterbook.com/row_repeaters/index.php?state_id=none --Dan

4 4

[chirp_users] Linux Mint further details
by Angelo Marcone 15 Jan '23

15 Jan '23

Hi, after my first email, I tried chirp next 20230113 and the problem was fixed. Chirp run now OK. So, probably, there is some incompatibility in the newest version (20230115). 73 again de Angelo IK8VRQ/KG6DPO

1 0

[chirp_users] Baofeng UV82 Preprogrammed Channels
by K0LNY_Glenn 15 Jan '23

15 Jan '23

Hi, A friend of mine just got a new Baofeng UV82, he is about to take his Ham Tech test. I sent him a Chirp install file, but I don't know if he will be able to access it with his screenreader in windows 11. So I have worked with him over the phone on entering frequencies into frequency mode. So in channel mode, it came with some channels, but he is Blind, so there is no way for him to know what they are. Can anyone send me a list of the channels they put in one of these from the factory? Maybe someone saved their original file that you can copy the channels and associated frequencies for me please. Thanks Glenn

3 3

[chirp_users] New chirp-next build
by donotreply＠chirp.danplanet.com 15 Jan '23

15 Jan '23

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since yesterday and may include additional features, bug fixes, etc. As a reminder, this is different from the "daily" CHIRP builds in that new development and features are happening here. It is the latest and greatest, but also may be less stable than the "daily" builds at this time. If it works for you, we recommend using CHIRP-next, but if your radio is not yet working on it, then you may prefer to use the "daily" builds for the time being. You can get it from here: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: Changes for Build #39 [3046399+kk7ds] Formalize chirpc a bit and install it [3046399+kk7ds] Add back the easy chirpc runner [3046399+kk7ds] Make style target run flake8 on chirp.cli [3046399+kk7ds] Refactor repeaterbook item parsing for errors [3046399+kk7ds] Add RepeaterBook "rest of world" queries [3046399+kk7ds] Add support for RepeaterBook Notes field [3046399+kk7ds] Make cell background grey for immutable values [3046399+kk7ds] Align query source link on Windows [3046399+kk7ds] Ellipsize cells when column is resized smaller [3046399+kk7ds] Add repeaterbook tests and fix a bug found [3046399+kk7ds] Add super simple CLI test to get started [3046399+kk7ds] Remove two unit test files for chirp-legacy [3046399+kk7ds] drivers.ftm350: Define and set "visible" bit [3046399+kk7ds] Convert Yaesu FT-2900 for python3

1 0

[chirp_users] RepeaterBook GMRS Queries!
by Dan Smith 14 Jan '23

14 Jan '23

Hi All, I'm excited that today's build includes support for querying RepeaterBook's GMRS database! Thanks to Garrett (RepeaterBook's owner), CHIRP users now have the ability to pull this data in as well. It works the same way as the other RepeaterBook queries, with searching, sorting by distance, and local caching. Like CHIRP, RepeaterBook depends on volunteers to maintain the database and they are responsible for growing it into the extremely comprehensive and valuable resource that it is today. If you know of any GMRS activity in your area, I encourage you to pull up the query for your location and if you notice anything missing, help by submitting it for inclusion here: https://www.repeaterbook.com/gmrs/add_repeater.php I found one new open GMRS repeater in my local area that is missing, so I'll be doing the same today :) --Dan

1 0

[chirp_users] chirp-next: howto update correctly
by Angelo Marcone 14 Jan '23

14 Jan '23

Hi Everyone, I switched to chirp-next and I installed it with success in Linux Mint 'Vera' (21.1) and Debian 10 by downloading tar.gz file running sutup. The only question I have now is: how to update my installation wthi the new daily releases? Is it ok download the new version running, for this setup again? Thanks for yout time. 73 de Angelo IK8VRQ/KG6DPO

2 1

[chirp_users] New chirp-next build
by donotreply＠chirp.danplanet.com 14 Jan '23

14 Jan '23

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since yesterday and may include additional features, bug fixes, etc. As a reminder, this is different from the "daily" CHIRP builds in that new development and features are happening here. It is the latest and greatest, but also may be less stable than the "daily" builds at this time. If it works for you, we recommend using CHIRP-next, but if your radio is not yet working on it, then you may prefer to use the "daily" builds for the time being. You can get it from here: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: Changes for Build #38 [3046399+kk7ds] Mock time in test_alinco_clone [3046399+kk7ds] Add Alinco DJ-G7T [3046399+kk7ds] Fix TH-D74 editing of WX memories [3046399+kk7ds] Fix refreshing special channels losing labels [3046399+kk7ds] Fix setting defaults on immutable memory fields [3046399+kk7ds] Make memory properties dialog honor immutable [3046399+kk7ds] Add RepeaterBook GMRS query support [3046399+kk7ds] chirpc: Fix setting tone modes [3046399+kk7ds] Record IC-2300 and FT-65R as working [3046399+kk7ds] Add some safety around closing the clipboard [3046399+kk7ds] Make sure edit controls use the do_radio helper [3046399+kk7ds] Fix delete and shift not cleaning the tail [3046399+kk7ds] Fix delete with block shift in empty block [3046399+kk7ds] Schedule prefill jobs with lower priority [3046399+kk7ds] Use erase_memory when moving an empty memory [3046399+kk7ds] Properly report erase_memory jobs in the status [3046399+kk7ds] Disable bulk shift operations when radio is busy [3046399+kk7ds] Make row progress indicators work for edit ops

1 0

[chirp_users] New chirp-next build
by donotreply＠chirp.danplanet.com 13 Jan '23

13 Jan '23

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since yesterday and may include additional features, bug fixes, etc. As a reminder, this is different from the "daily" CHIRP builds in that new development and features are happening here. It is the latest and greatest, but also may be less stable than the "daily" builds at this time. If it works for you, we recommend using CHIRP-next, but if your radio is not yet working on it, then you may prefer to use the "daily" builds for the time being. You can get it from here: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: Changes for Build #36 [3046399+kk7ds] Fix radio identities on some test images [3046399+kk7ds] Remove old test runners [3046399+kk7ds] Massive driver test refactor [3046399+kk7ds] Mock out time functions in clone tests [3046399+kk7ds] Fix delete-and-shift with special channels [3046399+kk7ds] Record IC2730 as working in the wild [3046399+kk7ds] Log information about pasted data Changes for Build #37 No changes

1 0

[chirp_users] Importing a CSV file into the memory of an Alinco DJ-G7T
by Stuart Longland VK4MSL 12 Jan '23

12 Jan '23

Hi all, Has anyone had any luck loading a CSV file into an Alinco DJ-G7T. I have organised a list of FM repeaters for 2m/70cm/23cm from the WIA repeater data spreadsheet. I won't publish it here, but suffice to say, it's more than I want to try and punch in via the keypad. 556 records. First problem is getting Chirp to even talk to the DJ-G7T. I have no idea what firmware it runs. I went looking in its menus but could not find where this information is shown. All I can say is I bought this from a online retailer (Andrews Communications) in Sydney around 2020. I am running the latest commit of Chirp: commit 49698a5b21a5a696be7f2121bc3ec8f4605b5b0c on Gentoo Linux AMD64 with Python 3.10.6, wxpython 4.0.7-r2 and wxgtk 3.0.5.1. Gentoo no longer ship Python 2.7. No I do not have a Windows-based PC as I don't use legacy operating systems for production work. To even get Chirp to talk to the Alinco, I needed to patch it (I think this will preclude me using a pre-made "binary"): diff --git a/chirp/drivers/alinco.py b/chirp/drivers/alinco.py index 7bfffa39..b3350653 100644 --- a/chirp/drivers/alinco.py +++ b/chirp/drivers/alinco.py @@ -595,7 +595,7 @@ class AlincoDJG7EG(AlincoStyleRadio): TMODES = ["", "??1", "Tone", "TSQL", "TSQL-R", "DTCS"] # This is a bit of a hack to avoid overwriting _identify() - _model = b"AL~DJ-G7EG" + _model = b"AL~DJ-G7T" _memsize = 0x1a7c0 _range = [(500000, 1300000000)] I was then able to download an image file from the radio. If I load up my CSV file, the upload option is greyed out. So clearly I don't directly open the CSV file, I have to "import" it somehow. If I try to copy the repeaters into the image from the radio, even just one repeater, Chirp segfaults. So clearly it's not a matter of copy and paste. How does one import a CSV file into an existing radio image? -- Stuart Longland (aka Redhatter, VK4MSL) I haven't lost my mind... ...it's backed up on a tape somewhere.

3 5

Re: [chirp_users] Importing a CSV file into the memory of an Alinco DJ-G7T
by Dan Smith 12 Jan '23

12 Jan '23

> I believe others already have, at least two or three times looking at > the bug tracker, many of which have patches. I didn't want to clutter > it with duplicates. > > https://chirp.danplanet.com/projects/chirp/search?utf8=%E2%9C%93&scope=&iss… Fair enough. I've never taken patches through the bug tracker as a general rule, although people attach them there sometimes. That's why those issues aren't open and have comments about following the process. I also need a test image of the radio in order to add it to the tree, not just a patch. If you can muster the github steps to get that submitted that would be great. However, if you can either test one of the existing patches and attach your test image, or open a new one with your image and patch, I can work the process for you. > As far as I know this is the US version of the DJ-G7. Here in > Australia we have a 4MHz-wide 2m band (144-148MHz) and nearly all the > FM repeaters are in the upper 2MHz. > > The other difference is the European DJ-G7 uses 9kHz spacing for MW > broadcast reception -- whereas the US DJ-G7 uses 10kHz (annoying, > because Australia has had a 9kHz spacing on MW since 1978). > > Other than that, I suspect the two sets are practically identical. Neither of those are likely to impact CHIRP, so yep, should be okay. > I'll have to do some investigation then. The files I'm working with > are here (patch, image dump from radio and my repeater listing): > > http://static.vk4msl.id.au/chirp/2023/01/13-djg7t/ I can probably turn that into a patch, but I need someone to test it before I'll put it in. If you'll open an issue for this, we can collaborate on getting something tested and into the tree. > I guess a feature to allow one to import memory channels from a CSV > (overwriting existing ones) would be handy as copying and pasting > channels gets cumbersome. Feedback from the legacy version was that copy and paste was far more flexible and user-friendly, and even being a CLI and developer type myself, that's how I do it. I rarely want to import everything from my master list into every radio, given a non-overlapping set of supported features, bands and modes. The legacy version had a very complex import mechanism, which I never used, and if you watch some of the youtube videos people have made, it far complicates for them what would be much easier with copy and paste. The mere existence seemed to make people think they had to do import instead of copy/paste. Having a just-overwrite-everything import is an option and I could add that, and may in the future, but for the moment copy and paste is the workflow. Sometimes simpler is better, especially in a GUI app. > Another prospect might be a CLI interface, so I could just prepare the > file, then tell `chirp` to download from the radio (or load from an > existing image), replace the channels, then upload it back to the > radio. There is a CLI in the git tree and some people do use it. If you find it useful, feel free to file a feature request to have it included in the source distribution. --Dan

1 0

[chirp_users] New chirp-next build
by donotreply＠chirp.danplanet.com 12 Jan '23

12 Jan '23

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since yesterday and may include additional features, bug fixes, etc. As a reminder, this is different from the "daily" CHIRP builds in that new development and features are happening here. It is the latest and greatest, but also may be less stable than the "daily" builds at this time. If it works for you, we recommend using CHIRP-next, but if your radio is not yet working on it, then you may prefer to use the "daily" builds for the time being. You can get it from here: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: Changes for Build #35 [3046399+kk7ds] Fix insert/delete operations off-by-one [3046399+kk7ds] Re-fix UV3R for python 3 [3046399+kk7ds] Disable selecting rows in the bank editor [3046399+kk7ds] [uv5r.py] Add ability to upload all ranges [3046399+kk7ds] Add DN to mode list for Yaesu System Fusion [3046399+kk7ds] Make RepeaterBook return YSF (DN mode) repeaters [3046399+kk7ds] Add mode filtering to RepeaterBook query [3046399+kk7ds] Fix bug in RepeaterBook band selection [3046399+kk7ds] Add __contains__ handler for RadioSettingGroup [3046399+kk7ds] Fix setting boolean mem.extra properties [3046399+kk7ds] Fix post-properties memory refresh [3046399+kk7ds] Add DN mode support to FT1, FT2, FT3

5 7

[chirp_users] chirp-next - Row selection on banks tab
by Matt Foster 11 Jan '23

11 Jan '23

I was just doing some work on my image file for a Yaesu FT-60R. I was assigning memories to banks, and I somehow got multiple rows in the table highlighted. I think I may have clicked and dragged slightly to cause this. I can not un-highlight the rows, nor do I see the point of highlighting rows in the banks table. If there is not anything useful to be done after selecting multiple rows of this table, would it be possible to just disable the row selection there? 73, Matt, N0EYE

3 2

[chirp_users] New chirp-next build
by donotreply＠chirp.danplanet.com 11 Jan '23

11 Jan '23

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since yesterday and may include additional features, bug fixes, etc. As a reminder, this is different from the "daily" CHIRP builds in that new development and features are happening here. It is the latest and greatest, but also may be less stable than the "daily" builds at this time. If it works for you, we recommend using CHIRP-next, but if your radio is not yet working on it, then you may prefer to use the "daily" builds for the time being. You can get it from here: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: Changes for Build #32 [3046399+kk7ds] AnyTone 5888UVIII Python 3 updates, tested with radio, added to cpep8 manifest [3046399+kk7ds] Remove quotes from flake8 execution [3046399+kk7ds] Squelch pep8.py warnings [3046399+kk7ds] Fix TS-2000 driver empty memory weirdness [3046399+kk7ds] Mark TS-2000 as tested in py3 by ZS6CRW [3046399+kk7ds] Default File->Open box to all supported formats [3046399+kk7ds] Add ADMS file compatibility for FT1, FT2, FT3 [3046399+kk7ds] Fix style errors in ft2d.py [3046399+kk7ds] Add NFM mode to Yaesu FT1, FT2, FT3 drivers [3046399+kk7ds] [kguv9dplus] Fix some python3 integer division and b strings [3046399+kk7ds] [kguv9dplus] make _do_upload() work with python3 [3046399+kk7ds] [kguv9dplus] Add frequency limit settings [3046399+kk7ds] [kguv9dplus] fix brighness 5 settings screen crash [3046399+kk7ds] [kguv9dplus] fix code formatting [3046399+kk7ds] [kguv9dplus] convert to MemoryMapBytes [3046399+kk7ds] Add website alias for Wouxun KG-UV9D Mate [3046399+kk7ds] Make CSV support cross_mode and rx_dtcs [3046399+kk7ds] Fix Save/SaveAs on non-default tabs [3046399+kk7ds] Add ADMS file compatibility to FT-70D [3046399+kk7ds] Add NFM mode to FT-70 Changes for Build #33 No changes Changes for Build #34 No changes

1 0

[chirp_users] New chirp-next build
by donotreply＠chirp.danplanet.com 10 Jan '23

10 Jan '23

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since yesterday and may include additional features, bug fixes, etc. As a reminder, this is different from the "daily" CHIRP builds in that new development and features are happening here. It is the latest and greatest, but also may be less stable than the "daily" builds at this time. If it works for you, we recommend using CHIRP-next, but if your radio is not yet working on it, then you may prefer to use the "daily" builds for the time being. You can get it from here: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: Changes for Build #31 [3046399+kk7ds] Remove Incorrect Class and Alias from 935G driver [3046399+kk7ds] Remove UV8T [3046399+kk7ds] Make sure we never set cur > max on clone status [3046399+kk7ds] Remove universal newlines flag in csv driver [3046399+kk7ds] Fix crash if wx.GetSystemLanguage() is unknown [3046399+kk7ds] Mark FT60 as actually tested by N0EYE [3046399+kk7ds] Remove myGMRS query source

1 0

[chirp_users] Kenwood TH-D74A
by K0LNY_Glenn 09 Jan '23

09 Jan '23

Hi, Assuming this is a Chirp supported radio, I'm wondering if TX for FRS/MRS/GMRS can be programmed into it. Thanks.

3 2

[chirp_users] Regarding Chirp Software For Yaesu System Fusion C4FM Radios.
by Joseph 09 Jan '23

09 Jan '23

Chirp For Yaesu System Fusion Radios For example Yaesu FT-70, Chirp doesn't recognize C4FM digital fusion repeaters. Kindly improve this to add this feature functionally. Thank you. [image: GeoTrack] <https://streaklinks.com/BWPMuUMVFQKfnaazJgHHwtgV/https%3A%2F%2Fgeotrack.ema…> Sender notified with GeoTrack <https://streaklinks.com/BWPMuUQ2tiTY_c-DlAxDOSgv/https%3A%2F%2Fgeotrack.ema…> [image: Mailtrack] <https://streaklinks.com/BWPMuUQqqrfUKUmAkAd_m-gI/https%3A%2F%2Fgeotrack.ema…> Sender notified by Mailtrack <https://streaklinks.com/BWPMuUQwMG_i-wo3OAGjE2fJ/https%3A%2F%2Fgeotrack.ema…> 01/08/23, 12:19:33 PM [image: 19] ᐧ

6 11

[chirp_users] New chirp-next build
by donotreply＠chirp.danplanet.com 09 Jan '23

09 Jan '23

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since yesterday and may include additional features, bug fixes, etc. As a reminder, this is different from the "daily" CHIRP builds in that new development and features are happening here. It is the latest and greatest, but also may be less stable than the "daily" builds at this time. If it works for you, we recommend using CHIRP-next, but if your radio is not yet working on it, then you may prefer to use the "daily" builds for the time being. You can get it from here: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: Changes for Build #30 [3046399+kk7ds] Only show browser tab for CloneModeRadio [3046399+kk7ds] Wrap browser init to catch errors [3046399+kk7ds] Record Icom W32A as working [3046399+kk7ds] Fix tone display for radios without ctone field [3046399+kk7ds] Log paste errors for forensics [3046399+kk7ds] Fix radio browser on Windows

1 0

[chirp_users] Possible Virus
by g7jiq1 08 Jan '23

08 Jan '23

Thank you to all that replied, I thought it would be a false positive, as I am using Norton and would put it to the group to be sure. Cheers Dave...

4 3

[chirp_users] New chirp-next build
by donotreply＠chirp.danplanet.com 08 Jan '23

08 Jan '23

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since yesterday and may include additional features, bug fixes, etc. As a reminder, this is different from the "daily" CHIRP builds in that new development and features are happening here. It is the latest and greatest, but also may be less stable than the "daily" builds at this time. If it works for you, we recommend using CHIRP-next, but if your radio is not yet working on it, then you may prefer to use the "daily" builds for the time being. You can get it from here: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: Changes for Build #29 [3046399+kk7ds] Fix two mis-named bands in bandplan_na [3046399+kk7ds] Add a get_repeater_bands() function to BandPlans [3046399+kk7ds] Allow filtering RepeaterBook queries by band [3046399+kk7ds] Move port assist to the port drop-down

1 0

[chirp_users] Possible Virus
by g7jiq1 07 Jan '23

07 Jan '23

I thought I would give the new chirp-next a try, but unfortunately my virus checker deletes the chirpwx.exe file saying it has a Heur.AdvMLB Heuristic Virus. Has anyone else had this warning ? Until this is verified as not the case or a false positive I have had to go back to the chirp-daily. Cheers Dave..

4 3

[chirp_users] New chirp-next build
by donotreply＠chirp.danplanet.com 07 Jan '23

07 Jan '23

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since yesterday and may include additional features, bug fixes, etc. As a reminder, this is different from the "daily" CHIRP builds in that new development and features are happening here. It is the latest and greatest, but also may be less stable than the "daily" builds at this time. If it works for you, we recommend using CHIRP-next, but if your radio is not yet working on it, then you may prefer to use the "daily" builds for the time being. You can get it from here: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: Changes for Build #26 [3046399+kk7ds] Wouxun KG-935G Radio testing [3046399+kk7ds] Let memedit use the default system font [3046399+kk7ds] Add MemoryMapBytes to check_commit.sh [3046399+kk7ds] Add insert, delete-and-shift operations

3 6

[chirp_users] Novel solution to Baofeng UV-5R's "Radio did to respond" problem?
by Graham Christensen 07 Jan '23

07 Jan '23

Hey folks, Debugging tonight I managed to get my radio to talk to CHIRP a few times, but very unreliably. I trimmed the connector and made sure it was well plugged in. I even updated to the next -nightly in case that helped. No. Eventually what I figured out something that works 100% of the time for me: squeezing the radio and programming adapter tightly in my hands while programming. Thanks for CHIRP, it was very easy to re-join the world of ham radio and get connected to a lot of local repeaters. 73, KI4VCD

8 9

[chirp_users] New chirp-next build
by donotreply＠chirp.danplanet.com 07 Jan '23

07 Jan '23

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since yesterday and may include additional features, bug fixes, etc. As a reminder, this is different from the "daily" CHIRP builds in that new development and features are happening here. It is the latest and greatest, but also may be less stable than the "daily" builds at this time. If it works for you, we recommend using CHIRP-next, but if your radio is not yet working on it, then you may prefer to use the "daily" builds for the time being. You can get it from here: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: Changes for Build #28 [3046399+kk7ds] Fix TYT TH-UV8000 [3046399+kk7ds] Fix crash on linux due to missing print preview

1 0

Re: [chirp_users] chirp_users Digest, Vol 169, Issue 5
by Dave B 06 Jan '23

06 Jan '23

Dan. Why not give people a choice...? Fixed or Variable? Or for that matter, any font the system knows about? (Like most other software titles in one form or another...) Have to say, a fixed width font for me is the way to go in spreadsheets etc, but I suspect that is not what is being talked about. From the few screenshots I've seen of the new version, the default UI is very poor contrast (dark grey on light grey, not good.) (So no doubt making readability much worse than it otherwise could be.) Still not got the new version to run yet, so "Devils Advocate" mode at the moment. (There again, I never managed to build the old version from source, as I wanted to do for some work on the Puxing PX-2R driver.) I now have ... ~$ python3.7 -V Python 3.7.5 ... working, but I suspect something in the chirp blob is dialling up an earlier version for some reason, and that is preventing the virtual environment from being correctly created. 2.7 and 3 also exist on this system (for various odd reasons, Chirp being one!) I like Python as a language, but the inter-version incompatibilities are becoming a major issue. Is it even possible at present to have old and new versions co-existing on the same system? (Not urgent, as earlier I know the OS needs upgrading.) 73. Dave G8KBV On 05/01/2023 20:00, chirp_users-request(a)intrepid.danplanet.com wrote: > If there are users here who prefer the fixed-width font the way it is today, speak up and I'll make a way for you to choose which one is used. If I'm the only one, then I won't bother 😄 -- Created on and sent from a Unix like PC running and using free and open source software:

3 2

[chirp_users] New chirp-next build
by donotreply＠chirp.danplanet.com 06 Jan '23

06 Jan '23

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since yesterday and may include additional features, bug fixes, etc. As a reminder, this is different from the "daily" CHIRP builds in that new development and features are happening here. It is the latest and greatest, but also may be less stable than the "daily" builds at this time. If it works for you, we recommend using CHIRP-next, but if your radio is not yet working on it, then you may prefer to use the "daily" builds for the time being. You can get it from here: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: Changes for Build #27 [3046399+kk7ds] Fix printing window parent [3046399+kk7ds] Add separate print and print preview menu items [3046399+kk7ds] Support delete memories from the edit menu [3046399+kk7ds] Disable cell editing for immutable memory fields [3046399+kk7ds] Allow selecting fixed/variable fonts for memedit [3046399+kk7ds] Clean up _update_window_for_editor()

1 0

[chirp_users] Nice!
by John KI4RO 05 Jan '23

05 Jan '23

Really like the new look of CHIRP! I still cannot use CHIRP on Windows to program my AnyTone 778UV, but other than that it works just fine. 73 KI4RO.

15 18

Re: [chirp_users] chirp_users Digest, Vol 169, Issue 4
by K5MRB 04 Jan '23

04 Jan '23

David Bucha, Thanks for this little note below when it comes to Ubuntu 22.04 installs. This did the the trick for getting past pip and make Chirp work. Mike On 1/4/23 14:00, chirp_users-request(a)intrepid.danplanet.com wrote: > Note: On ubuntu 22.04 you might have to install "python3-wxgtk4.0" before > the pip install step. >

1 0