<html><body><div style="color:#000; background-color:#fff; font-family:tahoma, new york, times, serif;font-size:12pt"><div><span>Yeah, belay this for another round. </span></div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: tahoma, 'new york', times, serif; background-color: transparent; font-style: normal; ">I'm currently working on mapping out the special channels (vfos, calls, u/l scan limits) as well as the some of the global settings.</div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: tahoma, 'new york', times, serif; background-color: transparent; font-style: normal; ">I'm not sure exactly how those special channels are dealt with, as I didnt see a sample implementation in template, just an actual implementation like ft-857, etc.</div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: tahoma, 'new york', times, serif; background-color: transparent; font-style: normal; "><br></div><div style="color:
rgb(0, 0, 0); font-size: 16px; font-family: tahoma, 'new york', times, serif; background-color: transparent; font-style: normal; ">How can I solve the issues with importing from floats that dont match (i.e., 6.25)? do I need to bracket them into my list at get_memory or set_memory time?</div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: tahoma, 'new york', times, serif; background-color: transparent; font-style: normal; "><br></div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: tahoma, 'new york', times, serif; background-color: transparent; font-style: normal; ">On the ToneSql type, how do I preserve a channel setting for Bell or Auto, if chirp doesnt support it. Do I have to be destructive and box all channels into one of the supported types? It's totally possible to have set Bell or Auto in memory on the radio. What happens when I import this now? How should I deal with this, if I cant tell chirp what are
possible/legal values for my radio?</div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: tahoma, 'new york', times, serif; background-color: transparent; font-style: normal; "><br></div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: tahoma, 'new york', times, serif; background-color: transparent; font-style: normal; ">I commented out the ARS code, but now if I can do custom fields (i'll see how it's done with uv-5r) then I may be able to make this a bool field, and deal with the logic of ignoring/setting duplex field in get/set memory members.</div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: tahoma, 'new york', times, serif; background-color: transparent; font-style: normal; "><br></div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: tahoma, 'new york', times, serif; background-color: transparent; font-style: normal; ">I'll check the DCS values, probably differs from chirp_common list, but
it has a field for it in radio memory. I'll do what you suggest, i.e., import chirp_common tones/dcs tones list, and remove unsupported tones. </div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: tahoma, 'new york', times, serif; background-color: transparent; font-style: normal; ">I understand it is semantics and style, but since these allowed tone values for this particular radio will NEVER change, I don't want to be dependent upon chirp_common tones never changing. It would be a long shot that they ever do change, but if they do, it would be more difficult to determine which tones are now supported/unsupported, since the "source of truth" gets altered. Anyhow, as I do doubt they will change upstream, I'll go with the subtractive pattern you suggest.</div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: tahoma, 'new york', times, serif; background-color: transparent; font-style: normal; "><br></div><div><br></div>
<div style="font-family: tahoma, 'new york', times, serif; font-size: 12pt; "> <div style="font-family: 'times new roman', 'new york', times, serif; font-size: 12pt; "> <div dir="ltr"> <hr size="1"> <font size="2" face="Arial"> <b><span style="font-weight:bold;">From:</span></b> Dan Smith <dsmith@danplanet.com><br> <b><span style="font-weight: bold;">To:</span></b> chirp_devel@intrepid.danplanet.com <br> <b><span style="font-weight: bold;">Sent:</span></b> Sunday, August 25, 2013 3:19 PM<br> <b><span style="font-weight: bold;">Subject:</span></b> Re: [chirp_devel] [FT-90] add initial support for FT-90R. #1087<br> </font> </div> <div class="y_msg_container"><br>
> Initial support for Yaesu FT-90R. Probably a bit buggy. #1087<br><br>Do you want this to go into the tree, or are you just floating it for<br>comments?<br><br>> +# Copyright 2011 Dan Smith <<a ymailto="mailto:dsmith@danplanet.com" href="mailto:dsmith@danplanet.com">dsmith@danplanet.com</a>><br><br>Be sure to add your copyright here.<br><br>> + STEPS = [5, 10, 12.5, 15, 20, 25, 50]<br><br>Steps are floats, so these will cause issues during import from<br>something else, I think.<br><br>> + MODES = ["AM", "FM", "Auto"]<br>> + TMODES = ["", "Tone", "TSQL", "Bell", "DTCS"]<br><br>Auto and Bell aren't allowed, so memories that resolve to these are<br>going to break, right?<br><br>> + TONES = [ 67.0, 69.3, 71.9, 74.4, 77.0, 79.7, 82.5,<br>> + 85.4, 88.5, 91.5, 94.8, 97.4, 100.0, 103.5,<br>> + 107.2, 110.9,
114.8, 118.8, 123.0, 127.3,<br>> + 131.8, 136.5, 141.3, 146.2, 151.4, 156.7,<br>> + 159.8, 162.2, 167.9, 173.8, 179.9, 183.5,<br>> + 186.2, 189.9, 192.8, 196.6, 199.5, 203.5, <br>> + 206.5, 210.7, 218.1, 225.7, 229.1, 233.6,<br>> + 241.8, 250.3, 254.1,<br>> + ] <br><br>Is this list different than the main one in chirp_common? While it's a<br>little messy, I think it would be better to stick with the convention<br>of copying the main list and adding/removing tones to get to the<br>supported list. At the very least, it makes it easyier to come back<br>and figure out what the deltas are. <br> <br>> + POWER_LEVELS = ["Hi","Mid1","Mid2","Low"]<br><br>Need spaces after the commas<br><br>> +
#DUPLEX = ["", "-", "+", "split", "Auto"]<br>> + DUPLEX = ["", "-", "+", "split"]<br><br>I like to avoid commented-out code whenever possible. Perhaps just a<br>comment above that says "Duplex index 4 is auto mode". Will memories<br>with auto set create an IndexError trying to look their value up in<br>this list?<br><br>> + def get_memory(self, number):<br>> + _mem = self._memobj.memory[number-1]<br>> +<br>> + mem = chirp_common.Memory()<br>> + mem.number = number<br>> + mem.freq = _mem.rxfreq * 10 <br>> + mem.offset = _mem.txfreqoffset * 10<br>> + if not _mem.tmode < len(self.TMODES):<br>> + _mem.tmode = 0<br>> + mem.tmode =
self.TMODES[_mem.tmode]<br>> + mem.rtone = self.TONES[_mem.tone]<br>> + mem.mode = self.MODES[_mem.mode]<br>> +<br>> + '''<br>> + # ars mode note yet working...<br>> + # ARS mode:<br>> + if _mem.ars and _mem.shift == 0:<br>> + mem.duplex = self.DUPLEX[4] <br><br>This will fail, right?<br><br>> + else:<br>> + mem.duplex = self.DUPLEX[_mem.shift]<br>> + '''<br>> + mem.duplex = self.DUPLEX[_mem.shift]<br>> + mem.power = self.POWER_LEVELS[_mem.power]<br>> + # radio has a known bug with 5khz step and squelch<br>> +
if _mem.step == 0:<br>> + _mem.step = 2<br>> + mem.tuning_step = self.STEPS[_mem.step]<br>> + mem.skip = _mem.skip and "S" or ""<br>> + <a target="_blank" href="http://mem.name/">mem.name</a> = <a target="_blank" href="http://_mem.name/">_mem.name</a><br>> + return mem<br><br>I don't see the DCS code being decoded anywhere. IIRC, that was the<br>thing I could never figure out.<br><br>Thanks!<br><br>-- <br>Dan Smith<br><a target="_blank" href="http://www.danplanet.com/">www.danplanet.com</a><br>KK7DS<br><br>_______________________________________________<br>chirp_devel mailing list<br><a ymailto="mailto:chirp_devel@intrepid.danplanet.com" href="mailto:chirp_devel@intrepid.danplanet.com">chirp_devel@intrepid.danplanet.com</a><br><a
href="http://intrepid.danplanet.com/mailman/listinfo/chirp_devel" target="_blank">http://intrepid.danplanet.com/mailman/listinfo/chirp_devel</a><br>Developer docs: <a href="http://chirp.danplanet.com/projects/chirp/wiki/Developers" target="_blank">http://chirp.danplanet.com/projects/chirp/wiki/Developers</a><br><br></div> </div> </div> </div></body></html>