May 2015 - Users - lists.chirpmyradio.com

[chirp_users] New Daily Build
by Build System 30 May '15

30 May '15

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-20150530 A list of the changes included in this build (since the last daily) follows: Changes for Build #350 [Marco Filippi <iz3gme.marco(a)gmail.com>] [th9800] Align freq ranges with those in manual fix #2619 [Marco Filippi <iz3gme.marco(a)gmail.com>] [FT-1D] Aprs messages and beacons must be unmutable There's no reason to change this values Discovered working on #2509 [Marco Filippi <iz3gme.marco(a)gmail.com>] [FT-1D] Sanitize aprs message string before loading them in settings Aprs messages can contain non printable chars, replace them with * to obtain a printable string Fix #2509

1 0

Re: [chirp_users] More baofeng woes (UV-B5) (Scott Martin)
by Richard Menedetter 28 May '15

28 May '15

> From: Scott Martin <scott(a)kc9qen.com> > > Hey, all. > > I picked up a UV-B5 and am unable to program it with chirp. Yes ... sadly there is an open ticket for this for 4 months ... unfixed as of yet. http://chirp.danplanet.com/issues/2293 New UV-B5 software is not recognized by Chirp. There is a one line patch for Linux Chirp floating around that makes it work. Or you can use the Baofeng SW to download the image, rename it, use chirp to edit it, rename it back and use baofeng SW to upload it. I hope this will be addressed by Chirp soon! CU, Ricsi

2 1

[chirp_users] IC-T70A not communicating with Chirp
by Nicholas Papadonis 28 May '15

28 May '15

Folks, I’m having a similar issue as below and filed the following bug: http://chirp.danplanet.com/issues/2605 I have tested both Genuine FTDI and Prolific USB->Serial cables with no success. The USB->Serial chips are detected by both Windows 7 and Mac OS, however when Chirp sends out the 0xE0 detection frame, there is always a 0 byte response back when I would have suspected at least a byte for the Model ID according to the code. I have tested Chirp all the way back to v1.1 when the code log says T70A support was first added. My assumption is that it must have worked back then, however this is not confirmed yet. It’s odd that both cables resulted in 0 byte reads and now I’m suspecting either the T70A has a different protocol or newer manufactured firmware that changed the control codes. Has anyone validated the IC-T70A *ever* worked with Chirp? If so, can you share your experience and possibly the serial number and purchase date of the radio? Thanks, Nick KB1GZN > Thank you very much David, After trying many other things... I ran the cable loop back tester software, and set to COM3. Ran the test and nothing happens. I have tried this with the radio just turned on. I have tried this with hreadio in the CLONE mode. I have tried this with the radio in the CLONE OUT mode. I never get any response. I think perhaps I have a bad cable - sigh! One other clue is that the cable makes the radio SCAN whenevr I plug it in normally I have to fiddle with it and reinsert it numerous times before it will stop scanning and sit at a fixed frequency. The supplier assures me these are not the fake chips but genuine FTDI chips he is using, and charged a premium price for it. The cable came from Mark Dunkle, KJ6ZWL. I will relay all of this information and see if he can send me another cable that works. Manufacturer: FTDI on USB Serial Converter Driver Provided: FTDI 8/26/2014 Driver Version: 2.12.0.0 Brian Carling

2 2

[chirp_users] More baofeng woes (UV-B5)
by Scott Martin 27 May '15

27 May '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hey, all. I picked up a UV-B5 and am unable to program it with chirp. The console output is as follows: %chirpw ERROR: -- Exception: -- ERROR: Traceback (most recent call last): File "/usr/lib64/python2.7/site-packages/chirp/ui/clone.py", line 238, in run self.__radio.sync_in() File "/usr/lib64/python2.7/site-packages/chirp/drivers/uvb5.py", line 315, in sync_in self._mmap = do_download(self) File "/usr/lib64/python2.7/site-packages/chirp/drivers/uvb5.py", line 202, in do_download do_ident(radio) File "/usr/lib64/python2.7/site-packages/chirp/drivers/uvb5.py", line 181, in do_ident raise errors.RadioError("Radio did not ack programming mode") RadioError: Radio did not ack programming mode ERROR: ---------------- ERROR: Clone failed: Radio did not ack programming mode ERROR: --- Exception Dialog: Radio did not ack programming mode --- ERROR: None ERROR: ---------------------------- I've tried two different cables to no avail, and yes I had them seated. Not a windows environment so I don't think the IP hindrance is the issue. The radio's xmit light comes on but it seams to not be able to communicate with chirp. How can I provide more information to be helpful? Thanks in advance. Be well, Scott Also, props to all the dev's and users whom have helped make chirp what it is! -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBAgAGBQJVZhmGAAoJEMHo5RVayTw1mrYH/3GvTPwK/+OuOQZCZWN+6zNV bMvdA6um4TY48BvWH/bmcx0SEb2kfl5aiQSZy8ahlwNbpnxHSXMFaTzEb8QyNvpD 6tbWq11Znz9Dd4WT0/8HA63pi0GwF3Wk+1YYtsg19ro2qXveszDBZhsyPFRGox8b mM0JLs6yBfjOp/MBLhOq6xTzq+Lw1KPVAHZ3Xbg+PZ5oeZoBAoSvGF6HS7HHKRU6 nyGOybUyU8hk8bGgKtUrLwqEDejnjDtS5z+pDkHlAg3ggnL8m2Eu2nv6XBs8vtj7 08YvoFVE2RZe9DUebDoJB+IhBauDsAj/d6EIw6xf50pe5T58wJIS1gxqeMN0bHE= =8dnB -----END PGP SIGNATURE-----

3 4

[chirp_users] HOW DO I CLONE A KENWOOD TK-272G ??
by GARYJACKSO＠aol.com 27 May '15

27 May '15

: : Hello to All...... I need to clone a Kenwood TK-272G, downloading it onto a TK-270G. 1. Can I do it with CHIRP, and if so, HOW? 2. If NOT............how can I do it? 3. If really a bad NOT.........where can I get the right software to program a TK-270G?? Thanks in Advance........... Gary Jackson KC5QVI

1 0

[chirp_users] Kenwood TH-D72 Issue
by Mark Herson, N2MH 26 May '15

26 May '15

Hello to the Group, Like several other users have posted, I too have a Kenwood TH-D72 portable and just recently started using Chirp. In addition, I also have had problems sending an image to the radio in Clone mode. I see where issues 2455 and 1611 address this problem. After playing with the radio and seeing what is in it after the upload, I'd like to add several pieces of information. 1. Both issues 2455 and 1611 appear to me to be the same issue. Yes, the newly progammed 2m channels don't transmit (same as non-functional). However, when I look at the memories in the radio by band, the newly programmed 2m channels show up on the UHF side of the radio, not the VHF side. Apparently, when you try to transmit on these channels, the radio thinks these channels are out-of-band and will not transmit. Otherwise, the channels appear to receive OK. 2. Before programming these new channels, I completely read all the memories in the radio, both VHF and UHF channels and saved the image. I then added several new VHF channels to the image and then programmed everything back to the radio. When everything was finished, the new channels were added in the correct memory position but on the UHF side of the radio (as described above). However, the original channels were in their original positions and worked normally. There were no problems with transmitting on the original VHF channels. 3. If I didn't know anything about the inner workings of Chirp, I'd probably conclude that: - The write (clone) process works OK (the original channels went back to where they were and work OK). - The process of taking the image and putting the contents on the wire to the radio works OK. - Something in Chirp is classifying VHF frequencies as UHF channels at data entry time. Upon upload to the radio, the radio is instructed somehow to place these entries in the UHF side where they will fail instead of the VHF side where they belong.- The process of taking the image and putting the contents on the wire to the radio works OK. Software in use: Chirp 0.4.1 and nightly build 20150513. PC is running slackware 14.1 (64-bit). Hope this helps the developers fix the bug. 73, Mark, N2MH

3 2

[chirp_users] Software info
by Ste Bus 23 May '15

23 May '15

Hi, i’ve a Baofeng UV8HX, which software i have to use with this radio to program it ? Can I use the UV-5R series software and the CHIRP software with the UV8HR radio? Thanks in advance. Stefano

3 2

[chirp_users] American Human Right Self Defense
by Peter Grace 22 May '15

22 May '15

God is unhappy, Please read and fix. God gave you a self and does want you to defend that self. http://wp.me/p5FtCq-pd Peter Grace pcg(a)acm.org Technical Project Manager

1 0

[chirp_users] UV5R+
by Jim 22 May '15

22 May '15

Am trying to program a uv5r+,have done many. I downloaded a cloned copy of the radios program from the radio,copied the program I wish to install into the downloaded copy,but when I tried to upload it back to the radio,got an error report that stated "unsupported firmware version:NR-323F8HP-1". Any help is appreciated.Thank you. Jim Sites

2 1

[chirp_users] IC-T70A: has anyone programmed it successfully?
by Nicholas Papadonis 22 May '15

22 May '15

Hi Folks, Has anyone heard reports of an Icom IC-T70A or IC-T70E working with Chirp? I'm having difficulty programming this radio, however can program my Baofeng. I have a Genuine FTDI USB cable. Unfortunately, I keep getting an error downloading from the radio. "Failed to communicate with the radio: Unexpected response from radio". As device manager says the COM port is ok, I'm suspecting something else is going on. The USB serial cable is properly detected by my Mac OSX v10.10.3 as a USB serial device. The device properly appears in the OS as /dev/cu.usbserial-A9030T4G. I tried a couple versions of Chirp and used this device path. In my tests I tried downloading from the radio both by specifying Icom / IC-T70 and then Icom / Autodetect. Both setting resulted in failure to communicate with the radio. The radio then begins to cycle memory channels after the download fails. I have tried placing radio into clone mode by pressing V/M/C and Power button at the same time, then pressing the PTT button both before and after clicking Chirp Download from Radio button. I have tried without placing radio into clone mode. I have attached the Chirp debug log from a recent daily build 2015-05-02. I tried an older build from a year ago from 2014-12-15 with the same results. I have also noticed a few bugs around this radio and wondering if perhaps an older Chirp build works correctly. Any insight is appreciated. Thanks, Nick KB1GZN New York, NY USA

1 0