October 2023 - Developers - lists.chirpmyradio.com

[chirp_devel] TOX testing - potential unexpected condition?
by wcurlew＠juno.com 31 Oct '23

31 Oct '23

I've been working on the FT450d/450 changes, and was having issues getting through TOX. The problem was set and test special memories. On the FT450/450D, you can use the CLAR button to 'clear" a memory (which really just makes it not visible for the PMS memories), and the PMS upper and lower memories all allow this. In my test image, I have a couple of the PMS memories blanked out. In the FT450/D py get memory routines we set mem.empty = true to keep them from displaying on the gui. When the test_edges.py test_get_set_specials routine tries to set the special memories, it does not clear the mem.empty to False after reading what's already there. The FT450/D set special memory routines see an incoming request for an "empty" memory, and they make no changes and do not return a memory element. (as expected). The test_get_set_specials routine barfs on this, as the memory element returned is not what they expected. I added the m1.empty = False statement to the routine test_edges.py and the test now passes properly for the cleared memory. I ran a TOX with the full set of files in image and driver directories, and it screwed up 10 other radio models. While I would love for Chirp to accurately reflect what is on the radio, I'm concerned about perturbing the other radio models. (Just the testing obviously) Looking for comments/suggestions. Regards, Bill Result Test Duration Links Failed tests/test_drivers.py::TestCaseEdges_Icom_IC-U82::test_get_set_specials 222 ms Failed tests/test_drivers.py::TestCaseEdges_Icom_IC-E90_Radio::test_get_set_specials 00:00:02 Failed tests/test_drivers.py::TestCaseEdges_Kenwood_TM-D710G_CloneMode::test_get_set_specials 842 ms Failed tests/test_drivers.py::TestCaseEdges_Kenwood_TM-D710_CloneMode::test_get_set_specials 296 ms Failed tests/test_drivers.py::TestCaseEdges_Kenwood_TH-D74_clone_mode::test_get_set_specials 00:00:03 Failed tests/test_drivers.py::TestCaseEdges_Yaesu_FT-1D_R::test_get_set_specials 00:00:06 Failed tests/test_drivers.py::TestCaseEdges_Yaesu_FT-817ND_US::test_get_set_specials 00:00:02 Failed tests/test_drivers.py::TestCaseEdges_Yaesu_FT-857_897_US::test_get_set_specials 803 ms Failed tests/test_drivers.py::TestCaseEdges_Yaesu_FT3D_R::test_get_set_specials 00:00:07 Failed tests/test_drivers.py::TestCaseEdges_Yaesu_FT2D_R::test_get_set_specials

2 2

[chirp_devel] Ft450/450d driver changes
by wcurlew＠juno.com 30 Oct '23

30 Oct '23

Rick - The original author of the 450d code did not have a way of implementing the special data modes without changing the CHIRP_COMMON library. I also changed it to get my original 450 driver to work, and was properly chastised. So I came up with using the existing code "DIG" from common, and then putting together an mem.extra RS segment to hold the "extended" digital modes. This is working a treat for my FT-450, but now I need to see if I clobbered any of the 450D handling before submitting this. I'm not sure how to test the 450D backwards compatibility from a memory settings point of view. If you would like to see the driver prototype email me and I will send you my latest driver and a test img file for the FT450. Bill

2 1

[chirp_devel] RESOLVED Newbie to this, trouble with edits I think...
by wcurlew＠juno.com 29 Oct '23

29 Oct '23

I figured this out! During the processing of the special data_mode element in mem.extra, I was not testing to determine if the mode was moving between DIG and Non-DIG modes. The MEM.EXTRA data_mode processing when moving from a previous DIG mode going to a NON DIG mode always reset the _mode and _mode2 memories, which forced the mode column back to DIG. Now when I get a change to MODE, if it is non-DIG, I set the data_mode extra element to "N/A" When I get a DATA MODE change from N/A to any DIG mode, and the previous data_mode was "N/A", I force the mode to DIG In addition to solving my GUI entry problem, this way you never get an invalid combo of MODE and DATA MODE. What a pain! I've learned way to much more that I ever wanted to about how this stuff hangs together. Thanks for listening. Bill

2 1

[chirp_devel] Newbie to this, trouble with edits I think...
by wcurlew＠juno.com 28 Oct '23

28 Oct '23

I'm hacking up the FT450D driver to include support for the FT450 and FT450AT. At the same time I'm trying to improve the MODES to include the digital modes. I do NOT have Automatic Edits enabled. I've added a new column for the extended modes, and that is working fine. When I get a data mode (USER-U, USER-L, RTTY) I set the main MODE to DIG and update the value in the DATA MODES column. This is working great when I download from the radio or load up a saved image. The GUI seems to display everything OK. Some issues I am having are: On an existing memory, sa y a straight USB memory, If I change the MODE from USB to DIG, is if I change the MODE from anything to DIG, nothing happens, and the column still says USB. The debug log shows it is trying to set the right value, but something else is going on under the covers. No error messages in the log. Then, again on an existing memory, again USB, I change the DATA MODE from N/A to USER-U. Magically the MODE becomes DIG (who did that? Not me!) Now I can't put the mode back to USB, nor can I set the DATA MODE to N/A. I can change an existing , non-data mode to any other mode that has DATA MODE as N/A, but as soon as I try DIG, I am stuck. Can someone point me to this might be happening. This is the last major hurdle I need to get over. Thanks, Bill

2 1

[chirp_devel] Baofeng BF-5R = Baofeng BF-888 minus some features
by KC9MHE Eric Muehlstein 11 Oct '23

11 Oct '23

Hi all, Now I'm playing with a Baofeng BF-5R. I can successfully clone and write to the radio with the BF-888 driver but there isn't feature parity so I'm attempting a new class for the BF-5R. I was hoping that setting the following _has_ variables to False would make them disappear from the UI but they haven't. I have the opposite problem with my BF-C50 driver where I need to add a side-tone setting to the UI. Does anyone have any pointers for me? I feel like I'm pretty close on completing drivers for the BF-5R and BF-C50. Thanks! @directory.register class BF5R(H777Radio): VENDOR = "Baofeng" MODEL = "BF-5R" ALIASES = [] VALID_BANDS = (400000000, 470000000) _has_fm = False _has_sidekey = False _has_scanmodes = False _has_scramble = False POWER_LEVELS = [chirp_common.PowerLevel("Low", watts=3.00), chirp_common.PowerLevel("High", watts=5.00)] @classmethod def match_model(cls, filedata, filename): # This model is only ever matched via metadata return False

2 1

[chirp_devel] Radioddity PR-T3
by Saverio Proto 08 Oct '23

08 Oct '23

Hello Folks, I noticed I am not the only one with Radioddity PR-T3: https://chirp.danplanet.com/issues/10536 I wanted to give it a try to implement the support for this radio. I am following instructions here: https://chirp.danplanet.com/projects/chirp/wiki/DevelopersAdd_a_Radio and here: https://chirp.danplanet.com/projects/chirp/wiki/DevelopersUSB_Sniffing_in_L… I was able to capture the USB traffic, and I have pcap files of a read and a write with the original software for Windows from Radioddity. I can't find BAUD READ or WRITE strings in my captures. I share here my pcap files: https://www.dropbox.com/scl/fo/p2eb7bn3ig0cypkny20zq/h?rlkey=t8re5i0xil2jzt… Could please anyone confirm the captures are done correctly ? I am stuck at the moment, I need to understand what to do next. Thanks Saverio

2 1

[chirp_devel] Baofeng BF-C50 Work In Progress
by KC9MHE Eric Muehlstein 07 Oct '23

07 Oct '23

Hi All, I've been working on a driver for the Baofeng BF-C50 based on a T18 radio. I am able to upload/download from the radio, I have the settings memory map done, and I'm trying to tie up some loose ends. Maybe someone here can point me in the right direction... 1) I'm collecting a "side tone" from the settings; however, it's now clear how I add this to the radiosettings so that it's available in the UI. 2) I don't understand what the how the _frs and _grms settings work on T18Radio classes (do they validate that a frequency/width/power is appropriate for a band?). When I set them both to False I avoid problems with some memories being uneditable. 3) What is a jumpcode? I collect that on a per memory basis but I can't find any documentation on what it actually means/does. Attached, you'll find the partially complete driver file for reference. The driver as well as several reference images are available on github: https://github.com/emuehlstein/baofeng_bfc50 Regards, Eric KC9MHE

2 1