March 2024 - Developers - lists.chirpmyradio.com

Welcome to the new list
by Dan Smith 22 Mar '24

22 Mar '24

Hi all (again), I'm emailing you via the new mailing list on the new domain. The site for the new list software is: https://lists.chirpmyradio.com You should be able to do the "forgot password" routine if you want to log in and change your settings. I've imported the old subscription list, as well as the archives which are viewable in the new software as well. I don't want to generate too much noise for people, but if at least a few people could reply and indicate that this worked (as well as any other issues like it landing in spam) I'd appreciate it. Thanks! --Dan

8 9

[chirp_devel] Introduction
by Eric Poole 12 Mar '24

12 Mar '24

Good morning all, from a new CHIRP user and new member of the developer's reflector. (Incidentally, is it CHIRP or Chirp or chirp? I've seen all three used. What is the proper way to refer to the product?) I've joined the developer's reflector because I would like to contribute to CHIRP by writing drivers for the Icom IC-746PRO and IC-706MKIIG. I'm a retired software developer with 40+ years experience, mostly in C with some assembly language and C++. I have almost no experience with Python, have just done some minor modifications on existing programs. I do understand object-oriented design and programming. I have only limited experience with Git, having used it on only two projects, mostly used Subversion on past projects. I'm wondering if any of you have any recommendations for a good tutorial, available on the net, for someone like me who wants to learn enough Python to be effective in writing drivers for CHIRP. I know there are many such tutorials out there and wanted to find out if you have any recommendations for one over the others. I'd appreciate any suggestions, and meanwhile I'll be around the reflector as I go about figuring out how to do this correctly. Thanks... Rick WA1RKT Londonderry, NH Catch me on 14.300 MHz Intercon / MMSN most days See my QRZ page

2 5

[chirp_devel] Radioddity FS-T3 seems related to Retevis RB18
by Charles Terrell 05 Mar '24

05 Mar '24

Trying to get Chirp to talk to my Radioddity FS-T3 (same as PR-T3). Using a typical USB cable with FTDI chip. Proprietary software from Radioddity runs well in Win 10, and tolerably in Fedora using "bottles". Using plain wine is more complicated due to .net DLL errors. Based on earlier FCC filings and similar appearance, it could be a rebadged Baofeng BF-T12. Could not find a free working serial port capture solution for Win 10. Linux capture scripts from chirp docs yielded a pcap file but nothing parsed out. Finally just loaded the pcap file into wireshark. Confirmed baud and flow settings. Exported as plain text from there, grepped for "payload", cleaned it up with my own perl script. What I found: PC sends "PROGRAL" and radio replies with "P3107". Digging through existing chirp code, Retevis RB18 driver (radtel_t18.py) has both PROGRAL and P3107. Tried it: Yes! Radioddity FS-T3 actually works with RB18 driver. But it's not perfect. It's limited to 22 channels, while the real radio can handle up to 99 memory channels. 22 seems to be hard-coded in the RB18 driver. This is sort of a big deal because the radio offers no way to change squelch tones / codes without using a computer. Sometimes it's easier just to add another channel for a particular group or event. Also, the radio can do separate RX/TX freqs via its original software, making it GMRS repeater compatible. (Note that it is not marketed as GMRS. Based on signal reports, I suspect it forces narrowband for GMRS repeaters. Possibly because repeater inputs are in the same general freq range as FRS channels 8-14.) But the RB18 driver forces simplex. Haven't tried other drivers yet, but at least 3 other files mention P3107. This is a good start though. As it is now, the RB18 driver gives the functionality one would need for pure FRS-only usage. I think we can do better for GMRS / PMR446 / 70cm ham / extra FRS channels, which the mfg's software already can do. I'll check my dev tools setup and see what I can come up with. ---- Charles Terrell <tachyon(a)pobox.com>

4 6

Re: [chirp_devel] Introduction
by Dan Smith 29 Feb '24

29 Feb '24

> The IC-746 driver is a bit of an oddball insofar as it's the only one of the Icom CI-V drivers that doesn't appear to define its own memory format. Whether that's because it was the first of these drivers, and therefore got to define the core classes, I don't know. Nope, it was actually the third (after the 7200 and then the 7000)! FWIW, I think it _does_ actually have its own frame format, it just calls it "DupToneFrame" because it was like the earlier ones, but.. had duplex/tone which the 7200 doesn't. I think that at that point we were probably thinking that the memory format would be more consistent among models. Nothing else actually uses that except the 746, if I'm reading correctly. > As such, though, it's perhaps not the best place to start. Following the design of the IC-910 driver is likely a better bet, though you'll probably want to look at others for tips on what the format might look like. Given that I've seen the IC-746Pro referred to as the IC-7400, it's possible that you may get tips from looking at the IC-7300 format. I wrote the IC-910 driver, and am happy to help with questions. Perhaps just one reason to look at the 746 instead is that it's very bare-bones and the 910 has a lot more features and the 23cm probing thing. But yeah, fair point that starting with (or at least consulting) one that has gotten much more love over the years is probably a good idea. --Dan

2 1