Send chirp_devel mailing list submissions to
chirp_devel@intrepid.danplanet.com
To subscribe or unsubscribe via the World Wide Web, visit
http://intrepid.danplanet.com/mailman/listinfo/chirp_devel
or, via email, send a message with subject or body 'help' to
chirp_devel-request@intrepid.danplanet.com
You can reach the person managing the list at
chirp_devel-owner@intrepid.danplanet.com
When replying, please edit your Subject line so it is more specific
than "Re: Contents of chirp_devel digest..."
Today's Topics:
1. Re: Yaesu FT2D and "preset channels" question (NNN Wx)
------------------------------------------------------------ ----------
Message: 1
Date: Sat, 7 Oct 2017 15:39:45 -0600
From: NNN Wx <nthreewx@gmail.com>
Subject: Re: [chirp_devel] Yaesu FT2D and "preset channels" question
To: Robert Terzi <rct@r-t.org>
Cc: chirp_devel@intrepid.danplanet.com
Message-ID: <E96002F0-8EB4-4D23-AE4F-CAE13E0F16CC@gmail.com >
Content-Type: text/plain; charset="utf-8"
I?ve heard nothing else about this problem from the list, so I really hope you?ve something to help in your notes!
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.
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.)
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.
Declan Rieb WD5EQY
wd5eqy@arrl.net
> On Oct 6, 2017, at 15:16, Robert Terzi <rct@r-t.org> wrote:
>
> [Was just cleaning out some old list mail and came across this.]
>
> 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.
>
> 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.
>
> (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.)
>
> ?Rob
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_devel/ attachments/20171007/18738b35/ attachment-0001.html
------------------------------
_______________________________________________
chirp_devel mailing list
chirp_devel@intrepid.danplanet.com
http://intrepid.danplanet.com/mailman/listinfo/chirp_devel
End of chirp_devel Digest, Vol 78, Issue 3
******************************************