- Users - lists.chirpmyradio.com

[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 30 Sep '23

30 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 27 Sep '23

27 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