June 2015 - Users - lists.chirpmyradio.com

[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] Problem solved UV-5RV+
by doogle1953＠fastmail.net 13 Jun '15

13 Jun '15

Please disregard my HELP request. I figured out how to transfer a working program from one radio to another using 'IMPORT' all is well again in Northern Indiana. Thanks and best wishes to all. Doug KB9MIC

1 0

[chirp_users] UV82 firmware incompatible
by John Hutchinson 13 Jun '15

13 Jun '15

I have successfully programmed UV82 in the past, seven in fact with the same .img file. I just bought 3 more and tried to upload to the radio but got error message that the Firmware version doesn't match that of the radio. I could Download from that radio and saved that file. Maybe upgrading CHIRP to the latest version 0.4.1 would help but didn't, so also ran Daily Build install hoping but no luck. I still get the same error message when trying to Upload and if I now try to Download, I get a message that it's the wrong model! I can still download from my older UV82. I see in Settings>Other Settings it shows the Firmware Message 1&2 which is different for the old and new radios but they are greyed out so can't change it. Older radios Firmware Message 1> ver Older radios Firmware Message 2> B82525 New radios Firmware Message 1> N822411 New radios Firmware Message 2> N822411 What do I do? Please help. John

4 4

[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] Icw32a. Uhf memory channels
by anthony hollister 12 Jun '15

12 Jun '15

I tried programming my Icw32a with a variety of memory channels, but when testing I found that only the vhf channels took. There are no Uhf frequencies in memory. Am I missing a specific step ?

2 2

[chirp_users] Bao-Feng BF-F8HP
by bravert＠woh.rr.com 12 Jun '15

12 Jun '15

Howdy, Please forgive my apparent ineptness, but despite searches, I cannot figure out how to upload more than 22 channels to my recently acquired BF-F8HP. I know it is capable of 128 channels, but the CHIRP UI limits me to 22, no matter what. Many thanks. Best Regards, Brian

2 1

[chirp_users] More baofeng woes (UV-B5)
by Richard Menedetter 11 Jun '15

11 Jun '15

Hi New UV-B5 not supported. > I tried this and it had no ill affect on my very old UV-B5. Can I somehow assist you in this? Maybe send you debug output? Just tell me what you need! CU, Ricsi

1 0

[chirp_users] Definition-file for ICOM-W32E (solved)
by David Krause 09 Jun '15

09 Jun '15

Hi Everybody, I just want to let you know that CHIRP does not work with the ICOM IC-W32E (european version)! This is due to the different model-ID. The W32A uses the hex id 18 82 00 01 while the W32E uses 18 82 00 02! So no response from a W32E appears... I found this after using chirp for a while with no problems with my W32A but getting no connection with a friends W32E. Even the direct cloning with the icom cable was not possible, but gave us the hint to the different modell-id. After changing the line with _model = "\x18\x82\x00\x01" in the ICW32A.PY-file to _model = "\x18\x82\x00\x02" everything runs smooth now! So as this is easy done, but just a quick workaround it would be nice to see a proper definition-file and the IC-W32E added to the list of compatible gear... This was also subject of issue #280 on http://chirp.danplanet.com/issues/280 but I don't want to go to much inside development as I allready have a long list of things to do! So maybe somebody else has the capacity to put things together.... Regards, David

1 0

[chirp_users] Chirp users e-mails leaked?
by YL3IM 08 Jun '15

08 Jun '15

Good day everyone. Just received a spam message to the address I have used uniquely by creating an account on http://chirp.danplanet.com Return-Path: <hongdbsfsbbaa(a)163.com> X-Original-To: MY(a)EMAIL.ADDRESS X-Received-SPF: pass (toivo: domain of 163.com designates 220.181.13.37 as permitted sender) client-ip=220.181.13.37; envelope-from=hongdbsfsbbaa(a)163.com; helo=m13-37.163.com; Received: from m13-37.163.com (m13-37.163.com [220.181.13.37]) by toivo.Toivo.Lv (Postfix) with ESMTP id D0EF01FB9D7 for <chirp(a)inga.lv>; Mon, 8 Jun 2015 11:59:53 +0300 (EEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=163.com; s=s110527; h=Date:From:Subject:MIME-Version:Message-ID; bh=JgC9q 0TSEEITKRlM4uOQljn9Q3fiyDX/ZP7sfUaeq9A=; b=mm0P4KBkN3DHqqAgm6B7P OkurCjmqJbNVHsZcH3qRAqYw1wwB5af8KWCo/h8uYIlWvNjhQOcj3BA05WqGB6LO ca7G/JdXAk7bsEYa1JaQiUS/XYqgqig+GyR/KFxASEo0tP+rkR9FiGE7pggGN0uK EJ515t9vyWQrQHO8ijmQX4= Received: from hongdbsfsbbaa$163.com ( [14.208.232.197] ) by ajax-webmail-wmsvr37 (Coremail) ; Mon, 8 Jun 2015 16:14:57 +0800 (CST) X-Originating-IP: [14.208.232.197] Date: Mon, 8 Jun 2015 16:14:57 +0800 (CST) From: hongdbsfsbbaa <hongdbsfsbbaa(a)163.com> To: MY(a)EMAIL.ADDRESS Subject: 2015 unique product X-Priority: 3 X-Mailer: Coremail Webmail Server Version SP_ntes V3.5 build 20150119(59087.7062) Copyright (c) 2002-2015 www.mailtech.cn 163com X-CM-CTRLDATA: 7pLHQmZvb3Rlcl9odG09Nzc2MTk6ODE= Content-Type: multipart/alternative; boundary="----=_Part_429437_346457996.1433751297806" MIME-Version: 1.0 Message-ID: <3d3ab3aa.1a25e.14dd23c9f0e.Coremail.hongdbsfsbbaa(a)163.com> X-CM-TRANSID:JcGowGAZFUwCT3VVjPWsAA--.41W X-CM-SenderInfo: pkrqwvpevi2uxeddqiywtou0bp/xtbBLwETo1UL2fxMTQAAsk X-Coremail-Antispam: 1U5529EdanIXcx71UUUUU7vcSsGvfC2KfnxnUU== -- 73! de YL3IM

4 4

Re: [chirp_users] Windows 10 and CHIRP
by N7TZK 08 Jun '15

08 Jun '15

Many thanks for the quick replies regarding Win 10 and Chirp/Prolific. If only it was so easy to keep my Windows Media Center after the "upgrade"! Dave

1 0