- Users - lists.chirpmyradio.com

Re: [chirp_users] chirp_users Digest, Vol 177, Issue 9
by Dave B 18 Sep '23

18 Sep '23

Well Sean. If you read my original post, you'd have seen that the line:- pipx install --system-site-packages ./chirp-20230509-py3-none-any.whl Is the line in error at this time... As to suggesting to learn how to build a package from the sources... Why is that not already done by the authors/maintainers? Surely they know what's needed better than anyone... 73. Dave. On 15/09/2023 20:00, chirp_users-request(a)intrepid.danplanet.com wrote: > From: Sean Dennis > Out of curiosity, what step(s) in those instructions "fail [you] every > time"? -- Sent from a MicroSoft free zone:

5 6

[chirp_users] Linux install instructions, not quite 100%...
by Dave B 17 Sep '23

17 Sep '23

Hi. I just installed the current Chirp on this LMDE 5 system, using the instructions as shown on :- https://chirp.danplanet.com/projects/chirp/wiki/ChirpOnLinux There is a "slight wrinkle" in para 2.2. The command line invocation:- *pipx install --system-site-packages ./chirp-20230509-py3-none-any.whl* Fails as the file "chirp-20230509-py-none-any.whl" was not present anywhere. That is also an old version now as well. OK, simple for me to figure out, but for many other windoze refugees probably less so, so perhaps either some additional instruction regarding actually getting the .whl file "First" (finding the link to that was not as easy as it should be I think either) or including a wget somewhere to pull the latest from the server, and make it all work "automagically" ? Otherwise, 20230911 is working OK with the shack Kenwood TM-V71 on a 64 bit LMDE 5 system. Re the use of pipx, and the comment that pipx users will need to uninstall Chirp, before installing a new version. Is there a reason why "pipx upgrade" cant be used? If so, what is the reason? Lastly, where is the Chirp Icon file hidden these days? (So I can put it in my menu system.) Oh, I also find that this version of Chirp, does not remember the custom port name for the radio, in this case /dev/ttyTMV71 as assigned by a udev rule for consistency. The resulting entry in the port dropdown, is also mostly obscured by being shoved over to far to the left in that field. 73. Dave G8KBV. -- Sent from a MicroSoft free zone:

5 8

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

17 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: d20da97c ft2800: Fix getting subtype from older images 8afe1773 baofeng_wp970i.py: Correct UV-9G Power Level Selection - fixes #10842 c6668e11 mml_jc8810.py: support RT470 FW V1.25A - fixes #10839 --

1 0

[chirp_users] Linux install instructions, not quite 100%...
by chirp＠ish.net 16 Sep '23

16 Sep '23

There is no need to separately download CHIRP to install it because pip will do that for you. This works perfectly on Ubuntu. Just use "copy link" in the web browser for the Python wheel file and then paste it as part of the command. $ pip install -U https://trac.chirp.danplanet.com/chirp_next/next-20230911/chirp-20230911-py… Defaulting to user installation because normal site-packages is not writeable Collecting chirp==20230911 Downloading https://trac.chirp.danplanet.com/chirp_next/next-20230911/chirp-20230911-py… (1.5 MB) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1.5/1.5 MB 862.1 kB/s eta 0:00:00 Requirement already satisfied: pyserial in /usr/local/lib/python3.10/dist-packages (from chirp==20230911) (3.5) Requirement already satisfied: requests in ./.local/lib/python3.10/site-packages (from chirp==20230911) (2.28.1) Requirement already satisfied: six in /usr/lib/python3/dist-packages (from chirp==20230911) (1.16.0) Requirement already satisfied: future in /usr/lib/python3/dist-packages (from chirp==20230911) (0.18.2) Requirement already satisfied: yattag in /usr/local/lib/python3.10/dist-packages (from chirp==20230911) (1.15.0) Requirement already satisfied: charset-normalizer<3,>=2 in ./.local/lib/python3.10/site-packages (from requests->chirp==20230911) (2.1.1) Requirement already satisfied: idna<4,>=2.5 in /usr/lib/python3/dist-packages (from requests->chirp==20230911) (3.3) Requirement already satisfied: urllib3<1.27,>=1.21.1 in /usr/lib/python3/dist-packages (from requests->chirp==20230911) (1.26.5) Requirement already satisfied: certifi>=2017.4.17 in /usr/lib/python3/dist-packages (from requests->chirp==20230911) (2020.6.20) Installing collected packages: chirp Successfully installed chirp-20230911

2 1

[chirp_users] UV-9R Pro Settings Error
by Brennan Mann 16 Sep '23

16 Sep '23

When I attempt to access the "settings" tab on my uv-9r pro i get the error message "Value 16665 not in range 130-179". How should i proceed? -- Best Regards, Brennan Mann

2 2

[chirp_users] UV-82c newbie
by Andrew Jones 11 Sep '23

11 Sep '23

Would anyone know the proper settings or what I'm missing to program my radio to work with my current land mobile frequencies? I do not use a repeater. Thanks. Sent from my iPhone

3 2

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

11 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: c2a2137b Prune empty comments from metadata 21aa6ee7 Show image metadata in info tab c9b253cd rt98.py: fix check_ver() error - fixes #10833 850ae809 ft1d: fix room number length check cf3609aa Add support for Retevis RT20 --

1 0

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

06 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: 7ac0a159 ft50: Fix clone out for python3 30c3c205 Add fake serial echo tester 9bf02c41 id800: Add power level --

1 0

[chirp_users] Corrupted memories
by Gary Halleen 05 Sep '23

05 Sep '23

I’m using CHIRP next-20230905, but had the same problem with the last release as well. When programming my Yaesu FT-65R, I’m running into a couple issues: 1. If I set even a single memory to NFM instead of FM, then the next time I upload to my radio, all memories after that one are set to NFM. Example: I set memory 36 to NFM. Memories 36-100 all are set to NFM, even though in CHIRP, they look like they should be set to FM. I’ve tried doing a full reset of the radio, and also tried a memory reset of the radio. Next time I upload, they go back to NFM. 2. If I have memories assigned to Banks, and then delete a memory without first unchecking the box for the bank, the memory stays as a phantom memory. To replicate: Add a new memory and assign it to a bank number (Bank 2 is what I used). Then, after it’s been uploaded to the radio, delete the memory in CHIRP, and re-upload to the radio. When the radio is not set on a Bank, the memory does not show up in the radio. Now, switch the radio to Bank 2. The memory and all of its settings are there even though it was deleted. To resolve it, set a new memory to the same memory number, and go into banks, and uncheck Bank 2. Then, save and go back to memories and delete the memory. Re-upload to the radio and the memory is now gone. Thanks for your hard work keeping CHIRP running for all of us! Gary K7TRO

1 0

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

05 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: 19dc13de Fix for issue #10226 --

1 0