May 2012 - Developers - lists.chirpmyradio.com

[chirp_devel] [PATCH 0 of 2 ] Add cross dtcs support
by Marco Filippi IZ3GME 22 May '12

22 May '12

This patches add the long waited support for cross dtcs in UI and FT857 Still missing the related CSV format changes to have time to test everything before to make it Please people out there with an FT857, test tones carefully as in the big number of possible combinations it's not so difficult i've missed something

3 4

[chirp_devel] [PATCH 0 of 2 ] Fix for bug #181 (valid band check bounds)
by Marco Filippi IZ3GME 22 May '12

22 May '12

This two patches are the fix for bug #181 for tip and stable

2 3

[chirp_devel] [PATCH] [FT8x7] Support for attenuator flag
by Marco Filippi IZ3GME 22 May '12

22 May '12

# HG changeset patch # User Marco Filippi <iz3gme.marco(a)gmail.com> # Date 1337702261 -7200 # Node ID 6584d54fd0ba7b63436787f6e31ecdc3e36d4c01 # Parent 03593b9e97e26c5ddd0b577d29c6492e282551a0 [FT8x7] Support for attenuator flag Demonstration for #165 diff -r 03593b9e97e2 -r 6584d54fd0ba chirp/ft817.py --- a/chirp/ft817.py lun mag 21 14:38:53 2012 -0600 +++ b/chirp/ft817.py mar mag 22 17:57:41 2012 +0200 @@ -519,6 +519,11 @@ RadioSettingValueBoolean(bool(_mem.ipo))) ipo.set_doc("Bypass preamp") mem.extra.append(ipo) + + att = RadioSetting("ATT", "att", + RadioSettingValueBoolean(bool(_mem.att))) + att.set_doc("10dB front end attenuator") + mem.extra.append(att) return mem @@ -554,8 +559,6 @@ i += 1 _mem.tx_freq_range = i _mem.skip = mem.skip == "S" - _mem.ipo = 0 # not supported in chirp - _mem.att = 0 # not supported in chirp self._set_tmode(mem, _mem) try: _mem.ssb_step = self.STEPSSSB.index(mem.tuning_step)

2 1

[chirp_devel] [PATCH] tmd700: allow 8-char names. Fixes #176
by Tom Hayward 21 May '12

21 May '12

# HG changeset patch # User Tom Hayward <tom(a)tomh.us> # Date 1337632733 21600 # Node ID 03593b9e97e26c5ddd0b577d29c6492e282551a0 # Parent 6ec24fe428341a6315d59f5151671cca209d9476 tmd700: allow 8-char names. Fixes #176 diff -r 6ec24fe42834 -r 03593b9e97e2 chirp/kenwood_live.py --- a/chirp/kenwood_live.py Mon May 21 13:10:31 2012 -0700 +++ b/chirp/kenwood_live.py Mon May 21 14:38:53 2012 -0600 @@ -493,7 +493,7 @@ rf.valid_modes = ["FM"] rf.valid_tmodes = ["", "Tone", "TSQL", "DTCS"] rf.valid_characters = chirp_common.CHARSET_ALPHANUMERIC - rf.valid_name_length = 7 + rf.valid_name_length = 8 rf.memory_bounds = (1, self._upper) return rf

1 0

[chirp_devel] VX2r stuff
by Andrew Errington 21 May '12

21 May '12

Hi everyone, So far I have these fields decoding successfully: # mode # duplex # freq # power # tmode # name # offset I'm a little worried because when I change a single property of a single memory I get a large number of changes in the memory file. For example, if I change only one channel from high power to low power I get about 37 bytes affected. I expected to see only two or three (the byte that records the power level, and the checksum). 'tune_step' might be working, but I'm not sure, and I need to work on 'tone' and 'dcs'. I think I should have started with the VX3 code instead of VX7, but I just copy stuff from VX3 anyway. I am focusing on decoding the memory image. I haven't done anything to the code that writes a modified memory image. Finally, I seem to have a problem where occasionally I get or lose a null byte at the beginning of the file, which of course messes up the byte count. I think I should get "\x00AHN015" but sometimes I just get "AHN015". That's all for now. I guess there won't be a patch as the VX2r is a new program file. I'll send the whole thing when I'm done, or I can send the current horribly broken mess to anyone who wants to look at it. 73, Andrew ZL3AME

3 3

[chirp_devel] New user here - TS-2000 support
by Tom Wilson 14 May '12

14 May '12

Hi, all. I recently discovered Chirp, and I am hoping to be able to customize it to work with my Kenwood TS-2000. After writing a programmer for the TS-2000 in C#, I am starting to love Kenwood's communication protocol. There's no "memory dump" programming method here; the radio actually validates input and uses an actual command/response system for programming the machine. The nice part is that you can program just what you need: setting one menu change or one memory slot is a cinch. On my Yaesus, it was all or nothing... on this rig, changing the PL tone of one channel without affecting anything else is simple. So here's my situation: I am an experienced programmer. You talk to me about technical stuff and I follow right along. I've already written a programmer for the TS2K, even though it doesn't have much of a UI. However, I don't know Python - at all. I do know c and its descendants (C++, C#, Java, etc), VB (both VBA/VBScript and .Net), and enough php to get by... but I've never set up a Python dev environment. So is there a site where I can get the whirlwind tour on setting up a Windows box to use Python? Also, which source control tool will I need for downloading from the repository? Thanks for your help -Tom -- Tom Wilson wilsontp(a)gmail.com (619)940-6311 KI6ABZ

3 9

[chirp_devel] [PATCH 0 of 1 ] 857 cross tones fix
by Marco Filippi IZ3GME 14 May '12

14 May '12

Waiting for the cross dtcs I fixed the cross tones usage now that I fully understand ctone and rtone fields thanks to Dan's infos http://chirp.danplanet.com/projects/chirp/wiki/DevelopersToneModes I guess cross dtcs but I'll test it only after having implemented it

1 1

[chirp_devel] Adding a debian directory
by David Griffith 13 May '12

13 May '12

Is there any reason why there isn't a debian directory in the codebase? -- David Griffith dave(a)661.org

2 1

[chirp_devel] VX-7r: power levels for 1.25m band
by David Griffith 10 May '12

10 May '12

The Yaesu VX-7r supports L1 and L2 power settings for the 1.25m, but for some reason Chirp will not accept L2 for that band. Looking at the code in chirp/vx7.py I see where the check is made and L2 should be accepted. I cannot figure out why this check refuses to accept L2. The workaround is to manually reset the power level to L2 and re-save. Has anyone else tried to fix this? Slightly related to this problem, one can modify the VX-7r to boost the transmit power for the 1.25m band. This is done by entering the factory setup mode. Looking again at chirp/vx7.py, I see statements that look like this: chirp_common.PowerLevel("L2", watts=0.30) What does that "watts=0.30" mean for the rest of Chirp? Will that interfere with the power mod mentioned above? -- David Griffith dave(a)661.org

2 7

[chirp_devel] bug 155: VX-7 1.25m power levels
by David Griffith 10 May '12

10 May '12

Pretty simple and straightforward. # HG changeset patch # User David Griffith <dave(a)661.org> # Date 1336626680 25200 # Node ID 7b5bcb2537798b08e841055372afb606a4e6a764 # Parent ef3839880347f6591ce04101a7e73c3f805c4c24 # Parent c0037561deee06cd5c84b682de1e8142efbcdf3d Bug 155 fix: VX-7 1.25m power levels diff -r ef3839880347 -r 7b5bcb253779 chirp/vx7.py --- a/chirp/vx7.py Wed May 09 13:09:02 2012 -0700 +++ b/chirp/vx7.py Wed May 09 22:11:20 2012 -0700 @@ -311,7 +311,7 @@ msgs = yaesu_clone.YaesuCloneModeRadio.validate_memory(self, mem) if mem.freq >= 222000000 and mem.freq <= 225000000: - if mem.power not in POWER_LEVELS_220: + if str(mem.power) not in ["L1", "L2"]: msgs.append(chirp_common.ValidationError(\ "Power level %s not supported on 220MHz band" % \ mem.power))

2 1