[chirp_devel] receive-only channels?

[Dan Clemmensen]

Thanks, Dan. I will look at forcing the "off". (As a newbie Ham, it did not
even occur to me that "duplex==off" must meand "TX disabled".) I will run
the tests and see what happens, and patch the test code to make it work. I
think you will want to review any changes I make to the test code very
carefully before accepting them.

With respect to the MARS/CAP mod: It appears that this basically turns the
FT-4XR or FT-4 XE into the "Asian" version, which  in effect removes the
regulatory restriction and lets you use the radio's entire UHF and VHF
capability. A user could then select the "Asian" version if they mod the
radio.

That was going to be my next question. I propose to add two new radios:
FT-4XE and FT-4(Asian).
Since I don't understand the aliasing scheme, I intended to subclass the
FT-4 class and modify only the frequencies (and the step size), so the
number of lines of code is truly tiny. However, this will add these radio
names to the list of Yaesu radios as full top-level peers, not aliases or
something. Is this acceptable?

On Thu, Mar 14, 2019 at 1:16 PM Dan Smith via chirp_devel <
chirp_devel at intrepid.danplanet.com> wrote:

> > is there a way to indicate that a channel is receive-only? The FT-4 is
> tri-band for receive, but (clearly) does not transmit on the FM broadcast
> frequencies. In UHF and VHF, the receive-only frequency ranges are larger
> than the allowed TX frequencies of rthe European and US versions. My
> current code is schizophrenic: my valid_bands list has the full
> receive-only band for FM broadcast but only the TX-allowed bands for VHF
> and UHF
>
> If you support the duplex "off" that means no TX is allowed. I'd say that
> if they program something in the RX-only range, just ignore the duplex and
> offset they provide, and force the memory back to "off" duplex.
>
> > I would like to permit a user to program the RO frequencies but to know
> that TX will be disabled on that channel, and for the test suite to work
> with this.
>
> Similarly, they can choose "off" as the duplex if they want to tx-disable
> a channel. We could just make the tests not freak out if your radio
> supports "off" and we set a memory that comes back with that duplex.
>
> That said, I'm not really sure it's that important to communicate to the
> user that a frequency they have programmed will not be transmit-able by the
> radio, as this could also depend on whether or not they have done the
> MARS/CAP mod. With the latter mod, the frequencies at the edges of bands
> that are normally only supported for receive become valid for transmit.
> Conveying that "this whole band is receive-only" does not seem
> substantially different to me and thus my choice would be to just leave it
> as ambiguous.
>
> --Dan
> _______________________________________________
> chirp_devel mailing list
> chirp_devel at intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_devel
> Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_devel/attachments/20190314/9b95316b/attachment-0001.html