- Users - lists.chirpmyradio.com

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

20 Dec '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. Unless you have a reason not to, we recommend using the latest build of CHIRP-next at all times. You can get it from here: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: 04dee787 radtel_t18.py: rb629 tone fix - fixes #10856 7abe0c19 retevis_rt98.py: add AnyTone AT-779W support - fixes #11023 c62380b6 retevis_rt98.py: address DeprecateionWarning - prep for #11023 2f64333e radtel_t18.py: add Baofeng BF-T20FRS (22-channel model) - 2 of 2 fixes #9821 bda6310c radtel_t18.py: address DeprecationWarning - prep for #9821 part 2 4181d983 retevis_rt22.py: add Baofeng BF-T20 (16-channel model) - 1 of 2 for #9821 6a3a858f retevis_rt22.py: address DeprecationWarning f5573e7a Format serial port with COM first on Windows 98682e9a mml_jc8810.py: support Radtel RT-470 PCB v2 - fixes #11004 bc552dc1 Fix bug in getting grid property in ChirpSettingsEdit._apply_settings --

1 0

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

17 Dec '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. Unless you have a reason not to, we recommend using the latest build of CHIRP-next at all times. You can get it from here: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: a40e0557 Updated Spanish Translation f7cd1fcd Update French translation 4790e3ba v71: Fix lowercase characters 604d144f Reflect settings modifications from RadioSettingValue._validate_callback onto a GUI --

1 0

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

13 Dec '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. Unless you have a reason not to, we recommend using the latest build of CHIRP-next at all times. You can get it from here: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: aa779a93 update ja_JP locale bbe1c55a uvk5: add translation targets ee381677 NFM and were FM were switched for the UV17 driver. Fixes #11002 f17dd675 fix always loading fake drivers 2dc8771f Empty tx frequency broken for some Baofeng radios. Fixes #10999 --

1 0

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

09 Dec '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. Unless you have a reason not to, we recommend using the latest build of CHIRP-next at all times. You can get it from here: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: 8bc70be9 Fix style target using sitepackages cc90ed6b tdh8: Enable lowercase name characters b1ce4174 uv5r.py: fix Duplex=off detection - fixes #10993 e0254648 Fix UV17 dates on the support matrix c45d230e Add Baofeng 5RM 02addee8 UV17: Hide bank names on radios without them 88598f92 UV17: Correct memory_bounds to start at 1 --

1 0

[chirp_users] Alinco DR-235
by Jerry Kuhn 08 Dec '23

08 Dec '23

2 1

[chirp_users] Drivers
by Ian Bush 08 Dec '23

08 Dec '23

Hi, I’ve downloaded Chirp to my laptop and cannot get my Yaesu FTM 6000 or my FT70D to link up to the program. Do I need to download a driver? Sorry compete beginner at this With Kind Regards Ian Bush M1IRB Sent from Ian's iPhone

2 1

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

07 Dec '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. Unless you have a reason not to, we recommend using the latest build of CHIRP-next at all times. You can get it from here: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: 6115b3e6 Fix Windows icon missing other resolutions a5963ffa Add TIDRADIO TD-H3 --

1 0

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

04 Dec '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. Unless you have a reason not to, we recommend using the latest build of CHIRP-next at all times. You can get it from here: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: b903042d Update locale after jp_JP addition 04074b20 added ja_JP locale 8d8fb313 ftm350: Add duplex=off and fix decoding of them 3a189095 Update chirp.svg for newer standards 72066698 Fix decoding module during SHA calculation 77f80ef6 uv5r.py: fix broken Range Override Parameter function - fixes #10955 e1e047d9 uv5r.py: address most DepricationWarning messages - prep for #10955 6668dae9 mml_jc8810.py: Add HI-8811 firmware v2.00 support - fixes #10975 4a40000d baofeng_common.py: honor _ack_block for UV-6R - fixes #10979 6f67136c Fix DeprecationWarning messages - prep for #10979 --

1 0

[chirp_users] Install experience on Linux Mint 21.2
by Matt Foster 30 Nov '23

30 Nov '23

I had been using Chirp on Windows 11 without issue, but I decided I wanted to give it a shot on my Mint 21.2 (Victoria) laptop. The following is what I noted. FWIW...I consider myself to be pretty well-versed in Linux, although my experience with Ubuntu-based distros is lesser and more recent. - Installed the dependencies with 'apt install' with no issue. - "managed flag" vs "no managed flag"...I wasn't sure what this meant, and there isn't any explanation other than Ubuntu and Debian version numbers. It looks like maybe it has something to do with Python virtual environments. I had to dig around a little to find that my Mint version is based on Ubuntu 22.04 LTS, so NO "managed flag". I feel like other, less experienced, Linux users might struggle a bit to figure this out. - I had downloaded the latest .whl file into ~/Downloads, so...'pip install Downloads/chirp-blah.whl'. This worked fine, and chirp launches out of ~/.local./bin. - A step could be saved if pip were just pointed to the whl file online. Would it be possible to have something like 'chirp-latest.whl' that links to the latest version? Overall, it was pretty smooth and I completed the steps in about 10 minutes, including figuring out the Mint vs Ubuntu version thing, although I have not yet had Chirp communicate with a radio! ;-) -- 73, Matt, N0EYE

1 0

[chirp_users] I'll use the old version for now... Thanks.
by Bruce 30 Nov '23

30 Nov '23

OS: Linux Mint v20.3 Uma Python installs are so unwieldy... Why would anyone choose that over C++ Source ?! Did as instructed for the install of the .whl file, made sure all the depends where there (I already had all of the most recent versions installed). Ran the command for the UnManaged (Ubu v22.10<) on the wheel file, and got interpreter failure... Will try running it directly on the tar.gz archive, but not hopeful. Unless the snake is pretty smart. Compiling and installing from 'C' has always worked well. But I've had nothing but problems with Py3.9 -- 73 4 Now, Bruce

2 1

[chirp_users] This is exactly what I'm talking about...
by Bruce 30 Nov '23

30 Nov '23

First off, I want ALL the user accounts (all me) to be able to access chirp, If I'm logged in to my GMRS account I want to use chirp to program THOSE radios, if I'm logged in under my Amateur Call I want to use chirp THERE to program my Ham Rigs... And have the associated data files available THERE... After reinstalling Py3.9 a couple times I FINALLY got chirp to install, but not without complaining about the out of date pip util. So I followed the instruct on how to upgrade that, and v21.3.1 is STILL being used. <sigh> Even though the upgrade to v23.3.1 succeeded. So I tried the install of chirp under another user and got an OSError Permission failures, so I 'sodo'd it and THIS is what I got... C was SO much more straight forward... WTF is 'testresources' ?! Tried it in a 'virtual environment' first and we know how THAT worked... And I *DID* upgrade pip you daffy computer !!! And WHY is there any "uninstalling" going on !?!? I guess if a Python is going to kill it's prey, it needs to confuse it first... Like I said, I think I'll stick with the old version of chirp, if what I've done here hasn't totally FUBAR'd that up... ============= Successfully uninstalled future-0.18.2 ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts. launchpadlib 1.10.13 requires testresources, which is not installed. Successfully installed certifi-2023.11.17 charset-normalizer-3.3.2 chirp-20231129 future-0.18.3 idna-3.6 importlib-resources-6.1.1 pyserial-3.5 requests-2.31.0 six-1.16.0 urllib3-2.1.0 yattag-1.15.2 zipp-3.17.0 WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv WARNING: You are using pip version 21.3.1; however, version 23.3.1 is available. You should consider upgrading via the '/usr/bin/python3.9 -m pip install --upgrade pip' command. -- 73 4 Now, Bruce

2 2

[chirp_users] I give Up !!! Please go back to C...
by Bruce 30 Nov '23

30 Nov '23

Traceback (most recent call last): File "/home/sysop/.local/bin/chirp", line 8, in <module> sys.exit(chirpmain()) File "/home/sysop/.local/lib/python3.9/site-packages/chirp/wxui/__init__.py", line 65, in chirpmain import wx File "/usr/lib/python3/dist-packages/wx/__init__.py", line 17, in <module> from wx.core import * File "/usr/lib/python3/dist-packages/wx/core.py", line 12, in <module> from ._core import * ModuleNotFoundError: No module named 'wx._core' -- 73 4 Now, Bruce

3 2

[chirp_users] CHIRP Tips: Advanced Editing
by Dan Smith 29 Nov '23

29 Nov '23

Hi all, I posted another "CHIRP Tips" video, this time on advanced editing techniques. This covers a number of tools CHIRP provides for bulk editing, organizing, and arranging memories. https://youtu.be/9UgJjwaXlrY Hopefully there's at least one tip in there you didn't already know about! --Dan

4 6

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

29 Nov '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. Unless you have a reason not to, we recommend using the latest build of CHIRP-next at all times. You can get it from here: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: 016475bd ft1d: Fix failure to encode callsign ee751584 uv17Pro: Fix handling out-of-range hangup time --

1 0

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

28 Nov '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. Unless you have a reason not to, we recommend using the latest build of CHIRP-next at all times. You can get it from here: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: 5ac5cb69 Updated Spanish Translation (#827) 0a6397c3 Update test matrix for UV-17 variants 346a3087 Added driver for Baofeng UV-17 fixes #10865 df11f150 Refactor UV-17Pro driver for UV-17 reuse 81a221d8 repeaterbook: Support digital-as-FM conversion cef97bab update chirp.desktop change MimeType from directory to app-specific, fix bug #2955 --

1 0

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

25 Nov '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. Unless you have a reason not to, we recommend using the latest build of CHIRP-next at all times. You can get it from here: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: c315781d Removed unnecessary lines and fixed some bugs 3c1ff5b1 Disable match_model PR check because it's too dumb e21d78a8 Update locale files for rt490 85a22f8d Add Radtel RT490 - fixes #9665 53765302 th_uv88.py: Add Retevis RA89 - fixes #10821 5732be40 th_uv88.py: Address 'DeprecationWarning' messages --

1 0

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

23 Nov '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. Unless you have a reason not to, we recommend using the latest build of CHIRP-next at all times. You can get it from here: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: 468da8c3 mml_jc8810.py: Add Radtel RT-470X firmware v2 support - fixes #10915 caa72570 mml_jc8810.py: address Deprication Warnings c7b3aa6e Update turkish language 71fa3f40 Updated Spanish Translation e424cdd1 yaesu ft-4xe: retry command multiple times when radio responds with not ack. Fixes #10198 0b311fc0 Added a driver for the Baofeng UV17 Pro and Pro GPS a1331151 Add a note to PR guidelines about commit messages cf4eefd0 Only check added python files for sameness 2f28fccd Change common-file check definition --

1 0

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

20 Nov '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. Unless you have a reason not to, we recommend using the latest build of CHIRP-next at all times. You can get it from here: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: 00658341 tmd710: Fix some non-byteclean serial activity 7fd60d4e th_uv8000: Corrected upload & download prompt text. 525facfe Updated Spanish Translation 6605759e baofeng_common.py: fix dropped byte issue - fixes #10505 --

1 0

[chirp_users] "Power-On Password Protection" setting for UV-K5?
by Western Retro 18 Nov '23

18 Nov '23

Looking for the field to set a power-on password for the UV-K5. I don't see it in the settings tabs.

1 0

[chirp_users] Yaesu FT-60R issue and fix endorsement
by jerry 09 Nov '23

09 Nov '23

Hi, I just wanted to endorse the "fix" that I gathered from the back and forth dialog on the issues board. I, too, found that I could download from the radio fine but it simply wouldn't upload. Seeing the OP got things to work with a new cable from BlueMax49ers.com I went ahead and ordered one although I could not see how the cable I used for years with other Yaesu radios did not work. Amazingly, the CT-91 BlueMax cable worked immediately and I just wanted to further endorse this "solution" to other FT-60 owners. Another suggestion: There seems to be a missing line in the instruction drop down for uploading to the radio. There is no prompt to hit the OK as the final step as there is on the download instruction. You do have to hit the OK button or the download will not start. Great program and great support. Thank you. Jerry

1 0

[chirp_users] Baofeng UV-17 / UV-18
by Gary Halleen 09 Nov '23

09 Nov '23

I see that a dev driver for supporting UV-17/BF-17 series of radios, as well as the UV-18/BF-18 on Miklor. I’ve tried it and it seems to work fine on my UV-18 Pro I Black and on my UV-17 Pro L radios. It doesn’t support uploading a new logo, but everything else I’ve tried seems to be okay. Is there a plan for including this support directly into the Chirp-Next release in the near future? Thanks! Gary K7TRO

1 0

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

08 Nov '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. Unless you have a reason not to, we recommend using the latest build of CHIRP-next at all times. You can get it from here: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: aaa669c9 hg_uv98: Modernize and fix style ce299949 ic2100: Clean up non-byte-clean get/set_raw() 1e2c277d Add test for strict bitwise seeks d892b56e Add warnings for non-byte-clean raw methods 67cc858e Fix deprecated __trunc__ instead of __int__ 63d9a061 Default bitwise's get_raw() to byte-native 3e672bba Add a way to test for compat bytes usage a80b3b85 gtk: Work around wxGTK Ctrl-C bug 203d7395 ft450: Remove another set_memory() setting modification 6b083e22 ft450: Fix IF filter setting breaking UI 2c3460de Update locale for ft450 changes 935507f1 Add FT-450 support to FT450D driver --

1 0

Re: [chirp_users] New chirp-next build
by Markus Scherer 08 Nov '23

08 Nov '23

Am 29.03.23 um 06:06 schrieb Markus Scherer: > > Grms on the kg-uv980p where did you hear read it?? > > > max > > > Am 29.03.23 um 01:35 schrieb Jeff Gallaway: >> Does anyone know how to unlock gmrs transmit on the Wouxun KG-UV980P? >> I read somewhere that it can be done with chirp but wasn't sure how >> it's done. I think there's another way to do it by downloading a file >> on ham files but I'm more familiar with chirp and would rather go >> that route if it's possible. >> >> >> >> >> Thanks, Jeffrey Gallaway >> >> On Mon, Feb 20, 2023, 12:08 AM <max(a)m-u-m.info> wrote: >> >> Good morning, >> >> I read the post and was patient, but the days of the driver for >> the kg-uv980p have come, so my hopes for the 950p are victorious >> again. >> >> Although the devices look the same, they also make the same only >> the firmware should be different, because if you read the 950 >> with the software from the 980, only the texts are completely >> illegible like "YYYÖ--WWcv" I find that on the Keyboard not at all. >> >> So the driver for that 980 would work, only the fine-tuning is >> missing and I'm not enough a programmer to be able to do that. >> >> The only thing I can do is test if its working, or what do you >> need for the fine tuning, logs or.... >> >> >> >> Max >> >> >> Am 19.02.23 um 16:36 schrieb Martin Cooper: >>> From the FAQ: >>> >>> https://chirp.danplanet.com/projects/chirp/wiki/FAQ#How-can-I-get-my-radio-… >>> >>> and then looking at New Model Requests: >>> >>> https://chirp.danplanet.com/projects/chirp/issues?query_id=15 >>> >>> we find: >>> >>> https://chirp.danplanet.com/issues/1489 >>> >>> So please do not open another new model request. >>> >>> Martin. >>> KD6YAM >>> >>> On Sun, Feb 19, 2023 at 7:26 AM John La <JohnLa(a)usa.net> wrote: >>> >>> . . If your model is not currently in the Supported Radios >>> list, it's >>> possible a request hasn't been submitted. >>> Here's the request procedure for CHIRP-next. >>> ________________ >>> >>> The official CHIRP website is: >>> https://chirp.danplanet.com/projects/chirp/wiki/Home >>> >>> Here's the procedure for requesting a new radio... >>> If you would like to open a request, you would need to >>> - Go to the CHIRP website. (link above) >>> - Register to the website (upper right corner) >>> - Select the Issues Tab and verify that the request for the >>> new radio hasn't >>> already been submitted. >>> - If it's not found, select the New Issue tab and submit >>> your request. >>> - Check back periodically to review the status of your request. >>> At that time a volunteer interested in taking on the project >>> will respond to >>> the request. >>> In most cases, a loaner radio is required so the software >>> can be backward >>> engineered and tested. >>> >>> Stay safe and healthy. >>> John K3NXU >>> >>> https://www.Miklor.com <https://www.Miklor.com> >>> https://www.Miklor.com/DMR/ <https://www.Miklor.com/DMR/> >>> https://www.Miklor.com/GMRS/ <https://www.Miklor.com/GMRS/> >>> >>> >>> -----Original Message----- >>> From: chirp_users-bounces(a)intrepid.danplanet.com >>> [mailto:chirp_users-bounces@intrepid.danplanet.com] On Behalf Of >>> max(a)m-u-m.info >>> Sent: Sunday, February 19, 2023 9:26 AM >>> To: chirp_users(a)intrepid.danplanet.com >>> Subject: Re: [chirp_users] New chirp-next build >>> >>> Hi everone, >>> >>> >>> i have ask i there are any plans to ad the wouxun kg - >>> uv950p, but got >>> no answer. >>> >>> >>> So i try it again. >>> >>> >>> >>> THX >>> >>> _______________________________________________ >>> chirp_users mailing list >>> chirp_users(a)intrepid.danplanet.com >>> http://intrepid.danplanet.com/mailman/listinfo/chirp_users >>> This message was sent to John LaMartina at johnla(a)usa.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 >>> >>> _______________________________________________ >>> chirp_users mailing list >>> chirp_users(a)intrepid.danplanet.com >>> http://intrepid.danplanet.com/mailman/listinfo/chirp_users >>> This message was sent to Martin Cooper at mfncooper(a)gmail.com >>> 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 >>> >>> >>> _______________________________________________ >>> chirp_users mailing list >>> chirp_users(a)intrepid.danplanet.com >>> http://intrepid.danplanet.com/mailman/listinfo/chirp_users >>> This message was sent to max202 atmax(a)m-u-m.info >>> To unsubscribe, send an email tochirp_users-unsubscribe(a)intrepid.danplanet.com >>> To report this email as off-topic, please emailchirp_users-owner(a)intrepid.danplanet.com >>> Searchable archive:https://www.mail-archive.com/chirp_users@intrepid.danplanet.com >> _______________________________________________ >> chirp_users mailing list >> chirp_users(a)intrepid.danplanet.com >> http://intrepid.danplanet.com/mailman/listinfo/chirp_users >> This message was sent to Jeff at jeffrey.gallaway(a)gmail.com >> 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 >> >> >> _______________________________________________ >> chirp_users mailing list >> chirp_users(a)intrepid.danplanet.com >> http://intrepid.danplanet.com/mailman/listinfo/chirp_users >> This message was sent to max202 atmax(a)m-u-m.info >> To unsubscribe, send an email tochirp_users-unsubscribe(a)intrepid.danplanet.com >> To report this email as off-topic, please emailchirp_users-owner(a)intrepid.danplanet.com >> Searchable archive:https://www.mail-archive.com/chirp_users@intrepid.danplanet.com

2 3

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

06 Nov '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. Unless you have a reason not to, we recommend using the latest build of CHIRP-next at all times. You can get it from here: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: ad73f0b5 Check mem.extra structure when comparing memories 1ccf0398 Add temporary XFAIL test list 90027b48 Add test to assert mem.extra contents 6301c585 Check for new instances of match_model() 4092a86d Make extra settings frozen in FrozenMemory 6e330ddb tk3140: Fix setting duplex=off 29424a67 fd268: Fix setting mem.extra values f440e393 ftx800: Cache bank model for improved performance 9f40416f Make test_get_set_specials set empty=False c4725149 Improve memory change debug logging 134c3e83 Log the first block received from Yaesu radios --

1 0

[chirp_users] Uninstall Chirp NEXT - linux pipx whl
by Christian 05 Nov '23

05 Nov '23

Greetings All, Successfully installed chirp on linux (Debian 12) using pipx and the most current .whl file. Runs as expected, but I'd like to uninstall completely and change to flatpak for ease of version management. Anyone have instructions on how to uninstall completely? The install instructions do mention uninstalling old versions but provide no detail. 73! KD9ZCM

2 1

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

31 Oct '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. Unless you have a reason not to, we recommend using the latest build of CHIRP-next at all times. You can get it from here: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: 35c8a1c0 add Anysecu UV-K5 to model alias map 33fd3102 ft2800.py: initialize unknown memory objects - fixes #10916 195f56b2 Fix bitwise grammar for bitfield 4e375c9f th9000: Fix program mode negotiation 62ce876e uvk5: Fix invalid return when firmware probe fails 5ef71ddc Remove UV-9R Pro from Model Alias Map 61460218 uvk5.py: add Retevis RA79 - fixes #10828 --

1 0

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

27 Oct '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. Unless you have a reason not to, we recommend using the latest build of CHIRP-next at all times. You can get it from here: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: e13ae1c0 Add a note about the master mode list 5f14b51a Fix check_commit for added image files 684e0e5d ft8100: Fix split implementation 2e76c84c uv5r.py: address 'dropped byte' issue - related to #10505 --

2 1

[chirp_users] Malicious use of chirp_users email addresses
by Tim Lavoie 26 Oct '23

26 Oct '23

Hello all, long-time lurker here. I have noticed that the list-specific email address that I use here, has been used in attempted logins to my email server. >From the last couple days, these login attempts have been showing up in my dovecot-related logs, from the following IPs: 103.181.14.250 103.251.143.14 111.70.14.8 121.138.183.176 122.151.32.167 122.169.42.241 123.157.4.248 14.85.88.26 157.208.36.100 180.130.175.136 182.70.242.47 182.75.197.174 183.213.25.118 183.62.20.2 190.93.189.227 196.191.212.238 222.110.220.110 27.72.41.155 31.173.28.23 50.58.168.150 60.221.224.220 61.153.208.38 80.21.208.94 84.235.46.149 91.73.247.158 There is little chance of harm done on this system, but if they have mine, they're likely trying the same on other members' hosts as well. Cheers, Tim

4 3

Re: [chirp_users] chirp release email links
by Rich NE1EE 25 Oct '23

25 Oct '23

This sounds as if it should be true, but it is not. I have recently been working with exactly this problem...a link to an http URL //sometimes// is changed to https (not sure why, perhaps a DNS or browser problem), and an error msg is generated because the certificate doesn't match the link. In addition (not to argue, but to wonder), why not have the link be correct? I'm gonna guess it is a single change to a template. Rich NE1EE On 2023-10-25 09:21:-0700, you wrote: >It doesn't really matter. http redirects to the same resource as https. > >73 >Danny, K5CG >HH 550-000-0609 >SKCC 14257 > >----- Original Message ----- >From: "Rich NE1EE" <TheDustyKey(a)imaginarian.org> >To: "chirp users" <chirp_users(a)intrepid.danplanet.com> >Sent: Tuesday, October 24, 2023 6:03:25 PM >Subject: [chirp_users] chirp release email links > >>From an Oct 3 email, I have >You can get it from here: >http://trac.chirp.danplanet.com/chirp_next/ > >*** Note this is http > >*** Now note that it actually resolved to >https://trac.chirp.danplanet.com/chirp_next/ >*** This is https !!! > >Perhaps it would be helpful to have the link the same as the actual target URL?

2 1

[chirp_users] Quansheng UV-K6 scan issue
by Ken Hansen 25 Oct '23

25 Oct '23

Hello, I recently picked up a Quansheng UV-K6 Dual-band HT, and had an issue with scanning memory channels - I just wanted to share my findings here, I've opened a request for Chirp_next to change this. The issue is that manually programmed channels have a field "scanlists" that is set to "1+2", but new channels added thru chirp_next have this field blank, meaning the channel is not included in channel scanning by default. To access the "scanlists" setting, you have to enable "extra" settings under the View menu item in chirp_next. (Inside the radio, the scanlists setting is actually a couple different fields that combine to populate the chirp_next specific "scanlists" setting - there is no "scanlists" setting in the UV-K6 radio.) I had this issue running chirp_next 20231021. Ken, N2VIP

2 2

[chirp_users] chirp release email links
by Rich NE1EE 25 Oct '23

25 Oct '23

>From an Oct 3 email, I have You can get it from here: http://trac.chirp.danplanet.com/chirp_next/ *** Note this is http *** Now note that it actually resolved to https://trac.chirp.danplanet.com/chirp_next/ *** This is https !!! Perhaps it would be helpful to have the link the same as the actual target URL? 73 Rich NE1EE The Dusty Key On the banks of the Piscataqua

2 1

[chirp_users] Chirp will not install
by Gene 22 Oct '23

22 Oct '23

I have downloaded Chirp several times. Try to install with No luck. I have tried different browsers. I have tried rebooting. I have tried in safe mode. I have tried all the tricks I can find on the internet, and nothing works. It's like something or some file is missing. I am at my wits end. The install gets to the screen to verify and agree to the license but nothing appears. No license. It sits there for about 5 seconds then vanishes and nothing more. I am on an HP Laptop using Windows 10. Please help. [62cc90ee-bbbd-4080-a05b-465351b94590]

13 50

Re: [chirp_users] Chirp will not install
by Rich NE1EE 21 Oct '23

21 Oct '23

I got the impression that the OP was "streaming" the thought. I suspect it meant that before working on computer internals, pay attention to operator grounding. My experience was that older edge connectors were subject to oxidation. Removing the device and rubbing the edge pins with a "genuine" rubber erase, which contains an abrasive (compare with the eraser that removes polymer lead marks), would scrub off the oxidation. Problem is that used aggressively it tended to wear right through the electrical coating on the pins. On 2023-10-21 14:10:-0400, you wrote: >How do you "ground" something with� a rubber eraser? >DR >N1EA > >On Sat, Oct 21, 2023 at 12:48 PM Chuck Hast <<mailto:kp4djt@gmail.com>kp4djt(a)gmail.com> wrote: >Doing proper grounding, the old trick used for years was a >proper rubber pencil eraser. 73 Rich NE1EE

3 3

Re: [chirp_users] Chirp will not install
by Roger Jane 21 Oct '23

21 Oct '23

3 3

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

21 Oct '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. Unless you have a reason not to, we recommend using the latest build of CHIRP-next at all times. You can get it from here: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: 2c99778f Tdh8 duplex adds off option fc76242c Convert FT-8100 for chirp-next 410ea15a [UV-K5] add Quansheng UV-K6 as alias to Quansheng UV-K5 f9bbde3a tox: use distro's default python --

1 0

Re: [chirp_users] Chirp will not install
by Michael E. Jaggers 20 Oct '23

20 Oct '23

This still begs the question: What about Chirp requires it to be built in 64-bit? Is it a requirement of the current version of Python? Mike, WB4TTZ -----Original Message----- From: Dan Smith <dsmith(a)danplanet.com>, Discussion of CHIRP <chirp_users(a)intrepid.danplanet.com> Sent: Oct 20, 2023 4:12 PM To: Discussion of CHIRP <chirp_users(a)intrepid.danplanet.com> Subject: Re: [chirp_users] Chirp will not install > No, Marc, it's not necessicarily a PC issue. We don't know yet, because when he responds he has yet to give us the Type of Windows 10 he is running. The installer is 32-bit and will run just fine on even a pretty old machine (32-bit and Windows XP), so there's really nothing about his system being incompatible that should be causing the behavior he's seeing. Thus, knowing the architecture and version of his OS is pretty immaterial at this point. I'd place serious money on it being some sort of "security" software killing the installer as soon as it sees it do something totally legit that it decides is suspicious. For the rest of the readers in this thread, the installer we use is a separate thing and not under the direct control of the CHIRP project. It's a 32-bit application because it doesn't need to be a 64-bit one and gives the best opportunity to run everywhere as a result. However, I'm working on adding an architecture and OS version check to the script so that it will positively identify these unsupported situations in the future. That will rule out any need to suspect these sorts of issues when someone reports a problem. --Dan _______________________________________________ chirp_users mailing list chirp_users(a)intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Michael Jaggers at mej(a)mindspring.com 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

5 4

[chirp_users] Alinco DR135 ect.
by wa6scr wa6scr 20 Oct '23

20 Oct '23

1 0

[chirp_users] jedi1.gh@gmail.com
by Gene 20 Oct '23

20 Oct '23

[8eb54e4d-0b88-464d-8f20-6cbbd8369600]

2 1

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

16 Oct '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. Unless you have a reason not to, we recommend using the latest build of CHIRP-next at all times. You can get it from here: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: f59b5b25 btech.py: fix BTECH GMRS-50V2 MEM_FORMAT - fixes #10883 60420d48 Update Russian translation 42363834 uvk5: Implement unknown byte in lock; killed flags. 603c9736 uv5k.py: Add powerlevels and battery calibration. --

1 0

[chirp_users] R-tone and C-tone
by K0LNY ?? 12 Oct '23

12 Oct '23

Hi, My local repeater uses 131.8 for a PL tone. I at one point had 88.5 in one place and 131.8 in the other. So I changed both to 131.8, and it seems that it should still work, but it isn't keying the repeater. I'm guessing the R in r-tone is for repeater, and the C in C-tone is CTCSS? Anyway, which one of these is the repeater wanting to hear to open up? Thanks. Glenn A man with a clock always knows what time it is. A man with two clocks is never sure. -- A derivative of Segal's law

3 3

[chirp_users] CHIRP @ Wouxun KG-Q10H
by Gary 06 Oct '23

06 Oct '23

Just bought the KG-Q10H, and immediately came here to see if CHIRP was now available for the radio. Looks like it's BETA, and that's fine...will wait till it's gold. I already have a Baofeng UV8 that I use the latest version of CHIRP with, so I'm now wondering if the programming cable I have now for the Baofeng will work. It's one of the recommended cables (when I first got my Baofeng, I came up here to get CHIRP and bought a good recommended cable), and I've physically plugged it into the Wouxun with no problems. Of course, Wouxun wants to sell me their cable, for another $25, but if the one I now have works, I don't want yet another cable plugged into my computer. So what do you think? If it works well with the Baofeng, should it work with the Wouxun. I saw a remark from another BETA tester who said his "cheap Amazon cable was working fine." Cheers -= Gary =-

4 10

[chirp_users] UV-5RIII better with older software
by Graham Whaley 06 Oct '23

06 Oct '23

Hi Chirp users, (New list subscriber. First post) I recently had an issue (re)programming my Baofeng UV-5RIII with CHIRP next-20231003, and found a 'workaround' using CHIRP daily 20200226. I thought I'd document here for any possible future reference etc. Backstory: Back in January 2020 I purchased a 'Baofeng UV-5RIII'. I've a feeling that this model had probably just come out at that time, and I didn't realise that getting a (b)leeding edge model might cause problems (yes, I understand the land of 'UV-5R' firmware is a minefield... ;-). At that time I didn't have my license, so I grabbed CHIRP and programmed up the radio. As well as entering some channels I changed the greeting messages and disabled TX. As the 'III' was not listed (afaict) at the time in CHIRP I dug around and found that the Baofeng UV-5X setting worked.... all good. Now: Three years later, I finally find a reason to try and transmit, having forgotten that I disabled TX. I grab a new CHIRP (next-20231003), find that the recommended model is the Radioddity UV-5RX3, and have at it. Turns out I can program up the channels and edit a few of the settings page entries, but I: - cannot re-enable TX on either band listed - change the greeting messages I tried with the vanilla UV-5R and the UV-5X with basically the same result (iirc) - at least, nothing would let me re-enable TX or edit the message text. The workaround: Finally I figured I could try and dig out the original chirp version I'd used. I dug up the old laptop which still had the chirp and the .img files on it. Voila, using chirp 20200226 and Baofeng UV-5X I can edit and upload the TX settings and the messages. Sorted, my radio is now back to functional. side note: although the radio says it is a tri-band 'III', the band button only cycles through two bands and Chirp only shows the two (U/VHF) bands in the settings. I don't know if this is a consequence of me meddling or not - I have no plans to use the 1.2m/220MHz band, so I'm not too bothered. Not sure if that makes any sense to the developers, but hopefully it might help somebody else in the future. For reference, my radio firmware details are: 3B5RV01 (button 3 boot) 151123H HN5RV01 I'm sort of willing to help gather any more diagnostics if necessary, I'm fairly tech savvy. *But*, I'm wary of editing anything more on the radio in case it reverts to non-functional ;-), so hopefully non-invasive data gathering if possible. I'll stay signed up to this list for a bit in case there is some feedback or requests for more info, but if you want to ensure you reach me in the future you might have to send a PM. thanks, Graham, M7GRW

2 2

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

03 Oct '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. Unless you have a reason not to, we recommend using the latest build of CHIRP-next at all times. You can get it from here: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: 68f6a46f Add a basic pre-commit config ffd2e63e Make style checker use proper list for args b5647216 Don't force FRS on Retevis RT15 99189092 [UV-K5] add Quansheng UV-5R as alias to Quansheng UV-K5 (#780) --

1 0

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

29 Sep '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. Unless you have a reason not to, we recommend using the latest build of CHIRP-next at all times. You can get it from here: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: c7689ff7 Fix firing setting warnings for the wrong setting f69d888f Improve CSV import/export of DV memories --

2 1

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

28 Sep '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. Unless you have a reason not to, we recommend using the latest build of CHIRP-next at all times. You can get it from here: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: f3a0a86c Fix revealing locations like debug log 66c84ea1 Log query parameters for network sources 170cd2f5 mml_jc8810.py: Talkpod A36plus support firmware v1.22 - fixes #10860 fa7b6109 mml_jc8810.py: add missing support for Talkpod A36plus - fixes #10866 --

1 0

[chirp_users] Baofeng BF-18H
by Roger S Morgan 26 Sep '23

26 Sep '23

Can I use one of the other Baofeng radio settings in Chirp? Alternatively, will this model be added to Chirp in the future. Thanks

4 5

[chirp_users] Caller ID error message
by lhales＠cox.net 26 Sep '23

26 Sep '23

First thank you for the add. I have a question, one probably asked before but searching through each months archive was getting me nowhere. I downloaded Chirp Next in mid Sept 2023 and am trying to use it to make a minor change to my Wouxun KG-UV9PX. When I get to settings and go to the 'freq limit' any change I make immediately opens a dialog telling me "Caller ID must be at least 3 and no more than 6 digits." The change is shown in the settings window and the file seems to save with no problem, but when I reopen the file the changes have not been saved. I am still in the learning curve for the 9PX in particular and Ham radio in general, what is the 'caller ID' error telling me? The "caller IDs" in the 'Settings' window are the default that were downloaded from the radio when I set CHRIP up. Many thanks and my apology for asking a probably very often asked question. Lynn E. Hales lhales(a)cox.net <mailto:lhales@cox.net> (757) 243-1003

1 0

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

24 Sep '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. Unless you have a reason not to, we recommend using the latest build of CHIRP-next at all times. You can get it from here: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: 22b9389e bf_t8.py: fix BTech FRS-A1 broadcast FM preset - fixes #10845 --

1 0

[chirp_users] Icom ID-52 support
by IT1 Stuart Blake Tener, USNR 22 Sep '23

22 Sep '23

1 0

[chirp_users] Baofeng BF-C50 & Serial Sniffing
by KC9MHE Eric Muehlstein 21 Sep '23

21 Sep '23

Hi All, I'm working to discover the cloning protocol for the Baofeng BF-C50. I have the OEM programming software installed in a Win11 VM and I can read/write the memory from the radio. Despite trying several tools, I can't find a solution which allows me to sniff both the RX and TX of a serial connection in Win11 for ARM. https://github.com/emuehlstein/baofeng_bfc50 Instead, I've started a couple of Python scripts which emulate one side or the other and I've been slowly teasing data out of the radio and programmer. As is, my fake programmer sends the 4 byte initialization string the radio expects, the radio replies with 12 bytes, the programmer ACKs that and the radio sends a bunch more bytes but not enough bytes to be the full memory. Any recommendations for a serial sniffing tool which will work in a Win11 Parallels VM? Recommendations on how to proceed with the script to discovering the rest of the download routine? Thanks, Eric KC9MHE

4 4