Johnny RT470Owner wrote:
Hi Guys,
i'll try to explain as good as possible.
So, the easy thing, TOT set in ChirpNext to 120s. After programming to the radio, menu 12 in the radio says "TOT 240s".
This is a bug. I made the mistake of programming the CHIRP setting to match the OEM software. Unfortunately, as you have pointed out, it doesn't match the radio's choices. I will look into this and fix it. Does my radio's menu 12 choices match yours?
OFF, 30S, 60S, 120S, 240S, 480S
Second is the missing option in ChirpNext to set the top button to eg. Light/TX Power/Search/Scan/... like the RT-470L has in it's programming software. Is it possible to implement?
Unless your radio has more then 51 menu options (0-50), there is no missing option in CHIRP-next. My RT-470 (firmware V1.15) doesn't have the menu options to support it. The RT-470L has 57 menu options (0-56) which includes support for the additional features.
Menu 24: PF3 LONG PRESS
Menu 25: TOP KEY
Unless your radio has the additional menu options and you can prove that they work, no, it won't be implemented because the radio doesn't support it.
Last thing is the TX power indicator on the display of the radio when pressing PTT. As shown in the pictures. Low and High is at the "right" level of the bar.
Medium is at the same level as Low. That should reach all 7 dots before the purple zone begins. Correct me if i'm wrong.
You are wrong. This is nothing that CHIRP has control over. CHIRP just sets the memory location that controls the TX power level and the radio's firmware controls the radio's TX power level and what it displays. Simply use menu 20 to set the PF2 key to TX POWER and then short press the PF2 key to cycle through the H/M/L power levels. The behavior will be exactly the same. CHIRP has nothing to do with it.
So I will be using this ticket to update the TOT setting choices to match the radio's menu 09 and ignoring the OEM software since it is obviously incorrect. If your radio does have the menu 24 and menu 25 that the RT-470L does, then you will have to open a separate issue. It will require separate testing and I don't want it to interfere with getting the TOT bug addressed.
Jim KC9HI