May 2016 - Developers - lists.chirpmyradio.com

[chirp_devel] Gnome nautilus script to clean portmon logs.
by Pavel Milanes (CO7WT) 20 May '16

20 May '16

Hi to all, Today I want to share one of y tools to make the process of debugging portmon logs more faster and eye refreshing, this nautilus script is intended for the users that has a GNU/Linux with any of the Gnome flavors as a develop environment. (works with the default Ubuntu's Unity) The goal is to clean the original portmon serial logs from all the non essential "garbage" to make it more easy to analyze, but remember that under certain circumstances you will have to look at the original log, so this tool will preserver it. To make it work you must surf into the folder ~/.local/share/nautilus/scripts/ and copy it inside; It's as easy as follow this instructions: * Press Alt+F2 and paste "~/.local/share/nautilus/scripts/" in the box + Enter, a nautilus window will open, o If it complains about the folder not existing or do nothing, please do this extra steps: o Press Alt+F2 and paste "~/.local/share/nautilus/", A nautilus window will open o Create a folder named "scripts" (without quotes) and open it, now follow the next step * Just paste the file there, * Right-click the file and select properties, then permissions * Tick the box about allowing to run it as a program * Close the nautilus windows, that's all. After that you will need to find a portmon serial log and right-click it, search for and option named "Scripts" and after expanding it you will find the "Chirp portmon clean log" option, select it and a file with the exact name and an extension of .clean will appear on your folder, additionally the Gedit text editor will pop up with the clean log on it. Compare the original and cleaned log and your will find that your eyes/brain will thanks you for this. This also works with several files at once; as always use it, share it, improve it, it's GNU GPL 3.0 [The long name is because I have a lot of scripts in my script folder and I group them by the main related activity, of course you can change the name of it once it's recognized by the system] 73 -- 73 Pavel CO7WT.

1 0

[chirp_devel] [PATCH][KT8900R] Settings fix about the 220Mhz band, fixes #3547
by Pavel Milanes (CO7WT) 17 May '16

17 May '16

Now we have two of this radios that has 220/240 Mhz support in the base class and we need to validate the freq ranges for each one of them, this patch is to realize that. Thanks to Jim Unroe for the help with it. -- 73 Pavel CO7WT.

1 0

[chirp_devel] [PATCH][KT8900R] Initial support for the QYT KT8900R, fixes #3547
by Pavel Milanes (CO7WT) 16 May '16

16 May '16

This radio is like the BTECH UV-2501+220 but it has the 220 band in the Chinese area (240-270 Mhz) well outside the USA ham band. This is the initial support patch for this radio, it may need further work on the settings part. -- 73 Pavel CO7WT.

1 0

[chirp_devel] [PATCH][BTECH] Add a flag to know we have a BTECH gen3, fixes #3015
by Pavel Milanes (CO7WT) 16 May '16

16 May '16

This 3 gen wave of BTECH radios has new settings items and we need a flag to know when we are dealing with one of these to show the settings properly. This is an advance to the real settings modification. 73

1 0

[chirp_devel] [PATCH][BTECHs] Add support for the new Gen3 wave of BTECHs, fixes #3015
by Pavel Milanes (CO7WT) 13 May '16

13 May '16

This add support for the new generation (3gen) if the following BTECHs: * UV-2501 * UV-2501+220 * UV-5001 73

1 0

[chirp_devel] [PATCH][KT8900] Comment about old versions of KT8900 in the UI, fixes #3539
by Pavel Milanes (CO7WT) 13 May '16

13 May '16

All points that the QYT KT8900 is the main OEM model, and there are two variants of it, from the prespective of the communication dance: * One is with just the ID and right to the down/up process (clone of WACCOM Mini8900) * The other (is the default now) with a second id read & a extra step on the upload process. As both uses different communications steps we can't put them both under the same case, fortunately the "older" model has a clone in the WACCOM Mini8900. We put here a notice on the failure to read a KT8900 to warn the users to try the WACCOM Mini8900 instead.

1 0

[chirp_devel] [PATCH 1 of 3] [mq]: kt8900
by Pavel Milanes (CO7WT) 13 May '16

13 May '16

# HG changeset patch # User Pavel Milanes (CO7WT) <pavelmc(a)gmail.com> # Date 1462560219 14400 # Fri May 06 14:43:39 2016 -0400 # Node ID 906ba819a626dfdb3d732d8fa2b006848d3dc656 # Parent 44e9390fd40dc92ad3e926246ef903f38867fe86 [mq]: kt8900 diff -r 44e9390fd40d -r 906ba819a626 chirp/drivers/btech.py --- a/chirp/drivers/btech.py Thu May 05 21:01:34 2016 -0700 +++ b/chirp/drivers/btech.py Fri May 06 14:43:39 2016 -0400 @@ -468,7 +468,13 @@ # open the radio into program mode if _start_clone_mode(radio, status) is False: - raise errors.RadioError("Radio didn't entered in the clone mode") + if radio.MODEL == "KT8900": + error = "Radio didn't entered in clone mode; there is a generation" + error += " of this radios that are a clone of the WACCOM Mini-8900" + error += " please try that also." + raise errors.RadioError(error) + else: + raise errors.RadioError("Radio didn't entered in the clone mode") # Ok, get the ident string ident = _rawrecv(radio, 49)

2 3

[chirp_devel] [PATCH][KT8900] Add support for 3 new variants of this radios, fixes #3539
by Pavel Milanes (CO7WT) 13 May '16

13 May '16

[KT8900] Add support for 3 new variants of this radios, fixes #3539 Thanks to the users we have identified 3 direct new variants of this radios. Thist patch add support for it. 73 Pavel CO7WT.

2 1

[chirp_devel] [PATCH 2 of 3] [KT8900] Add support for 3 new variants of this radios,
by Pavel Milanes (CO7WT) 13 May '16

13 May '16

# HG changeset patch # User Pavel Milanes (CO7WT) <pavelmc(a)gmail.com> # Date 1463022522 14400 # Wed May 11 23:08:42 2016 -0400 # Node ID 42b1f1065bbd4f415248139a35908a3111332f62 # Parent 906ba819a626dfdb3d732d8fa2b006848d3dc656 [KT8900] Add support for 3 new variants of this radios, fixes #3539 Thanks to the users we have identified 3 direct new variants of this radios. Thist patch add support for it. I have detected also a variant of this radios that has a different comm dance and it can be handled as a WACCOM Mini-8900. 73 Pavel CO7WT. diff -r 906ba819a626 -r 42b1f1065bbd chirp/drivers/btech.py --- a/chirp/drivers/btech.py Fri May 06 14:43:39 2016 -0400 +++ b/chirp/drivers/btech.py Wed May 11 23:08:42 2016 -0400 @@ -291,6 +291,10 @@ # QYT KT8900 & Juentai JT-6188 KT8900_fp = "M29154" +# New generations KT8900 +KT8900_fp1 = "M2C234" +KT8900_fp2 = "M2G1F4" +KT8900_fp3 = "M2G2F4" # this radio has an extra ID KT8900_id = " 303688" @@ -1599,7 +1603,7 @@ _vhf_range = (136000000, 175000000) _uhf_range = (400000000, 481000000) _magic = MSTRING_KT8900 - _fileid = [KT8900_fp, ] + _fileid = [KT8900_fp, KT8900_fp1, KT8900_fp2, KT8900_fp3] _id2 = KT8900_id

2 1

[chirp_devel] [GT-890] Remove direct support for the Sainsonic GT-890, fixes #3533
by Pavel Milanes (CO7WT) 12 May '16

12 May '16

This patch is to remove the direct support for the Sainsonic GT-890 as it's a perfect clone of the QYT KT8900, this applies to the two known variants of the GT-890 so far. The change to the Wiki (Supported Radios page) is already done We are paving the way for the new radio.ALIASES feature that will put aliases on the UI in a user friendly way. We have internal tests going on about it.

1 0