I have a new TD-H3 that allows me to enable 1.25m TX.
What does that mean? Is there a setting in the radio? That would surprise me, but...
I tried to chirp it to set up some local 1.25m repeaters, but could not because of the _txbands limitation. (It also allows setting TX on some bands that aren't ham bands in the US.) I would like to chirp those 1.25m repeaters into the unit, which would require me to update chirp.
Why not just put the radio into unrestricted mode where there are basically no limits?
It seems obvious to this naive newcomer that the approach is to dump images modifying each of the settings not currently present to reverse them, and add them to the MEM_FORMAT, then add them to settings handling, after which I should be able to update _txbands to include frequency ranges that have been enabled on the particular HT being chirped, including setting those TX modes in settings.
Maybe this is the answer to the question above -- there's some setting in the radio that lets you enable this band? Is it in the radio itself or the software?
If there are settings, then sure, you can decode them so they're accessible in chirp.
However, I'm confused about how to deal with at least two things.
- While the menu on the HT has setting 42. Version "AM_240316 I don't see anything like that in the image I downloaded, so it's not clear to me whether I can make the new settings conditional on some new-enough firmware version.
If not then probably not, yeah. _Is_ this new behavior from a new firmware version? If so, do you have a link to a changelog or something that explains it?
Do we get the firmware version during the clone exchange perhaps? If so, we can memorize it at that point for later.
- There's only one MEM_FORMAT for the radios supported in tdh8.py and I have no idea whether the formats have diverged between radios because I have only a TD-H3 to play with.
There are two, one for the H3 and one for the H8. No structural changes due to firmware versions have happened that I know of.
I have one of each that I can test with, but I'm not super familiar with them. It's very important that we not break older firmware versions if this really is new, as you indicate, so thanks for already thinking in that mode.
--Dan