<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">I’ve heard nothing else about this problem from the list, so I really hope you’ve something to help in your notes!<div class=""><br class=""><div class="">It’s clear that the UI for banks will need to be changed and/or augmented, and that part of the code is exceptionally opaque to me ATM.</div><div class=""><br class=""></div><div class="">Had you any ideas for even displaying the presets in the bank map? I’m thinking that the “channels” column on the left get augmented with, say “WX #0”… “WX #11”… “IVHF #0” … “SW #0” … probably only as needed, with the same types of bank checkboxes on the right across the screen. The FT2D radio allows the presets to be interspersed with the memory entries and not necessarily collocated at the end of the bank, so the chirp memory model for the FT2D is already more restrictive than the radio (not necessarily bad, but that’s how we got into this mess in the first place: something doable with the radio breaks chirp.)</div><div class=""><br class=""></div><div class="">Unfortunately for the Yaesu FT2D and maybe the FT1D, the actual preset frequencies don’t seem to reside in programmable memory and thus are not in the radio image that chirp uses. Right now it seems one would have to transcribe the information for “preset channels” from the printed documentation (and heaven help chirpers if the manufacturer changes those listings somehow. chirp would then have to support “stepping” versions of the radio.) I can imagine that “immutable memory” could hold these presets but I don’t see any radios with such extensive data in that poorly-described memory store. I could imagine that the flag bits would just cause chirp and the UI to point to entries in “immutable memory” instead of the memory channels. </div><div class=""><br class=""><div class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Declan Rieb WD5EQY<div class=""><a href="mailto:wd5eqy@arrl.net" class="">wd5eqy@arrl.net</a></div><div class=""><br class=""></div></div><br class="Apple-interchange-newline">
</div>
<br class=""><div><blockquote type="cite" class=""><div class="">On Oct 6, 2017, at 15:16, Robert Terzi <<a href="mailto:rct@r-t.org" class="">rct@r-t.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" class="">
<div text="#000000" bgcolor="#FFFFFF" class="">
<div class="moz-cite-prefix">[Was just cleaning out some old list
mail and came across this.]<br class="">
<br class="">
Thanks for working on this. FWIW, This feature of preset
channels goes back to at least the VX-8 and probably earlier. A
long, long time ago, The initial banks implementation in chirp
crashed when loading my VX-8's image because it contained preset
channels in one of the banks. <br class="">
<br class="">
I did a little reverse engineering and what you discovered looks
familiar. I have to see if I can find my notes. I eventually
gave up because I realized it would need a decent bit of work to
make chirp handle this especially in the UI for working on the
banks.<br class="">
<br class="">
(I was only scanning a handful of the Marine special/preset
changes, so I just added those to the 900 regular memories and
problem solved. I also eventually got Uniden scanner which pretty
much ended any scanning/monitoring I was doing with the VX-8.)<br class="">
<br class="">
—Rob<br class=""></div>
</div>
</div></blockquote><br class=""></div><br class=""></div></div></body></html>