- Users - lists.chirpmyradio.com

[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

Re: [chirp_users] [CHIRP - Feature #10213] (In Progress) Add search field to repeaterbook query
by Steve Horning 04 Jan '23

04 Jan '23

Thank you! I like the new import options. 73 de N0XVZ, Steve On 1/3/2023 4:18 PM, Dan Smith wrote: > Issue #10213 <https://chirp.danplanet.com/issues/10213#change-35932> > has been updated by Dan Smith. > ------------------------------------------------------------------------ > > * *Status* changed from /New/ to /In Progress/ > > What I have now will search the County, Landmark, City, and Callsign > fields of the repeaterbook database for a string. If any amount of > that string is in any of those fields, the repeater will be included > in the result set, or excluded if not. And of course, if the search > string is blank, everything matches. > > This is substantially easier than populating a box with state-specific > counties, and also provides more generic searching, finding landmark > entries like "hospital" or "tower" easily. > > I hope that will be a reasonable compromise (if not better than before). > > ------------------------------------------------------------------------ > > > Feature #10213: Add search field to repeaterbook query > <https://chirp.danplanet.com/issues/10213#change-35932> open > > * *Author: *Dan Smith > * *Status: *In Progress > * *Priority: *Low > * *Assignee: *Dan Smith > * *Target version: *chirp-py3 > * *Start date: *2023-01-02 > * *Chirp Version: *next (py3) > * *Model affected: *RepeaterBook > > This could search county, city, landmark fields, perhaps filling some > of the gaps between the new and previous implementations > > ------------------------------------------------------------------------ > > You have received this notification because you have either subscribed > to it, or are involved in it. > To change your notification preferences, please click here: > http://chirp.danplanet.com/my/account > -- This email has been checked for viruses by Avast antivirus software. www.avast.com

1 0

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

04 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 #25 [3046399+kk7ds] Add generic search field to repeaterbook query [3046399+kk7ds] Save and restore main window position [3046399+kk7ds] Extend hint text on query fields [3046399+kk7ds] Make memedit font bold to help readability

2 1

Re: [chirp_users] New Chirp-Next Build
by Dave B 03 Jan '23

03 Jan '23

I'll have to wait to catch up with this needed (and welcome) change, as I first need to upgrade my OS (Mint 19.3 64 bit, still supported until April) to a later LTS version first. That... Is going to take me some time, just to recreate all the tools and utilities I've used over the last 5 years etc. I did try the "Python Wheel" (not heard of them before) but just spent 20 minutes untangling the mess it made of my home folder, after following instructions found at https://realpython.com/python-wheels/ The venv could not be created, as it was trying to create a folder ./env/bin/activate that is the same name as the file "activate" in ~/env/bin ! (I have Python 3.6.9 installed, and otherwise working well...) In the mean time... If anyone manages to create a FlatPack, or ApImage for Linux, that would help a lot more people do a lot of the needed testing, with (in the first instance) a known collection of files and dependencies etc all supplied as needed, at the expense of disk space... (Might even be an idea for overall user deployment on Linux? As most just want to use it, not fight the system just to get it running...) Just a thought. (Not all of us out here live on the bleeding edge, preferring stability and reliability instead of continual changes.) 73 and Happy New Year. Dave G8KBV (or G0WBX) -- Created on and sent from a Unix like PC running and using free and open source software:

1 0

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

03 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 #24 [3046399+kk7ds] Bajoie BJ-318: Settings panel error [3046399+kk7ds] BJ-318: driver updates [3046399+kk7ds] Fix KG-UV8DPlus for python3 [3046399+kk7ds] Fix KG-UV8E for python3 [3046399+kk7ds] Convert Wouxun KG-935 for python3 [3046399+kk7ds] Fix buttonsizer padding on query sources dialog

1 0

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

01 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 #22 [3046399+kk7ds] Add a PR template with requirements [3046399+kk7ds] Add check_commit.sh and github action [dsmith] One more PR rule [3046399+kk7ds] Fix TH-D74 clone driver for UHF frequencies [3046399+kk7ds] Fix prompting for offset when duplex=off [3046399+kk7ds] Specifically select defaults in RB query [3046399+kk7ds] Ensure selection in myGMRS state

1 0

[chirp_users] Error comport
by D Bunk 20 Dec '22

20 Dec '22

I have a brand new baofeng UV-82 but can not get the program to recognize it. I keep getting an error message “can not open port”. I have downloaded the lasted version of the program. Any ideas? Using windows 10 on pc. /r Dean /r Dean

6 9

[chirp_users] Please Provide SHA256 and signed signatures of Downloads
by Rusty Fedora 19 Dec '22

19 Dec '22

Please tell the developers to provide pgp signed checksums of he downloads aswell as SHA256 checksums. Since SHA1 is weak and broken and SHA256 is the key standard for almost all linux distros and major software. You could still keep the SHA1 but have SHA256 as well as a signed signature .asc file signed with the developer/s GPG key.

1 0

Re: [chirp_users] TRYING to program radios to RF channels?repeaters
by gandy-o＠twc.com 17 Dec '22

17 Dec '22

First you need to know that most of these newer/Chinese radios can also be used on business, FRS, & GMRS frequencies as well as Amateur so it depends on what you want as to where youneed to look. If you are wanting Amateur only repeaters you can as others have said use repeater book. It is built into chirp. All you need to do is install chirp plug in your radio and under the heading Radio download it to the app and then under the same heading look for import from or Query Repeaterbook and follow the prompts as to what you want. I hope this will help you. Sincerely KJ4RT -----------------------------------------From: "outlook_47D0A80C8D53B779(a)outlook.com" To: "chirp_users(a)intrepid.danplanet.com" Cc: Sent: Friday December 16 2022 12:34:06PM Subject: [chirp_users] TRYING to program radios to RF channels?repeaters Ok I’m completely lost I’ve been sitting here for an hour trying to find to RFchannels & repeaters in my area to program my radios and so far all I get is a bunch of FM channels. Please help Sent from Mail [1] for Windows 10 Links: ------ [1] https://go.microsoft.com/fwlink/?LinkId=550986

1 0

[chirp_users] New Daily Build
by donotreply＠chirp.danplanet.com 17 Dec '22

17 Dec '22

Greetings, A new daily build of CHIRP is available. This includes changes made directly to the tree yesterday, and may include additional features, bug fixes, and/or bugs. If you are interested in trying it, grab it from the following location: http://trac.chirp.danplanet.com/chirp_daily/daily-20221217 A list of the changes included in this build (since the last daily) follows: Changes for Build #728 [Dan Smith <dsmith(a)danplanet.com>] Fix TH-D74 name sanitization [Angus Peart <angusp(a)gmail.com>] [AT-778UV] Adds support for busy channel lockout

1 0

Re: [chirp_users] chirp_users Digest, Vol 168, Issue 7 REPEATERS...
by Gary or Coleen Ferguson 16 Dec '22

16 Dec '22

google this "repeater book or repeater app" that will give you all of the repeaters. you can search for your area. Good Luck. G. On Fri, Dec 16, 2022 at 1: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. TRYING to program radios to RF channels?repeaters > (outlook_47D0A80C8D53B779(a)outlook.com) > 2. Re: TRYING to program radios to RF channels?repeaters (Ken Hansen) > 3. Re: TRYING to program radios to RF channels?repeaters > (David Evans) > 4. Re: TRYING to program radios to RF channels?repeaters > (Don Goodrich) > 5. Re: TRYING to program radios to RF channels?repeaters (Jim Unroe) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 15 Apr 2022 20:22:30 -0700 > From: "outlook_47D0A80C8D53B779(a)outlook.com" <copperhead120(a)gmail.com> > Subject: [chirp_users] TRYING to program radios to RF > channels?repeaters > To: "chirp_users(a)intrepid.danplanet.com" > <chirp_users(a)intrepid.danplanet.com> > Message-ID: <335B38A9-BF10-4F9E-8FBE-5A65D78ABC8F(a)hxcore.ol> > Content-Type: text/plain; charset="us-ascii" > > An HTML attachment was scrubbed... > URL: > http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20220415/49… > > ------------------------------ > > Message: 2 > Date: Fri, 16 Dec 2022 11:45:09 -0600 > From: Ken Hansen <ken(a)n2vip.org> > Subject: Re: [chirp_users] TRYING to program radios to RF > channels?repeaters > To: Discussion of CHIRP <chirp_users(a)intrepid.danplanet.com> > Message-ID: <538E909B-AAD3-4DD1-8D86-D0FE7638A360(a)n2vip.org> > Content-Type: text/plain; charset="us-ascii" > > An HTML attachment was scrubbed... > URL: > http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20221216/d6… > > ------------------------------ > > Message: 3 > Date: Fri, 16 Dec 2022 11:48:44 -0600 > From: David Evans <kd7uch(a)gmail.com> > Subject: Re: [chirp_users] TRYING to program radios to RF > channels?repeaters > To: Discussion of CHIRP <chirp_users(a)intrepid.danplanet.com> > Message-ID: > < > CAOFT+79+0YGQqgX2eGvubU0YsTA-KVgqj_uwphM3Fobi6EL9tg(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > What kinds of things are you looking for? > > Thanks, > David, > KD7UCH(a)gmail.com > > On Fri, Dec 16, 2022, 11:34 outlook_47D0A80C8D53B779(a)outlook.com < > copperhead120(a)gmail.com> wrote: > > > Ok I?m completely lost I?ve been sitting here for an hour trying to find > > to RFchannels & repeaters in my area to program my radios and so far > all I > > get is a bunch of FM channels. Please help > > > > > > > > Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for > > Windows 10 > > > > > > _______________________________________________ > > chirp_users mailing list > > chirp_users(a)intrepid.danplanet.com > > http://intrepid.danplanet.com/mailman/listinfo/chirp_users > > This message was sent to David Evans at kd7uch(a)arrl.net > > To unsubscribe, send an email to > > chirp_users-unsubscribe(a)intrepid.danplanet.com > > To report this email as off-topic, please email > > chirp_users-owner(a)intrepid.danplanet.com > > Searchable archive: > > https://www.mail-archive.com/chirp_users@intrepid.danplanet.com >

1 0

[chirp_users] TRYING to program radios to RF channels?repeaters
by outlook_47D0A80C8D53B779＠outlook.com 16 Dec '22

16 Dec '22

5 4

[chirp_users] RepeaterBook query fails with 502 error
by David Boucha 14 Dec '22

14 Dec '22

When running Chirp from the py3 branch on Ubuntu 22.04 when I click on Radio -> Query Source -> RepeaterBook, then I choose my state and county I get an error message "Got error code 502 from server" It doesn't matter which Band I choose. [image: image.png]

3 2

[chirp_users] New Daily Build
by donotreply＠chirp.danplanet.com 14 Dec '22

14 Dec '22

Greetings, A new daily build of CHIRP is available. This includes changes made directly to the tree yesterday, and may include additional features, bug fixes, and/or bugs. If you are interested in trying it, grab it from the following location: http://trac.chirp.danplanet.com/chirp_daily/daily-20221214 A list of the changes included in this build (since the last daily) follows: Changes for Build #727 [Dominick C. Pastore <dominickpastore(a)dcpx.org>] Adjust charset for Yaesu VX-6 Add some ASCII-like characters that were missing from the VX-6 driver charset and modify the charset decoder to drop invalid or non-ASCII-like characters to fix chirp #10171

1 0

[chirp_users] New Daily Build
by donotreply＠chirp.danplanet.com 07 Dec '22

07 Dec '22

Greetings, A new daily build of CHIRP is available. This includes changes made directly to the tree yesterday, and may include additional features, bug fixes, and/or bugs. If you are interested in trying it, grab it from the following location: http://trac.chirp.danplanet.com/chirp_daily/daily-20221207 A list of the changes included in this build (since the last daily) follows: Changes for Build #726 [Dan Smith <dsmith(a)danplanet.com>] Squelch the warnings about dupes in bandplan AFAIK, these have always been dupes because the NA bandplan has overlaps. This generates a substantial amount of log spam for no gain, so this removes them for now. [Jim Unroe <rock.unroe(a)gmail.com>] [GMRS-V2] DTMF Settings aren't being stored in radio. The DTMF Speed (on/off), ANI Code, Alarm Code and related settings are in a memory rangee that was being blocked from being uploaded to the radio. This patch removes that block allowing these setting to be uploaded to the radio. fixes #10158

1 0

[chirp_users] New Daily Build
by donotreply＠chirp.danplanet.com 05 Dec '22

05 Dec '22

Greetings, A new daily build of CHIRP is available. This includes changes made directly to the tree yesterday, and may include additional features, bug fixes, and/or bugs. If you are interested in trying it, grab it from the following location: http://trac.chirp.danplanet.com/chirp_daily/daily-20221205 A list of the changes included in this build (since the last daily) follows: Changes for Build #723 [Dan Smith <dsmith(a)danplanet.com>] Try to fix DMR-MARC query source The API has moved and changed a bit, and the expected format of the query parameters is different. This seems to work for me in my area with the following: City: Portland State: Oregon Country: United States Using a state abbreviation, or a country name like "us" or "usa" do not work. Leaving fields blank seems to be allowed as well. Changes for Build #724 No changes Changes for Build #725 No changes

1 0

[chirp_users] New Daily Build
by donotreply＠chirp.danplanet.com 03 Dec '22

03 Dec '22

Greetings, A new daily build of CHIRP is available. This includes changes made directly to the tree yesterday, and may include additional features, bug fixes, and/or bugs. If you are interested in trying it, grab it from the following location: http://trac.chirp.danplanet.com/chirp_daily/daily-20221203 A list of the changes included in this build (since the last daily) follows: Changes for Build #722 [Dan Smith <dsmith(a)danplanet.com>] Add Icom ID-4100

1 0

[chirp_users] New Daily Build
by donotreply＠chirp.danplanet.com 01 Dec '22

01 Dec '22

Greetings, A new daily build of CHIRP is available. This includes changes made directly to the tree yesterday, and may include additional features, bug fixes, and/or bugs. If you are interested in trying it, grab it from the following location: http://trac.chirp.danplanet.com/chirp_daily/daily-20221201 A list of the changes included in this build (since the last daily) follows: Changes for Build #721 [Dan Smith <dsmith(a)danplanet.com>] Mock out time.time during tests This saves two minutes wall clock time on *just* the clone tests. [Dan Smith <dsmith(a)danplanet.com>] Add TH-D74 clone-mode driver [Dan Smith <dsmith(a)danplanet.com>] Add a directory compat routine This gives us compatibility with drivers from the py3 branch that will use this format registration scheme. [Dan Smith <dsmith(a)danplanet.com>] Fix tuning_step on TH-D72 This fixes chirp #10088 and revert the "fix" from chirp #1611. The latter figured these were meaningless bits that changed based on the band, but they're actually a tuning_step index (transmit and receive). I think the problem with distorted audio is the radio being off frequency slightly when the tuning step doesn't match what is needed for the frequency. [Dan Smith <dsmith(a)danplanet.com>] Add gitignore initiailzed from hgignore

1 0

[chirp_users] New Daily Build
by donotreply＠chirp.danplanet.com 30 Nov '22

30 Nov '22

Greetings, A new daily build of CHIRP is available. This includes changes made directly to the tree yesterday, and may include additional features, bug fixes, and/or bugs. If you are interested in trying it, grab it from the following location: http://trac.chirp.danplanet.com/chirp_daily/daily-20221130 A list of the changes included in this build (since the last daily) follows: Changes for Build #720 [Dan Smith <dsmith(a)danplanet.com>] Implement dv_code and dsql_mode for id31, et al This includes the ID-51, ID-51Plus and ID-51Plus2. [Dan Smith <dsmith(a)danplanet.com>] Make RadioSettingValueList nicer This makes us listify the options parameter, and also allows for controlling the value by index.

1 0

[chirp_users] Daily build 11/28/22 incomplete?
by jeramy cleghorn 29 Nov '22

29 Nov '22

I downloaded the most recent daily build and installed it. What model(s) listed are compatible with these two radios? #1 Baofeng BF-F9 V2N and #2 Baofeng UV9RPlus ??? I saw them listed on the main CHIRP page but don't see them in the program's list. Help please?

2 1

[chirp_users] Anytone radio
by Aubrey Akers 29 Nov '22

29 Nov '22

Good Day I am looking for programming software for the Anytone AT-929 VHF portable radio If anyone can help me please Thank You Aubrey

2 1

[chirp_users] Adding Yaesu FT5DR… any FT3DR/FT5DR users/devs able to help?
by Stuart Longland VK4MSL 28 Nov '22

28 Nov '22

Hi all, I recently purchased a FT5DR radio transceiver and note that at present, CHIRP does not yet support this model despite apparently supporting the earlier FT3DR. Architecturally, both radios are apparently similar, but the FT5DR uses a different memory layout making it incompatible. I tried adding some memory channels manually through the keypad and retrieving the memory dump: https://chirp.danplanet.com/issues/9365 I can figure out some bits of the dump, but I'm wondering if any of the format looks "familiar" to those who were involved in the FT3DR port, or if it's "totally new" and will require us to reverse engineer it from scratch. My hunch is maybe header fields have changed, but the actual channels themselves are the same. I don't mind getting my hands dirty to implement support, right now though I want to see if there's existing code that I can lean on. Regards, -- Stuart Longland (aka Redhatter, VK4MSL) I haven't lost my mind... ...it's backed up on a tape somewhere.

1 0

[chirp_users] New Daily Build
by donotreply＠chirp.danplanet.com 28 Nov '22

28 Nov '22

Greetings, A new daily build of CHIRP is available. This includes changes made directly to the tree yesterday, and may include additional features, bug fixes, and/or bugs. If you are interested in trying it, grab it from the following location: http://trac.chirp.danplanet.com/chirp_daily/daily-20221128 A list of the changes included in this build (since the last daily) follows: Changes for Build #719 [Dan Smith <dsmith(a)danplanet.com>] [icf] Change EtcData to hex to match OEM software The OEM software uses six zero-paded hex digits for EtcData, so fix icf to do the same. [Dan Smith <3046399+kk7ds(a)users.noreply.github.com>] Merge pull request #154 from kk7ds/icfhash Implement ICF hashing [Dan Smith <dsmith(a)danplanet.com>] Implement ICF hashing This adds generating the proper #CD=$hash value at the end of ICF files, which is required for the radio to read the image off of an SD card. Tested with a real ID31, but it also generate the same hash as CS-5100 for ID5100. [Frans van Gulik <48883389+HascEasyZ(a)users.noreply.github.com>] Add support for "CRT 279 UV" KT7900D Clone Added chip version VC5302 to KT7900D. Using QYT -> KT7900D Fully functional [Dan Smith <dsmith(a)danplanet.com>] Fix improperly-named driver modules These drivers are only importable by the magic directory stuff, but are not actually valid module names.

1 0

[chirp_users] New Daily Build
by donotreply＠chirp.danplanet.com 23 Nov '22

23 Nov '22

Greetings, A new daily build of CHIRP is available. This includes changes made directly to the tree yesterday, and may include additional features, bug fixes, and/or bugs. If you are interested in trying it, grab it from the following location: http://trac.chirp.danplanet.com/chirp_daily/daily-20221123 A list of the changes included in this build (since the last daily) follows: Changes for Build #715 [Dan Smith <dsmith(a)danplanet.com>] Fix ICF line ending encoding on windows Apparently python2 is converting CRLF to CRCRLF on windows only. This won't work for python3, but we need to open the file as 'wb' in order to have control. [Dan Smith <dsmith(a)danplanet.com>] Add a model alias map to the tree This is sort of a decoder ring for the massive number of straight rebrands that exist out there. We can use this to generate the SupportedRadios list on the web site and potentially add something to chirp itself to help users find the right model. Some of the aliases from the web site also pointed at non-existent models. Those lines are in the data file, but commented out until we know what to do with them. Note that the test added here uncovered a number of situations where we have subclassed radios with aliases, making the subclasses inherit the aliases, unintentionally. This also fixes those, and will prevent that from happening in the future. [Dan Smith <dsmith(a)danplanet.com>] Unify the id5100, id31, id51, etc call decoding Some Icom radios do some weird packing of 7-bit characters into bytes to save a few bits. I implemented a more generic handling of this for the id5100. This makes the others use it as well. [Dan Smith <dsmith(a)danplanet.com>] Remove last use of IcomRawCloneModeRadio The 2730 was using this, and this converts it to use the same base class as the rest of the drivers, with the proper feature flags. Changes for Build #716 No changes Changes for Build #717 No changes Changes for Build #718 No changes

1 0

[chirp_users] New Daily Build
by Build System 22 Nov '22

22 Nov '22

Greetings, A new daily build of CHIRP is available. This includes changes made directly to the tree yesterday, and may include additional features, bug fixes, and/or bugs. If you are interested in trying it, grab it from the following location: http://trac.chirp.danplanet.com/chirp_daily/daily-20221122 A list of the changes included in this build (since the last daily) follows: Changes for Build #714 [Dan Smith <dsmith(a)danplanet.com>] Initial ID-5100 support Tested only with a MapRev=3 radio. Fixes: #1647 [Dan Smith <dsmith(a)danplanet.com>] Add ID-51Plus2 Radio This is basically a clean subclass of the 51Plus, as they seem like almost the same radio for our purposes. However, the 51Plus2 speaks raw-mode ICF, unlike its sibling. Closes #4545 [Dan Smith <dsmith(a)danplanet.com>] Add full tracing support for ICF debugging Enabled by setting CHIRP_DEBUG_ICF=y in the environment [Dan Smith <dsmith(a)danplanet.com>] [ICF] Add model info decoding for newer radios This also rejects a clone write operation if the radio's model data claims to be a different version than our known MapRev. [Dan Smith <dsmith(a)danplanet.com>] Refactor IcomCloneModeRadio to support raw mode Some radios, like the ID51Plus2, inherit almost everything from their non-raw ancestors, but speak raw-mode ICF. When the IC-2730 was added, it was a brand new radio and it made sense to subclass the Icom base class to speak the different protocol. However, that will make supporting newer radios like the ID51Plus2 unnecessarily more difficult. This makes the base class able to do the raw things, based on flags like we have for other behavioral quirks. [Dan Smith <dsmith(a)danplanet.com>] Allow rfc2217 SoL connections By specifying a port of rfc2217://host:port you can run CHIRP against a radio connected over the network.

1 0

[chirp_users] New Daily Build
by Build System 21 Nov '22

21 Nov '22

Greetings, A new daily build of CHIRP is available. This includes changes made directly to the tree yesterday, and may include additional features, bug fixes, and/or bugs. If you are interested in trying it, grab it from the following location: http://trac.chirp.danplanet.com/chirp_daily/daily-20221121 A list of the changes included in this build (since the last daily) follows: Changes for Build #713 [Jim Unroe <rock.unroe(a)gmail.com>] [QRZ-1] Add support for Intro Lines that are padded with null characters The QRZ-1 (and variants like the TYT TH-UV88 and Retevis RT85) come from the factory with the Intro Lines right-padded with spaces. The CHIRP driver for these radios expects them to be padded with spaces. It is now known that it is possible for the Intro Lines to also be right- padded with null characters. When this is encountered, the Settings tabs are blank. This patch adds support to gracefully handle Intro Lines that have been padded with null characters. fixes #10129 [Dan Smith <3046399+kk7ds(a)users.noreply.github.com>] Merge pull request #133 from kk7ds/settings-bannedchars Reserve some characters from setting names [Dan Smith <dsmith(a)danplanet.com>] Reserve some characters from setting names This creates a list of banned characters for use in setting name identifiers so that the setting editor can mark them up in more convenient ways. [Dan Smith <3046399+kk7ds(a)users.noreply.github.com>] Merge pull request #130 from kk7ds/bug-10130 Replace six with sys.version_info [Dan Smith <dsmith(a)danplanet.com>] Replace six with sys.version_info Fixes #10130

1 0

[chirp_users] New Daily Build
by Build System 20 Nov '22

20 Nov '22

Greetings, A new daily build of CHIRP is available. This includes changes made directly to the tree yesterday, and may include additional features, bug fixes, and/or bugs. If you are interested in trying it, grab it from the following location: http://trac.chirp.danplanet.com/chirp_daily/daily-20221120 A list of the changes included in this build (since the last daily) follows: Changes for Build #712 [Dan Smith <dsmith(a)danplanet.com>] Make ICF log the full model query result [Dan Smith <dsmith(a)danplanet.com>] Long-overdue ICF cleanup The ICF driver has been accumulating a lot of cruft, from before the days where even hispeed cloning was supported. This doesn't clean up everything, but does improve consistency in frame parsing, generation, and makes the hispeed kicker use proper framing. It also (finally) actually digests the radio's CLONE_OK message for proper reporting. Some additional safety things are added, reporting of things to help debug, and unifies things such that merging with the py3 branch will be simpler. [Dan Smith <dsmith(a)danplanet.com>] Make ICF driver log the clone result frame [Dan Smith <dsmith(a)danplanet.com>] Make hexprint show proper data length Historically hexprint zero-pads the data it is printing, which makes it hard to see how much data is actually there. Fix that.

3 2

[chirp_users] New Daily Build
by Build System 19 Nov '22

19 Nov '22

Greetings, A new daily build of CHIRP is available. This includes changes made directly to the tree yesterday, and may include additional features, bug fixes, and/or bugs. If you are interested in trying it, grab it from the following location: http://trac.chirp.danplanet.com/chirp_daily/daily-20221119 A list of the changes included in this build (since the last daily) follows: Changes for Build #711 [Dan Smith <dsmith(a)danplanet.com>] A better fix to the ICF clone speed issue In commit 89467012 I "fixed" the issue with cloning to older Icom radios going too fast and causing them to choke on the data stream. A bug in that caused us to always hit the timeout reading echo frames (even if we got one) and thus slowed the clone process way down. This fixes that bug, and also tracks whether or not our cable is the echoing type to avoid us even needing to munch echoes once we have determined that we're on a non-echoing type. Tested with IC-2200, IC-2820, ID-800v2, ID-31A. [Dan Smith <dsmith(a)danplanet.com>] Improve native support for ICF files This makes CHIRP able to handle ICF files more natively, extending the save support recently added. We no longer warn the user about ICF files being readonly, and we can load/save them like .img files. Legacy models seem to have none of the metadata that the newer ones do, which makes this easier for them. Newer models have more things (like MapRev, EtcData), and this makes us persist those for a loaded file so that we can save them back out.

1 0

[chirp_users] New Daily Build
by Build System 18 Nov '22

18 Nov '22

Greetings, A new daily build of CHIRP is available. This includes changes made directly to the tree yesterday, and may include additional features, bug fixes, and/or bugs. If you are interested in trying it, grab it from the following location: http://trac.chirp.danplanet.com/chirp_daily/daily-20221118 A list of the changes included in this build (since the last daily) follows: Changes for Build #710 [Jim Unroe <rock.unroe(a)gmail.com>] [UV-50X2_G2] Add Baofeng Tech UV-50X2_G2 Baofeng Tech is releasing a second generation version of the BTech UV-50X2. This patch adds support for the BTech UV-50X2_G2. fixes #10126 [Dan Smith <dsmith(a)danplanet.com>] Make tests not require DV call lists If the radio driver does not require DV call lists, the tests should not require them either. Related to #1647 [Dan Smith <dsmith(a)danplanet.com>] Make the UI offer to save ICF files, if supported For drivers that expose the ICF details, allow File->Save to ICF file format. Related to #1647 [Dan Smith <dsmith(a)danplanet.com>] Add ICF write support for ID-31A Related to #1647 [Dan Smith <dsmith(a)danplanet.com>] Make ICF module able to write files We have long supported reading ICF files, but not writing them. The format is *mostly* well-understood, with the exception of some metadata. This is not as useful for all radios, but for the ones that support SD cards, being able to write ICF files means those can be programmed without a cable and/or before we have figured out the cloning details. This adds the basic capability to icf.py, but requires drivers to declare the metadata details for it to be useful. Note this also includes some py3 fixes so this will more directly apply to the py3 branch. Related to #1647 [Dan Smith <dsmith(a)danplanet.com>] Run py2 tests on Focal Github just switched ubuntu-latest to jammy, so make sure these run on focal. [Dan Smith <dsmith(a)danplanet.com>] Don't fail to create PR if merge commit fails If we fail to run makesupported, we will not touch anything, but return nonzero, which will try to git commit, which will fail because nothing is changed. Just ignore that and push the PR anyway so we have something to work from.

1 0

[chirp_users] New Daily Build
by Build System 09 Nov '22

09 Nov '22

Greetings, A new daily build of CHIRP is available. This includes changes made directly to the tree yesterday, and may include additional features, bug fixes, and/or bugs. If you are interested in trying it, grab it from the following location: http://trac.chirp.danplanet.com/chirp_daily/daily-20221109 A list of the changes included in this build (since the last daily) follows: Changes for Build #709 [Masen Furer <m_github(a)0x26.net>] hg_uv98: skip register if `future` is not available this driver currently depends on builtins.bytes ass try/except ImportError when doing from builtins import bytes since some platforms dont have the `future` package and the driver shouldn't crash the whole program in those cases. fixes #10110

1 0

[chirp_users] New Daily Build
by Build System 08 Nov '22

08 Nov '22

Greetings, A new daily build of CHIRP is available. This includes changes made directly to the tree yesterday, and may include additional features, bug fixes, and/or bugs. If you are interested in trying it, grab it from the following location: http://trac.chirp.danplanet.com/chirp_daily/daily-20221108 A list of the changes included in this build (since the last daily) follows: Changes for Build #708 [Dan Smith <dsmith(a)danplanet.com>] Fix ICF-based radios for clone out At some point we apparently started slamming data down the serial line at too high a rate for older radios. When using an ID-800, the clone dialog finishes in a few seconds, and the radio times out because it missed a huge chunk of the image because it overran its buffer. This seemed to work okay for radios that use the direct serial connection to the 2.5mm data jack, but not via the OPC-478 type interface. This change makes us read our own echo frames before sending the next one, which slows us down a lot. It feels a lot slower, but it means we're at least pacing the physical echo. Tested with an ID-800, ID-880 and IC-2820 and this fixes things. [Masen Furer <m_github(a)0x26.net>] add Lanchonlh HG-UV98 driver (#100) * hg_uv98: add Lanchonlh HG-UV98 driver fixes #7999 [Dan Smith <dsmith(a)danplanet.com>] py3-pr needs to push *after* matrix commit [Dan Smith <dsmith(a)danplanet.com>] py3-pr Needs file to commit [Dan Smith <dsmith(a)danplanet.com>] Update py3-pr to have tox for makesupported

3 2

[chirp_users] No mail getting to chirp-devel ML?
by Barry Jackson 05 Nov '22

05 Nov '22

I have sent 3 messages to the -devel ML recently and see none in the list. Also there are no archives since 24th October.

1 0

[chirp_users] Port names: (Was Re: Linux and chirp)
by Dave B 05 Nov '22

05 Nov '22

Those of you who are using Linux in one form or another, and need some "stability" as to how USB/Serial adapters are named/numbered each time you connect them to you computer, could do no worse than consult this site... http://hintshop.ludvig.co.nz/show/persistent-names-usb-serial-devices/ Very good and genuinely useful info regarding "udev rules". These are text files that you can create, so that the OS can assign a consistent device ID for your use, regardless of how the OS actually discovered them... Two things though... a) The place to put the needed udev configuration file, can vary between Linux distro's, worse, more than one place can be used. One for "system" and one for "users". (On this now older Mint 19.3 system, my "Shack" udev file (99-shack.rules) is located at:- /lib/udev/rules.d) You also need to kick the OS into re-scanning the udev rules after you added new rule or made a change. $ sudo udevadm control --reload-rules && udevadm trigger (Your login password will be asked for.)| |b) Sadly, most USB<>Serial adapters, do NOT have any unique identifying feature in the information they present to the OS when connected, or as found during the boot process. But, you can use the "path" to them (the convoluted route via all the USB hubs etc, between OS and device) if needed. Just that you then *MUST* connect things up exactly the same each time. But.. FTDI bless them, DO HAVE a unique serial number for each and every one of their devices. ("Genuine" devices that is, there are fake FTDI chips about as well!) It is trivial then, to use that serial number to create (for example) a rule that results in a "device" name for example of:- /dev/ttyTMV71 Whenever that programming lead is connected. The corresponding rule itself is:- #TM-V71 (using the FTDI based lead) SUBSYSTEM=="tty", ATTRS{serial}=="AK06ML2R", SYMLINK+="ttyTMV71" In this case, the FTDI unique "serial number" is AK06ML2R You can discover that in several ways. One of the easiest is to perform a $ dmesg -wH command in a seperate terminal window. You will see instantly what happens when you connect or disconnect things. The -w means wait, and the H means human readable output. So, it just sits there reporting stuff as it happens. Untill you use a Control+C character to quit dmesg, then allowing you to close the terminal session as you need. The output of that contains (for example)... [ +0.114801] usb 1-1.4.2: New USB device found, idVendor=0403, idProduct=6001 [ +0.000003] usb 1-1.4.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ +0.000002] usb 1-1.4.2: Product: FT232R USB UART [ +0.000002] usb 1-1.4.2: Manufacturer: FTDI [ +0.000002] usb 1-1.4.2: SerialNumber: *AK06ML2R* [ +0.002668] ftdi_sio 1-1.4.2:1.0: FTDI USB Serial Device converter detected [ +0.000047] usb 1-1.4.2: Detected FT232RL [ +0.000534] usb 1-1.4.2: FTDI USB Serial Device converter now attached to ttyUSB5 [ +12.717166] usb 1-1.4.2: USB disconnect, device number 17 [ +0.000237] ftdi_sio ttyUSB5: FTDI USB Serial Device converter now disconnected from ttyUSB5 Note the "usb 1-1.4.2:" common parts of each line. the "1.4.2" after the initial "1-" changes if the same device is plugged into a different port, as below... [ +0.000002] usb 1-1.4.5.5: Manufacturer: FTDI [ +0.000001] usb 1-1.4.5.5: SerialNumber: *AK06ML2R* [ +0.002685] ftdi_sio 1-1.4.5.5:1.0: FTDI USB Serial Device converter detected [ +0.000047] usb 1-1.4.5.5: Detected FT232RL [ +0.000408] usb 1-1.4.5.5: FTDI USB Serial Device converter now attached to ttyUSB5 It now has a path of 1.4.5 You can use that information in a udev rule thus, below. #TS-870s SUBSYSTEM=="tty", ATTRS{devpath}=="1.3.3", SYMLINK+="ttyTS870" (In this case, for my Kenwood TS-870s, that is connected to one "leg" of a 4 port Prolific based device. The line beginning with a # Is a comment, you can for example include human readable text as a reminder...) Example readlink outputs: $ readlink /dev/ttyTMV71 ttyUSB5 or... $ readlink /dev/ttyTS870 ttyUSB2 Note! Your "custom" name "ttyTMV71" for example is valid, but what it points to, the "default" device name "ttyUSB5" is also still valid. The only difference is that "ttyTM-V71" will not change, regardless of the "ttyUSBn" device it actually relates to. So, in this instance, you would ordinarily use "/dev/ttyUSB5" in Chirp to work with the connected Kenwood TM-V71 radio. However, you CAN manually edit the port name in Chirp, to show "/dev/ttyTMV71", and it remembers it between sessions, so regardless of what ttyUSB device number is actually uses, it will work. (Or specify "/dev/ttyTS870" in Flrig or Fldigi. You of course can use readlink in a script to set an environment variable prior to launching some software that needs a port specified in it's command line invocation. It's not difficult, and there is ton's of good instructional pages out there that will help you automate things for a stable life...) You can also use udev rules to give consistent names to other devices, if you have multiple of the same type. Some USB sound cards for example also have a unique ID of some sort you can use. Hope something above helps. It seems like a lot of trouble and faffing about at first, but explore it, and you'll never look back. It is also one of the more compelling reasons to buy only genuine FTDI USB/Serial products too! It just makes life easier! Lastly. If you go this route.. DO make backups of your rules files! You will likely need them if/when you upgrade/replace your OS. Or just to remind your faded grey cell, what you did to make it work in the past. Have Fun! 73. Dave G8KBV (just another Linux user, "NOT" an expert by any means.) On 03/11/2022 19:00, chirp_users-request(a)intrepid.danplanet.com wrote: > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 3 Nov 2022 02:26:57 -0500 > From: W Paul Mills<ac0hy(a)wpmills.com> > Subject: Re: [chirp_users] Linux and chirp > To:chirp_users@intrepid.danplanet.com > Message-ID:<cf28ae50-a629-50ea-542b-4d0db3ee525c(a)wpmills.com> > Content-Type: text/plain; charset=UTF-8; format=flowed > > But if you plug in both, one will be ttyUSB0 and one will be ttyUSB1, etc. > > On 10/29/22 01:05, Cinaed Simson wrote: -- Created on and sent from a Unix like PC running and using free and open source software:

1 0

[chirp_users] Linux and chirp
by Julian Macassey 03 Nov '22

03 Nov '22

I am running kubuntu 22.04.1 on a Framework laptop. I have loaded the daily build from flatpak and Chirp comes up when opened. My radio is a Baofeng UV-5RV2+ I followed the instructions in: https://chirp.danplanet.com/projects/chirp/wiki/CSV_HowTo + A Clean Start + + If you want to get an empty CHIRP-compatible CSV file, the + easiest way is to let CHIRP create one for you. Here are the + approximate steps for creating an empty file, editing it in an + external editor and opening it back up in CHIRP: + + Start CHIRP + Go to File > New to create an empty CSV file + + Add a memory to the first row, by entering a frequency + such as 146.52 + + + Go to File > Export to save the template file to something + ending with a .csv extension + + Open the file in your spreadsheet or external application of + choice, make edits and save + Re-open the file in CHIRP to validate that the format is + still correct, by going to File > Open and choosing your file + + Optionally use File > Import to import the contents of your + CSV file into another radio image + ... + If you have a clone-mode radio, upload the changes back to your + device using Radio > Upload To Radio. If you are using a + live-mode radio, wait until all of the changes finish + synchronizing back to the device by watching the status bar in + the lower right corner of the main window. So, when I plug in my radio, I see the following in /var/logsyslog: ------ Oct 28 18:07:10 localhost kernel: [218263.636611] usb 3-4: new full-speed USB device number 15 using xhci_hcd Oct 28 18:07:11 localhost kernel: [218264.061760] usb 3-4: New USB device found, idVendor=067b, idProduct=2303, bcdDevice= 3.00 Oct 28 18:07:11 localhost kernel: [218264.061769] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Oct 28 18:07:11 localhost kernel: [218264.061772] usb 3-4: Product: USB-Serial Controller Oct 28 18:07:11 localhost kernel: [218264.061775] usb 3-4: Manufacturer: Prolific Technology Inc. Oct 28 18:07:11 localhost kernel: [218264.064089] pl2303 3-4:1.0: pl2303 converter detected Oct 28 18:07:11 localhost kernel: [218264.066251] usb 3-4: pl2303 converter now attached to ttyUSB0 Oct 28 18:07:11 localhost mtp-probe: checking bus 3, device 15: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-4" Oct 28 18:07:11 localhost mtp-probe: bus: 3, device: 15 was not an MTP device Oct 28 18:07:11 localhost snapd[13154]: hotplug.go:200: hotplug device add event ignored, enable experimental.hotplug Oct 28 18:07:11 localhost mtp-probe: checking bus 3, device 15: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-4" Oct 28 18:07:11 localhost mtp-probe: bus: 3, device: 15 was not an MTP device Oct 28 18:07:13 localhost ModemManager[824]: <info> [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:14.0/usb3/3-4': not supported by any plugin --- In Chirp I select Radio and slide down to select "Upload to Radio". I get a dialogue box saying:Port /dev/ttyS0, Bofeng, UV5R, I select OK. I get "An error has occurred Could configure port: (5, 'Input/output error') So just in case, I fiddles with the /dev/ttyS0 permissions: crw-rw-rw- 1 root dialout 4, 64 Oct 25 11:15 ttyS0 So what have I not done? What should I do? Yours GM5LUK -- "We can’t be successful unless we lie to customers.” Larry Ellison to Bruce Scott.

8 14

[chirp_users] Installation errors
by Tom 29 Oct '22

29 Oct '22

Hi, I have encountered a bunch of "C\ProFiles(x86)\CHIRP\XXX errors when installing the current CHIRP program. I stopped counting at 32. Here is a list of some of the errors: C\ProFiles(x86)\CHIRP\_ctypes.pyd \hashlib.pyd \socket.pyd \ssl.pyd \atik.pyd \cairo._cairo.pyd \chirpw.exe \freetype6.dll And many more. What went wrong? Thanks & 73, Tom KX7TRW

3 2

[chirp_users] New Daily Build
by Build System 25 Oct '22

25 Oct '22

Greetings, A new daily build of CHIRP is available. This includes changes made directly to the tree yesterday, and may include additional features, bug fixes, and/or bugs. If you are interested in trying it, grab it from the following location: http://trac.chirp.danplanet.com/chirp_daily/daily-20221025 A list of the changes included in this build (since the last daily) follows: Changes for Build #707 [Dan Smith <dsmith(a)danplanet.com>] Make the auto-sync PR update support matrix [Dan Smith <dsmith(a)danplanet.com>] Fix TK-8180 creating new zones with invalid data This fixes an issue when expanding the zone list. Related to #10093 [Dan Smith <dsmith(a)danplanet.com>] Add TK-8180E and TK-7180E model support Fixes #10093 [Dan Smith <dsmith(a)danplanet.com>] Add IC-7610 and fix IC-7300 Somehow the initial apply of the 7300 support duplicated some lines in the memory structure that prevented proper parsing of memory channels. This worked for reading memories, but would break when we went to send memories to the radio as we were writing past the end of our buffer. I'm not sure how this went unnoticed for the last two years, but this patch fixes it.

1 0

[chirp_users] New Daily Build
by Build System 22 Oct '22

22 Oct '22

Greetings, A new daily build of CHIRP is available. This includes changes made directly to the tree yesterday, and may include additional features, bug fixes, and/or bugs. If you are interested in trying it, grab it from the following location: http://trac.chirp.danplanet.com/chirp_daily/daily-20221022 A list of the changes included in this build (since the last daily) follows: Changes for Build #706 [Dan Smith <dsmith(a)danplanet.com>] Fix kenwood_live lock safety The command() function uses a threading.Lock to make sure only one thread accesses the serial port at a time. This makes us use a context manager to ensure that we drop that lock even if we encounter an exception. (cherry picked from commit bbd9915d14db55fea76ed7096b603f97c053b54f) [Dan Smith <3046399+kk7ds(a)users.noreply.github.com>] Merge pull request #76 from kk7ds/fix-tidh6 Fix TID H6 and TH-D74 [Dan Smith <dsmith(a)danplanet.com>] Fix TH-D74 complex tone mode handling This finishes the cross_modes support for D74. [Dan Smith <dsmith(a)danplanet.com>] [TH6] Fix failure to clone At some point the GA510 was subclassed, which duplicated the list of ALIASES and resulted in the clone dialog choosing one of the wrong alias classes, and thus sending the wrong ID string to the radio. This converts it to a proper subclass so that doesn't happen again. Fixes #10095

1 0

[chirp_users] New Daily Build
by Build System 21 Oct '22

21 Oct '22

Greetings, A new daily build of CHIRP is available. This includes changes made directly to the tree yesterday, and may include additional features, bug fixes, and/or bugs. If you are interested in trying it, grab it from the following location: http://trac.chirp.danplanet.com/chirp_daily/daily-20221021 A list of the changes included in this build (since the last daily) follows: Changes for Build #705 [Dan Smith <3046399+kk7ds(a)users.noreply.github.com>] Merge pull request #74 from kk7ds/apply-20221020 Apply 20221020 [Jim Unroe <rock.unroe(a)gmail.com>] [BF-V8A] Add Baofeng BF-V8A This patch adds support for the Baofeng BF-V8A 16-channel UHF handheld radio. fixes #10091 [Jim Unroe <rock.unroe(a)gmail.com>] [RT622] Add additional 'ID string' It seems that the OEM CPS can "zero" the identification string. Apparently it can be edited to be anything that you want. For now, this patch includes this new identification string to the list of strings known strings. If additional strings appear in the future, another solution will need to be found. fixes #10080 [Dan Smith <dsmith(a)danplanet.com>] Initial Kenwood TH-D74 live driver The Kenwood D74 does not have a full serial command set, which unfortunately means no support for memory names. So, this will never be very useful, but because the Kenwood live protocol is so easy, this will still be worthwhile. Like the D72 (and D710) a clone mode driver will be needed for full capability.

1 0

[chirp_users] Wouxun KG-UV8G
by Peter Lundberg 20 Oct '22

20 Oct '22

Hi, I am looking for Chirp support for Wouxun KG-UV8G. Does not appear to be supported now by Chirp? Ham-shop says that Chirp may ’wreck’ the unit, due to lack of appropriate checksums. Requiring out-of-warranty service. 73, Peter Sent from my iPad To a poet nothing can be useless. [SJ]

1 0

[chirp_users] Yaesu FVS-1
by K0LNY_Glenn 20 Oct '22

20 Oct '22

Hi, I'm writing this on this list because I'm sure there are folks here who have been inside all the Chirp supported radios. Yaesu makes a voice chip for the visually impaired, and I think the FVS-1 voice chip will work in the 8900. If this is the case, I'm wondering if anyone believes the Yaesu 8900 clone, Tytera 9800 would accept this chip? Or is the clone aspect of the two radios too superficial for this to be a possibility? Thanks. Glenn

2 2

[chirp_users] Alinco DJ-X11 Receiver
by charleswkelly＠gmail.com 19 Oct '22

19 Oct '22

Hi all, Has this handheld receiver ever been considered for programming by CHIRP? Alinco does provide rudimentary software, but it's awful, and programming by hand is torturous. I have a current unit, and the ERW-8 USB programming cable that I could loan to a developer. 73, Chuck Kelly W9MDO Noblesville, IN USA

3 2