- Users - lists.chirpmyradio.com

[chirp_users] Baofeng UV82 Preprogrammed Channels
by K0LNY_Glenn 15 Jan '23

15 Jan '23

Hi, A friend of mine just got a new Baofeng UV82, he is about to take his Ham Tech test. I sent him a Chirp install file, but I don't know if he will be able to access it with his screenreader in windows 11. So I have worked with him over the phone on entering frequencies into frequency mode. So in channel mode, it came with some channels, but he is Blind, so there is no way for him to know what they are. Can anyone send me a list of the channels they put in one of these from the factory? Maybe someone saved their original file that you can copy the channels and associated frequencies for me please. Thanks Glenn

3 3

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

15 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 #39 [3046399+kk7ds] Formalize chirpc a bit and install it [3046399+kk7ds] Add back the easy chirpc runner [3046399+kk7ds] Make style target run flake8 on chirp.cli [3046399+kk7ds] Refactor repeaterbook item parsing for errors [3046399+kk7ds] Add RepeaterBook "rest of world" queries [3046399+kk7ds] Add support for RepeaterBook Notes field [3046399+kk7ds] Make cell background grey for immutable values [3046399+kk7ds] Align query source link on Windows [3046399+kk7ds] Ellipsize cells when column is resized smaller [3046399+kk7ds] Add repeaterbook tests and fix a bug found [3046399+kk7ds] Add super simple CLI test to get started [3046399+kk7ds] Remove two unit test files for chirp-legacy [3046399+kk7ds] drivers.ftm350: Define and set "visible" bit [3046399+kk7ds] Convert Yaesu FT-2900 for python3

1 0

[chirp_users] RepeaterBook GMRS Queries!
by Dan Smith 14 Jan '23

14 Jan '23

Hi All, I'm excited that today's build includes support for querying RepeaterBook's GMRS database! Thanks to Garrett (RepeaterBook's owner), CHIRP users now have the ability to pull this data in as well. It works the same way as the other RepeaterBook queries, with searching, sorting by distance, and local caching. Like CHIRP, RepeaterBook depends on volunteers to maintain the database and they are responsible for growing it into the extremely comprehensive and valuable resource that it is today. If you know of any GMRS activity in your area, I encourage you to pull up the query for your location and if you notice anything missing, help by submitting it for inclusion here: https://www.repeaterbook.com/gmrs/add_repeater.php I found one new open GMRS repeater in my local area that is missing, so I'll be doing the same today :) --Dan

1 0

[chirp_users] chirp-next: howto update correctly
by Angelo Marcone 14 Jan '23

14 Jan '23

Hi Everyone, I switched to chirp-next and I installed it with success in Linux Mint 'Vera' (21.1) and Debian 10 by downloading tar.gz file running sutup. The only question I have now is: how to update my installation wthi the new daily releases? Is it ok download the new version running, for this setup again? Thanks for yout time. 73 de Angelo IK8VRQ/KG6DPO

2 1

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

14 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 #38 [3046399+kk7ds] Mock time in test_alinco_clone [3046399+kk7ds] Add Alinco DJ-G7T [3046399+kk7ds] Fix TH-D74 editing of WX memories [3046399+kk7ds] Fix refreshing special channels losing labels [3046399+kk7ds] Fix setting defaults on immutable memory fields [3046399+kk7ds] Make memory properties dialog honor immutable [3046399+kk7ds] Add RepeaterBook GMRS query support [3046399+kk7ds] chirpc: Fix setting tone modes [3046399+kk7ds] Record IC-2300 and FT-65R as working [3046399+kk7ds] Add some safety around closing the clipboard [3046399+kk7ds] Make sure edit controls use the do_radio helper [3046399+kk7ds] Fix delete and shift not cleaning the tail [3046399+kk7ds] Fix delete with block shift in empty block [3046399+kk7ds] Schedule prefill jobs with lower priority [3046399+kk7ds] Use erase_memory when moving an empty memory [3046399+kk7ds] Properly report erase_memory jobs in the status [3046399+kk7ds] Disable bulk shift operations when radio is busy [3046399+kk7ds] Make row progress indicators work for edit ops

1 0

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

13 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 #36 [3046399+kk7ds] Fix radio identities on some test images [3046399+kk7ds] Remove old test runners [3046399+kk7ds] Massive driver test refactor [3046399+kk7ds] Mock out time functions in clone tests [3046399+kk7ds] Fix delete-and-shift with special channels [3046399+kk7ds] Record IC2730 as working in the wild [3046399+kk7ds] Log information about pasted data Changes for Build #37 No changes

1 0

[chirp_users] Importing a CSV file into the memory of an Alinco DJ-G7T
by Stuart Longland VK4MSL 12 Jan '23

12 Jan '23

Hi all, Has anyone had any luck loading a CSV file into an Alinco DJ-G7T. I have organised a list of FM repeaters for 2m/70cm/23cm from the WIA repeater data spreadsheet. I won't publish it here, but suffice to say, it's more than I want to try and punch in via the keypad. 556 records. First problem is getting Chirp to even talk to the DJ-G7T. I have no idea what firmware it runs. I went looking in its menus but could not find where this information is shown. All I can say is I bought this from a online retailer (Andrews Communications) in Sydney around 2020. I am running the latest commit of Chirp: commit 49698a5b21a5a696be7f2121bc3ec8f4605b5b0c on Gentoo Linux AMD64 with Python 3.10.6, wxpython 4.0.7-r2 and wxgtk 3.0.5.1. Gentoo no longer ship Python 2.7. No I do not have a Windows-based PC as I don't use legacy operating systems for production work. To even get Chirp to talk to the Alinco, I needed to patch it (I think this will preclude me using a pre-made "binary"): diff --git a/chirp/drivers/alinco.py b/chirp/drivers/alinco.py index 7bfffa39..b3350653 100644 --- a/chirp/drivers/alinco.py +++ b/chirp/drivers/alinco.py @@ -595,7 +595,7 @@ class AlincoDJG7EG(AlincoStyleRadio): TMODES = ["", "??1", "Tone", "TSQL", "TSQL-R", "DTCS"] # This is a bit of a hack to avoid overwriting _identify() - _model = b"AL~DJ-G7EG" + _model = b"AL~DJ-G7T" _memsize = 0x1a7c0 _range = [(500000, 1300000000)] I was then able to download an image file from the radio. If I load up my CSV file, the upload option is greyed out. So clearly I don't directly open the CSV file, I have to "import" it somehow. If I try to copy the repeaters into the image from the radio, even just one repeater, Chirp segfaults. So clearly it's not a matter of copy and paste. How does one import a CSV file into an existing radio image? -- Stuart Longland (aka Redhatter, VK4MSL) I haven't lost my mind... ...it's backed up on a tape somewhere.

3 5

Re: [chirp_users] Importing a CSV file into the memory of an Alinco DJ-G7T
by Dan Smith 12 Jan '23

12 Jan '23

> I believe others already have, at least two or three times looking at > the bug tracker, many of which have patches. I didn't want to clutter > it with duplicates. > > https://chirp.danplanet.com/projects/chirp/search?utf8=%E2%9C%93&scope=&iss… Fair enough. I've never taken patches through the bug tracker as a general rule, although people attach them there sometimes. That's why those issues aren't open and have comments about following the process. I also need a test image of the radio in order to add it to the tree, not just a patch. If you can muster the github steps to get that submitted that would be great. However, if you can either test one of the existing patches and attach your test image, or open a new one with your image and patch, I can work the process for you. > As far as I know this is the US version of the DJ-G7. Here in > Australia we have a 4MHz-wide 2m band (144-148MHz) and nearly all the > FM repeaters are in the upper 2MHz. > > The other difference is the European DJ-G7 uses 9kHz spacing for MW > broadcast reception -- whereas the US DJ-G7 uses 10kHz (annoying, > because Australia has had a 9kHz spacing on MW since 1978). > > Other than that, I suspect the two sets are practically identical. Neither of those are likely to impact CHIRP, so yep, should be okay. > I'll have to do some investigation then. The files I'm working with > are here (patch, image dump from radio and my repeater listing): > > http://static.vk4msl.id.au/chirp/2023/01/13-djg7t/ I can probably turn that into a patch, but I need someone to test it before I'll put it in. If you'll open an issue for this, we can collaborate on getting something tested and into the tree. > I guess a feature to allow one to import memory channels from a CSV > (overwriting existing ones) would be handy as copying and pasting > channels gets cumbersome. Feedback from the legacy version was that copy and paste was far more flexible and user-friendly, and even being a CLI and developer type myself, that's how I do it. I rarely want to import everything from my master list into every radio, given a non-overlapping set of supported features, bands and modes. The legacy version had a very complex import mechanism, which I never used, and if you watch some of the youtube videos people have made, it far complicates for them what would be much easier with copy and paste. The mere existence seemed to make people think they had to do import instead of copy/paste. Having a just-overwrite-everything import is an option and I could add that, and may in the future, but for the moment copy and paste is the workflow. Sometimes simpler is better, especially in a GUI app. > Another prospect might be a CLI interface, so I could just prepare the > file, then tell `chirp` to download from the radio (or load from an > existing image), replace the channels, then upload it back to the > radio. There is a CLI in the git tree and some people do use it. If you find it useful, feel free to file a feature request to have it included in the source distribution. --Dan

1 0

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

12 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 #35 [3046399+kk7ds] Fix insert/delete operations off-by-one [3046399+kk7ds] Re-fix UV3R for python 3 [3046399+kk7ds] Disable selecting rows in the bank editor [3046399+kk7ds] [uv5r.py] Add ability to upload all ranges [3046399+kk7ds] Add DN to mode list for Yaesu System Fusion [3046399+kk7ds] Make RepeaterBook return YSF (DN mode) repeaters [3046399+kk7ds] Add mode filtering to RepeaterBook query [3046399+kk7ds] Fix bug in RepeaterBook band selection [3046399+kk7ds] Add __contains__ handler for RadioSettingGroup [3046399+kk7ds] Fix setting boolean mem.extra properties [3046399+kk7ds] Fix post-properties memory refresh [3046399+kk7ds] Add DN mode support to FT1, FT2, FT3

5 7

[chirp_users] chirp-next - Row selection on banks tab
by Matt Foster 11 Jan '23

11 Jan '23

I was just doing some work on my image file for a Yaesu FT-60R. I was assigning memories to banks, and I somehow got multiple rows in the table highlighted. I think I may have clicked and dragged slightly to cause this. I can not un-highlight the rows, nor do I see the point of highlighting rows in the banks table. If there is not anything useful to be done after selecting multiple rows of this table, would it be possible to just disable the row selection there? 73, Matt, N0EYE

3 2