[chirp_devel] other duplex choices?
So some yaesu radios in addition to various shift/duplex options like off/+/-, have "auto repeater shift" or ARS. I have added auto as a choice to my duplexes and set it as valid_duplexes: DUPLEX = ["", "-", "+", "split", "Auto"] ... rf.valid_duplexes = list(self.DUPLEX)
But it's failing like:
Exception running RadioJob: `Auto' is not in valid list: ['', '+', '-', 'split', 'off'] -- Exception: -- Traceback (most recent call last): File "/home/jens/build/chirp.hg/chirpui/common.py", line 111, in _execute result = func(*self.args, **self.kwargs) File "/home/jens/build/chirp.hg/chirp/ft90.py", line 244, in get_memory mem.duplex = self.DUPLEX[4] File "/home/jens/build/chirp.hg/chirp/chirp_common.py", line 329, in __setattr__ self._valid_map[name])) ValueError: `Auto' is not in valid list: ['', '+', '-', 'split', 'off']
Any idea what I'm missing?
So some yaesu radios in addition to various shift/duplex options like off/+/-, have "auto repeater shift" or ARS. I have added auto as a choice to my duplexes and set it as valid_duplexes: DUPLEX = ["", "-", "+", "split", "Auto"] ... rf.valid_duplexes = list(self.DUPLEX)
Yeah, we don't support that right now. We could, but it's kindof annoying because not everything would and, I dunno, it seems like a mode and not a duplex to me. If it's really stored in the channel instead of a duplex, then I guess you'll have to calculate what the default is for that band and region (there's code in chirp already to do that) and synthesize it for now.
ok, so that brings me to another question, how do we expose custom fields in the UI?
________________________________ From: Dan Smith dsmith@danplanet.com To: chirp_devel@intrepid.danplanet.com Sent: Saturday, August 24, 2013 2:48 PM Subject: Re: [chirp_devel] other duplex choices?
So some yaesu radios in addition to various shift/duplex options like off/+/-, have "auto repeater shift" or ARS. I have added auto as a choice to my duplexes and set it as valid_duplexes: DUPLEX = ["", "-", "+", "split", "Auto"] ... rf.valid_duplexes = list(self.DUPLEX)
Yeah, we don't support that right now. We could, but it's kindof annoying because not everything would and, I dunno, it seems like a mode and not a duplex to me. If it's really stored in the channel instead of a duplex, then I guess you'll have to calculate what the default is for that band and region (there's code in chirp already to do that) and synthesize it for now.
ok, so that brings me to another question, how do we expose custom fields in the UI?
You mean miscellaneous per-memory controls? Create a list of setting objects in memory.extra. See the UV-5R driver for a pretty extensive example.
participants (2)
-
Dan Smith -
Jens J.