May 2015 - Users - lists.chirpmyradio.com

[chirp_users] HELP
by Jim Russell 19 Jul '15

19 Jul '15

I bought two baofeng radios, one is UV-82C an the other is BF-F8H and I can get neither one to up load to the computer it says in the paper i got with the radios that the small CD disc has all the software on it but when i click on it open it there is just a bunch of files, it says in the instructions that to click on the radio on the menu bar but so far I have found no menu bar with a radio to click on. It says I have to upload to the computer before I can program the radio OKAY what do I have to do get past this point. I'm lost I can't even get started till this happens. thank you Jim KM6WC CM97iw

9 12

[chirp_users] Issue with Umlauts
by Christian Hilgers 28 Jun '15

28 Jun '15

Hi, I tested chirp 0.4.1 on Debian Jessie with my Kenwood TH-F7e via USB-serial Adapter and a serial-RIG Cable. It worked very well and I could read and write data from and to the handheld. It failed while reading Frequency Names like Düsseldorf or others with Umlauts. I am running UTF8 on my box. Are there other recommendations on the Locale to be used? Thanks Christian = DG7PC :wq!

2 3

[chirp_users] "length 0" error DLing from FT-8900
by Charles Boling (AD7UF) 13 Jun '15

13 Jun '15

Hi, longtime CHiRP user for Icom,Yeasu,Wouxun,Baofeng here. I just got a Yeasu FT-8900R (and a USB programming cable) and am having difficulty getting it to download. I'm running CHiRP 0.4.0 on Python 2.7.8 under Ubuntu 14.10. I put the radio in clone mode, have CHiRP waiting for the data, and as soon as I press the V/M button to send the data, I get the error: "ord() expected a character, but string of length 0 found" and the radio shows a clone error. I read the recent (May 4) thread on this list between Dan & Benjamin entitled "Chirp IndexError" that describes the same error. In his case, Benjamin wasn't getting anything from the radio, and it proved to be a loose cable. Not so with me. In my case, here's what I know: I can connect a terminal program (PuTTY) to the correct port and get echo. I also receive data from the radio when pressing the V/M button that looks right. Specifically, the radio sends this string, viewed in PuTTY: AH008$.$ ("." is non-ASCII char) I captured it to a file and this is the exact data stream in hex: 41 48 30 30 38 24 80 24 The correct data stream only appears at 9600 baud, which is what ft7800.py says it should be fixed at. AH008 is the model that the code shows for the FT8900. Here's the terminal output from the failure: ... User selected Yaesu FT-8900 on port /dev/ttyUSB1 Clone thread started Download finished in 1 seconds -- Exception: -- Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/chirpui/clone.py", line 227, in run self.__radio.sync_in() File "/usr/lib/python2.7/dist-packages/chirp/ft7800.py", line 320, in sync_in self.check_checksums() File "/usr/lib/python2.7/dist-packages/chirp/yaesu_clone.py", line 209, in check_checksums if checksum.get_existing(self._mmap) != \ File "/usr/lib/python2.7/dist-packages/chirp/yaesu_clone.py", line 156, in get_existing return ord(mmap[self._address]) TypeError: ord() expected a character, but string of length 0 found ------ Clone failed: ord() expected a character, but string of length 0 found Clone thread ended --- Exception Dialog: ord() expected a character, but string of length 0 found --- None ---------------------------- Any ideas?

6 14

[chirp_users] Yaesu FT-60
by Jerry A 12 Jun '15

12 Jun '15

Hello, Would anyone be able to offer help with the Yaesu FT-60 and Chirp? For some reason I am getting an error message about communication between the radio and software. I have used FT-60 Commander, a Prolific USB to com port interface and Windows XP successfully but am unable to make things work with Chirp and Windows 7 using the same procedure, interface and com port. 73, Jerry - VE9CD

5 5

[chirp_users] BF-A58
by Michael Walker 06 Jun '15

06 Jun '15

I just got a bunch of BF-A58's from Baofeng. I know it isn't on the list, but has anyone tried to work with them on any other model? Mike va3mw

2 1

Re: [chirp_users] I picked up a UV-B5 and am unable to program it with chirp.
by Stan 04 Jun '15

04 Jun '15

Hi all. This has been my experience with a UV5R. Maybe a little help????? When I plug in my cable and turn on the radio (UV5R), _it comes on in transmit mode_, and stays key-down. As soon as I _send the updated data_ to the radio, it will fail, but the _radio will come out of transmit mode . . . USUALLY_ . . . BUT sometimes I have to send the data 2 or 3 times before it comes out of transmit mode. Then, _after it's come out of transmit mode_, it will accept the data OK. So, I try to tune to a frequency that most likely will not be in use when I turn the radio on, that way, when it starts up in transmit mode it won't interfere with someone else's QSO. Also, and I'm not sure what chipset is in my cheap cable, I had to just roll the driver back to the previous driver BEFORE it would work. The next update made it fail again, so I rolled it back again and stopped it from updating the driver again and it has worked OK ever since. Just my 2Hz worth! 73 Stan K8LL NW Ohio 10-10# 76801 FP# 3255 Propagation is our master . . . but sometimes the master is cruel! ------------------------------------------------------------ On 5/28/2015 3:00 PM, chirp_users-request(a)intrepid.danplanet.com wrote: > 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. > >

3 2

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

31 May '15

Hi > >> 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! > > Where is this one line patch? It only works on Linux, as there the Python code is directly accessible. I was very much hoping that Chirp gets changed to work with the "new" UV-B5. If you are using Linux I can search for the old message and send it to you. > Jim KC9HI CU, Ricsi

3 2

Re: [chirp_users] Cable driver needed
by Dave Gomberg 30 May '15

30 May '15

At 13:35 5/30/2015, Jim Unroe wrote: >On Sat, May 30, 2015 at 4:00 PM, Dave Gomberg <dave1(a)sfwcf.com> wrote: > > Running XP Home SP3, using a USB port to drive an Icom programming > > cable part# 4566-7831. > > I need a link to the appropriate driver to support this cable as a > > serial device for Chirp. > > >Dave, >Assuming that you have a programming cable with a Prolific type >USB-to-TTL chip, the driver that you need is v2.0.2.1 and there is a >link to it on the miklor.com website. >http://www.miklor.com/COM/UV_Drivers.php >Jim KC9HI Thanks Jim, that worked FB -- Dave Gomberg, San Francisco NE5EE Programming since 1961 All addresses, phones, etc. at http://www.sfwcf.com/ham/info.html -----------------------------------------------------------------

1 0

[chirp_users] Cable driver needed
by Dave Gomberg 30 May '15

30 May '15

Running XP Home SP3, using a USB port to drive an Icom programming cable part# 4566-7831. I need a link to the appropriate driver to support this cable as a serial device for Chirp. I am pretty sure I used to have one but it seems to have disappeared. Many thanks for your help. -- Dave Gomberg, San Francisco NE5EE Programming since 1961 All addresses, phones, etc. at http://www.sfwcf.com/ham/info.html -----------------------------------------------------------------

2 1

[chirp_users] Cable driver needed
by Dave Gomberg 30 May '15

30 May '15

Running XP Home SP3, using a USB port to drive an Icom programming cable part# 4566-7831. I need a link to the appropriate driver to support this cable as a serial device for Chirp. I am pretty sure I used to have one but it seems to have disappeared. Many thanks for your help. -- Dave Gomberg, San Francisco NE5EE Programming since 1961 All addresses, phones, etc. at http://www.sfwcf.com/ham/info.html -----------------------------------------------------------------

1 0