[chirp_devel] [PATCH 3 of 5] [ft4] compander, 6.25 suppress, freq range fix [#4787]
Dan Clemmensen
Thu Feb 28 07:53:56 PST 2019
There are only the two lists so far and there may never be another, so I
suppose we could. However, it's not the same
for all radio variants. I wanted to make this explicit, so I built the
"legal" list on a radio-by-radio basis to make it clear
that each new variant will need to decide on its own list. the It's a
stylistic choice, but I thought the "remove" construct
was better as a self-documenting way to make it clear that the legal list
must be a subset of the coded list.
On Thu, Feb 28, 2019 at 6:52 AM Dan Smith via chirp_devel <
chirp_devel at intrepid.danplanet.com> wrote:
> > @@ -1023,7 +1018,22 @@
> > Pkeys = 2 # number of programmable keys on the FT-4
> > namelen = 6 # length of the mem name display on the FT-4
> front-panel
> > id_str = b'IFT-35R\x00\x00V100\x00\x00'
> > -
> > + # names for the setmode function for the programmable keys. Mode
> zero means
> > + # that the key is programmed for a memory not a setmode.
> > + SETMODES = [
> > + "mem", "apo", "ar bep", "ar int", "beclo", #00-04
> > + "beep", "bell", "cw id", "cw wrt", "dc vlt", #05-09
> > + "dcs cod", "dt dly", "dt set", "dtc spd", "edg.bep", #10-14
> > + "lamp", "led.bsy", "led.tx", "lock", "m/t-cl", #15-19
> > + "mem.del", "mem.tag", "pag.abk", "pag.cdr", "pag.cdt", #20-24
> > + "pri.rvt", "pswd", "pswdwt", "rf sql", "rpt.ars", #25-29
> > + "rpt.frq", "rpt.sft", "rxsave", "scn.lmp", "scn.rsm", #30-34
> > + "skip", "sql.typ", "step", "tn frq", "tot", #35-39
> > + "tx pwr", "tx save", "vfo.spl", "vox", "wfm.rcv", #40-44
> > + "w/n.dev", "wx.alert" #45-46
> > + ]
> > + legal_steps = list(STEP_CODE)
> > + legal_steps.remove(6.25) #should not remove if euro version
> >
> > # don't register the FT-65 in the production version until it is tested
> > # @directory.register
> > @@ -1038,7 +1048,6 @@
> > # VHF, RX (136000000, 174000000)
> > # UHF, RX (400000000, 480000000)
> > ]
> > - valid_bands = [(108000000, 520000000), (700000000, 999990000)]
> > _valid_chars = chirp_common.CHARSET_ASCII
> > numblocks = 0x215 # number of 16-byte blocks in the radio
> > _memsize = 16 * numblocks # used by CHIRP file loader to guess
> radio type
> > @@ -1046,4 +1055,20 @@
> > Pkeys = 4 # number of programmable keys on the FT-65
> > namelen = 8 # length of the mem name display on the FT-65 front
> panel
> > id_str=b'IH-420\x00\x00\x00V100\x00\x00'
> > + # names for the setmode function for the programmable keys. Mode
> zero means
> > + # that the key is programmed for a memory not a setmode.
> > + SETMODES = [
> > + "mem", "apo", "arts", "battsave", "b-ch.l/o", #
> 00-04
> > + "beep", "bell", "compander", "ctcss", "cw id", #
> 05-09
> > + "dc volt", "dcs code", "dtmf set", "dtmf wrt", "edg bep", #
> 10-14
> > + "key lock", "lamp", "ledbsy", "mem del", "mon/t-cl", #
> 15-19
> > + "name tag", "pager", "password", "pri.rvt", "repeater", #
> 20-24
> > + "resume", "rf.sql", "scn.lamp", "skip", "sql type", #
> 25-29
> > + "step", "tot", "tx pwr", "tx save", "vfo.spl", #
> 30-34
> > + "vox", "wfm.rcv", "wide/nar", "wx alert", "scramble" #
> 35-39
> > + ]
>
> This list is the same as the one above, right? Can we define that in one
> place and use it in both?
>
> --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/20190228/92ccf965/attachment-0001.html
More information about the chirp_devel
mailing list