[chirp_devel] Call for help

[pizzi.joe at gmail.com]

I have a Yaesu FT-991A. I don't see it on the list. Is it expected to be
compatible? I've never tried using Chirp with it.

Joe Pizzi
KI5LST

-----Original Message-----
From: chirp_devel-bounces at intrepid.danplanet.com
<chirp_devel-bounces at intrepid.danplanet.com> On Behalf Of Dan Smith via
chirp_devel
Sent: Sunday, December 4, 2022 12:13 PM
To: chirp-devel <chirp_devel at intrepid.danplanet.com>
Subject: Re: [chirp_devel] Call for help

> Can you define what you mean by "test"?  Do you want me to just read from
the radio?  Write say one memory location?  Can you be specific here so
there can be some testing consistency?

Sorry, that was dumb of me, thanks for pointing out the ambiguity.

What I mean by test is cover the things we can't really test for in the
automated tests. That *mostly* means read and write the radio over the
serial port. However, since we load the memory map slightly differently
after a clone than we do when loading from file, it's best to also test
editing a memory between download and upload, to make sure we got our types
set properly. That, and the settings (for radios that have them) can also be
problem areas. So, in summary, the following would probably be a good
baseline, and I think it's in line what what Jim and I have both been doing:

1. Download from the radio
2. Make a change to a memory
3a. If the driver has settings, load the settings tab, and
3b. Make some settings change
4. Upload to the radio
5. Confirm that the changes look right (and if not, see if it's more broken
than the py2 release)

Make sense?

--Dan
_______________________________________________
chirp_devel mailing list
chirp_devel at intrepid.danplanet.com
http://intrepid.danplanet.com/mailman/listinfo/chirp_devel
Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers