January 2023 - Developers - lists.chirpmyradio.com

[chirp_devel] Invalid version: 'py3dev' breaks build.
by Barry Jackson 31 Jan '23

31 Jan '23

Hi Dan, Since our (Mageia) most recent python3 updates sometime this month chirp-next builds fail with: packaging.version.InvalidVersion: Invalid version: 'py3dev' The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/lib/rpm/pythondistdeps.py", line 626, in <module> raise RuntimeError("Error: pythondistdeps.py generator encountered an unhandled exception and was terminated.") from exc RuntimeError: Error: pythondistdeps.py generator encountered an unhandled exception and was terminated. error: Dependency tokens must begin with alpha-numeric, '_' or '/': *** PYTHONDISTDEPS_GENERATORS_FAILED *** Provides: application() application(chirp.desktop) chirp = 1:0.4.0-0.20230101.1.mga Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PartialHardlinkSets) <= 4.0.4-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 Requires: python(abi) = 3.10 python3.10dist(future) python3.10dist(pyserial) python3.10dist(requests) python3.10dist(six) python3.10dist(yattag) /-------------------------------------- For now I have used: sed -i 's/py3dev/%{version}/' chirp/__init__.py .. in our spec. to fix the above issue for our package. Since you do not make releases it's difficult to decide on any sort of versioning that makes sense for our packages. I use 0.4.0 as version and add the date from git into the release, which keeps our packages in order but means little outside of the distro. e.g. chirp-0.4.0-0.20230125.2 I really wish you actually made releases. /OT Today's package works fine with my test radio. (UV5RE) :) Cheers, Barry

5 12

[chirp_devel] Missing svg from release tarball/whl
by Tony Fuller 30 Jan '23

30 Jan '23

Hey Dan, I'm working on the snapcraft build script again, and I need a small bit of help on thi In the git repository, there's a chirp.svg file that makes the snap icon look great (the png file does not look so good on Ubuntu's application menu) but it appears that neither the release tarballs or the whl files contain the SVG file in the share directory -- just an ICO and a PNG. Would you be able to add this to the tarball and/or whl releases? Thanks, Tony

3 2

Re: [chirp_devel] chirp_devel Digest, Vol 141, Issue 10
by Mel Terechenok 21 Jan '23

21 Jan '23

Read and write is what Wouxun CPS uses.... but at least adding "To radio " or "From Radio" would help clarify direction of transfer for those less radio/computer literate. As upload and download are dependent on your perspective. On Sat, Jan 21, 2023, 3:02 PM <chirp_devel-request(a)intrepid.danplanet.com> wrote: > Send chirp_devel mailing list submissions to > chirp_devel(a)intrepid.danplanet.com > > To subscribe or unsubscribe via the World Wide Web, visit > http://intrepid.danplanet.com/mailman/listinfo/chirp_devel > or, via email, send a message with subject or body 'help' to > chirp_devel-request(a)intrepid.danplanet.com > > You can reach the person managing the list at > chirp_devel-owner(a)intrepid.danplanet.com > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of chirp_devel digest..." > > > Today's Topics: > > 1. Thoughts on upload/download terminology (Dan Smith) > 2. Re: Thoughts on upload/download terminology (Matthew Poletiek) > 3. Re: Thoughts on upload/download terminology (David Boucha) > 4. Re: Thoughts on upload/download terminology (Dan Smith) > 5. Re: Thoughts on upload/download terminology (Jim Unroe) > 6. Re: Thoughts on upload/download terminology (Dan Smith) > 7. Re: Thoughts on upload/download terminology (Martin Cooper) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 20 Jan 2023 15:34:14 -0800 > From: Dan Smith <dsmith(a)danplanet.com> > Subject: [chirp_devel] Thoughts on upload/download terminology > To: chirp devel <chirp_devel(a)intrepid.danplanet.com> > Message-ID: <021DF205-CBA7-4BE1-AC1B-F41499FEACB2(a)danplanet.com> > Content-Type: text/plain; charset=us-ascii > > Hi all, > > Someone just filed a bug about the fact that CHIRP-next uses only "upload" > and "download" in the Radio menu. This wasn't intentional, but is a > departure from what it used to be, which is "Upload TO radio" and "Download > FROM radio". Changing that completely now *might* catch some users > off-guard, but I think he's probably right that the single-word options are > too vague. > > Any strong opinions on moving from upload/download (to/from radio), to > "Read from Radio" and "Write to Radio"? Even "Read" and "Write" might be > okay, given they're under the "Radio" menu. > > https://chirp.danplanet.com/issues/10303?next_issue_id=10301 > > I initially knee-jerked in my usual hates-change way to moving to > read/write but perhaps that would be better, and does (I think) match other > software. > > --Dan > > ------------------------------ > > Message: 2 > Date: Fri, 20 Jan 2023 18:22:35 -0600 > From: Matthew Poletiek <matthew.poletiek(a)gmail.com> > Subject: Re: [chirp_devel] Thoughts on upload/download terminology > To: Dan Smith <dsmith(a)danplanet.com>, chirp devel > <chirp_devel(a)intrepid.danplanet.com> > Message-ID: > < > CAJhSV8uTqcoAk6+HDMA5P789t2mw547CETRiqSHSdot6ze6wcQ(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Probably thinking about it too hard myself, but here are some thoughts. > > Upload and download infer a temporary, potentially unstable connection or a > remote/temporary target. > > Read and write infer something less remote and much more stable and > consistent. > > I think upload and download make the most sense for this use case > considering protocols in use and the temporary connection or potentially > unstable one. > > Read and write might set expectations too high for some users. > > 2cents. > > On Fri, Jan 20, 2023, 17:34 Dan Smith via chirp_devel < > chirp_devel(a)intrepid.danplanet.com> wrote: > > > Hi all, > > > > Someone just filed a bug about the fact that CHIRP-next uses only > "upload" > > and "download" in the Radio menu. This wasn't intentional, but is a > > departure from what it used to be, which is "Upload TO radio" and > "Download > > FROM radio". Changing that completely now *might* catch some users > > off-guard, but I think he's probably right that the single-word options > are > > too vague. > > > > Any strong opinions on moving from upload/download (to/from radio), to > > "Read from Radio" and "Write to Radio"? Even "Read" and "Write" might be > > okay, given they're under the "Radio" menu. > > > > https://chirp.danplanet.com/issues/10303?next_issue_id=10301 > > > > I initially knee-jerked in my usual hates-change way to moving to > > read/write but perhaps that would be better, and does (I think) match > other > > software. > > > > --Dan > > _______________________________________________ > > chirp_devel mailing list > > chirp_devel(a)intrepid.danplanet.com > > http://intrepid.danplanet.com/mailman/listinfo/chirp_devel > > Developer docs: > http://chirp.danplanet.com/projects/chirp/wiki/Developers > > >

2 1

[chirp_devel] Thoughts on upload/download terminology
by Dan Smith 21 Jan '23

21 Jan '23

Hi all, Someone just filed a bug about the fact that CHIRP-next uses only "upload" and "download" in the Radio menu. This wasn't intentional, but is a departure from what it used to be, which is "Upload TO radio" and "Download FROM radio". Changing that completely now *might* catch some users off-guard, but I think he's probably right that the single-word options are too vague. Any strong opinions on moving from upload/download (to/from radio), to "Read from Radio" and "Write to Radio"? Even "Read" and "Write" might be okay, given they're under the "Radio" menu. https://chirp.danplanet.com/issues/10303?next_issue_id=10301 I initially knee-jerked in my usual hates-change way to moving to read/write but perhaps that would be better, and does (I think) match other software. --Dan

7 8

[chirp_devel] Yaesu memories
by Declan Rieb 17 Jan '23

17 Jan '23

> > So, I think the way to handle this is to expose these memories as "special channels" with everything marked as immutable. If they're not actually in the memory image, we'll just need to store all that data in the ft1d.py file, and return them as memories when requested. Then we can expose those in the memory editor, but they will be un-editable if everything is immutable. That way they can show up in the bank editor (more work may be required here) and then we can reflect those mappings and allow them to be changed. > > Does that sound like a plan? Yes, that sounds quite plausible; I had even experimented with something similar in an earlier toy version. But i had the wrong idea, thinking they were memories and not bank entries. Thanks for the thought you put into this to help me avoid playing with my own mental blocks! How does CHIRP-next GUI handle specials? The old GUI had a way to hide and show specials; Yaesu has some 150 pre-defined addresses! With the thousand memory locations already in the radio, that’s a lot of scrolling (especially since we also cannot hide undefined memory locations now.)

2 1

[chirp_devel] Was: Yaesu question(s)
by Declan Rieb 16 Jan '23

16 Jan '23

Thanks for the replies. Yes, I have a Yaesu FT2D. I’ll try looking at your suggested radios for guidance on the digital-mode settings. I’ll also try to better check the DN and FM settings on the real radio. The FT1 is substantially similar based upon the preexisting FT-1 driver and Yaesu’s manual; FT2D inherits almost everything from FT1. (That looks to be true for the FT-3 as well.) To get CHIRP working on FT-2D, I also made substantial changes to FT-1 driver because they’re so similar I often only needed to tweak the FT-1 to enable any newer stuff. IIRC, most changes were in character representation. I believe the Yaesu FTM3200 also uses the FT-1D driver. You’ve asked some questions whose answers are getting me to suss out some flaws in my understanding of how the FT-numeral series works. There is (in the radio somewhere, but not apparently in CHIRP-accessible memory) non-variable memory describing SW broadcast, WX, and VHF Marine (NOT GMRS as I’d said before.) They’re called “preset receiver memory channels” in the manual. The channels may be registered into a MEMORY BANK (not into the actual volatile memories, AFAICT) and that information used in the A receiver [FT2DR Instruction Manual (APRS Version), p 69 or <https://www.yaesu.com/downloadFile.cfm?FileID=8930&FileCatID=151&FileName=F…> ] A memory bank channel datum includes an index into the actual memories; high-order bits are used to flag that the data should come from any of the preset receiver memory channels. A memory entry CAN be defined to use, say a WX frequency and modulation mode without any reference to the “preset receiver memory channels”; the radio should automagically prevent transmission, but receiver will work. During bank operations, the FT-1D driver uses the memory BANK channel data to index into the CHIRP memory. IF a user has placed a preset into a bank memory, then CHIRP used to use the BANK channel index WITH its flag bits set, which is an address way too large for CHIRP to handle; chirp will abort trying to read or write to that address. To “correct” that behavior (yes, I had submitted a ticket, but that was long ago) I had ANDed out the flags sections, and included a LOG. warn message indicating that CHIRP doesn’t handle this case correctly. See, e.g., ft1d.py line 503 et seq. _update_bank_with_channel_numbers [I got the source file from a git pull just now; there were no changes to ft1d.py] Yaesu Memory banks (there are 24) can each contain 100 entries, which are pointers to either the FT1D memory locations or to the “preset receiver memory channels”, depending upon the flag bits. But memory entries need not be registered into any banks AFAICT, nor should CHIRP memory entries be accessed during the processing of presets. I would like to have CHIRP understand, display and set these bank channels to the preset receiver memory channels. It makes sense to have some of these presets usable in a memory bank for use in a special location (repeaters, weather and VHF for scanning, e.g…. indeed that was the use case prompting the ticket submission; the user had manually entered the preset into a bank set up for camping.) CHIRP’s a fine tool for that, and your easy access to the GMRS/FRS data seems to indicate similar considerations. I think that if I “simply” predefine the data needed, I can fix BANK processing to point to the appropriate “preset receiver memory channels” and avoid memory processing in CHIRP. I’ll have to imagine some way to display a preset memory entry, and to select one if it’s desired. I will have to think about this. I fear refactoring the ft1d.py may break some things, and I only have an FT2D, so won’t be able to check everything. So: no decisions yet, bu I’ve got some studying to do! ______ Declan Rieb WD5EQY wd5eqy(a)arrl.net

2 1

[chirp_devel] Yaesu question: Digital mode
by Declan Rieb 14 Jan '23

14 Jan '23

Thanks for finding and putting in the “DN” mode. Interestingly, on the FT-2D, the “automatic” mode is displayed as DN or FM with a line over the characters, meaning that the radio will default to trying the letter-configured mode but will automagically convert itself to the opposite one if appropriate. (It doesn’t always revert back to that automatic mode after changing itself, AFAICT.) The Yaesu FT-1 and successors are able to handle YSF and Wires-X digital data in the DN or bar-above-FM mode. I have mapped much of the memory space for configuring these (sub?) modes, and even tried to create a settings capability via the old TK GUI interface. Although I doubt there is a burning need for this, wouldn’t it be nice to be able to at least access the settings? Is there any walkthrough to help one use drive the CHIRP data model and GUI to display and configure top-level as well as hierarchical settings? Clearly, Somebody already has done that for the APRS data. and I tried using that as a model, but there’s no easy hierarchy in there. If it looks to be not-useless to others, I may submit a ticket for this and a proposed but incomplete solution. ______ Declan Rieb WD5EQY wd5eqy(a)arrl.net

2 1

[chirp_devel] Yaesu question: fixed memory
by Declan Rieb 14 Jan '23

14 Jan '23

Many Yaesu models (FT-1, FT2, FT-3, and probably others) have some fixed memory data (frequencies for SW broadcast, Weather, Marine and GMRS/FRS) pre-installed. In the FT-1 and above, these fixed memories are accessed via flags in the memory module (one flag bit per type of location). That makes the memory locations appear much bigger than the ‘real' channel memory; ‘real’ channels are at the moment accessed by stripping off the flag bits, and not saving any such data in the CHIRP model. This has caused at least one error request to be submitted and fixed when a Yaesu FT-2D user entered a WX channel into his radio by hand and tried to use CHIRP to help modify and save his memories; CHIRP died until I did the masking and prevented CHIRP from reading or saving such a memory. BUT I’d like to find an adjunct to the CHIRP model so that the fixed memories can be accessed. Are “immutable” memories an appropriate mechanism? I have no idea where the fixed memories are stored in the actual radio. I presume that one would build several tables of “immutable” memories that can be pre-defined and accesssed. The fixed memory definitions are listed in the Yaesu manuals, and seem to be identical between models. Is there an easily-accessible memory model that would allow this to “just work”??? Please and thank-you. ______ Declan Rieb WD5EQY wd5eqy(a)arrl.net

2 1

Re: [chirp_devel] Mode designator for YSF?
by Mathias Weyland 11 Jan '23

11 Jan '23

On 2023-01-11 02:17, Dan Smith via chirp_devel wrote: > Wow, yeah. It sounds to me from the above (correct me if I'm wrong) > that maybe DN encompasses two things, sort of layer 1 and layer (or > 7). Layer 1 being the lowest protocol and Layer 7 being some of the > voice/data/codec stuff , and that VW mode would reuse a lot of layer 1 > but swap out more of the Layer 7 stuff than just "twice as many voice > packets" (so to speak). Maybe? I'm not sure if it helps if I lay this out but we can try... So basically every single digital Fusion transmission has the following structure; each frame is 0.1 s and 960 bits: Header Frame, Frame, Frame, Frame, ..., Frame, Termination Frame All frames have the same structure, which is as follows: frame sync (40) -- frame information (200) -- payload (720). For DN, the payload of 720 bits comes in two variants. Variante (I) consists of 10 sub-frames with 72 bits each. Except for the header and termination frame, the payload sub-frames are voice data and metadata sent in an alternating fashion. The voice data sub-frames are produced by algorithm "A" and the metadata sub-frames are produced by algorithm "X". Alternatively, (II) the payload consists of 5 digital voice sub-frames of 104 bits and 5 metadata sub-frames of 40 bits, again arranged in alternating fashion. The voice sub-frames are produced by algorithm "B" (this is not documented by Yaesu and is the part that I reverse engineered) and the metadata sub-frames are produced by algorithm "Y". "X" and "Y" are very similar and which of the two variants is used depends on the amount of metadata that is to be sent. For VW, the first non-header frame is special and contains metadata produced according to algorithm "Z" wich is similar to "X" and "Y". The remaining regular frames have a payload that consists of five voice sub-frames of 144 bits each, back to back. They are produced by algorithm "C". "A" and the algorithm used in DMR to create digital voice frames are the same. Algorithms "A" and "B" are moderately similar (we can discuss the details but there's probably no point in doing that here...). "C" is very different from "A" and "B", yet still based on the MBE speech model like all the other ones... Is that somehow compatible with your layer concept? In my world, the layers would be as follows: 0: Physics 1: Modulation scheme 2: Structure of frames 3: Structure of payload into sub-frames 4: "Algorithms" > Well, I'm not planning to actually expose these as columns in the main > editor, but options in the RightClick->Properties dialog, like D-STAR > stuff is now. I see. What bothers me the most about this approach (and I guess that is more important than the technobabble from above): At least around here, some repeaters are multimode analog & digital and some others are digital only. With the solution you propose, I would want to set the multimode ones to DN with the default AMS and the digital only ones to DN with no AMS. I would definitely not want to leave AMS on for the latter ones, as that would leave me with random analog squelch openings when I hit QRM, or it would require met to set up some kind of mock-TSQL to avoid that. But what I should do instead is turn AMS off. And entering a context menu and property dialog to do that would annoy me quite a bit in particular if I would not see the current setting in the main editor. Regards Matt

2 1

[chirp_devel] Mode designator for YSF?
by Dan Smith 10 Jan '23

10 Jan '23

Hi all, I'm not a Yaesu guy and thus not very YSF-literate. It looks to me like the YSF radios call their digital mode "DN" when enabled (as opposed to "FM"), like D-STAR has DV. Is that right and does it make sense to use that in chirp's mode list for editing these channels? I had originally thought "YSF" like "DMR" would make sense, but now I'm not sure after looking at a radio. Yaesu's documentation doesn't seem to be super clear on this. It also seems like maybe the convention is to actually set the radio to Auto mode because of the dual FM/digital nature of YSF repeaters, is that right? If we add support for this, does that mean "Auto" is really what we should be setting in most cases? There's also a "VW" mode, but it seems to be sort of an additional flag, more so than just a mode. So does it make sense to set a channel to FM/DN (or Auto) and then have VW be a separate flag via extra/properties? If there's someone that is YSF-literate that might be able to test some stuff in the coming week or so, speak up :) --Dan

3 5