- Users - lists.chirpmyradio.com

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

19 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 10 Nov '23

10 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 06 Nov '23

06 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 27 Oct '23

27 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