<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">The new driver is almost-working to read (only) the Elecraft KX3 (and only basic memories.) But I’ve a few questions, and a problem:<div class=""><br class=""></div><div class="">Question: this radio’s memories contain data for TWO VFOs in each memory. I’m confident I can display the second VFO as mem.extra fields (frequency and mode) but is there any workaround way to get CHIRP to display both sets of fields in the normal display? Or possibly to preset the “display extras” menu item for the radio at startup?</div><div class=""><br class=""></div><div class="">Question: The driver's routine “get_features” shows up as being called 24 times(!) I’ve put a LOG.debug inside to show that valid_modes has the appropriate values. I expected it to be called once. It’s not a problem to me, but it is a surprise. Is this normal?</div><div class=""><br class=""></div><div class="">Problem: Having set ‘valid_modes’ to be appropriate for the radio, when I try to use one of the more esoteric ones (“AM-S/LSB”) CHIRP complains that the value is not in a (default? canonical?) list of modes… that list is NOT the one that is shown as having been set in “get_features”! It looks to be one set in chirp_common.py. What have I done wrong?</div><div class=""><br class=""></div><div class="">This problem is stumping me. </div><div class=""><br class="">The debug is from an execution aborted after the errors. Memories 8 and 10 have mode ‘AM-S/LSB’!</div><div class="">Source is in the new “elecraft” branch on darieb/darchirp hub. It won’t pass any of your standard tests, yet.</div><div class=""><br class=""></div><div class="">Thanks in advance.</div><div class=""><br class=""></div><div class=""></div></body></html>