April 2016 - Users - lists.chirpmyradio.com

[chirp_users] News about the Chirp development in the next spin.
by Pavel Milanes (CO7WT) 14 Apr '16

14 Apr '16

Hi to all, some news about the patches in the development queue and some other infos. The btech driver (for all supported radios looking similar to the btechs) has a bug about the driver not retrying the identification (aka: the driver does just one attempt) a patch for fixing that is on the queue, the driver will do 3 attempts, all due to a line not being tabulated correctly. (sorry, my fault) That must fix what some user are reporting as "not working in the first try" or "not working from a cold start" A new generation for the BTECH UV-2510+220 was discovered today, if any of you had faced a "Radio identification failed" error with this model you must try the next daily of Chirp that will contain support for this new version, all points that this is a second generation of the BTECH UV-2510+220. *Mental note for you:* If you found a BTECH like radio that is supported on Chirp but it says "Radio identification failed" you may have hit a new variant, go to the chirp forum and left us a issue with a debug.log attached, that will speed up things a lot. (search in the chirp's wiki for "how to report a bug" for instructions) Support for the Sainsonic GT-890 is waiting on the develop queue to be applied also. Some users have experimented problems working the Juentai JT-6188 *Mini* with Chirp, we realize today that there is a new spin on this radios: the Juentai JT-6188 *Plus*. If any of you has this new _Plus_ radio we are willing to work with you for get it supported on chirp, just drop me and email. This is getting the users confused as Chirp listed the JT-6188 *Mini* as a Clone of the QYT KT8900, but the new JT-6188 *Plus* is a totally different radio and is not supported by Chirp yet (this new model has 220Mhz and a fan) -- 73 Pavel CO7WT. A proud Chirp's developer

2 2

[chirp_users] settings support for yaesu ft-8900r
by ronnie lavoie 13 Apr '16

13 Apr '16

i would like to know if settings support for the yaesu ft-8900r is planned?, if not i would like to request settings support for the yaesu ft-8900r. thank you.

2 2

[chirp_users] New Daily Build
by Build System 12 Apr '16

12 Apr '16

Greetings, A new daily build of CHIRP is available. This includes changes made directly to the tree yesterday, and may include additional features, bug fixes, and/or bugs. If you are interested in trying it, grab it from the following location: http://trac.chirp.danplanet.com/chirp_daily/daily-20160412 A list of the changes included in this build (since the last daily) follows: Changes for Build #395 [Jim Unroe <rock.unroe(a)gmail.com>] [BTECH] Add Other Settings Add Settings from "Aux" Memory. releated to #3015 [Jim Unroe <rock.unroe(a)gmail.com>] [BTECH] Add Advanced Settings Add settings from the OEM software "Optional Features" menu that are not related to the internal menus of these radios. releated to #3015 [Jim Unroe <rock.unroe(a)gmail.com>] [BTECH] Add Basic Settings Add settings from the OEM software "Optional Features" menu that are related to the internal menus of these radios. releated to #3015 [Jim Unroe <rock.unroe(a)gmail.com>] [BTECH] Update SPMUTE Setting SPMUTE was accidentally programmed as RadioSettingValueBoolean when in reality is should have been programmed as RadioSettingValueList related to #3015 [Pavel Milanes (CO7WT) <pavelmc(a)gmail.com>] [PATCH][BTECH] Bug fix about radios resetting on the download, fixes #3015 The radios with the second ID can run into a conditions in which the timeouts concatenates and get the radios resets after ident and before download. Afected models QYT KT 8900 & BTECH 2501+220 so far. Setting a temporal lower timeout in the second ID part has proved to fix this issue.

1 0

Re: [chirp_users] ARM Distribution?
by NP3AR 09 Apr '16

09 Apr '16

I use chirp on a pi 2 without problem. Downlod the version for linux. Sent from my Samsung Galaxy Tab®4 -------- Original message -------- From: patrick(a)ogrd.net Date:04/07/2016 9:34 AM (GMT-04:00) To: chirp_users(a)intrepid.danplanet.com Subject: [chirp_users] ARM Distribution? I've got a little Raspberry Pi 2 (ARM) computer setup with UbuntMATE, and when I went to install everything I ran into problems, however we did work it out. Either way I just wanted to bring this bit to the table to request a version of CHIRP for ARM. Also, as much as I can tell what I've got setup is a text-based Python program, and documentation is slim; is there more documentation somewhere else where I'm not looking? -- http://www.ogrd.net _______________________________________________ chirp_users mailing list chirp_users(a)intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to joe at np3ar(a)gmx.com To unsubscribe, send an email to chirp_users-unsubscribe(a)intrepid.danplanet.com

7 11

Re: [chirp_users] ARM Distribution?
by NP3AR 07 Apr '16

07 Apr '16

That's correct. What I did was install it that way to make sure that all dependencies are met and then download the latest and call it from the terminal. Sent from my Samsung Galaxy Tab®4 -------- Original message -------- From: Dan Smith <dsmith(a)danplanet.com> Date:04/07/2016 7:23 PM (GMT-04:00) To: Discussion of CHIRP <chirp_users(a)intrepid.danplanet.com> Subject: Re: [chirp_users] ARM Distribution? > DItto. I just installed CHIRP on my Pi-2 (OS=raspbian/wheezy) by running: > > sudo apt-get install chirp > > and it works perfectly with my Boafeng UV-5R. Just so you know, the chirp package you're getting is beyond ancient. Like, crusty petrified old :) If you're not installing chirp-daily from the PPA, or installing from the tarball, then you're probably getting 0.3.x or 0.4.x which is...OLD. :) --Dan _______________________________________________ chirp_users mailing list chirp_users(a)intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to joe at np3ar(a)gmx.com To unsubscribe, send an email to chirp_users-unsubscribe(a)intrepid.danplanet.com

1 0

[chirp_users] Baofeng UV-82
by Tim Billingsley 07 Apr '16

07 Apr '16

This is pretty sad and maybe a little off topic but .... How do you get these things to go into "Name" mode? I picked up a pair of these to have on hand when my YL and I go on a trip and I CANNOT get them to go into anything but VFO mode. I have them set to "Name" mode in the chirp settings and have tried changing them to Name mode in the menu of the radio and they will not change to anything but VFO. What am I missing? Please enlighten me before I return them.

7 11

[chirp_users] ARM Distribution?
by patrick＠ogrd.net 07 Apr '16

07 Apr '16

I've got a little Raspberry Pi 2 (ARM) computer setup with UbuntMATE, and when I went to install everything I ran into problems, however we did work it out. Either way I just wanted to bring this bit to the table to request a version of CHIRP for ARM. Also, as much as I can tell what I've got setup is a text-based Python program, and documentation is slim; is there more documentation somewhere else where I'm not looking? -- http://www.ogrd.net

3 3

[chirp_users] Download from Yaesu FT-2900
by Al Cohan 06 Apr '16

06 Apr '16

I have installed the FTDI driver for the FT-2900 and see it in Device Manager. I shows in dev mgr and CHiRP software as Com 20. I plug in FTDI cable (from Valley-Ent) the select open then new then go to radio tab and download from radio (which is in clone mode). Several times ago it said in a popup to press ok, then the MW D/MR button briefly. The display says wait, then a popup error says can't read header. I vaguely recall a while back that there were two different button to press. One if reading the radio and another to upload to the radio. Suggestions appreciated. Thank You, Al

2 1

[chirp_users] Digest mode
by Steve Johnson 06 Apr '16

06 Apr '16

How can I change the settings to just receive a daily digest instead of numerous individual emails? Thanks KD4KOC

3 4

[chirp_users] New Daily Build
by Build System 02 Apr '16

02 Apr '16

Greetings, A new daily build of CHIRP is available. This includes changes made directly to the tree yesterday, and may include additional features, bug fixes, and/or bugs. If you are interested in trying it, grab it from the following location: http://trac.chirp.danplanet.com/chirp_daily/daily-20160402 A list of the changes included in this build (since the last daily) follows: Changes for Build #394 [Pavel Milanes (CO7WT) <pavelmc(a)gmail.com>] [PATCH][BTECH] nB: Extra step on the upload updated, fixes #3015 As we begin to find clones and they use the extra id and the extra step on the upload I updated the code to just check the common place on this step: last byte being an ACK. Comments on the definition updates for the radio clones found. [Pavel Milanes (CO7WT) <pavelmc(a)gmail.com>] [PATCH][BTECH] nA: Support for the QYT KT8900, fixes #3015 Added support for the radio QYT KT8900. Updated the extra ID code portion, as this radio uses it. Corrected a comment with the correct name for the radio KT-UV980 Related also to the issue #2673 [Pavel Milanes (CO7WT) <pavelmc(a)gmail.com>] [PATCH][BTECH] n9: Var name correction and debug/error fix, fixes #3015 Corrected the var name for the QYT KT-UV980. Applied some rationalization with the debug and error messages. [Pavel Milanes (CO7WT) <pavelmc(a)gmail.com>] [PATCH][BTECH] n8: Fixed a bug on the upload (BTECH UV2501+220), fixes #3015 The BTECH UV2501+220 has a trick on the upload, it must push an ACK and get two bytes, ending with an ACK; this just before the data upload. Also the first block of data to upload must no start with an ACK. [Pavel Milanes (CO7WT) <pavelmc(a)gmail.com>] [PATCH][BTECH] n7: Simplified the part for the extra id, fixes #3015 Some radios like the BTECH UV2501+220 (and others) has a second id. Just a special string on a high zone of the mem, I improved and simplified the handling of this extra ID for the BTECH UV2501+220. [Pavel Milanes (CO7WT) <pavelmc(a)gmail.com>] [PATCH][BTECH] n6: New _recv function, now less intensive, fixes #3015 Full rewrite of the _recv() function to read a full block of data instead of doing short syscalls, hence less resource intensive [Pavel Milanes (CO7WT) <pavelmc(a)gmail.com>] [PATCH][BTECH] n5: New serial send function (simplified), fixes #3015 Simplified the serial send function to remove the time wait that is not needed now with the recent changes. [Pavel Milanes (CO7WT) <pavelmc(a)gmail.com>] [PATCH][BTECH] n4: New raw data receive function, fixes #3015 New aproach on the raw receive of the data, it's way more secure and less resource intensive now, and even faster. [Pavel Milanes (CO7WT) <pavelmc(a)gmail.com>] [PATCH][BTECH] n3: Improved the serial timeout, fixes #3015 Set a general serial timeout and apply it in the correct places. [Pavel Milanes (CO7WT) <pavelmc(a)gmail.com>] [PATCH][BTECH] n2: New serial flush function, fixes #3015 New serial flush function, it has the capability of survive a infinite serial data stream and warn the user about [Pavel Milanes (CO7WT) <pavelmc(a)gmail.com>] [PATCH][BTECH] n1: Update email for author, fixes #3015 Just updating the email for one of the autors.

1 0