Thank you for doing this Steve. I think it is a big improvement. The only issue to me is that MacDoppler neither complained at an old-style value nor automatically fixed it. (It could have told it was wrong with a TS-2000. I don't know about other radios--perhaps the best it could do is the first time 2.3 was run notice that there were any tones on the mode page and put up a warning dialog box).

73,

Burns

On Thu, Jul 18, 2019 at 2:06 PM Steve Nordahl via AMSAT-BB < amsat-bb@amsat.org> wrote:

Burns, I posted this same response on FB. I asked for this change some time ago and Don made the change in Version 2.30 Beta 4.Here's what I asked for initially..

Don,

This topic has come up by other users asking this question so I'm posing it to you.. Currently users have to refer to a tone list to select the the correct TX tone for editing satellites. In the case of SO-50 for example.. Why can't we manually enter the working or wake-up tone of 67.0 (1 in this case) or 74.4 (3 in this case) rather than cross check a list to find out what tone number 1 or 3 means?

Don's response.. "Version 2.30 Beta 4 requires the actual tone and ctcss values to be stored in mode.dat (e.g. 67.0) and the Modes editor - zero or blank still signifies no tone."

Steve Nordahl, NS3L

---

Sent via AMSAT-BB@amsat.org. AMSAT-NA makes this open forum available to all interested persons worldwide without requiring membership. Opinions expressed are solely those of the author, and do not reflect the official views of AMSAT-NA. Not an AMSAT-NA member? Join now to support the amateur satellite program! Subscription settings: https://www.amsat.org/mailman/listinfo/amsat-bb