January 2020 - Developers - lists.chirpmyradio.com

[chirp_devel] Add new radio Icom IC-E90/T90/T90A
by Jaroslav Skarvada 21 May '20

21 May '20

Hi, attached is the patch adding support for Icom IC-E90/T90/T90A radios and memory map for this radio. The radio is a bit tricky - it has multiple special channels and TV channels (well analog TV is a bit off-topic today, but I wanted to support all features of this radio). I added TV channels as a subdevice, because I have no better idea how to do it. Also I had to modify the icf driver a bit, because it seems the clone status doesn't work with this radio. Maybe I am just missing something here, but I wasn't able to persuade my radio to behave this way. The proposed icf driver change should be harmless for other ICOM radios, because it's adding new option and the memory size calculation should be backward compatible. One test from the testsuite is failing: ./run_tests.py -d 'Icom_IC-E90' Icom IC-E90 Detect PASSED: All tests Icom IC-E90 Settings PASSED: All tests Icom IC-E90 Clone PASSED: All tests Icom IC-E90 Edges FAILED: Field `name' is ` ', expected `' Icom IC-E90 BruteForce PASSED: All tests Icom IC-E90 CopyAll PASSED: All tests Icom IC-E90 Banks PASSED: All tests Icom IC-E90 TV Detect PASSED: All tests Icom IC-E90 TV Settings PASSED: All tests Icom IC-E90 TV Clone PASSED: All tests Icom IC-E90 TV Edges FAILED: Field `name' is ` ', expected `' Icom IC-E90 TV BruteForce PASSED: All tests Icom IC-E90 TV CopyAll PASSED: All tests Icom IC-E90 TV Banks SKIPPED: Banks not supported ---------------------------------------------------------------------- Results: TOTAL : 14 FAILED : 2 SKIPPED: 1 PASSED : 11 CRASHED: 0 But by inspection of the logs (see bellow) I am not sure whether there is a bug in my driver or in the test suite: ---- Begin test Edges ---- Field `name' is ` ', expected `' ### Wanted: vfo:0 tmode: name: <SPACE> power:None duplex: skip: tuning_step:5.0 number:0 comment: immutable:[] rx_dtcs:23 dtcs_polarity:NN extd_number: mode:AM dtcs:23 offset:600000 freq:1495000 cross_mode:Tone->Tone ctone:88.5 empty:False rtone:88.5 ### Got: vfo:0 tmode: name: <SPACE> power:None duplex: skip: tuning_step:5.0 number:0 comment: immutable:[] rx_dtcs:23 dtcs_polarity:NN extd_number: mode:AM dtcs:23 offset:600000 freq:1495000 cross_mode:Tone->Tone ctone:88.5 empty:False rtone:88.5 ---- End test Edges ---- I added <SPACE> where there was ' ' in the log for the problem to be clearly visible. So it seems the "wanted" is the same as the "got". It's the same for the 'TV' subdevice thanks & regards Jaroslav

3 17

[chirp_devel] Patch for #7119 BF-888 "Refused to enter programming mode."
by Nicklas Lindgren 02 Mar '20

02 Mar '20

Hi, Sorry if this becomes a duplicate message. I was at first but subscribed to the list with the correct email, and my first message didn't come through. About the patch: This change fixes the problem with my two radios, but i can't be sure that its the same problem that the original reporter of the bug has. I'm a bit concerned about raising the timeout globally. I can't rule out that it has any other consequences, but at the same time i don't imagine anything depends on a particular serial read timeout. -- Nicklas Lindgren 59D8 27AD 2632 F349 9B20 F5CB D363 3177 0A12 1B95

4 7

[chirp_devel] [Yaesu FT-25] has been added to FT-4 driver.
by Bernhard Hailer 01 Feb '20

01 Feb '20

# HG changeset patch # Parent 53cd045bbf8253d32b43a528b245caff243e4c02 [Yaesu FT-25] has been added to FT-4 driver. Thanks to Dan Clemmensen for all his work to prepare for it! A test image is attached. A few issues with the FT-4 driver were discovered while the work for the FT-25 was carried out; see #7601, #7603, #7605. Additional patches will be provided. 73 Bernhard AE6YN Fixes: #7543 diff --git a/chirp/drivers/ft4.py b/chirp/drivers/ft4.py --- a/chirp/drivers/ft4.py +++ b/chirp/drivers/ft4.py @@ -2,6 +2,7 @@ # Derives loosely from two sources released under GPLv2: # ./template.py, Copyright 2012 Dan Smith <dsmith(a)danplanet.com> # ./ft60.py, Copyright 2011 Dan Smith <dsmith(a)danplanet.com> +# Edited 2020 Bernhard Hailer <ham73tux(a)gmail.com> # # This program is free software: you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by @@ -261,7 +262,8 @@ msg = "Bad echo. Sent:" + util.hexprint(cmd) + ", " msg += "Received:" + util.hexprint(echo) LOG.debug(msg) - raise errors.RadioError("Incorrect echo on serial port. Bad cable?") + raise errors.RadioError( + "Incorrect echo on serial port. Radio off? Bad cable?") if response_len is None: return variable_len_resp(pipe) if response_len > 0: @@ -475,7 +477,7 @@ SKIPS = ["", "S"] BASETYPE_FT4 = ["FT-4XR", "FT-4XE"] -BASETYPE_FT65 = ["FT-65R"] +BASETYPE_FT65 = ["FT-65R", "FT-25R"] POWER_LEVELS = [chirp_common.PowerLevel("Low", watts=0.5), chirp_common.PowerLevel("Mid", watts=2.5), chirp_common.PowerLevel("High", watts=5.0)] @@ -569,6 +571,12 @@ BAND_ASSIGNMENTS = [2, 1, 0, 1, 2, 0, 1, 2] # bands for the vfos and homes FT65_PROGS = ("prog", ["P1", "P2", "P3", "P4"]) FT65_SPECIALS = list(SPECIALS) # a shallow copy works here +FT25_SPECIALS = [ + ("pms", PMSNAMES), + ("vfo", ["VFO A UHF", "VFO A VHF", "VFO B FM"]), + ("home", ["HOME FM", "HOME VHF"]), + ("prog", ["P1", "P2"]) + ] FT65_SPECIALS[-1] = FT65_PROGS # replace the last entry (P key names) @@ -669,8 +677,6 @@ rf.has_dtcs_polarity = False # REV TN reverses the tone, not the dcs rf.has_cross = True rf.has_settings = True - rf.valid_tuning_steps = self.legal_steps - return rf def get_bank_model(self): @@ -1027,31 +1033,50 @@ mem = chirp_common.Memory() _mem, ndx, num, regtype, sname = self.slotloc(memref) mem.number = num - mem.freq = int(_mem.freq) * 10 - mem.offset = int(_mem.offset) * self.freq_offset_scale - mem.duplex = DUPLEX[_mem.duplex] - self.decode_sql(mem, _mem) - mem.power = POWER_LEVELS[_mem.tx_pwr] - mem.mode = ["FM", "NFM"][_mem.tx_width] - mem.tuning_step = STEP_CODE[_mem.step] - + """ + First, we need to know whether a channel is enabled, + then we can process any channel parameters. + It was found (at least on an FT-25) that channels might be + uninitialized and memory is just completely filled with 0xFF. + """ if regtype == "pms": mem.extd_number = sname + if regtype in ["memory", "pms"]: ndx = num - 1 mem.name = clean_name(self._memobj.names[ndx].chrs) mem.empty = not retrieve_bit(self._memobj.enable, ndx) mem.skip = SKIPS[retrieve_bit(self._memobj.scan, ndx)] - txfreq = int(self._memobj.txfreqs[ndx].freq) * 10 - if (txfreq != 0) and (txfreq != mem.freq): - mem.duplex = "split" - mem.offset = txfreq else: mem.empty = False mem.extd_number = sname mem.immutable = ["number", "extd_number", "name", "skip"] + """ + So, now if channel is not empty, we can do the evaluation of + all parameters. Otherwise we set them to defaults. + """ + if mem.empty: + mem.freq = 0 + mem.offset = 0 + mem.duplex = "off" + mem.power = POWER_LEVELS[2] # "High" + mem.mode = "FM" + mem.tuning_step = 0 + else: + mem.freq = int(_mem.freq) * 10 + txfreq = int(self._memobj.txfreqs[ndx].freq) * 10 + if (txfreq != 0) and (txfreq != mem.freq): + mem.duplex = "split" + mem.offset = txfreq + else: + mem.offset = int(_mem.offset) * self.freq_offset_scale + mem.duplex = DUPLEX[_mem.duplex] + self.decode_sql(mem, _mem) + mem.power = POWER_LEVELS[mem.tx_pwr] + mem.mode = ["FM", "NFM"][_mem.tx_width] + mem.tuning_step = STEP_CODE[_mem.step] return mem def enforce_band(self, memloc, freq, mem_num, sname): @@ -1117,7 +1142,7 @@ # UHF, RX (400000000, 480000000) ] _valid_chars = chirp_common.CHARSET_ASCII - numblocks = 0x215 # number of 16-byte blocks in the radio + numblocks = 0x215 # number of 16-byte blocks in the radio _memsize = 16 * numblocks # used by CHIRP file loader to guess radio type MAX_MEM_SLOT = 200 Pkeys = 2 # number of programmable keys on the FT-4 @@ -1180,3 +1205,40 @@ "step", "tot", "tx pwr", "tx save", "vfo.spl", # 30-34 "vox", "wfm.rcv", "wide/nar", "wx alert", "scramble" # 35-39 ] + + +(a)directory.register +class YaesuFT25Radio(YaesuSC35GenericRadio): + MODEL = "FT-25R" + _basetype = BASETYPE_FT65 + valid_bands = [ + (65000000, 108000000), # broadcast FM, receive only + (144000000, 148000000), # VHF, US version, TX and RX + # VHF, RX (136000000, 174000000) + ] + _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 + MAX_MEM_SLOT = 200 + 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'IFT-25R\x00\x00V100\x00\x00' + freq_offset_scale = 50000 + legal_steps = US_LEGAL_STEPS + # we need a deep copy here because we are adding deeper than the top level. + class_group_descs = copy.deepcopy(YaesuSC35GenericRadio.group_descriptions) + add_paramdesc( + class_group_descs, "misc", ("compander", "Compander", ["OFF", "ON"])) + class_specials = FT25_SPECIALS + # 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 + ]

2 3

[chirp_devel] Integrate new radio into tox
by Bernhard Hailer 28 Jan '20

28 Jan '20

Hi all, question: I just added a radio (FT-25) to the ft4.py driver and provided a patch and an image. When I tried to add the next radio (FT-4V), I realized that tox never picked it up as one of the radios to test, and it also doesn't pick up the FT-25. What do I have to do to make tox accept a new radio to do its thing with it? Thanks and 73, Bernhard

2 1

[chirp_devel] [patch] show 8.33 tuning step in the UI
by Jaroslav Skarvada 28 Jan '20

28 Jan '20

Hi, this is an attempt to fix Bug #7073, thanks & regards Jaroslav

1 0

[chirp_devel] Issues
by Bernhard Hailer 27 Jan '20

27 Jan '20

Hi all, strolling through all the open issues, I found a lot of duplicates or already resolved tickets which are still marked "New". I'd like to volunteer a little of my spare time to do some clean-up. What's the policy here: not being the contributing partymyself to that particular issue, can I just: * go and set duplicates to "Rejected"? * mark issues as "Resolved" if nobody else did, but the feedback suggests that there is a solution? * go and make the header lines be more telling? * go and close nonsensical requests, such as for non-existing radios (such as issue #5)? I just don't want to step on anyone's toes and abuse my freshly earned privileges. 73 Bernhard AE6YN

3 8

[chirp_devel] Python 3 Build
by Rick DeWitt 27 Jan '20

27 Jan '20

Dan- Which version of Python 3 should I download to test modified drivers? I am having a terrible time installing pyobject and PyGTK to get the pi repository; multiple failures... -- Rick DeWitt AA0RD Sequim, Washington, USA 360-681-3494

2 1

[chirp_devel] Remote testing
by Bernhard Hailer 27 Jan '20

27 Jan '20

Hello fellow devs, for me as a developer with a Python Development Environment, it's simple to make a change and to test it right away - given, that I have a radio to test it with. Now, if I don't have that radio, but I do have contact to another person (without Python environment) willing to test a code change, is there a way to either make a build or to send the changed driver so that the test can be done remotely? The other way would be to ask for a loaner, obviously... Thanks! Bernhard

3 3

[chirp_devel] [Yaesu FT-4, FT-65, FT-25] Sometimes channel names are not displayed correctly
by Bernhard Hailer 25 Jan '20

25 Jan '20

# HG changeset patch # Parent 2e2a687a26517de7f015cb95976ec01d28153a68 [Yaesu FT-4, FT-65, FT-25] Sometimes channel names are not displayed correctly When user was programs radio manually and was adding a name shorter than 8 characters, the remaining characters were filled with garbage on the Chirp UI. The reason was that the radio pads remaining characters with 0x7F, but Chirp wants to see 0x20. 73 Bernhard AE6YN Fixes: #7601 diff --git a/chirp/drivers/ft4.py b/chirp/drivers/ft4.py --- a/chirp/drivers/ft4.py +++ b/chirp/drivers/ft4.py @@ -1029,6 +1029,8 @@ y = obj[x] if y == 0: break + if y == 0x7F: # when programmed from VFO + y = 0x20 name += chr(y) return name.rstrip()

1 0

[chirp_devel] [Yaesu FT-4, FT-65, FT-25] After CSV import, channels are always low power
by Bernhard Hailer 25 Jan '20

25 Jan '20

# HG changeset patch # Parent a23356ce262d9e262866f5be6b7513b11bc973e3 [Yaesu FT-4, FT-65, FT-25] After CSV import, channels are always low power When a CSV file was imported, then all imported channels were programmed with Low power. This has been fixed, it's now defaulting to High power. 73 Bernhard AE6YN Fixes: #7603 diff --git a/chirp/drivers/ft4.py b/chirp/drivers/ft4.py --- a/chirp/drivers/ft4.py +++ b/chirp/drivers/ft4.py @@ -479,9 +479,10 @@ BASETYPE_FT4 = ["FT-4XR", "FT-4XE"] BASETYPE_FT65 = ["FT-65R", "FT-25R"] -POWER_LEVELS = [chirp_common.PowerLevel("Low", watts=0.5), - chirp_common.PowerLevel("Mid", watts=2.5), - chirp_common.PowerLevel("High", watts=5.0)] +POWER_LEVELS = [ + chirp_common.PowerLevel("High", watts=5.0), # high must be first (0) + chirp_common.PowerLevel("Mid", watts=2.5), + chirp_common.PowerLevel("Low", watts=0.5)] # these steps encode to 0-9 on all radios, but encoding #2 is disallowed # on the US versions (FT-4XR) @@ -1076,7 +1077,7 @@ mem.freq = 0 mem.offset = 0 mem.duplex = "off" - mem.power = POWER_LEVELS[2] # "High" + mem.power = POWER_LEVELS[0] # "High" mem.mode = "FM" mem.tuning_step = 0 else: @@ -1092,7 +1093,7 @@ else: mem.duplex = DUPLEX[_mem.duplex] self.decode_sql(mem, _mem) - mem.power = POWER_LEVELS[mem.tx_pwr] + mem.power = POWER_LEVELS[2 - _mem.tx_pwr] mem.mode = ["FM", "NFM"][_mem.tx_width] mem.tuning_step = STEP_CODE[_mem.step] return mem @@ -1125,7 +1126,9 @@ _mem.freq = txfreq self.encode_sql(mem, _mem) if mem.power: - _mem.tx_pwr = POWER_LEVELS.index(mem.power) + _mem.tx_pwr = 2 - POWER_LEVELS.index(mem.power) + else: + _mem.tx_pwr = 0 # set to "High" if CHIRP canonical value is None _mem.tx_width = mem.mode == "NFM" _mem.step = STEP_CODE.index(mem.tuning_step)

1 0