- Users - lists.chirpmyradio.com

[chirp_users] Regarding Chirp Software For Yaesu System Fusion C4FM Radios.
by Joseph 09 Jan '23

09 Jan '23

Chirp For Yaesu System Fusion Radios For example Yaesu FT-70, Chirp doesn't recognize C4FM digital fusion repeaters. Kindly improve this to add this feature functionally. Thank you. [image: GeoTrack] <https://streaklinks.com/BWPMuUMVFQKfnaazJgHHwtgV/https%3A%2F%2Fgeotrack.ema…> Sender notified with GeoTrack <https://streaklinks.com/BWPMuUQ2tiTY_c-DlAxDOSgv/https%3A%2F%2Fgeotrack.ema…> [image: Mailtrack] <https://streaklinks.com/BWPMuUQqqrfUKUmAkAd_m-gI/https%3A%2F%2Fgeotrack.ema…> Sender notified by Mailtrack <https://streaklinks.com/BWPMuUQwMG_i-wo3OAGjE2fJ/https%3A%2F%2Fgeotrack.ema…> 01/08/23, 12:19:33 PM [image: 19] ᐧ

6 11

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

09 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 #30 [3046399+kk7ds] Only show browser tab for CloneModeRadio [3046399+kk7ds] Wrap browser init to catch errors [3046399+kk7ds] Record Icom W32A as working [3046399+kk7ds] Fix tone display for radios without ctone field [3046399+kk7ds] Log paste errors for forensics [3046399+kk7ds] Fix radio browser on Windows

1 0

[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