- Developers - lists.chirpmyradio.com

[chirp_devel] [ft50] Yaesu FT-50 new Driver info, patch, & image. Fixes #1233.
by Mark Adams 02 Feb '16

02 Feb '16

Hello everyone! I've gotten enough completed on the FT-50 driver that I thought it was time for a patch. I'd like some eyes on it to make sure I'm not doing something really wrong or going in a bad direction. I'm no expert on all of the advanced features of the radio, but I've done the best I can to map out the important stuff. If anyone sees something missing just let me know. Feel free to critique away and send me questions or suggestions. I've been a developer for quite a while, but this is my first python project. The image I've attached is an empty image. It's what I got from the radio after a master reset and enabling extended reception. NOTE: the chirp/drivers/ft50_ll.py file is no longer needed and should be removed. I don't know how to include that change in the soft-commit and patch. Thanks! -mark

2 3

[chirp_devel] Build test results: Failure
by Build System 31 Jan '16

31 Jan '16

Tested changes: [Pavel Milanes (CO7WT) <co7wt(a)frcuba.co.cu>] [PATCH][FD-268] Improved detection + new models, PEP8, fixes #2169 Please note the updated images, detection has been improved and old img on the tree can make the test fail. Feidaxin driver is now PEP8 compatible. Minor changes in the structure, typos cleaning, fix some sentences with bad/confuse syntax (sorry native Spanish speaking here) Add support to the following new feidaxin radios: FD-150A FD-160A FD-460A FD-450A FD-288A This radios was tested hacking a FD-268A with the factory software, so maybe there is some bug in there, please report if so. Full log: Started by an SCM change Building in workspace /var/lib/jenkins/jobs/chirp-test/workspace [workspace] $ hg showconfig paths.default [workspace] $ hg pull --rev default [workspace] $ hg update --clean --rev default 1 files updated, 0 files merged, 0 files removed, 0 files unresolved [workspace] $ hg log --rev . --template {node} [workspace] $ hg log --rev . --template {rev} [workspace] $ hg log --rev 6a1b2e2cc788dd64104ed2d2ee08a26523f8f651 [workspace] $ hg log --template "<changeset node='{node}' author='{author|xmlescape}' rev='{rev}' date='{date}'><msg>{desc|xmlescape}</msg><added>{file_adds|stringify|xmlescape}</added><deleted>{file_dels|stringify|xmlescape}</deleted><files>{files|stringify|xmlescape}</files><parents>{parents}</parents></changeset>\n" --rev default:0 --follow --prune 6a1b2e2cc788dd64104ed2d2ee08a26523f8f651 No emails were triggered. [workspace] $ /bin/sh -xe /tmp/hudson1439626202906486592.sh + cd tests + ./run_tests Build step 'Execute shell' marked build as failure Email was triggered for: Failure Sending email for trigger: Failure

3 11

[chirp_devel] TYT MD-380
by Andrew Jorgensen 30 Jan '16

30 Jan '16

Greetings, Many Linux hams have written elsewhere about wanting support for the Connect Systems CS700 or the Tytera MD-380 DMR radios in CHIRP. I don't personally have much time to devote to the task, but I will soon have an MD-380 which I will give (free as in beer, down from $140) to a developer who wants to get into DMR and put in the time to add support to CHIRP. The two radios use the same configuration format, based on DfuSe, and method of writing the config - a modified USB Device Firmware Update (DFU). The MD-380 is very popular right now, because of its price, and it seems that similar radios will be on the market for some time to come. Some reverse engineering and USB debugging on Windows is likely required. Existing open source DFU utilities have not (for me) succeeded in writing the configuration, but there are a number of examples of code (including Python code) for handling DfuSe files, and some documents on some of the specific layout of the configuration. I've been told that CHIRP is (almost?) entirely serial-based so far. I don't know how much of a wrench that throws in this. There's also some trepidation about accidentally bricking the radio, but I would guess that concern is common here. I'm a Linux Systems Engineer and mostly write code in Python, but I'm just too busy with kids and work to believe that I'd be able to make much progress on my own. I'm happy to test from time to time, and to help figure out the file format and USB protocol. If you're sufficiently interested in DMR and in adding a new radio to CHIRP, and you believe you can pull it off, please let me know off-list. I expect no payment, and I'm accepting the risk that the work may never get done. I've decided opening DMR to the world of hams who don't own any Windows machines is worth that risk. I hope there's nothing inappropriate about making this offer on this list, and that you'll all forgive me if there is. Kind Regards, Andrew Jorgensen KC7RBW

2 2

Re: [chirp_devel] chirp_devel Digest, Vol 57, Issue 11
by Tyler Tidman 28 Jan '16

28 Jan '16

> Message: 1 > Date: Wed, 27 Jan 2016 00:57:09 -0800 > From: Dan Smith <dsmith(a)danplanet.com> > Subject: Re: [chirp_devel] Update WX channel stock config. Fixes > #2697. > To: chirp_devel(a)intrepid.danplanet.com > Message-ID: <56A88665.9040109(a)danplanet.com> > Content-Type: text/plain; charset=windows-1252 > > Hi Tyler, > >> diff -r 6a1b2e2cc788 -r ef0c41960ec0 stock_configs/NOAA Weather Alert.csv >> --- a/stock_configs/NOAA Weather Alert.csv Tue Dec 22 10:32:27 2015 -0800 >> +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 > > I have the same concern about renaming this file as I did before, > because people will now have a confusing and overlapping set of stock > configs. Did you want to scrap the entire patch then or just do it sans rename? Tyler

2 1

[chirp_devel] Update WX channel stock config. Fixes #2697.
by Tyler Tidman 27 Jan '16

27 Jan '16

2 1

[chirp_devel] [PATCH][FD-268] Fix author declaration, fixes #2169
by Pavel Milanes (CO7WT) 20 Jan '16

20 Jan '16

1 0

[chirp_devel] [PATCH][TK-760G] Fix author declaration, fixes #2999
by Pavel Milanes (CO7WT) 20 Jan '16

20 Jan '16

1 0

[chirp_devel] [PATCH][TK-868] Fix bad amount of channels declared, fixes #3139
by Pavel Milanes (CO7WT) 20 Jan '16

20 Jan '16

1 0

[chirp_devel] [TK-760G] New Model, support the VHF part of the Kenwood 60G family, fix #2999
by M.Sc. Pavel Milanes Costa 20 Jan '16

20 Jan '16

This patch is the support to the VHF part of the Kenwood 60G family, and must be applied after the patch for the issue #3119 Attached also is the imgs of a portable and a mobile radios for this driver.

3 2

[chirp_devel] [PATCH 1 of 4] [CIV radios] Fix common code for radio with no skip flag
by Marco Filippi IZ3GME 19 Jan '16

19 Jan '16

# HG changeset patch # User Marco Filippi <iz3gme.marco(a)gmail.com> # Date 1453220451 -3600 # Tue Jan 19 17:20:51 2016 +0100 # Node ID 8b30f8921b6006272f1ffd2aaa027e89a940fe14 # Parent 0758ce12bbae704776ab0cc854b207b521f00d81 [CIV radios] Fix common code for radio with no skip flag Introducing skip support for IC-7000 common CIV code have been modified but other radio (eg 7200) do not have that flag Introduced with fix for #3085 Fix #3185 diff -r 0758ce12bbae -r 8b30f8921b60 chirp/drivers/icomciv.py --- a/chirp/drivers/icomciv.py Fri Jan 15 09:08:36 2016 -0800 +++ b/chirp/drivers/icomciv.py Tue Jan 19 17:20:51 2016 +0100 @@ -307,10 +307,14 @@ memobj = f.get_obj() LOG.debug(repr(memobj)) - if memobj.skip == 1: - mem.skip = "" - else: - mem.skip = "S" + try: + if memobj.skip == 1: + mem.skip = "" + else: + mem.skip = "S" + except AttributeError: + pass + mem.freq = int(memobj.freq) mem.mode = self._rf.valid_modes[memobj.mode] @@ -386,7 +390,10 @@ if mem.skip == "S": memobj.skip = 0 else: - memobj.skip = 1 + try: + memobj.skip = 1 + except KeyError: + pass memobj.freq = int(mem.freq) memobj.mode = self._rf.valid_modes.index(mem.mode) if self._rf.has_name:

1 3