- Users - lists.chirpmyradio.com

[chirp_users] yaesu ft 2800m
by fergy1 11 Aug '16

11 Aug '16

chirp just will not read header or communicate with radio tried ftdi cables plus serial cables chines cables 3 xp computers plus win 7 run chip check cables show up good radio goes to clone then comes up error chirp says cant read header error cables all work with ft 1802 all other radios program fine must be a weird ft 2800 been trying to program this radio for over 10 years tired of programming manually ill send the bug attachment if any one can figure out whats going on thanks --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

1 0

[chirp_users] removel of Plan
by bernard.dowley＠sky.com 11 Aug '16

11 Aug '16

Hi Using Chirp with either a Baofeng UV-5R or Intek KT 980HP is it possible to remove the 2 metre and 70 centimetre facility so that only the user programmed frequencies are available for use. Any help appreciated Regards BernieBernard Dowley

4 9

[chirp_users] Baofeng data to Yaesu
by djkwasny＠aol.com 10 Aug '16

10 Aug '16

Hi, I am trying to move Baofeng data to a Yaesu ft-7900R. If I load the Baofeng data into Chirp It selects Baofeng in the upload box and I cannot change it as it is grayed out. Any help anyone can provide will be appreciated. Thanks, Joe - K5WAS

5 5

Re: [chirp_users] General: Updating CHIRP
by Kc6iih＠aol.com 10 Aug '16

10 Aug '16

sometimes every day at other times it might be a week or more. they don't seem to have a set schedule. before I use CHIRP I check for any updates. Jock KC6IIH In a message dated 8/10/2016 6:20:17 P.M. Pacific Daylight Time, pavilion(a)pinefields.com writes: How are non-alpha/beta updates handled? That is, given all the daily releases (i.e., alpha testing), is there ever a "looks pretty stable to me" release? What I've got now does what I need done (very well - good on ya!). OTOH, a new release might do something useful that I don't have in the release I use. But I prefer not to do alpha or beta testing if I can avoid it. So... how often does a stable release come out? 73 de KC3DOO Rick _______________________________________________ chirp_users mailing list chirp_users(a)intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Jock at kc6iih(a)aol.com To unsubscribe, send an email to chirp_users-unsubscribe(a)intrepid.danplanet.com

2 1

[chirp_users] Baofeng to Yaesu
by djkwasny＠aol.com 10 Aug '16

10 Aug '16

I have tried to copy and paste, the copy goes fine but the paste doesn't. Without importing a file there is no grid to paste to. What am I missing. Thanks, Joe - K5WAS

2 1

Re: [chirp_users] B to Y
by Aubrey Turner 10 Aug '16

10 Aug '16

Doesn't really matter what's in the Yaesu but you have to download from it so that CHIRP understands its memory and settings layout. Once you have a tab with the Yaesu download data you can paste the data from the Baofeng into it. Then you can upload from the Yaesu tab to the Yaesu radio. On Aug 10, 2016 1:12 PM, "Kwas via chirp_users" < chirp_users(a)intrepid.danplanet.com> wrote: I have nothing in the Yaesu now. When I import a Baofeng the proplem is as explained in my first post. Joe _______________________________________________ chirp_users mailing list chirp_users(a)intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Aubrey Turner at aubrey.c.turner(a)gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@ intrepid.danplanet.com

1 0

[chirp_users] B to Y
by djkwasny＠aol.com 10 Aug '16

10 Aug '16

I have nothing in the Yaesu now. When I import a Baofeng the proplem is as explained in my first post. Joe

1 0

[chirp_users] Yaesu FT-8900 Not Accepting File
by Deane Bouvier 09 Aug '16

09 Aug '16

The FT-8900 returns an error message that it doesn't ack block 0 when I try to write to it. That is after a successful read. The USB to serial device is operating properly and Chirp is pointed to the correct Com Port. OS is Windows 7. I have been successful before so this seems to be a new problem. Any help would be appreciated. Thanks. N5DQ

1 0

[chirp_users] ft 2800m
by Richard 09 Aug '16

09 Aug '16

radio keeps coming up failed to read header cable and everything works on my ft 1802 so cant be setup is their a bug or something wrong with the program it never did work for this radio fine with all my others thanks --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

2 1

[chirp_users] Baofeng UV-6R
by stephen johnston 09 Aug '16

09 Aug '16

i know this radio is not supported yet, i have some info to help driver writers. the "magic string" is: "\x50\xBB\xFF\x20\x14\x11\x22" and the firmware is: ["HDBF230"] i have put these into the driver, but i am now stuck with this: -------------------------- [2016-08-08 14:12:07,872] chirp.ui.mainapp - DEBUG: User selected Baofeng UV-6R on port /dev/ttyUSB0 [2016-08-08 14:12:07,912] chirp.ui.clone - DEBUG: Clone thread started [2016-08-08 14:12:07,916] chirp.drivers.uv5r - INFO: Sending Magic: 000: 50 bb ff 20 14 11 22 00 P.....". [2016-08-08 14:12:09,045] chirp.drivers.uv5r - INFO: Ident: 000: aa 36 74 04 00 05 20 dd .6t..... [2016-08-08 14:12:09,296] chirp.ui.reporting - INFO: Reporting disabled [2016-08-08 14:12:09,297] chirp.ui.reporting - DEBUG: Reporting is disabled [2016-08-08 14:12:09,297] chirp.ui.common - ERROR: -- Exception: -- [2016-08-08 14:12:09,297] chirp.ui.common - ERROR: Traceback (most recent call last): File "/home/user/Downloads/radio/chirp/chirp-daily-20160802/chirp/ui/clone.py", line 249, in run self.__radio.sync_in() File "/home/user/Downloads/radio/chirp/chirp-daily-20160802/chirp/drivers/uv5r.py", line 675, in sync_in self._mmap = _do_download(self) File "/home/user/Downloads/radio/chirp/chirp-daily-20160802/chirp/drivers/uv5r.py", line 491, in _do_download radio_version = _get_radio_firmware_version(radio) File "/home/user/Downloads/radio/chirp/chirp-daily-20160802/chirp/drivers/uv5r.py", line 467, in _get_radio_firmware_version block2 = _read_block(radio, 0x1F00, 0x40, False) File "/home/user/Downloads/radio/chirp/chirp-daily-20160802/chirp/drivers/uv5r.py", line 436, in _read_block "Radio refused to send second block 0x%04x" % start) RadioError: Radio refused to send second block 0x1f00 --------------------------- does anybody have any idea's what to try next? i dont know python and cant really follow the code in the driver anyway! -- stephen johnston

2 1

[chirp_users] Introduction & Question
by Richard B. Emerson 08 Aug '16

08 Aug '16

Hello - I'm new to 2m and just started groping my way into what I need to know. I've held a General ticket for a couple of years. However, my main interest is PACTOR comms via Winlink while aboard our sailboat (/MM or /C6A). We've been to the Bahamas few times; having Winlink to back up other options is great. I inherited a Baofeng UV-5RE Plus from a friend, sadly SK. At this point I'm able to program the radio, etc. My biggest concern is a way to organize the entries. That is, being NW of Philadelphia, I want the 2m repeaters for the counties/areas I'm most likely to be in. So far, so good. Repeater Book is my friend. But! Is there some way to tag a cluster of calls with at least the country name in some form? I guess I could add a two letter code to the back of each call, but if I'm missing a useful option...? 73 de KC3DOO Rick Emerson

6 8

Re: [chirp_users] Introduction & Question
by NP3AR 08 Aug '16

08 Aug '16

My two cents. I use on my Baofeng HT this way: first three characters are the last digit in mhz followed by the khz digits and then the first 3 letters of the location. Sent from my Samsung Galaxy Tab®4 -------- Original message -------- From: "Richard B. Emerson" <pavilion(a)pinefields.com> Date:08/08/2016 7:05 PM (GMT-04:00) To: Discussion of CHIRP <chirp_users(a)intrepid.danplanet.com> Subject: Re: [chirp_users] Introduction & Question I guess being a newbie is showing, huh. I figured that seeing the call beats the location. OTOH, if I do make an initial call, it's my call (KC3DOO listening) or whoever I'm talking with, not the repeater's call. Hmmm... gotta think about that. At least CHIRP makes it much easier to enter settings. If ever there was a manual designed to confuse and obfuscate, the UV-5etc. manual is it. 73 de KC3DOO PS If anyone is interested in operating in the Bahamas, there's no reciprocity. The "license" application process isn't that hard. The woman who handles the applications very helpful. Drop me a note and I can fill in the details. I assume there are no repeaters, except maybe on New Providence (the island Nassau's on). Otherwise, it's operating simplex. _______________________________________________ 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

5 4

[chirp_users] AUTO: Adam K Collins is out of the office. (returning 08/15/2016)
by Adam_K_Collins＠graco.com 08 Aug '16

08 Aug '16

I am out of the office until 08/15/2016. I will respond to your message when I return. thanks! Note: This is an automated response to your message "Re: [chirp_users] Kenwood TK-762H" sent on 08/08/2016 10:35:43. This is the only notification you will receive while this person is away.

1 0

[chirp_users] FT-8900 will not upload
by R Datus 07 Aug '16

07 Aug '16

Yaesu FT-8900 will download to CHIRP, but will not upload. I get "an error has occurred radio did not ack block at (various numbers, e.g., 520, 584, 9854)" Please help me find a solution to using Chirp to program the FT-8900 that my wife worked extra hours to give me for HER birthday. HRO wants another $40 for programming software. Please help. KD0RLZ@ yahoo.com

2 1

[chirp_users] USB LiveBoot ?
by Bruce LeGrande 06 Aug '16

06 Aug '16

Just looked at the LiveCD image file for Chirp and woah!, that seems MUCH larger than it needs to be... (600+Mb) I'm interested in setting up a bootable USB stick with an autorun Chirp session for programming my Baofeng UV-82HP. I'm getting the 'Unsupported firmware version: "N82-33 US2S35 /Uffffffff/Uffffffff" with Chirp v0.4.0 The hardware is an ACER AspireOne NetBook (AMD64). It would seem that this project SHOULD fit on a 1-Gb USB Stick with plenty of room to spare to store radio programming data. Anyone have an ISO for this... I'm getting Puppy Linux and DSLinux Live boot ISO's right now in case I have to use an IMG burn file of Chirp. PuppyLinux ISO is only 225Mb, and I think DamnSmallLinux is even smaller. And on a second note... Is anyone working on an Android App port of Chirp ? Sure would be nice to prgm the radios with a SmartPhone or Tablet... Of course, that would require a cable with a MicroUSB connector. 73 4 now Bruce Sent from BlueMail

11 27

[chirp_users] Baofeng UV6S83
by Marcus van Dam 06 Aug '16

06 Aug '16

Hi, I recently bought a Baofeng UV-6 at the 409shop, which I all exited hooked up and figured out that it gave the dreaded 'Radio did not respond' and 'Refused to clone' messages. After some digging and comparing to the Baofeng windows tool (UV6UV7_CPS) I found the following; When you try to read the radio with Chirp, the magic is send (50 bb ff 20 12 08 23 00), the ACK is received, 0x02 is send, and from here, Chirp seems to expect 8 bytes of data as ident (ident = serial.read(8)), but looking at the serial traffic of the BF software, the radio sends 12 bytes (AA 01 01 36 01 74 01 04 00 05 20 DD). As Chirp only read 8, the next write and read will not return the expected results and the clone fails. I tried to increase that initial ident read size in Chirp to 12 bytes (ident = serial.read(12)), which got me to the "Incorrect 'Model' selected" error, saying in the debug, that the model is actually ' Ver UV6S83 '. In a desperate attempt I added "UV6S83" to the array "BASETYPE_UV6", which allowed Chirp to read the data, but in the end it could not make sense of the content. This is where my debug skills ended and I hope your expertise comes in. I have attached a couple of captures to this email; UV6S83-CHIRP_8bytes-ident.txt = Chirp, all default trying to read the UV-6 UV6S83-CHIRP_12bytes-ident.txt = Chirp, modified the ident length and added the basetype as an UV-6 UV6S83-UV6UV7.txt = Original Baofeng software doing a full dump. The modified Chirp dump contains an interesting snippet in the first memory block: BAOFENG UV-5R .. Ver UV6S83 Would the have build a Frankenstein device? Let me know if there is anything I can do to help debugging. // Marcus

3 4

[chirp_users] FT-8900 will not upload from Chirp
by R Datus 06 Aug '16

06 Aug '16

Yaesu FT-8900 will download to CHIRP, but will not upload. I get "an error has occurred radio did not ack block at (various numbers, e.g., 520, 584, 9854)" Please help me find a solution to using Chirp to program the FT-8900 that my wife worked extra hours to give me for HER birthday. HRO wants another $40 for programming software. Please help. KD0RLZ@ yahoo.com

1 0

[chirp_users] UV-82, Ubuntu 16.04 LTS, can't connect...
by David McGuire 06 Aug '16

06 Aug '16

Hello. I need some help with getting my UV-82 to talk with my laptop. I'm using Ubuntu 16.04 LTS and Chirp. It had been working prior to the upgrade to 16.04. Don't know what happened. Here is the message I receive: Failed to communicate with radio: 'Serial' object has no attribute 'setTimeout'. Here are my settings for the radio: - Port: /dev/ttyUSB0 - Vendor: Baofeng - Model: UV-82 I am using a genuine Baofeng USB cable. This was working very nicely, so I am sure it is a setting someplace. Any help is appreciated. 73 de David AE4LH

4 6

Re: [chirp_users] UV-82, Ubuntu 16.04 LTS, can't connect...
by Angus Ainslie 06 Aug '16

06 Aug '16

On 2016-08-06 07:30, David McGuire wrote: > python --version > > Python 2.7.12 > > ------------------------- > That should work. Check the pyserial version apt-cache policy python-serial > FROM: Angus Ainslie <angus(a)akkea.ca> > SENT: Saturday, August 6, 2016 8:28 AM > TO: Discussion of CHIRP > CC: David Buss; David McGuire > SUBJECT: Re: [chirp_users] UV-82, Ubuntu 16.04 LTS, can't connect... > > It shouldn't be a driver problem with Ubuntu. > > That message sounds more like a python version or pyserial version > problem. > > What do you get from > > python --version > > On 2016-08-06 07:13, David Buss wrote: >> Double check your cable driver. "Genuine Baofeng" is still a > prolific >> clone. Will need to be driver version 3.2.2.0 [1] >> >> -----Original Message----- >> From: David McGuire <leviticus25_9(a)hotmail.com> >> To: "chirp_users(a)intrepid.danplanet.com" >> <chirp_users(a)intrepid.danplanet.com> >> Sent: Sat, 06 Aug 2016 8:07 >> Subject: [chirp_users] UV-82, Ubuntu 16.04 LTS, can't connect... >> >> Hello. I need some help with getting my UV-82 to talk with my > laptop. >> I'm using Ubuntu 16.04 LTS and Chirp. >> >> It had been working prior to the upgrade to 16.04. Don't know what >> happened. >> >> Here is the message I receive: Failed to communicate with radio: >> 'Serial' object has no attribute 'setTimeout'. >> >> Here are my settings for the radio: >> >> - Port: /dev/ttyUSB0 >> >> - Vendor: Baofeng >> >> - Model: UV-82 >> >> I am using a genuine Baofeng USB cable. >> >> This was working very nicely, so I am sure it is a setting > someplace. >> >> >> Any help is appreciated. >> >> 73 de David AE4LH >> >> >> >> Links: >> ------ >> [1] http://3.2.2.0 >> >> _______________________________________________ >> chirp_users mailing list >> chirp_users(a)intrepid.danplanet.com >> http://intrepid.danplanet.com/mailman/listinfo/chirp_users >> This message was sent to Angus Ainslie at angus(a)akkea.ca >> To unsubscribe, send an email to >> chirp_users-unsubscribe(a)intrepid.danplanet.com

1 0

[chirp_users] Programming for
by Stan M 02 Aug '16

02 Aug '16

Anysecu TM 218?

2 1

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

02 Aug '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-20160802 A list of the changes included in this build (since the last daily) follows: Changes for Build #422 [Jim Unroe <rock.unroe(a)gmail.com>] [Luiton] Add Support for the Luiton LT-898UV Mobile Radio The LT-898UV mobile radio can be programmed using the Leixen VV-898 vendor/model selection. This pattach adds a LUITON LT-898UV vendor/model selection using the newly added (chirp_common.Alias) support. fixes #3705

1 0

[chirp_users] Is there a radio programming for dummies?
by Nigel A. Gunn G8IFF/W8IFF 01 Aug '16

01 Aug '16

Drop in and see me sometime and I'll sit down with you and explain. > Date: Mon, 1 Aug 2016 13:38:59 -0500 > From: "David Kimball" <david(a)lazycreek.com> > Subject: [chirp_users] Is there a radio programming for dummies? > To: <chirp_users(a)intrepid.danplanet.com> > Message-ID: <000f01d1ec23$f8346990$e89d3cb0$(a)lazycreek.com> > Content-Type: text/plain; charset="us-ascii" > > So, > > > > Very very new and was trying to program a new Baofebg GT-5TP. > > > > Found a radio in the drop down that appears to work on this model, UV-82HP. > > > > How do you remove a entry from the loc. I want to delete the information on > an entry. > > > > If I type 0.000 I get an error message. A blank also gives the same error. > > > > Dave

2 1

[chirp_users] Is there a radio programming for dummies?
by David Kimball 01 Aug '16

01 Aug '16

So, Very very new and was trying to program a new Baofebg GT-5TP. Found a radio in the drop down that appears to work on this model, UV-82HP. How do you remove a entry from the loc. I want to delete the information on an entry. If I type 0.000 I get an error message. A blank also gives the same error. Dave

2 2

[chirp_users] New Daily Build
by Build System 31 Jul '16

31 Jul '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-20160731 A list of the changes included in this build (since the last daily) follows: Changes for Build #419 [Pavel Milanes (CO7WT) <pavelmc(a)gmail.com>] [PATCH][Kenwood Serie 60G] Widen the band limits for some radios, fixes #3813 The OEM software for this radios can program it out of it's default band limits, some of the models has ranges of operations close but outside the ham bands. This patch widen the default band limits for this radios, allowing the programming of these for hamm radio use, some of the new limits are tested by me and others by Stephen GN5SWP, other are just guesses. Changes for Build #420 Changes for Build #421

1 0

[chirp_users] Baofeng x Misuta uv-82plus
by Brian Battison 30 Jul '16

30 Jul '16

Hi, I have just purchased as stated by seller the latest model Baofeng x Misuta uv-82plus, a new crossover version. The firmware version reads N822413 when switched on, and the S/N is uv-82 plus00086. I cannot find any information for programming software for this model and wanted to ask if I just treat it as the using the older uv-82 model information. Thank you. Regards. Brian. --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

3 4

[chirp_users] Website maintenance this weekend
by Dan Smith 29 Jul '16

29 Jul '16

Hi all, I need to move the CHIRP website to a new location, and I'm planning to do that this weekend. While it's down I will have a stub of a site up with working current-version download links for anyone that needs it during the transition. However, the main site with the wiki and issue trackers will be unavailable during that time. I apologize for the downtime, but it's the easiest way to do the move. Thanks for your understanding! --Dan

2 1

Re: [chirp_users] FTDI drivers
by kc6iih 27 Jul '16

27 Jul '16

It doesn't pay to be cheap with the cables . I have found thru experience that good cables like those from www.rtsystems are the best . Sent from my Samsung Galaxy Tab®|PRO -------- Original message -------- From: Jim Pruitt <jpruitt67(a)gmail.com> Date:07/26/2016 9:44 PM (GMT-08:00) To: Discussion of CHIRP <chirp_users(a)intrepid.danplanet.com> Subject: Re: [chirp_users] FTDI drivers Hello John. What you missed (or I did not make clear) was that when I switched cables to the real FTDI cable (also says Baoefeng) it worked. When I went back to the other cable (FTDI clone) the same GT3 (UR5 definitions) then it said radio was not responding. The only change was the cable itself. It works now but none of the 4 cheap cables that appear to be FTDI clones do not work. That was why I was looking for the old drivers and info as to which drivers worked with the FTDI copies. I also have an XP machine that I have to set up as well and that will be fun. Thank you. Jim Pruitt On Tue, Jul 26, 2016 at 5:21 PM, John LaMartina <JohnLa(a)usa.net> wrote: Jim, I don’t believe your issue is driver related. When you stated Win7 stated the cable was recognized and everything was working, I believe that is correct. The cable and driver are not the issue. The GT3 is more than likely the issue. http://www.miklor.com/COM/UV_ErrorMess.php#error1 Radio did Not Respond is stating the radio isn’t seeing the cable. You may need to trim the cable or the yellow rubber on the case. The lip on the yellow GT3 edge may be preventing some cables to plug in completely. I hope this assists. John Miklor From: chirp_users-bounces(a)intrepid.danplanet.com [mailto:chirp_users-bounces@intrepid.danplanet.com] On Behalf Of Jim Pruitt Sent: Tuesday, July 26, 2016 7:19 PM To: Discussion of CHIRP Subject: [chirp_users] FTDI drivers I set up my pc for the latest build of Chirp this past weekend. I ran into trouble as I went out and grabbed the (latest) drivers from FTDI as suggested. When I tried to upload the current list from my GT3's it reported that they were not responding. Windows 7 said the cable was recognized and everything was working. I fought this for several minutes then switched cables. Then it worked so the first cable had to have been a clone even though it had the Baeofeng stamp on it. I see some other posts with new users having trouble and it looks similar to what I was experiencing until I changed cables. This cable cost $21 (Amazon) compared to $3 for the other cables so I am sure others will have the non FTDI cables and not know it. I know that there has been a lot of discussion on here in the past about this. I didn't see a link on FTDI's site to get the older drivers that work with clone cables. Does anyone have that link for the older FTDI drivers that still work with FTDI clone cables? Is there any problem with replacing the new drivers with the older ones? Thank you. Jim Pruitt _______________________________________________ chirp_users mailing list chirp_users(a)intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Jim at jpruitt67(a)gmail.com To unsubscribe, send an email to chirp_users-unsubscribe(a)intrepid.danplanet.com

4 5

[chirp_users] FTDi, HT, driver or user issue? Help
by Dennis Yocom, President & CEO 27 Jul '16

27 Jul '16

John et. al.: I'm completely confused now. I bought one PC03 FTDI Authentic <https://www.amazon.com/gp/product/B00HUB0ONK/ref=oh_aui_detailpage_o04_s00? ie=UTF8&psc=1> Genuine USB Programming Cable for BaoFeng, Kenwood, etc from Amazon, which said, Sold by: <https://www.amazon.com/gp/help/seller/at-a-glance.html/ref=oh_aui_sellerpro file_o04_s00?ie=UTF8&isAmazonFulfilled=1&marketplaceSeller=1&orderID=115-982 3267-6753002&seller=AA3MGRC7F9EI2> BaoFeng Tech for $20.46 The cable, which doesn't have any ID on it anywhere (except for a USB symbol and something else near it which I don't recognize) was supposed to be the correct cable to use in programming a pair of new Baofeng F8HPs. With my Windows 7 machine, I got the "Radio did not respond" message about a dozen times. I've pushed that cable in so hard I surprised it didn't come out the other side. I realize I'm not the brightest crayon in the box, but does this sound like a cable issue, HT, user or a driver issue ( I've tried several times to manually install a driver with no luck)? The BaofengTech instructions with the cable indicate the cable was supposed to initiate the proper downloads, and it was supposed to be a snap. Can someone lighten this poor fool? DR Yocom - dryocom(a)comcast.net <javascript:window.top.ZmObjectManager.__doClickObject(document.getElementBy Id(%22OBJ_PREFIX_DWT2282_com_zimbra_email%22));> DR Yocom - Dennis(a)basiclifetraining.com

5 4

[chirp_users] FTDI drivers
by Jim Pruitt 27 Jul '16

27 Jul '16

I set up my pc for the latest build of Chirp this past weekend. I ran into trouble as I went out and grabbed the (latest) drivers from FTDI as suggested. When I tried to upload the current list from my GT3's it reported that they were not responding. Windows 7 said the cable was recognized and everything was working. I fought this for several minutes then switched cables. Then it worked so the first cable had to have been a clone even though it had the Baeofeng stamp on it. I see some other posts with new users having trouble and it looks similar to what I was experiencing until I changed cables. This cable cost $21 (Amazon) compared to $3 for the other cables so I am sure others will have the non FTDI cables and not know it. I know that there has been a lot of discussion on here in the past about this. I didn't see a link on FTDI's site to get the older drivers that work with clone cables. Does anyone have that link for the older FTDI drivers that still work with FTDI clone cables? Is there any problem with replacing the new drivers with the older ones? Thank you. Jim Pruitt

3 3

Re: [chirp_users] FTDI drivers
by awake 26 Jul '16

26 Jul '16

1 0

Re: [chirp_users] Default settings for programming
by Randy McKenzie 25 Jul '16

25 Jul '16

Is there a way to default chirp to settings such as "skip" for scan lists? With the slow scan rates of many of the radios, I only want to scan a few channels, by default it selects scan. Just a thought. Randy On Monday, July 25, 2016 1:37 PM, Randy McKenzie <kk4ej(a)yahoo.com> wrote: Is there a way to default chirp to settings such as "skip" for scan lists? With the slow scan rates of many of the radios, I only want to scan a few channels, by default it selects scan. Just a thought. Randy

2 1

[chirp_users] European characters in Windows user name
by Björn Ekelund 25 Jul '16

25 Jul '16

Chirp crashes/aborts when the Windows user name contains European/Cyrillic characters. The last line of the debug.log file reads: "UnicodeDecodeError: 'utf8' codec can't decode byte 0xf6 in position 9: invalid start byte" Is there a workaround? Like a command like option to set the file location to a location without "strange characters"? Changing the user name to something else isn't really an option since it used for other systems... Björn Ekelund SM7IUN

6 10

Re: [chirp_users] No response from radio, TM-V71 and DR-235, Debian
by guncrafter 25 Jul '16

25 Jul '16

Sent from my Samsung Galaxy smartphone. -------- Original message -------- From: Keith Murlless <kmurlless(a)gmail.com> Date:07-25-2016 6:08 AM (GMT-05:00) To: Discussion of CHIRP <chirp_users(a)intrepid.danplanet.com> Cc: Subject: Re: [chirp_users] No response from radio, TM-V71 and DR-235, Debian At the risk of offending our highly technical brethren, I'd like to compliment CHIRP for producing an excellent "plug - n-play" version for Mac. Honestly, aside from having to maintain separate files for each Baofeng firmware set, my experience in up/down-loading from Baofeng to Mac, via CHIRP, has truly been just that easy. Good thing too... The frustrations and technical details that you discuss in this thread are beyond me. Good luck with that... I will offer that cable quality has popped up in various threads as a likely culprit in the case of up/down-load fails Keith On Jul 24, 2016 23:56, "CN85rq" <chirp-info(a)aberle.net> wrote: Ken: Thanks for your suggestions. Since both radios are mobiles with serial ports, the PTT isn't an issue. I was testing with both USB-to-serial cables (with chips) and serial-to-serial cables (no chips). The CheckChipVersion appears to be Windoze-only (an OS I haven't had in over a decade), and I don't see an equivalent linux tool. Tom: I appreciate you pointing me in the right direction on breaking the problem in half, and the "ID" command for the TM-V71. I moved over to testing with a 3rd computer, one known to connect with my Kantronics 9612. Using the serial port monitor in Outpost PM and the linux minicom utility I was able to isolate issues, solve part of the problem, and better characterize the remaining difficulties. All: The dual-port MCS9865-based serial card on the Gigabyte GA-MA790X-UD4P motherboard uses /dev/ttyS1 and /dev/ttyS2. The USB-to-serial cable uses /dev/USB0 on both the Gigabyte motherboard and the Raspberry Pi. Both USB-to-serial cables (FTDI and unknown) and the Kenwood PG-5G PC Serial Programming Cable all work. Note to self: In order to make problem isolation easier, clearly mark the three special APC 940-0024C cables so they don't get mixed in with the other serial cables. So, chirp works with the Kenwood TM-V71 using both a straight serial cable and the both USB-to-serial cables. Neither chirp, minicom, nor the serial port monitor in Outpost PM will communicate with the Alinco DR-235 MkIII. In fact, when I put the mini-tester in line on the serial cable, there is no signal (neither a green nor a red LED lit) on the Receive Data line. This is true for all three computers using both cable types. Is a special cable needed for the Alinco DR-235 to work with chirp? Tom Hayward wrote on 07/24/2016 11:19 AM: > > You might try removing Chirp from the equation and test just the > serial port on the TM-V71. First, note the rate set in menu 519, > PC.SPD. Then launch a terminal emulator at this rate. Type ID and hit > enter. You should get the model number of the radio printed to your > console. If not, you've got a problem with your computer/USB serial > port, cable, or the radio's serial port. > > If you do get a response, move on to Chirp. Use only the latest daily > build, available on the PPA or here: > http://trac.chirp.danplanet.com/chirp_daily/LATEST/ > > Tom KD7LXL Ken Cone wrote on 07/24/2016 10:58 AM: > Hello, > In my recent experience programming an Yaesu FT60R, two issues popped up: > 1) finding the correct driver for the cable chipset, and 2) holding the PTT > button long enough. > The chipset driver information was here: > http://www.prolific.com.tw/US/ShowProduct.aspx?p_id=225&pcid=41 > > About half way down the page, in red is a link to an app that identified > the Prolific the chipset. Other chipset manufacturers may have similar > tools. > "Run PL2303 CheckChipVersion tool..." This helped tremendously in > identifying the correct driver. > Holding the PTT button long enough came from page 65 of the FT-60R manual, > in the section on Cloning. After resolving these two issues, I was able to > download memory contents to CHiRP, edit, and upload back to the HT. > > Hope this helps. > 73, > Ken > KI7EIH > > > Ken Cone > kencone(a)gmail.com > KI7EIH _______________________________________________ chirp_users mailing list chirp_users(a)intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Keith Murlless at kmurlless(a)gmail.com To unsubscribe, send an email to chirp_users-unsubscribe(a)intrepid.danplanet.com

1 0

[chirp_users] No response from radio, TM-V71 and DR-235, Debian
by CN85rq 25 Jul '16

25 Jul '16

These are my first attempts at using CHIRP and I'm not having much luck. I've tried connecting to two different radios from two different computers with a total of three different CHIRP versions and three different cables. I could easily be missing some tribal knowledge known to experienced users, so hopefully someone can point me in the right direction for a solution. CONFIGURATION #1 Computer: Gigabyte GA-MA790X-UD4P motherboard, MCS9865 serial card, running Debian 7 (Wheezy) Radio: Kenwood TM-V71, connected with Kenwood PG-5G PC Serial Programming Cable CHIRP Version: 0.1.12 (from the Debian repository) Symptom: “Download From Radio” results in a “No response from radio” message Additional Info: The timestamp on /dev/ttyS0 updates when the radio is turned on. CONFIGURATION #2 Computer: Raspberry Pi 1 Model B, running Raspian (Jesse) with Compass mods by NW Digital Radio Radio: Kenwood TM-V71, connected (first) with a generic USB-Serial cable (unknown chipset) and (second) with a Sabrent CB-FTDI USB-Serial cable (FTDI chipset) CHIRP Versions: (first) 0.4.0 and (second) chirp-daily-20160717 Symptom: “Download From Radio” results in a “No response from radio” message Additional Info: Tested with and without the “console=serial0,115200” setting in the /boot/cmdline.txt file Additional Info: Serial speed on radio tested at both 9600 and 19200 CONFIGURATION #3 Computer: Raspberry Pi 1 Model B, running Raspian (Jesse) with Compass mods by NW Digital Radio Radio: Alinco DR-235 MkIII, connected (first) with a generic USB-Serial cable (unknown chipset) and (second) with a Sabrent CB-FTDI USB-Serial cable (FTDI chipset) CHIRP Versions: (first) 0.4.0 and (second) chirp-daily-20160717 Symptom: “Download From Radio” results in a “No response from radio” message Additional Info: Tested without the “console=serial0,115200” setting in the /boot/cmdline.txt file CONSOLE WINDOW OUTPUT captured for Configuration #2 root@compass:/usr/local/bin/chirp-daily-20160717# ./chirpw (process:911): Gtk-WARNING **: Locale not supported by C library. Using the fallback 'C' locale. ./chirpw:135: GtkWarning: gtk_window_realize_icon: assertion 'info->icon_pixmap == NULL' failed a.show() ERROR: Timeout waiting for data ERROR: Giving up ERROR: Timeout waiting for data ERROR: Giving up ERROR: Timeout waiting for data ERROR: Giving up ERROR: Timeout waiting for data ERROR: Giving up ERROR: Timeout waiting for data ERROR: Giving up ERROR: Timeout waiting for data ERROR: Giving up ERROR: Timeout waiting for data ERROR: Giving up ERROR: Timeout waiting for data ERROR: Giving up Traceback (most recent call last): File "/usr/local/bin/chirp-daily-20160717/chirp/ui/mainapp.py", line 1430, in mh self.do_download(*args) File "/usr/local/bin/chirp-daily-20160717/chirp/ui/mainapp.py", line 691, in do_download radio = settings.radio_class(ser) File "/usr/local/bin/chirp-daily-20160717/chirp/drivers/kenwood_live.py", line 159, in __init__ radio_id = get_id(self.pipe) File "/usr/local/bin/chirp-daily-20160717/chirp/drivers/kenwood_live.py", line 121, in get_id raise errors.RadioError("No response from radio") chirp.errors.RadioError: No response from radio root@compass:/usr/local/bin/chirp-daily-20160717# CONSOLE WINDOW OUTPUT captured for Configuration #3 root@compass:/usr/local/bin/chirp-daily-20160717# ./chirpw (process:980): Gtk-WARNING **: Locale not supported by C library. Using the fallback 'C' locale. ./chirpw:135: GtkWarning: gtk_window_realize_icon: assertion 'info->icon_pixmap == NULL' failed a.show() ERROR: -- Exception: -- ERROR: Traceback (most recent call last): File "/usr/local/bin/chirp-daily-20160717/chirp/ui/clone.py", line 249, in run self.__radio.sync_in() File "/usr/local/bin/chirp-daily-20160717/chirp/drivers/alinco.py", line 196, in sync_in self._mmap = self._download(self._memsize) File "/usr/local/bin/chirp-daily-20160717/chirp/drivers/alinco.py", line 138, in _download data += self._download_chunk(addr) File "/usr/local/bin/chirp-daily-20160717/chirp/drivers/alinco.py", line 116, in _download_chunk raise errors.RadioError("No response from radio") RadioError: No response from radio ERROR: ---------------- ERROR: Clone failed: No response from radio ERROR: --- Exception Dialog: No response from radio --- ERROR: None ERROR: ---------------------------- root@compass:/usr/local/bin/chirp-daily-20160717#

5 5

[chirp_users] YEASU FT-991
by Jon G 22 Jul '16

22 Jul '16

Hi Dan, Any chance that the Yaesu FT-991 will be added to CHIRP in the future? Love CHIRP!! Thanks for all your work. Jon Goodson KM4UJP Sent from Mail for Windows 10

4 5

[chirp_users] Establishing a radio connection
by Tom Simonson 18 Jul '16

18 Jul '16

I have been using the CHIRP software for about a year and a half, mainly with Chinese radios: Baofeng and B-Tech, and have a question about the process of connecting the radios for upload/download. I have programmed a number of 888S radios and UV-82C models, and recently bought a UV-82HP. I found the 82HP fussier about establishing a connection for upload/download than the other radios, and required multiple tries - particularly for an upload. This is using the same FTDI cable used with the other handheld radios. When requesting an upload or download, two windows pop up: the first indicates the type of radio and comm port, followed by a window giving instructions to connect the radio, power it up, possibly going to full volume etc. I believe that there is a checkbox to suppress the second window (which I have not checked). My question is about the need for power cycling the radio, and the timing of doing it. Does this play a role in the connection? For example, suppose that one has downloaded settings from a radio, modified them (by editing or importing settings), and will then upload the settings back to the same radio. Is anything accomplished by power cycling the radio? --- Tom Simonson, Alameda CA (tom(a)tsimonson.com)

2 1

[chirp_users] KT UV980
by fergy 18 Jul '16

18 Jul '16

Tried your QYT KT UV 980 software did not work Shuts radio off & on then comes up error reading from radio Chines Software works with cable so cable must be ok The radio was one of the first ones bought 2015 Could their be other problems Thanks

2 1

[chirp_users] New Daily Build
by Build System 17 Jul '16

17 Jul '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-20160717 A list of the changes included in this build (since the last daily) follows: Changes for Build #418 [Pavel Milanes (CO7WT) <pavelmc(a)gmail.com>] [PATCH][QYT-KT8900] Add a newvariant of this radios, fixes #3821 A new variant of this radios is on the wild, this adds the ID of it to mange it on Chirp. 73 Pavel CO7WT.

1 0

[chirp_users] MAC OS X 10.7.5
by John Benson 15 Jul '16

15 Jul '16

I am having a really difficult time trying to use Chirp. I moved from a Windows based program to MAC. The Operating system is X 10.7.5. Since this is an used system, I found out in hindsight I am not able to upgrade the software. I noticed Chirp is requiring OS X 10.8. (or latest version). Can anyone provide any insight as to an earlier Chirp version that I can use with this system. This is my first MAC system, I am learning via School of hard-knocks, which is proving challenging to say the least! Thanks in advance, John B. (KB3YWN)

4 3

[chirp_users] Yaesu VX-3R CHIRP/cable issue?
by bmw 15 Jul '16

15 Jul '16

I have one of the "proper" cables (https://www.valley-ent.com/store/yaesu-usb-ftdi-radio-programming-cable-ft-…), which works with my Yaesu FT-60R, but I can't get CHIRP working with my brand-new Yaesu VX-3R. Same computer (Windows 8.1), same driver, no issues with the FT-60R, but when I follow the CHIRP instructions on downloading the image from the radio, my VX-3R just sits on the "--TX--" screen, then gets an ERROR message. CHIRP then says it couldn't communicate with the radio. Is there some button press step or procedure I'm missing out on? Known issues with the cable (that is "supposed" to work with both radios)? Thanks for any suggestions. PS This message may look familiar, since I posted the same question in eham and RR forums. After doing so I thought I'd just go to the CHIRP source.

1 2

[chirp_users] KT-8900R
by Marc 15 Jul '16

15 Jul '16

I see that this radio is supported and would like to know if anyone has any experience with it? Will CHIRP allow permanent modifications to the band edge limits, particularly 220, as the radio is shipped 240-260 MHz? Will the radio operate with 220 in one VFO and 440 in the other? Thanks, Marc

4 3

[chirp_users] Newly Released Radio Gets Same Day CHIRP Support
by Jim Unroe 13 Jul '16

13 Jul '16

13-July-2016 - Baofeng Tech releases BTECH UV-50X3 tri-band mobile radio - CHIRP daily build provides nearly full support for the UV-50X3 I wish to thank Baofeng Tech for supplying a pre-production radio sample for use in the development of the CHIRP driver. I spent a lot of time over the last 4+ weeks quietly poking at the memory of this radio. I also want to thank the members of the [chirp_devel] mailing list that provided help in one way or another. You guys are a great resourse. Baofeng Tech must have liked the result, their website states "The UV-50X3 is the first radio to exclusively only use CHIRP software for programming." To find out more about this radio you can visit... UV-50X3 product detail page: https://baofengtech.com/uv-50x3 Miklor.com UV-50X3 review: http://www.miklor.com/COM/Review_50X3.php Jim KC9HI

2 1

Re: [chirp_users] Joey Girves
by Fred Erickson 13 Jul '16

13 Jul '16

On Tue, 12 Jul 2016 20:09:09 -0800 Alice Baker <albaker(a)gci.net> wrote: > Fred, > > Do you know anything about this person? > > Alice Hi Alice, I've never head of him. Have you asked anyone in the Moose Horn ARC? I don't know how active it is but the trustee is KL7AN. Ooops. I see he has no email in QRZ. Maybe someone else living on the Kenai might know? Fred

2 1

[chirp_users] Help
by Marvin Barnes 13 Jul '16

13 Jul '16

I have posted this already but no responses. Looking for a kind soul to help me. I sent the following to RadioReference: I have a Baofeg UV-5r and am using CHIRP to program it. When I go to Query from Data Source and select Radio Reference it asks me for my logon and password and a zip code. If I enter my old zip code of 78121 (La Vernia) I get a list of La Vernia frequencies. However if I enter 83301 which is where I live now I get the hour glass forever and really it is forever. How do I get the list from 83301 to come to me. I have changed my RR to show Idaho and even have select the area and specific agencies to watch. So what am I doing wrong. They replied: We aren't sure why that is occurring. Have you tried contacting CHIRP support for support of their software? Is there anyone out there who could help me please? Marvin Barnes

4 3

[chirp_users] New Daily Build
by Build System 13 Jul '16

13 Jul '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-20160713 A list of the changes included in this build (since the last daily) follows: Changes for Build #417 [Jim Unroe <rock.unroe(a)gmail.com>] [UV-50X3] Add Support for BTech UV-50X3 - Basic Settings(continued) This patch adds the remaining UV-50X3 basic settings. related to #3815 [Jim Unroe <rock.unroe(a)gmail.com>] [UV-50X3] Add Support for BTech UV-50X3 - DTMF Settings (bug fix) This patch fixes a bug in the UV-50X3 DTMF settings. related to #3815 [Jim Unroe <rock.unroe(a)gmail.com>] [UV-50X3] Add Support for BTech UV-50X3 - DTMF Settings This patch adds the UV-50X3 DTMF settings. Also return "elif element.value.get_mutable():" back to its proper position (it was accidentally moved in the last patch). related to #3815 [Jim Unroe <rock.unroe(a)gmail.com>] [UV-50X3] Add Support for BTech UV-50X3 - Work Mode Settings This patch adds the UV-50X3 work mode settings. related to #3815 [Jim Unroe <rock.unroe(a)gmail.com>] [UV-50X3] Add Support for BTech UV-50X3 - Other Settings This patch adds the UV-50X3 miscellaneous settings. related to #3815 [Jim Unroe <rock.unroe(a)gmail.com>] [UV-50X3] Add Support for BTech UV-50X3 - Basic Settings This patch adds the UV-50X3 settings that correspond to the radio's built in SET menu. related to #3815 [Dan Smith <dsmith(a)danplanet.com>] Add BTECH UV-50X3 image Related to #3815 [Jim Unroe <rock.unroe(a)gmail.com>] [UV-50X3] Add Support for BTech UV-50X3 This patch adds basic support (500 left memories/500 right memories) plus all per-channel settings. It also and exposes the structures that will be used to add settings in future patches. related to #3815

1 0

[chirp_users] QYT8900 or Mini-8900
by Adrian Mundy 11 Jul '16

11 Jul '16

Hi all. New to this group, but would appreciate some assistance please. I have used the latest software and can read, and probably write to a QTY 8900, but I am having problems with the Mini-8900 in that it sometimes it will not see the com port, and more often, will not enter into the clone mode of the radio. The cable is a purpose made commercial cable, and with the 2 radios side by side, I have made all the settings the same from what I can see. The settings are Waccom and mini-8900 Am I missing something Kind regards Adrian Mundy2E0LWR

2 3

[chirp_users] Cannot get BF-F8HP Radio to communicate with Mac OS 10.8.5
by Tom Massoll 09 Jul '16

09 Jul '16

I am new to Hand Held HAM radio and have a ton of trouble getting the radio to connect with the computer. Radio is BF-F8HP Operating system is Mac 10.8.5 I have installed everything Instructed to from the Chirp site. including the osx-pl2303 installer and the python runtime files I start Chirp plug in the cable, and then the radio, and finally turn on the radio I then select Radio > Download from radio select Port (and there are several to select from: 1. /dev/cu.Bluetooth-modem 2. /dev/cu.Bluetooth-Serial-1 3. /dev/cu.Bluetooth-Serial-2 4. /dev/cu.Bluetooth-(myname)-Wireless-iAP 5. /dev/cu.Bluetooth-PDA-Sync All of which result in 1. Chirp starts processing a gives error 16 Resource busy could not open port /dev/cu.Bluetooth-Modem 2. for serial-1 it appears to start cloning and then reports: radio did not respond 3. for serial-2 it appears to start cloning and then reports: radio did not respond 4. for Bluetooth (myname) Wireless-iAP it appears to start cloning and then reports: radio did not respond 5. could not open port /dev/cu.Bluetooth-PDA-Sync: [Errno 16] Resource busy: '/dev/cu.Bluetooth-PDA-Sync' Could anyone help me here, thanks, Tom

6 8

[chirp_users] Driver
by Gary Runningbear 08 Jul '16

08 Jul '16

I just picked up a win 10 tablet. I have chirp up and running but I need the driver for the programming cable and I forgot where to get it. Can someone help? Thanks, Gary N8GPZ

6 11

Re: [chirp_users] Cannot get BF-F8HP Radio to communicate with Mac OS 10.8.5
by John Schubert 08 Jul '16

08 Jul '16

On 7/7/16, Bill Bartilson<bill(a)mandytech.com> > > Just for reference: https://amzn.com/B00HUB0ONK > > I got this cable with my BF-F8HP in May, and it works splendidly on OSX 10.11 > with no driver installation needed. The port simply shows up in the list. I > specifically ordered that particular cable from that particular vendor on the > advice of others who had success... who had also been frustrated with other > cables. The temptation to order one of the cheaper ones was great, but for > $20 I've never had any trouble, was well worth it. > > 73, Bill +1 I'm using this cable w/OSX 10.9.5, no drivers needed, no problems. Don't waste your time w/cheap imitations... 73, John

1 0

[chirp_users] Cannot Roll Back Prolific Driver
by Rev. David E. Hamm 08 Jul '16

08 Jul '16

Last year, I programmed a Baofeng UV5R5 for a friend. I have been asked to program another Baofeng UV5R5. I have the standard Baofeng Programming Cable, BF-888S. For some reason, I cannot get Prolific driver version 3.2.0 to install. Every time I deinstall version 3.6.81.357 and try to reinstall version 3.2.0, I end up with 3.6.81.357 again. I have tried using the CD that came with the cable as well as the version 3.2.0 driver found at http://www.miklor.com/COM/UV_Drivers.php. Could somebody please give me a step-by-step as to how to install the version 3.2.0 driver? The "Roll Back" driver version button is greyed-out. Thanks in advance for help with this perplexing problem. Theoretically, this should be easy. 73, Dave K4EET

2 1

[chirp_users] TYT TH-9800(B) 220MHz
by Matthew Poertner 07 Jul '16

07 Jul '16

Hi, I have the 220 version of this quad band radio. This one has 220 instead of 440. I would love to see this specific model supported. I see someone added a "bug" request #3367 but should I start a "New Model Request" instead? I just don't want to cause any trouble with making duplicate requests. Thanks! Matt - K6PC

2 2

[chirp_users] Kenwood NX 320-k2
by beachwoodpeter＠gmail.com 07 Jul '16

07 Jul '16

Does know how to download the channels from a Kenwood NX 320-K2. Peter Wilcox Beachwood Productions Beachwoodproduction.com

3 2

[chirp_users] BF-F9V2+ Programming
by William Thompson 07 Jul '16

07 Jul '16

I'm helping a friend program his new Baofeng BF-F0V2+ and n we're receiving a "experimental firmware error". Has a version been released for this radio? 73, Bill KK4ZIU

2 1

[chirp_users] Problem retrieving freqs from RadioReference
by Marvin Barnes 06 Jul '16

06 Jul '16

Greetings, I sent the following to RadioReference: I have a Baofeg UV-5r and am using CHIRP to program it. When I go to Query from Data Source and select Radio Reference it asks me for my logon and password and a zip code. If I enter my old zip code of 78121 (La Vernia) I get a list of La Vernia frequencies. However if I enter 83301 which is where I live now I get the hour glass forever and really it is forever. How do I get the list from 83301 to come to me. I have changed my RR to show Idaho and even have select the area and specific agencies to watch. So what am I doing wrong. They replied: We aren't sure why that is occurring. Have you tried contacting CHIRP support for support of their software? Is there anyone out there who could help me please? Thanks. Marvin Barnes

1 0

[chirp_users] Icom ic-t70
by Adam_K_Collins＠graco.com 06 Jul '16

06 Jul '16

Hi, I'm looking for help with my ic-t70. For months I have been trying to get an image file into Chirp. I have confirmed correct drivers, COM ports, and no faulty cables. All I ever get is "failed to communicate with radio, unexpected response from radio." Also, I'm using Windows 10. My cables are from Valley Enterprises. I also have a cable for my Yaesu 817-ND and this works flawlessly. It seems I've eliminated all but a bad radio, or a programming issue. My radio is brand new and seems to function perfectly. Does anyone have any history with this... something to help? Thanks, ——————————————————————————— Adam Collins

4 7

[chirp_users] New Daily Build
by Build System 06 Jul '16

06 Jul '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-20160706 A list of the changes included in this build (since the last daily) follows: Changes for Build #416 [Tom Hayward <tom(a)tomh.us>] [ui] Replace / with _ in default filenames. Fixes #3797. Related to #3753 The FT-857/897 driver has a slash in the model name. When used in the filename, this slash is interpreted as a directory on Linux and implodes on Windows. Neither is intended behavior. This patch substitues an underscore for a slash when generating a default filename.

1 0

[chirp_users] unable to save img files
by GEO Badger 05 Jul '16

05 Jul '16

I'm on win10. I read the radio, FT-857D, then try to save the file, no joy. Doesn't work as a "save" or "save as". I can export to csv only. --- Ciao baby, catch you on the flip side. GEO http://www.w3ab.org Time flies like an arrow, fruit flies like a banana.

3 2

[chirp_users] New Daily Build
by Build System 03 Jul '16

03 Jul '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-20160703 A list of the changes included in this build (since the last daily) follows: Changes for Build #415 [Pavel Milanes (CO7WT) <pavelmc(a)gmail.com>] [PATCH][Zastone MP-300] Add support for the Zastone MP-300 radio, fixes #3783 It's a clone of a early versions of the QYT KT8900.

1 0

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

02 Jul '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-20160702 A list of the changes included in this build (since the last daily) follows: Changes for Build #413 [Tom Hayward <tom(a)tomh.us>] [TH-K2] Correct channel number bounds from 1-50 to 0-49. #2575 [Dan Smith <dsmith(a)danplanet.com>] Add HobbyPCB RS-UV3 Support Closes #3781 Changes for Build #414 [Dan Smith <dsmith(a)danplanet.com>] Allow recalling a memory channel on HobbyPCB This is rather unconventional for a chirp driver, but otherwise, you would need to use another tool to actually select a channel. Also, fix running in a test environment. Related to #3781

2 1

[chirp_users] Command-line Linux
by Mike Ray 01 Jul '16

01 Jul '16

Hello. Just joined, so, this is probably a question that has been asked before but here goes. I just bought a Baofeng UV5R and I want to be able to program it from the Linux command-line. Just uploading, downloading and editing memory channels etc. I don't really want to do this either from Windows or from the Linux GUI as I'm a blind user and it's my experience that a lot of these applications are not accessible. Particularly on Linux as unless it's written in GTK it'll be almost inevitably impossible for me to use. Mike G4XBF -- Michael A. Ray Analyst/Programmer Witley, Surrey, South-east UK Eyes-free Linux: http://eyesfreelinux.ninja/ Raspberry VI: http://www.raspberryvi.org/

4 6

[chirp_users] CSV File - No Channels Found
by Robert 01 Jul '16

01 Jul '16

I've been using Chirp for years on several radios and have successfully uploaded a multitude of CSV files. However, I just got a new radio – the TYT TH 9800. I've already loaded several CSV files successfully but when I try to add a new file for just the AMSAT birds I'm getting an error of "no channels found." I cannot even find a reference to "channels" as a header, or anywhere from Uncle Google that answers my questions. I've attached the file I'm trying to import. Suggestions welcome, 73 de Robert K3RRR

2 2

[chirp_users] Newbie questions - export/import in CSV
by Stormy 29 Jun '16

29 Jun '16

Hi there, So, got the UV-5RHP, and I hear everyone laughing, what diff do these letters at the end, anyways, it seems to be true 3-power with original UV-5R body: http://www.aliexpress.com/item/Real-8W-BAOFENG-UV-5R-High-Power-Walkie-Talk… Now, is there a way in chirp to: 1) change ALL channels to LOW or HIGH/MED ? it seems very tedious to do one by one, and even if you do, next import from CSV overwrites all values to high it seems. 2) In CSV format power field does not appear to be present, is there a way to export/import POWER field? 3) In CSV there are 4 extra fields compared to software, what are they used for? | Comment | URCALL | RPT1CALL | RPT2CALL | " thanks.

3 4

[chirp_users] Changing Power Settings in Chirp csv file
by Jon G 28 Jun '16

28 Jun '16

*I think the easiest way to make large changes, a whole column for example is to open the csv file in Excel, make the change to the column them save as the same csv file.* *Reopen in Chirp and viola! Change is there.* *Dr. Jonathan Goodson*

2 1

Re: [chirp_users] Newbie questions - export/import in CSV
by Rich Messeder 28 Jun '16

28 Jun '16

I bought what appears to be the same unit, but labeled UV-5RTP (for tri-power, I presume?). Jim's directions work for me. In addition, note that once those channels are programmed, then they cannot be changed from the radio controls. However, You /can/ temporarily change the power level. Press #-lock to cycle through the power levels. It seems that once you choose a power level this way, the power setting remains until you reset the power level, turn the radio off|on again, or change programmed channels. In the latter case, the power level goes to the power level programmed for the new channel. I keep mine all programmed to low level, and cycle to higher levels as required. In fact, I wish that the lowest level were 0.5 W, not 1 W. Could not find a way to hack the radio to change that. ~R~ NE1EE Short email? No html? Here's why: http://emailcharter.org/ On 2016-06-28 10:23:+0000, Stormy via chirp_users wrote: >Hi there, > >So, got the UV-5RHP, and I hear everyone laughing, what diff do these letters at the end, anyways, it seems to be true 3-power with original UV-5R body: > ><http://www.aliexpress.com/item/Real-8W-BAOFENG-UV-5R-High-Power-Walkie-Talk…>http://www.aliexpress.com/item/Real-8W-BAOFENG-UV-5R-High-Power-Walkie-Talk… > > > >Now, is there a way in chirp to: > >1) change ALL channels to LOW or HIGH/MED ? it seems very tedious to do one by one, and even if you do, next import from CSV overwrites all values to high it seems. > >2) In CSV format power field does not appear to be present, is there a way to export/import POWER field? > >3) In CSV there are 4 extra fields compared to software, what are they used for? > > > >Comment URCALL RPT1CALL RPT2CALL " > >thanks. >_______________________________________________ >chirp_users mailing list >chirp_users(a)intrepid.danplanet.com >http://intrepid.danplanet.com/mailman/listinfo/chirp_users >This message was sent to WeatheredSoul at rich.messeder(a)gmail.com >To unsubscribe, send an email to chirp_users-unsubscribe(a)intrepid.danplanet.com

1 0

[chirp_users] Zastone MP-300 a clone of the Waccom Mini 8900?
by Pavel Milanes (CO7WT) 27 Jun '16

27 Jun '16

Hi to all, Chirp developer here for the BTECH/Juentai/Waccom/QYT/(huge list...) family. I have a paper note here about the ZASTONE MP-300 radio being a clone of the Waccom Mini-8900 and I can't find the reference or confirmation to it. (busy days here, sorry.) Can any of you test/confirm this out? If any of you have a ZASTONE MP-300 and want to have it supported by Chirp, please contact me off list. Cheers. -- 73 Pavel CO7WT.

1 0

[chirp_users] IC92AD Download from radio issues
by Wenlock Burton 25 Jun '16

25 Jun '16

Hi, As of build 20160625 the read is getting much further, however after clicking the various sections I get to Bank Names (Band B) and get a pink window with no data displayed. The status bar shows [0] Getting bank information for memory 399 The DSTAR window is not populated either. Running in terminal reports the following errors: On clicking Banks (Band B): Exception in thread Thread-4: Traceback (most recent call last): File "/usr/lib/python2.7/threading.py", line 810, in __bootstrap_inner self.run() File "/usr/lib/python2.7/dist-packages/chirp/ui/common.py", line 261, in run job.execute(self.radio) File "/usr/lib/python2.7/dist-packages/chirp/ui/bankedit.py", line 138, in execute mappings = self.__model.get_memory_mappings(mem) File "/usr/lib/python2.7/dist-packages/chirp/drivers/icf.py", line 544, in get_memory_mappings index = self._radio._get_bank(memory.number) File "/usr/lib/python2.7/dist-packages/chirp/drivers/ic9x.py", line 83, in _get_bank return mem._bank AttributeError: Memory instance has no attribute '_bank' It seems that the bug in Bank A has been corrected, but the same or similar bug occurs in Bank B, once again trying to read Bank names for memories that dont have bank name attributes. Thanks Wenlock

1 0

[chirp_users] New Daily Build
by Build System 25 Jun '16

25 Jun '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-20160625 A list of the changes included in this build (since the last daily) follows: Changes for Build #412 [Dan Smith <dsmith(a)danplanet.com>] Disable FT2900E until detection is fixed Related to bug #3557 [Tom Hayward <tom(a)tomh.us>] [RepeaterBook] Convert iso-8859-1 to unicode so OSX pyGTK doesn't crash. #3769 [Dan Smith <dsmith(a)danplanet.com>] Remove the modded FT-2900R until detection is fixed Related to bug #3557

1 0

[chirp_users] New Daily Build
by Build System 24 Jun '16

24 Jun '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-20160624 A list of the changes included in this build (since the last daily) follows: Changes for Build #411 [Dan Smith <dsmith(a)danplanet.com>] Add TYT TH-7800 test image Related to #3477

1 0

Re: [chirp_users] Icom ic-t70
by Adam_K_Collins＠graco.com 23 Jun '16

23 Jun '16

I'm not familiar with debug logs. Does anything here suggest a course of action? Thanks, __________________ Here is the wording: [2016-06-22 22:10:36,045] chirp.logger - DEBUG: CHIRP daily-20160615 on WinVista/7 (Python 2.7.10) [2016-06-22 22:10:36,140] chirp.directory - INFO: Registered Alinco_DR03T = DR03Radio [2016-06-22 22:10:36,141] chirp.directory - INFO: Registered Alinco_DR06T = DR06Radio [2016-06-22 22:10:36,141] chirp.directory - INFO: Registered Alinco_DR135T = DR135Radio [2016-06-22 22:10:36,141] chirp.directory - INFO: Registered Alinco_DR235T = DR235Radio [2016-06-22 22:10:36,141] chirp.directory - INFO: Registered Alinco_DR435T = DR435Radio [2016-06-22 22:10:36,141] chirp.directory - INFO: Registered Alinco_DJ596 = DJ596Radio [2016-06-22 22:10:36,141] chirp.directory - INFO: Registered Jetstream_JT220M = JT220MRadio [2016-06-22 22:10:36,141] chirp.directory - INFO: Registered Alinco_DJ175 = DJ175Radio [2016-06-22 22:10:36,141] chirp.directory - INFO: Registered AnyTone_5888UV = AnyTone5888UVRadio [2016-06-22 22:10:36,141] chirp.directory - INFO: Registered Intek_HR-2040 = IntekHR2040Radio [2016-06-22 22:10:36,141] chirp.directory - INFO: Registered Polmar_DB-50M = PolmarDB50MRadio [2016-06-22 22:10:36,141] chirp.directory - INFO: Registered Powerwerx_DB-750X = PowerwerxDB750XRadio [2016-06-22 22:10:36,142] chirp.directory - INFO: Registered AnyTone_TERMN-8R = AnyToneTERMN8RRadio [2016-06-22 22:10:36,142] chirp.directory - INFO: Registered AnyTone_OBLTR-8R = AnyToneOBLTR8RRadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Baofeng_UV-3R = UV3RRadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Baojie_BJ-9900 = BJ9900Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Baofeng_UV-5R = BaofengUV5RGeneric [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Baofeng_F-11 = BaofengF11Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Baofeng_UV-82 = BaofengUV82Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Baofeng_UV-6 = BaofengUV6Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Intek_KT-980HP = IntekKT980Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Baofeng_BF-F8HP = BaofengBFF8HPRadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Baofeng_UV-82HP = BaofengUV82HPRadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Baojie_BJ-UV55 = BaojieBJUV55Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered BTECH_UV-2501 = UV2501 [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered BTECH_UV-2501+220 = UV2501_220 [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered BTECH_UV-5001 = UV5001 [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered WACCOM_MINI-8900 = MINI8900 [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered QYT_KT-UV980 = KTUV980 [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered QYT_KT8900 = KT9800 [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered QYT_KT8900R = KT9800R [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Feidaxin_FD-268A = FD268ARadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Feidaxin_FD-268B = FD268BRadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Feidaxin_FD-288A = FD288ARadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Feidaxin_FD-288B = FD288BRadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Feidaxin_FD-150A = FD150ARadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Feidaxin_FD-160A = FD160ARadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Feidaxin_FD-450A = FD450ARadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Feidaxin_FD-460A = FD460ARadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FT-1802M = FT1802Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FT-1D_R = FT1Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FT-2800M = FT2800Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FT-2900R_1900R = FT2900Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FT-2900E_1900E_E = FT2900ERadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FT-2900_1900_Modded_Opened_Xmit = FT2900ModRadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FT-50 = FT50Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FT-60 = FT60Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FT-7800_7900 = FT7800Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FT-8800 = FT8800Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FT-8900 = FT8900Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FT-8100 = FT8100Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FT-817 = FT817Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FT-817ND = FT817NDRadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FT-817ND_US = FT817NDUSRadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FT-857_897 = FT857Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FT-857_897_US = FT857USRadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FT-90 = FT90Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FTM-350 = FTM350Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Generic_CSV = CSVRadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Commander_KG-UV = CommanderCSVRadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered RT_Systems_CSV = RTCSVRadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered ARRL_Travel_Plus = TpeRadio [2016-06-22 22:10:36,191] chirp.directory - INFO: Registered Generic_XML = XMLRadio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Baofeng_BF-888 = H777Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_IC-208H = IC208Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_IC-2100H = IC2100Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_IC-2200H = IC2200Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_IC-2720H = IC2720Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_IC-2820H = IC2820Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_IC-91_92AD = IC9xRadio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_7200 = Icom7200Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_IC-7000 = Icom7000Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_746 = Icom746Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_IC-Q7A = ICQ7Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_IC-T70 = ICT70Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_IC-T7H = ICT7HRadio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_IC-T8A = ICT8ARadio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_IC-W32A = ICW32ARadio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_IC-W32E = ICW32ERadio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_IC-V82_U82 = ICx8xRadio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_ID-31A = ID31Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_ID-51 = ID51Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_ID-51_Plus = ID51PLUSRadio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_ID-800H_v2 = ID800v2Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_ID-880H = ID880Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_ID-80H = ID80Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Kenwood_HMK = HMKRadio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Kenwood_ITM = ITMRadio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Kenwood_TH-D7 = THD7Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Kenwood_TH-D7G = THD7GRadio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Kenwood_TM-D700 = TMD700Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Kenwood_TM-V7 = TMV7Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Kenwood_TM-G707 = TMG707Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Kenwood_TH-G71 = THG71Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Kenwood_TH-F6 = THF6ARadio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Kenwood_TH-F7 = THF7ERadio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Kenwood_TM-D710 = TMD710Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Kenwood_TH-D72_live_mode = THD72Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Kenwood_TM-V71 = TMV71Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Kenwood_TM-D710G = TMD710GRadio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Kenwood_TH-K2 = THK2Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Kenwood_TM-271 = TM271Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Kenwood_TM-281 = TM281Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Kenwood_TM-471 = TM471Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Wouxun_KG-UV8D = KGUV8DRadio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered KYD_NC-630A = NC630aRadio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered KYD_IP-620 = IP620Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Leixen_VV-898 = LeixenVV898Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Jetstream_JT270M = JetstreamJT270MRadio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Wouxun_KG-UVD1P = KGUVD1PRadio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Wouxun_KG-UV6 = KGUV6DRadio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Wouxun_KG-816 = KG816Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Wouxun_KG-818 = KG818Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Puxing_PX-777 = Puxing777Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Puxing_PX-2R = Puxing2RRadio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered TYT_TH-7800_File = TYTTH7800File [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered TYT_TH-7800 = TYTTH7800Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered TYT_TH9000_220 = Th9000220Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered TYT_TH9000_144 = Th9000144Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered TYT_TH9000_440 = Th9000440Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered TYT_TH-9800_File = TYTTH9800File [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered TYT_TH-9800 = TYTTH9800Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered TYT_TH-UV3R = TYTUV3RRadio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered TYT_TH-UV3R-25 = TYTUV3R25Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered TYT_TH-UVF8D = TYTUVF8DRadio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TH-D72_clone_mode = THD72Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered TYT_TH-UVF1 = TYTTHUVF1Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-260 = TK260_Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-270 = TK270_Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-272 = TK272_Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-278 = TK278_Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-360 = TK360_Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-370 = TK370_Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-372 = TK372_Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-378 = TK378_Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-760 = TK760_Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-762 = TK762_Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-768 = TK768_Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-860 = TK860_Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-862 = TK862_Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-868 = TK868_Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-868G = TK868G_Radios [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-862G = TK862G_Radios [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-860G = TK860G_Radios [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-768G = TK768G_Radios [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-762G = TK762G_Radios [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-760G = TK760G_Radios [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-278G = TK278G_Radios [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-272G = TK272G_Radios [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-270G = TK270G_Radios [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-260G = TK260G_Radios [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-7102 = KenwoodTK7102Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-8102 = KenwoodTK8102Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-7108 = KenwoodTK7108Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-8108 = KenwoodTK8108Radio [2016-06-22 22:10:36,239] chirp.directory - INFO: Registered Kenwood_TS-2000 = TS2000Radio [2016-06-22 22:10:36,239] chirp.directory - INFO: Registered Baofeng_UV-B5 = BaofengUVB5 [2016-06-22 22:10:36,240] chirp.directory - INFO: Registered Yaesu_VX-170 = VX170Radio [2016-06-22 22:10:36,240] chirp.directory - INFO: Registered Yaesu_VX-2 = VX2Radio [2016-06-22 22:10:36,240] chirp.directory - INFO: Registered Yaesu_VX-3 = VX3Radio [2016-06-22 22:10:36,240] chirp.directory - INFO: Registered Yaesu_VX-5 = VX5Radio [2016-06-22 22:10:36,242] chirp.directory - INFO: Registered Yaesu_VX-6 = VX6Radio [2016-06-22 22:10:36,243] chirp.directory - INFO: Registered Yaesu_VX-7 = VX7Radio [2016-06-22 22:10:36,243] chirp.directory - INFO: Registered Yaesu_VX-8_R = VX8Radio [2016-06-22 22:10:36,243] chirp.directory - INFO: Registered Yaesu_VX-8_DR = VX8DRadio [2016-06-22 22:10:36,243] chirp.directory - INFO: Registered Yaesu_VX-8_GE = VX8GERadio [2016-06-22 22:10:36,244] chirp.directory - INFO: Registered Vertex_Standard_VXA-700 = VXA700Radio [2016-06-22 22:10:36,244] elib.intl - DEBUG: Set environment variable 'LANG' to 'en_US' ('kernel32.SetEnvironmentVariableW') [2016-06-22 22:10:36,244] elib.intl - DEBUG: Set environment variable 'LANG' to 'en_US' ('msvcrt._putenv') [2016-06-22 22:10:36,244] elib.intl - DEBUG: Set environment variable 'LANG' to 'en_US' ('msvcr90._putenv') [2016-06-22 22:10:36,576] chirp.ui.mainapp - INFO: Skipping existing stock config [2016-06-22 22:10:36,576] chirp.ui.mainapp - INFO: Skipping existing stock config [2016-06-22 22:10:36,576] chirp.ui.mainapp - INFO: Skipping existing stock config [2016-06-22 22:10:36,576] chirp.ui.mainapp - INFO: Skipping existing stock config [2016-06-22 22:10:36,576] chirp.ui.mainapp - INFO: Skipping existing stock config [2016-06-22 22:10:36,576] chirp.ui.mainapp - INFO: Skipping existing stock config [2016-06-22 22:10:36,576] chirp.ui.mainapp - INFO: Skipping existing stock config [2016-06-22 22:10:36,576] chirp.ui.mainapp - INFO: Skipping existing stock config [2016-06-22 22:10:36,576] chirp.ui.mainapp - INFO: Skipping existing stock config [2016-06-22 22:10:36,576] chirp.ui.mainapp - INFO: Skipping existing stock config [2016-06-22 22:10:36,576] chirp.ui.mainapp - INFO: Skipping existing stock config [2016-06-22 22:10:36,576] chirp.ui.mainapp - INFO: Skipping existing stock config [2016-06-22 22:10:36,592] chirp.ui.reporting - DEBUG: Checking for updates [2016-06-22 22:10:36,760] chirp.ui.reporting - DEBUG: Server reports version daily-20160615 is latest [2016-06-22 22:10:42,934] chirp.ui.mainapp - DEBUG: User selected Icom IC-T70 on port COM4 [2016-06-22 22:10:42,950] chirp.ui.clone - DEBUG: Clone thread started [2016-06-22 22:10:43,477] chirp.ui.reporting - DEBUG: Reporting exception [2016-06-22 22:10:43,477] chirp.ui.common - ERROR: -- Exception: -- [2016-06-22 22:10:43,477] chirp.ui.common - ERROR: Traceback (most recent call last): File "chirp\ui\clone.pyo", line 249, in run File "chirp\drivers\icf.pyo", line 616, in sync_in File "chirp\drivers\icf.pyo", line 322, in clone_from_radio RadioError: Failed to communicate with the radio: Unexpected response from radio [2016-06-22 22:10:43,477] chirp.ui.common - ERROR: ---------------- [2016-06-22 22:10:43,477] chirp.ui.clone - ERROR: Clone failed: Failed to communicate with the radio: Unexpected response from radio [2016-06-22 22:10:43,614] chirp.ui.clone - DEBUG: Clone thread ended [2016-06-22 22:10:43,614] chirp.ui.reporting - DEBUG: Reporting model usage: Icom_IC-T70,download,True [2016-06-22 22:10:43,614] chirp.ui.reporting - DEBUG: Reporting exception [2016-06-22 22:10:43,614] chirp.ui.inputdialog - ERROR: --- Exception Dialog: Failed to communicate with the radio: Unexpected response from radio --- [2016-06-22 22:10:43,614] chirp.ui.inputdialog - ERROR: Traceback (most recent call last): File "chirpw", line 67, in <module> AttributeError: 'NoneType' object has no attribute 'split' [2016-06-22 22:10:43,614] chirp.ui.inputdialog - ERROR: ---------------------------- ——————————————————————————— Adam Collins Principal Designer Graco Process Division Office: 612-623-6449 Fax: 612-378-3510 www.graco.com/process __________________ Tom, I have my debug file here: The issue is "failed to communicate with radio, unexpected response from > radio." on my Icom ic-t-70. Thanks, ——————————————————————————— Adam Collins Principal Designer Graco Process Division Office: 612-623-6449 Fax: 612-378-3510 www.graco.com/process From: Tom Hayward <tom(a)tomh.us> To: Discussion of CHIRP <chirp_users(a)intrepid.danplanet.com>, Date: 06/21/2016 12:05 PM Subject: Re: [chirp_users] Icom ic-t70 Sent by: chirp_users-bounces(a)intrepid.danplanet.com On Tue, Jun 21, 2016 at 9:52 AM, <Adam_K_Collins(a)graco.com> wrote: > > Hi, I'm looking for help with my ic-t70. > > For months I have been trying to get an image file into Chirp. > > I have confirmed correct drivers, COM ports, and no faulty cables. All I > ever get is "failed to communicate with radio, unexpected response from > radio." "Unexpected response" means it did receive something, but that something wasn't what Chirp identifies as an IC-T70. Your debug log might tell you more, but since you didn't provide it I'll just go hunting myself... http://chirp.danplanet.com/projects/chirp/repository/entry/chirp/drivers/ic… It looks like that error comes up when your radio responds to the clone request with more than one frame of data. What's in that extra data? Who knows. You might find more in your debug log. http://chirp.danplanet.com/projects/chirp/wiki/How_to_report_issues#Getting… Tom KD7LXL _______________________________________________ chirp_users mailing list chirp_users(a)intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Adam at adam_k_collins(a)graco.com To unsubscribe, send an email to chirp_users-unsubscribe(a)intrepid.danplanet.com

2 1

[chirp_users] USB port 'Serial' object has no attribute 'setTimeout'
by Bob (KB3SYZ) 23 Jun '16

23 Jun '16

Running Chirp on Ubuntu 16.05 LTS. I am a total newbie to Linux. Learning as I go.I am having a hard time getting Chirp to work. I am attempting to connect to a Baofeng UV-5RA and, Wouxun KG-UV8D, also a Yeasu FT-2900R. I have made sure that I added myself to the group Dialout. I am getting the error; Failed to communicate with radio: 'Serial' object has no attribute 'setTimeout'. I have googled and searched for a solution to no avail. Any and all help greatly appreciated. Bob (KB3SYZ)

3 3

[chirp_users] Ubuntu
by NP3AR 23 Jun '16

23 Jun '16

Error on update attempt "The repository 'http://ppa.launchpad.net/dansmith/chirp-snapshots/ubuntu xenial Release' does not have a Release file. Sent from my Samsung Galaxy Tab®4

1 0

[chirp_users] Fwd: [chirp_devel] Build test results: Still Failing
by Pavel Milanes (CO7WT) 23 Jun '16

23 Jun '16

A new clone for the btech/qyt/waccom family has support now: Luiton LT-588UV TIP: I'm working on solving the Waccom mini8900 bugs, so far I'm nailing it, I have to do some extra testing with Jim KC9HI before patching. 73 Pavel CO7WT -------- Mensaje reenviado -------- Asunto: [chirp_devel] Build test results: Still Failing Fecha: Wed, 22 Jun 2016 18:47:38 -0700 (PDT) De: Build System via chirp_devel <chirp_devel(a)intrepid.danplanet.com> Responder-a:: Build System <donotreply(a)danplanet.com>, chirp_devel(a)intrepid.danplanet.com A: chirp_devel(a)intrepid.danplanet.com Tested changes: [Pavel Milanes (CO7WT) <pavelmc(a)gmail.com>] [PATCH][BTECH][LT-588UV] Add a new model to the BTECH family, fixes #3067 A new model for the btech driver family: the LUITON LT-588UV, it's not a clone it's a variant of the early QYT KT8900. Also some tidy of the radio variants in the code to group the vendors. [Tom Hayward <tom(a)tomh.us>] [ui] Default file name to include model and date. #3753 During Save As, default the filename to {vendor}_{model}_{date}.img. The user is free to edit the field to their liking before saving. In case you don't like {vendor}_{model}_{date}.img, a new configuration variable "default_filename" is provided. By setting this variable in your config file, you can reorder or omit parts of the default format. Example: [global] default_filename = {vendor}_{model} This omits the date. Example: [global] default_filename = Tom's_{vendor}_{model}_{date} This begins each filename with my name. Full log: Started by an SCM change Building in workspace /var/lib/jenkins/jobs/chirp-test/workspace [workspace] $ hg showconfig paths.default [workspace] $ hg pull --rev default [workspace] $ hg update --clean --rev default 2 files updated, 0 files merged, 0 files removed, 0 files unresolved [workspace] $ hg log --rev . --template {node} [workspace] $ hg log --rev . --template {rev} [workspace] $ hg log --rev cd4630e4151a435810e1eb3089f63927dfe2c626 [workspace] $ hg log --template "<changeset node='{node}' author='{author|xmlescape}' rev='{rev}' date='{date}'><msg>{desc|xmlescape}</msg><added>{file_adds|stringify|xmlescape}</added><deleted>{file_dels|stringify|xmlescape}</deleted><files>{files|stringify|xmlescape}</files><parents>{parents}</parents></changeset>\n" --rev default:0 --follow --prune cd4630e4151a435810e1eb3089f63927dfe2c626 No emails were triggered. [workspace] $ /bin/sh -xe /tmp/hudson3886142960528785677.sh [workspace] $ /bin/sh -xe /tmp/hudson4300370065474325300.sh + PATH=/usr/bin:/bin:/usr/local/bin ./run_all_tests.sh test_bit_array (tests.unit.test_bitwise.TestBitType) ... ok test_bit_array_fail (tests.unit.test_bitwise.TestBitType) ... ok test_bitfield_u16 (tests.unit.test_bitwise.TestBitfieldTypes) ... ok test_bitfield_u24 (tests.unit.test_bitwise.TestBitfieldTypes) ... ok test_bitfield_u8 (tests.unit.test_bitwise.TestBitfieldTypes) ... ok test_bitfield_ul16 (tests.unit.test_bitwise.TestBitfieldTypes) ... ok test_bitfield_ul24 (tests.unit.test_bitwise.TestBitfieldTypes) ... ok test_bbcd (tests.unit.test_bitwise.TestBitwiseBCDTypes) ... ok test_bbcd_array (tests.unit.test_bitwise.TestBitwiseBCDTypes) ... ok test_lbcd (tests.unit.test_bitwise.TestBitwiseBCDTypes) ... ok test_lbcd_array (tests.unit.test_bitwise.TestBitwiseBCDTypes) ... ok test_int_array (tests.unit.test_bitwise.TestBitwiseBaseIntTypes) ... ok test_type_u16 (tests.unit.test_bitwise.TestBitwiseBaseIntTypes) ... ok test_type_u24 (tests.unit.test_bitwise.TestBitwiseBaseIntTypes) ... ok test_type_u32 (tests.unit.test_bitwise.TestBitwiseBaseIntTypes) ... ok test_type_u8 (tests.unit.test_bitwise.TestBitwiseBaseIntTypes) ... ok test_type_ul16 (tests.unit.test_bitwise.TestBitwiseBaseIntTypes) ... ok test_type_ul24 (tests.unit.test_bitwise.TestBitwiseBaseIntTypes) ... ok test_type_ul32 (tests.unit.test_bitwise.TestBitwiseBaseIntTypes) ... ok test_char (tests.unit.test_bitwise.TestBitwiseCharTypes) ... ok test_string (tests.unit.test_bitwise.TestBitwiseCharTypes) ... ok test_string_invalid_chars (tests.unit.test_bitwise.TestBitwiseCharTypes) ... ok test_string_wrong_length (tests.unit.test_bitwise.TestBitwiseCharTypes) ... ok test_comment_cppstyle (tests.unit.test_bitwise.TestBitwiseComments) ... ok test_comment_inline_cppstyle (tests.unit.test_bitwise.TestBitwiseComments) ... ok test_missing_semicolon (tests.unit.test_bitwise.TestBitwiseErrors) ... ok test_seek (tests.unit.test_bitwise.TestBitwiseSeek) ... ok test_seekto (tests.unit.test_bitwise.TestBitwiseSeek) ... ok test_struct_one_element (tests.unit.test_bitwise.TestBitwiseStructTypes) ... ok test_struct_two_elements (tests.unit.test_bitwise.TestBitwiseStructTypes) ... ok test_struct_writes (tests.unit.test_bitwise.TestBitwiseStructTypes) ... ok split_tone_encode_test_cross_dtcs_tone (tests.unit.test_chirp_common.TestSplitTone) ... ok split_tone_encode_test_cross_none_dtcs (tests.unit.test_chirp_common.TestSplitTone) ... ok split_tone_encode_test_cross_none_tone (tests.unit.test_chirp_common.TestSplitTone) ... ok split_tone_encode_test_cross_tone_dtcs (tests.unit.test_chirp_common.TestSplitTone) ... ok split_tone_encode_test_cross_tone_tone (tests.unit.test_chirp_common.TestSplitTone) ... ok split_tone_encode_test_dtcs (tests.unit.test_chirp_common.TestSplitTone) ... ok split_tone_encode_test_none (tests.unit.test_chirp_common.TestSplitTone) ... ok split_tone_encode_test_tone (tests.unit.test_chirp_common.TestSplitTone) ... ok split_tone_encode_test_tsql (tests.unit.test_chirp_common.TestSplitTone) ... ok test_split_tone_decode_cross_dtcs_dtcs (tests.unit.test_chirp_common.TestSplitTone) ... ok test_split_tone_decode_cross_dtcs_tone (tests.unit.test_chirp_common.TestSplitTone) ... ok test_split_tone_decode_cross_none_dtcs (tests.unit.test_chirp_common.TestSplitTone) ... ok test_split_tone_decode_cross_none_tone (tests.unit.test_chirp_common.TestSplitTone) ... ok test_split_tone_decode_cross_tone_dtcs (tests.unit.test_chirp_common.TestSplitTone) ... ok test_split_tone_decode_cross_tone_tone (tests.unit.test_chirp_common.TestSplitTone) ... ok test_split_tone_decode_dtcs (tests.unit.test_chirp_common.TestSplitTone) ... ok test_split_tone_decode_none (tests.unit.test_chirp_common.TestSplitTone) ... ok test_split_tone_decode_tone (tests.unit.test_chirp_common.TestSplitTone) ... ok test_split_tone_decode_tsql (tests.unit.test_chirp_common.TestSplitTone) ... ok test_fix_rounded_step_250 (tests.unit.test_chirp_common.TestStepFunctions) ... ok test_fix_rounded_step_500 (tests.unit.test_chirp_common.TestStepFunctions) ... ok test_fix_rounded_step_750 (tests.unit.test_chirp_common.TestStepFunctions) ... ok test_is_12_5 (tests.unit.test_chirp_common.TestStepFunctions) ... ok test_is_2_5 (tests.unit.test_chirp_common.TestStepFunctions) ... ok test_is_5_0 (tests.unit.test_chirp_common.TestStepFunctions) ... ok test_is_6_25 (tests.unit.test_chirp_common.TestStepFunctions) ... ok test_is_fractional_step (tests.unit.test_chirp_common.TestStepFunctions) ... ok test_required_step (tests.unit.test_chirp_common.TestStepFunctions) ... ok test_required_step_fail (tests.unit.test_chirp_common.TestStepFunctions) ... ok test_format_freq (tests.unit.test_chirp_common.TestUtilityFunctions) ... ok test_parse_freq_bad (tests.unit.test_chirp_common.TestUtilityFunctions) ... ok test_parse_freq_decimal (tests.unit.test_chirp_common.TestUtilityFunctions) ... ok test_parse_freq_whitespace (tests.unit.test_chirp_common.TestUtilityFunctions) ... ok test_parse_freq_whole (tests.unit.test_chirp_common.TestUtilityFunctions) ... ok test_ensure_has_calls_almost_full (tests.unit.test_import_logic.DstarTests) ... ok test_ensure_has_calls_empty (tests.unit.test_import_logic.DstarTests) ... ok test_ensure_has_calls_partial (tests.unit.test_import_logic.DstarTests) ... ok test_ensure_has_calls_rptcall_full1 (tests.unit.test_import_logic.DstarTests) ... ok test_ensure_has_calls_rptcall_full2 (tests.unit.test_import_logic.DstarTests) ... ok test_ensure_has_calls_urcall_full (tests.unit.test_import_logic.DstarTests) ... ok test_import_bank (tests.unit.test_import_logic.ImportFieldTests) ... ok test_import_dtcs_diffA_dtcs (tests.unit.test_import_logic.ImportFieldTests) ... ok test_import_dtcs_diffB_dtcs (tests.unit.test_import_logic.ImportFieldTests) ... ok test_import_duplex_negative (tests.unit.test_import_logic.ImportFieldTests) ... ok test_import_duplex_too_big_vhf (tests.unit.test_import_logic.ImportFieldTests) ... ok test_import_duplex_uhf (tests.unit.test_import_logic.ImportFieldTests) ... ok test_import_duplex_vhf (tests.unit.test_import_logic.ImportFieldTests) ... ok test_import_mem (tests.unit.test_import_logic.ImportFieldTests) ... ok test_import_mem_with_errors (tests.unit.test_import_logic.ImportFieldTests) ... ok test_import_mem_with_warnings (tests.unit.test_import_logic.ImportFieldTests) ... ok test_import_mode_invalid (tests.unit.test_import_logic.ImportFieldTests) ... ok test_import_mode_valid_am (tests.unit.test_import_logic.ImportFieldTests) ... ok test_import_mode_valid_fm (tests.unit.test_import_logic.ImportFieldTests) ... ok test_import_name (tests.unit.test_import_logic.ImportFieldTests) ... ok test_import_power_closest (tests.unit.test_import_logic.ImportFieldTests) ... ok test_import_power_no_dst (tests.unit.test_import_logic.ImportFieldTests) ... ok test_import_power_no_src (tests.unit.test_import_logic.ImportFieldTests) ... ok test_import_power_same (tests.unit.test_import_logic.ImportFieldTests) ... ok test_import_tone_diffA_tsql (tests.unit.test_import_logic.ImportFieldTests) ... ok test_import_tone_diffB_tsql (tests.unit.test_import_logic.ImportFieldTests) ... ok test_mapping (tests.unit.test_mappingmodel.TestBaseBank) ... ok test_mapping_eq (tests.unit.test_mappingmodel.TestBaseBank) ... ok test_base_class (tests.unit.test_mappingmodel.TestBaseBankModel) ... ok test_get_name (tests.unit.test_mappingmodel.TestBaseBankModel) ... ok test_mapping (tests.unit.test_mappingmodel.TestBaseMapping) ... ok test_mapping_eq (tests.unit.test_mappingmodel.TestBaseMapping) ... ok test_base_class (tests.unit.test_mappingmodel.TestBaseMappingModel) ... ok test_get_name (tests.unit.test_mappingmodel.TestBaseMappingModel) ... ok test_base_class (tests.unit.test_mappingmodel.TestBaseMappingModelIndexInterface) ... ok test_add_memory_to_mapping (tests.unit.test_mappingmodel.TestIcomBankModel) ... ok test_get_mapping_memories (tests.unit.test_mappingmodel.TestIcomBankModel) ... ok test_get_mappings (tests.unit.test_mappingmodel.TestIcomBankModel) ... ok test_get_memory_mappings (tests.unit.test_mappingmodel.TestIcomBankModel) ... ok test_get_num_mappings (tests.unit.test_mappingmodel.TestIcomBankModel) ... ok test_remove_memory_from_mapping (tests.unit.test_mappingmodel.TestIcomBankModel) ... ok test_remove_memory_from_mapping_no_bank (tests.unit.test_mappingmodel.TestIcomBankModel) ... ok test_remove_memory_from_mapping_wrong_bank (tests.unit.test_mappingmodel.TestIcomBankModel) ... ok test_icom_bank (tests.unit.test_mappingmodel.TestIcomBanks) ... ok test_mapping (tests.unit.test_mappingmodel.TestIcomBanks) ... ok test_mapping_eq (tests.unit.test_mappingmodel.TestIcomBanks) ... ok test_add_memory_to_mapping (tests.unit.test_mappingmodel.TestIcomIndexedBankModel) ... ok test_get_index_bounds (tests.unit.test_mappingmodel.TestIcomIndexedBankModel) ... ok test_get_mapping_memories (tests.unit.test_mappingmodel.TestIcomIndexedBankModel) ... ok test_get_mappings (tests.unit.test_mappingmodel.TestIcomIndexedBankModel) ... ok test_get_memory_index (tests.unit.test_mappingmodel.TestIcomIndexedBankModel) ... ok test_get_memory_mappings (tests.unit.test_mappingmodel.TestIcomIndexedBankModel) ... ok test_get_next_mapping_index (tests.unit.test_mappingmodel.TestIcomIndexedBankModel) ... ok test_get_num_mappings (tests.unit.test_mappingmodel.TestIcomIndexedBankModel) ... ok test_remove_memory_from_mapping (tests.unit.test_mappingmodel.TestIcomIndexedBankModel) ... ok test_remove_memory_from_mapping_no_bank (tests.unit.test_mappingmodel.TestIcomIndexedBankModel) ... ok test_remove_memory_from_mapping_wrong_bank (tests.unit.test_mappingmodel.TestIcomIndexedBankModel) ... ok test_set_memory_index (tests.unit.test_mappingmodel.TestIcomIndexedBankModel) ... ok test_set_memory_index_bad_bank (tests.unit.test_mappingmodel.TestIcomIndexedBankModel) ... ok test_set_memory_index_bad_index (tests.unit.test_mappingmodel.TestIcomIndexedBankModel) ... ok test_auto_tone_mode_cross (tests.unit.test_memedit_edits.TestEdits) ... ok test_auto_tone_mode_dtcs (tests.unit.test_memedit_edits.TestEdits) ... ok test_auto_tone_mode_dtcs_pol (tests.unit.test_memedit_edits.TestEdits) ... ok test_auto_tone_mode_dtcs_rx (tests.unit.test_memedit_edits.TestEdits) ... ok test_auto_tone_mode_tone (tests.unit.test_memedit_edits.TestEdits) ... ok test_auto_tone_mode_tsql (tests.unit.test_memedit_edits.TestEdits) ... ok test_init (tests.unit.test_platform.Win32PlatformTest) ... ok test_serial_ports_bad_portnames (tests.unit.test_platform.Win32PlatformTest) ... ok test_serial_ports_sorted (tests.unit.test_platform.Win32PlatformTest) ... ok test_apply_callback (tests.unit.test_settings.TestSettingContainers) ... ok test_radio_setting (tests.unit.test_settings.TestSettingContainers) ... ok test_radio_setting_group (tests.unit.test_settings.TestSettingContainers) ... ok test_radio_setting_multi (tests.unit.test_settings.TestSettingContainers) ... ok test_changed (tests.unit.test_settings.TestSettingValues) ... ok test_radio_setting_value_boolean (tests.unit.test_settings.TestSettingValues) ... ok test_radio_setting_value_float (tests.unit.test_settings.TestSettingValues) ... ok test_radio_setting_value_integer (tests.unit.test_settings.TestSettingValues) ... ok test_radio_setting_value_list (tests.unit.test_settings.TestSettingValues) ... ok test_radio_setting_value_string (tests.unit.test_settings.TestSettingValues) ... ok test_validate_callback (tests.unit.test_settings.TestSettingValues) ... ok test_delete_hole_with_all (tests.unit.test_shiftdialog.ShiftDialogTest) ... ok test_delete_hole_with_all_full (tests.unit.test_shiftdialog.ShiftDialogTest) ... ok test_delete_hole_with_hole (tests.unit.test_shiftdialog.ShiftDialogTest) ... ok test_delete_hole_without_hole (tests.unit.test_shiftdialog.ShiftDialogTest) ... ok test_insert_hole_with_space (tests.unit.test_shiftdialog.ShiftDialogTest) ... ok test_insert_hole_without_space (tests.unit.test_shiftdialog.ShiftDialogTest) ... ok ---------------------------------------------------------------------- Ran 151 tests in 0.050s OK Patch 'tip' is OK Checking for PEP8 regressions... ./chirp/drivers/ft60.py:521:45: W291 trailing whitespace ./chirp/drivers/ft60.py:522:25: E128 continuation line under-indented for visual indent ./chirp/drivers/ft60.py:523:13: E301 expected 1 blank line, found 0 ./chirp/drivers/ft817.py:587:41: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:684:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:688:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:691:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:692:29: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:695:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:696:29: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:699:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:702:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:705:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:708:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:711:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:714:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:717:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:720:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:721:29: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:724:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:725:29: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:728:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:731:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:732:29: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:735:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:736:29: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:739:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:740:29: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:743:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:744:29: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:747:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:750:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:753:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:754:29: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:757:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:758:29: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:761:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:764:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:767:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:768:29: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:771:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:772:29: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:775:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:776:29: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:779:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:782:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:783:29: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:786:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:789:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:790:29: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:793:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:794:29: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:810:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:811:31: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:814:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:817:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:821:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:827:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:832:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:836:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:840:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:844:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:848:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:893:25: E128 continuation line under-indented for visual indent ./chirp/drivers/thd72.py:188:1: E302 expected 2 blank lines, found 1 ./chirp/drivers/thd72.py:203:23: E201 whitespace after '[' ./chirp/drivers/thd72.py:203:80: E501 line too long (171 > 79 characters) ./chirp/drivers/thd72.py:203:170: E202 whitespace before ']' ./chirp/drivers/thd72.py:204:13: E201 whitespace after '[' ./chirp/drivers/thd72.py:204:61: E202 whitespace before ']' ./chirp/drivers/thd72.py:205:23: E201 whitespace after '[' ./chirp/drivers/thd72.py:205:74: E202 whitespace before ']' ./chirp/drivers/thd72.py:206:18: E201 whitespace after '[' ./chirp/drivers/thd72.py:206:65: E202 whitespace before ']' ./chirp/drivers/thd72.py:595:1: W293 blank line contains whitespace ./chirp/drivers/thd72.py:603:1: W293 blank line contains whitespace ./chirp/ui/mainapp.py:646:13: E128 continuation line under-indented for visual indent ./chirp/ui/mainapp.py:660:5: E303 too many blank lines (2) ./chirp/ui/mainapp.py:1363:80: E501 line too long (81 > 79 characters) ./chirp/ui/mainapp.py:1367:80: E501 line too long (80 > 79 characters) ./chirp/ui/mainapp.py:1652:80: E501 line too long (85 > 79 characters) real 0m7.378s user 0m7.269s sys 0m0.048s ================================================ Tests FAILED: driver tests Build step 'Execute shell' marked build as failure Email was triggered for: Failure Sending email for trigger: Failure

1 0

Re: [chirp_users] Icom ic-t70
by Adam_K_Collins＠graco.com 23 Jun '16

23 Jun '16

Here is the wording: [2016-06-22 22:10:36,045] chirp.logger - DEBUG: CHIRP daily-20160615 on WinVista/7 (Python 2.7.10) [2016-06-22 22:10:36,140] chirp.directory - INFO: Registered Alinco_DR03T = DR03Radio [2016-06-22 22:10:36,141] chirp.directory - INFO: Registered Alinco_DR06T = DR06Radio [2016-06-22 22:10:36,141] chirp.directory - INFO: Registered Alinco_DR135T = DR135Radio [2016-06-22 22:10:36,141] chirp.directory - INFO: Registered Alinco_DR235T = DR235Radio [2016-06-22 22:10:36,141] chirp.directory - INFO: Registered Alinco_DR435T = DR435Radio [2016-06-22 22:10:36,141] chirp.directory - INFO: Registered Alinco_DJ596 = DJ596Radio [2016-06-22 22:10:36,141] chirp.directory - INFO: Registered Jetstream_JT220M = JT220MRadio [2016-06-22 22:10:36,141] chirp.directory - INFO: Registered Alinco_DJ175 = DJ175Radio [2016-06-22 22:10:36,141] chirp.directory - INFO: Registered AnyTone_5888UV = AnyTone5888UVRadio [2016-06-22 22:10:36,141] chirp.directory - INFO: Registered Intek_HR-2040 = IntekHR2040Radio [2016-06-22 22:10:36,141] chirp.directory - INFO: Registered Polmar_DB-50M = PolmarDB50MRadio [2016-06-22 22:10:36,141] chirp.directory - INFO: Registered Powerwerx_DB-750X = PowerwerxDB750XRadio [2016-06-22 22:10:36,142] chirp.directory - INFO: Registered AnyTone_TERMN-8R = AnyToneTERMN8RRadio [2016-06-22 22:10:36,142] chirp.directory - INFO: Registered AnyTone_OBLTR-8R = AnyToneOBLTR8RRadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Baofeng_UV-3R = UV3RRadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Baojie_BJ-9900 = BJ9900Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Baofeng_UV-5R = BaofengUV5RGeneric [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Baofeng_F-11 = BaofengF11Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Baofeng_UV-82 = BaofengUV82Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Baofeng_UV-6 = BaofengUV6Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Intek_KT-980HP = IntekKT980Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Baofeng_BF-F8HP = BaofengBFF8HPRadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Baofeng_UV-82HP = BaofengUV82HPRadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Baojie_BJ-UV55 = BaojieBJUV55Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered BTECH_UV-2501 = UV2501 [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered BTECH_UV-2501+220 = UV2501_220 [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered BTECH_UV-5001 = UV5001 [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered WACCOM_MINI-8900 = MINI8900 [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered QYT_KT-UV980 = KTUV980 [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered QYT_KT8900 = KT9800 [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered QYT_KT8900R = KT9800R [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Feidaxin_FD-268A = FD268ARadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Feidaxin_FD-268B = FD268BRadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Feidaxin_FD-288A = FD288ARadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Feidaxin_FD-288B = FD288BRadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Feidaxin_FD-150A = FD150ARadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Feidaxin_FD-160A = FD160ARadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Feidaxin_FD-450A = FD450ARadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Feidaxin_FD-460A = FD460ARadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FT-1802M = FT1802Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FT-1D_R = FT1Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FT-2800M = FT2800Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FT-2900R_1900R = FT2900Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FT-2900E_1900E_E = FT2900ERadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FT-2900_1900_Modded_Opened_Xmit = FT2900ModRadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FT-50 = FT50Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FT-60 = FT60Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FT-7800_7900 = FT7800Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FT-8800 = FT8800Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FT-8900 = FT8900Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FT-8100 = FT8100Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FT-817 = FT817Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FT-817ND = FT817NDRadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FT-817ND_US = FT817NDUSRadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FT-857_897 = FT857Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FT-857_897_US = FT857USRadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FT-90 = FT90Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FTM-350 = FTM350Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Generic_CSV = CSVRadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Commander_KG-UV = CommanderCSVRadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered RT_Systems_CSV = RTCSVRadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered ARRL_Travel_Plus = TpeRadio [2016-06-22 22:10:36,191] chirp.directory - INFO: Registered Generic_XML = XMLRadio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Baofeng_BF-888 = H777Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_IC-208H = IC208Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_IC-2100H = IC2100Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_IC-2200H = IC2200Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_IC-2720H = IC2720Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_IC-2820H = IC2820Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_IC-91_92AD = IC9xRadio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_7200 = Icom7200Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_IC-7000 = Icom7000Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_746 = Icom746Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_IC-Q7A = ICQ7Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_IC-T70 = ICT70Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_IC-T7H = ICT7HRadio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_IC-T8A = ICT8ARadio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_IC-W32A = ICW32ARadio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_IC-W32E = ICW32ERadio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_IC-V82_U82 = ICx8xRadio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_ID-31A = ID31Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_ID-51 = ID51Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_ID-51_Plus = ID51PLUSRadio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_ID-800H_v2 = ID800v2Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_ID-880H = ID880Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_ID-80H = ID80Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Kenwood_HMK = HMKRadio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Kenwood_ITM = ITMRadio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Kenwood_TH-D7 = THD7Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Kenwood_TH-D7G = THD7GRadio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Kenwood_TM-D700 = TMD700Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Kenwood_TM-V7 = TMV7Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Kenwood_TM-G707 = TMG707Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Kenwood_TH-G71 = THG71Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Kenwood_TH-F6 = THF6ARadio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Kenwood_TH-F7 = THF7ERadio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Kenwood_TM-D710 = TMD710Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Kenwood_TH-D72_live_mode = THD72Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Kenwood_TM-V71 = TMV71Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Kenwood_TM-D710G = TMD710GRadio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Kenwood_TH-K2 = THK2Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Kenwood_TM-271 = TM271Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Kenwood_TM-281 = TM281Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Kenwood_TM-471 = TM471Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Wouxun_KG-UV8D = KGUV8DRadio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered KYD_NC-630A = NC630aRadio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered KYD_IP-620 = IP620Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Leixen_VV-898 = LeixenVV898Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Jetstream_JT270M = JetstreamJT270MRadio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Wouxun_KG-UVD1P = KGUVD1PRadio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Wouxun_KG-UV6 = KGUV6DRadio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Wouxun_KG-816 = KG816Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Wouxun_KG-818 = KG818Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Puxing_PX-777 = Puxing777Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Puxing_PX-2R = Puxing2RRadio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered TYT_TH-7800_File = TYTTH7800File [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered TYT_TH-7800 = TYTTH7800Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered TYT_TH9000_220 = Th9000220Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered TYT_TH9000_144 = Th9000144Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered TYT_TH9000_440 = Th9000440Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered TYT_TH-9800_File = TYTTH9800File [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered TYT_TH-9800 = TYTTH9800Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered TYT_TH-UV3R = TYTUV3RRadio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered TYT_TH-UV3R-25 = TYTUV3R25Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered TYT_TH-UVF8D = TYTUVF8DRadio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TH-D72_clone_mode = THD72Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered TYT_TH-UVF1 = TYTTHUVF1Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-260 = TK260_Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-270 = TK270_Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-272 = TK272_Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-278 = TK278_Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-360 = TK360_Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-370 = TK370_Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-372 = TK372_Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-378 = TK378_Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-760 = TK760_Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-762 = TK762_Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-768 = TK768_Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-860 = TK860_Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-862 = TK862_Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-868 = TK868_Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-868G = TK868G_Radios [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-862G = TK862G_Radios [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-860G = TK860G_Radios [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-768G = TK768G_Radios [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-762G = TK762G_Radios [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-760G = TK760G_Radios [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-278G = TK278G_Radios [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-272G = TK272G_Radios [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-270G = TK270G_Radios [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-260G = TK260G_Radios [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-7102 = KenwoodTK7102Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-8102 = KenwoodTK8102Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-7108 = KenwoodTK7108Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-8108 = KenwoodTK8108Radio [2016-06-22 22:10:36,239] chirp.directory - INFO: Registered Kenwood_TS-2000 = TS2000Radio [2016-06-22 22:10:36,239] chirp.directory - INFO: Registered Baofeng_UV-B5 = BaofengUVB5 [2016-06-22 22:10:36,240] chirp.directory - INFO: Registered Yaesu_VX-170 = VX170Radio [2016-06-22 22:10:36,240] chirp.directory - INFO: Registered Yaesu_VX-2 = VX2Radio [2016-06-22 22:10:36,240] chirp.directory - INFO: Registered Yaesu_VX-3 = VX3Radio [2016-06-22 22:10:36,240] chirp.directory - INFO: Registered Yaesu_VX-5 = VX5Radio [2016-06-22 22:10:36,242] chirp.directory - INFO: Registered Yaesu_VX-6 = VX6Radio [2016-06-22 22:10:36,243] chirp.directory - INFO: Registered Yaesu_VX-7 = VX7Radio [2016-06-22 22:10:36,243] chirp.directory - INFO: Registered Yaesu_VX-8_R = VX8Radio [2016-06-22 22:10:36,243] chirp.directory - INFO: Registered Yaesu_VX-8_DR = VX8DRadio [2016-06-22 22:10:36,243] chirp.directory - INFO: Registered Yaesu_VX-8_GE = VX8GERadio [2016-06-22 22:10:36,244] chirp.directory - INFO: Registered Vertex_Standard_VXA-700 = VXA700Radio [2016-06-22 22:10:36,244] elib.intl - DEBUG: Set environment variable 'LANG' to 'en_US' ('kernel32.SetEnvironmentVariableW') [2016-06-22 22:10:36,244] elib.intl - DEBUG: Set environment variable 'LANG' to 'en_US' ('msvcrt._putenv') [2016-06-22 22:10:36,244] elib.intl - DEBUG: Set environment variable 'LANG' to 'en_US' ('msvcr90._putenv') [2016-06-22 22:10:36,576] chirp.ui.mainapp - INFO: Skipping existing stock config [2016-06-22 22:10:36,576] chirp.ui.mainapp - INFO: Skipping existing stock config [2016-06-22 22:10:36,576] chirp.ui.mainapp - INFO: Skipping existing stock config [2016-06-22 22:10:36,576] chirp.ui.mainapp - INFO: Skipping existing stock config [2016-06-22 22:10:36,576] chirp.ui.mainapp - INFO: Skipping existing stock config [2016-06-22 22:10:36,576] chirp.ui.mainapp - INFO: Skipping existing stock config [2016-06-22 22:10:36,576] chirp.ui.mainapp - INFO: Skipping existing stock config [2016-06-22 22:10:36,576] chirp.ui.mainapp - INFO: Skipping existing stock config [2016-06-22 22:10:36,576] chirp.ui.mainapp - INFO: Skipping existing stock config [2016-06-22 22:10:36,576] chirp.ui.mainapp - INFO: Skipping existing stock config [2016-06-22 22:10:36,576] chirp.ui.mainapp - INFO: Skipping existing stock config [2016-06-22 22:10:36,576] chirp.ui.mainapp - INFO: Skipping existing stock config [2016-06-22 22:10:36,592] chirp.ui.reporting - DEBUG: Checking for updates [2016-06-22 22:10:36,760] chirp.ui.reporting - DEBUG: Server reports version daily-20160615 is latest [2016-06-22 22:10:42,934] chirp.ui.mainapp - DEBUG: User selected Icom IC-T70 on port COM4 [2016-06-22 22:10:42,950] chirp.ui.clone - DEBUG: Clone thread started [2016-06-22 22:10:43,477] chirp.ui.reporting - DEBUG: Reporting exception [2016-06-22 22:10:43,477] chirp.ui.common - ERROR: -- Exception: -- [2016-06-22 22:10:43,477] chirp.ui.common - ERROR: Traceback (most recent call last): File "chirp\ui\clone.pyo", line 249, in run File "chirp\drivers\icf.pyo", line 616, in sync_in File "chirp\drivers\icf.pyo", line 322, in clone_from_radio RadioError: Failed to communicate with the radio: Unexpected response from radio [2016-06-22 22:10:43,477] chirp.ui.common - ERROR: ---------------- [2016-06-22 22:10:43,477] chirp.ui.clone - ERROR: Clone failed: Failed to communicate with the radio: Unexpected response from radio [2016-06-22 22:10:43,614] chirp.ui.clone - DEBUG: Clone thread ended [2016-06-22 22:10:43,614] chirp.ui.reporting - DEBUG: Reporting model usage: Icom_IC-T70,download,True [2016-06-22 22:10:43,614] chirp.ui.reporting - DEBUG: Reporting exception [2016-06-22 22:10:43,614] chirp.ui.inputdialog - ERROR: --- Exception Dialog: Failed to communicate with the radio: Unexpected response from radio --- [2016-06-22 22:10:43,614] chirp.ui.inputdialog - ERROR: Traceback (most recent call last): File "chirpw", line 67, in <module> AttributeError: 'NoneType' object has no attribute 'split' [2016-06-22 22:10:43,614] chirp.ui.inputdialog - ERROR: ---------------------------- ——————————————————————————— Adam Collins Principal Designer Graco Process Division Office: 612-623-6449 Fax: 612-378-3510 www.graco.com/process __________________ Tom, I have my debug file here: The issue is "failed to communicate with radio, unexpected response from > radio." on my Icom ic-t-70. Thanks, ——————————————————————————— Adam Collins Principal Designer Graco Process Division Office: 612-623-6449 Fax: 612-378-3510 www.graco.com/process From: Tom Hayward <tom(a)tomh.us> To: Discussion of CHIRP <chirp_users(a)intrepid.danplanet.com>, Date: 06/21/2016 12:05 PM Subject: Re: [chirp_users] Icom ic-t70 Sent by: chirp_users-bounces(a)intrepid.danplanet.com On Tue, Jun 21, 2016 at 9:52 AM, <Adam_K_Collins(a)graco.com> wrote: > > Hi, I'm looking for help with my ic-t70. > > For months I have been trying to get an image file into Chirp. > > I have confirmed correct drivers, COM ports, and no faulty cables. All I > ever get is "failed to communicate with radio, unexpected response from > radio." "Unexpected response" means it did receive something, but that something wasn't what Chirp identifies as an IC-T70. Your debug log might tell you more, but since you didn't provide it I'll just go hunting myself... http://chirp.danplanet.com/projects/chirp/repository/entry/chirp/drivers/ic… It looks like that error comes up when your radio responds to the clone request with more than one frame of data. What's in that extra data? Who knows. You might find more in your debug log. http://chirp.danplanet.com/projects/chirp/wiki/How_to_report_issues#Getting… Tom KD7LXL _______________________________________________ chirp_users mailing list chirp_users(a)intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Adam at adam_k_collins(a)graco.com To unsubscribe, send an email to chirp_users-unsubscribe(a)intrepid.danplanet.com

1 0

[chirp_users] New Daily Build
by Build System 23 Jun '16

23 Jun '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-20160623 A list of the changes included in this build (since the last daily) follows: Changes for Build #410 [Pavel Milanes (CO7WT) <pavelmc(a)gmail.com>] [PATCH][BTECH][LT-588UV] Add a new model to the BTECH family, fixes #3067 A new model for the btech driver family: the LUITON LT-588UV, it's not a clone it's a variant of the early QYT KT8900. Also some tidy of the radio variants in the code to group the vendors. [Tom Hayward <tom(a)tomh.us>] [ui] Default file name to include model and date. #3753 During Save As, default the filename to {vendor}_{model}_{date}.img. The user is free to edit the field to their liking before saving. In case you don't like {vendor}_{model}_{date}.img, a new configuration variable "default_filename" is provided. By setting this variable in your config file, you can reorder or omit parts of the default format. Example: [global] default_filename = {vendor}_{model} This omits the date. Example: [global] default_filename = Tom's_{vendor}_{model}_{date} This begins each filename with my name.

1 0

[chirp_users] seeing my posting
by Richard Castleberry 21 Jun '16

21 Jun '16

I am confused how this users group works. I posted an question but am not sure how to get back to see responses. Is there also a web site version I might access? Thx, Richard

6 6

[chirp_users] basic programming
by Richard Castleberry 17 Jun '16

17 Jun '16

Super basic question about CHIRP programming... I have the latest 'daily build' and loaded some local freqs into my Baofeng. Have Chirp open on my PC (Windows 7) and can't seem to sort out how to re-load my settings back into my radio. (my programming cable seems to be fine) I had no trouble loading it the first time but now not sure where to find the backup file I made. Can someone advise? Thx!

10 101

[chirp_users] Resending message
by Wenlock Burton 17 Jun '16

17 Jun '16

Hi We seem to have a message stuck on repeat??? Wenlock Sent from my iPhone

1 0

Re: [chirp_users] PL tones (was Chirp's new Alias feature.)
by Jim Unroe 15 Jun '16

15 Jun '16

On Wed, Jun 15, 2016 at 5:13 PM, Curley Frazier <ricknbrook(a)gmail.com> wrote: > Love Chirp! Thanks for all you do. One question please? In my Baofung UV-5R+ > if I open menu to look at settings go tell a freind what PL tone a repeater > had on a stored frequency, or to to program another radio in the field, it > shows blank.....? Can this be edited to show each repeaters PL? > This discussion thread is about CHIRP's new alias feature. You should start a new thread instead of hijacking this one. You don't have to open the settings to see the tones programmed in a stored memory because they are all displayed in the spreadsheet style memory editor. That being said, if you try to open the settings tab and the menu is blank, then there is most likely a setting that is out-of-range. Attach a debug.log file and we should be able to determine which one it is and help you correct it in your radio so it will then show up properly in CHIRP (and possibly use that information to update CHIRP to handle the out-of-range value in the future). See the "how to report issues" page to learn how to find your debug.log file. http://chirp.danplanet.com/projects/chirp/wiki/How_to_report_issues Jim KC9HI

2 1

[chirp_users] New Daily Build
by Build System 15 Jun '16

15 Jun '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-20160615 A list of the changes included in this build (since the last daily) follows: Changes for Build #409 [Pavel Milanes (CO7WT) <pavelmc(a)gmail.com>] [PATCH][Feature] Add the know clones of the btech with the new alias feature, fixes #3749 This patch explicitly adds the following Btech clones to the UI: * Jetstream JT2705M * Juentai JT-6188 Mini * Juentai JT-6188 Plus * Sainsonic GT-890 This radios do show properly now in the download/upload dialog as vendor/model, this will ease the handling of clones in the user side. But it has a catch and the users will be notified on the chirp_user list: when you opens a saved image of a clone it will show in Chirp as the real radio, not the clone. 73 Pavel CO7WT [Dan Smith <dsmith(a)danplanet.com>] Add radio alias support This introduces a small class called Alias which defines the identifying attributes of a radio model. Radio inherits from that, and also has a list of ALIASES that can be zero or more of those classes. When we construct the clone box where a user chooses a model, show them all the models, including aliases. #0 [Pavel Milanes (CO7WT) <pavelmc(a)gmail.com>] [PATCH][KT-8900R] Fix the second ID to cope with a new variant, fixes #3547 The latest added variant has the second ID without the leading spaces, instead it's filled with '123456' We removed the leading spaces as the ID is the same of the others but they changed the leding spaces. [Nathan Crapo <nathan(a)n4nc3o.com>] Make radio model identification for TH-7800 and TH-9800 more specific so they don't interfere with each other, or completely different radios. The TH-7800 was ahead of the TH-9800 in the list of Radios to identify against, so Chirp would use it for TH-7800 _and_ TH-9800 radios. This patch makes both TH-7800 and TH-9800 drivers check their model more carefully so order of Radios Classes doesn't matter. It's more robust that way. TH-7800 seems to use "TH9800" for a model string too. Check for a "TH9800" _or_ "TH7800" string in the th7800.py driver in case TYT doesn't consistently set the model or in case owners change their model name. Fixes #3737.

4 3

[chirp_users] UV-5RA - latest build
by Steve London 11 Jun '16

11 Jun '16

Long story....but I'll summarize the current issue. I had my old UV-5RA talking to a 2014-vintage version of Chirp. Worked fine. Got a new UV-5RV2+. Doesn't talk to the 2014 version. Downloaded/Installed the latest nightly Chirp build - 20160604 . Won't talk to either the previously-working UV-5RA or the new UV-5RV2+. Radio does not respond. Where do I go from here ? 73, Steve, N2IC

10 21

[chirp_users] New Daily Build
by Build System 11 Jun '16

11 Jun '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-20160611 A list of the changes included in this build (since the last daily) follows: Changes for Build #408 [Dan Smith <dsmith(a)danplanet.com>] Add some extra debug to kguv8d driver download process To help with diagnosing #3733 [Nathan Crapo <nathan(a)n4nc3o.com>] Adding support for TYT TH-7800. Fixes #3477. [Pavel Milanes (CO7WT) <pavelmc(a)gmail.com>] [PATCH][KT-8900R] Add a new discovered variant, fixes #3547 A new variant of this radio was found on the wild. Also my IDE (Geany) has a strict policy for leading spaces, so it removed automaticaly some of them. 73 [Tom Hayward <tom(a)tomh.us>] Support pySerial 3+. Fixes #3167 #3209 #3521 #3671 #3703

1 0

[chirp_users] More UV8D Issues
by Chris Levi 09 Jun '16

09 Jun '16

Gentlemen, I have done the menu resets and attempted to program the radios by hand with no joy even after a hard reset with the language being Chinese and all settings reset I still am having transmit and receive issues. I have re-tried with Chirp and still no success. Best I can figure it has something to do with the "QT" modes not allowing the audio out, but that is a W.A.G. on my part and most likely only the tip of the iceberg. Is there a diagnostic suite available like moto-labs for these radios? Thank you for any help, Chris KG6TTN

1 0

Re: [chirp_users] Settings to match Motorola PL tones
by Rich Messeder 08 Jun '16

08 Jun '16

I think this is a good question. I have recently acquired 2 BaoFeng UV-5RTP. I have programmed them "successfully", but not tested the results. Here is my take on it. I think that CHIRP allows the user to select TSQL, indicating that the ToneSql value is used for repeater access. It is unfortunate that we all don't use the same terms. I opine that CTCSS is the same thing as PL; one is a generic term and the other a vendor term. I understand that Tone in CHIRP is used for receive. If you have Tone selected, then the sender must use the agreed tone to open your squelch. For repeaters, I am not sure that all repeaters use tone (PL, CTCSS) on transmit, as they do on receive. A repeater first senses the carrier on the inbound freq, and then look for the PL tone. My impression is that many radios do not (can not) use PL codes /from/ a repeater that are different from the sending PL tone. Now to 2 radios. The sending unit must send the same tone that the receiving unit is filtering on. So if you are both working simplex, and you both have tone squelch enabled and are using the same PL|CTCSS tones, it should work. I might try that later today or tomorrow if I have the time. From http://chirp.danplanet.com/projects/chirp/wiki/MemoryEditorColumns Tone This sets the CTCSS tone to be transmitted if the Tone Mode is set to Tone. In Cross mode, it has additional meanings (see description of Cross Mode for more details). ToneSql This sets the CTCSS tone to be transmitted and used for receiver squelch if the Tone Mode is set to TSQL. In Cross mode it has additional meanings (see description of Cross Mode for more details). I too have used TSQL for many entries, and now wonder if I should be using Tone, because I want to trigger the repeater with a PL tone, but then want the reply no matter what. ~R~ NE1EE Short email? No html? Here's why: http://emailcharter.org/ On 2016-06-08 09:26:-0400, Jeffrey wrote: >Hey everyone, > >I'm pretty new to radios in general, and more so programming them, but I'll do my best to get the terminology right. > >I'm trying to use CHIRP to program a UV-5R so that it can communicate with a Motorola radio on a certain frequency.� The Motorola is set to use 151.9400 with a PL tone of 67.0 for both send and receive. > >PL is the same as CTCSS correct? > >On the UV-5R, I've got Tone Mode set as TSQL and ToneSql set to 67.0 - and it does not work? The two radios are not communicating.� Am I missing something? Something special about Motorola PL tones? Should be a standard right? > >Thanks for any advice. > >Jeff >Jeffrey Fongemie � � >_______________________________________________ >chirp_users mailing list >chirp_users(a)intrepid.danplanet.com >http://intrepid.danplanet.com/mailman/listinfo/chirp_users >This message was sent to WeatheredSoul at rich.messeder(a)gmail.com >To unsubscribe, send an email to chirp_users-unsubscribe(a)intrepid.danplanet.com

8 8

[chirp_users] Settings to match Motorola PL tones
by Jeffrey 08 Jun '16

08 Jun '16

Hey everyone, I'm pretty new to radios in general, and more so programming them, but I'll do my best to get the terminology right. I'm trying to use CHIRP to program a UV-5R so that it can communicate with a Motorola radio on a certain frequency. The Motorola is set to use 151.9400 with a PL tone of 67.0 for both send and receive. PL is the same as CTCSS correct? On the UV-5R, I've got Tone Mode set as TSQL and ToneSql set to 67.0 - and it does not work? The two radios are not communicating. Am I missing something? Something special about Motorola PL tones? Should be a standard right? Thanks for any advice. Jeff -- ______________ Jeffrey Fongemie <http://instagram.com/jfongemie>

7 10

Re: [chirp_users] Settings to match Motorola PL tones
by Rich Messeder 08 Jun '16

08 Jun '16

Thanks, "Rich". ;-) "Direct" is called simplex. On my Kenwood TH-F6A, I can select "Tone" to activate a repeater that requires it, or I can select CTCSS (PL) to filter incoming calls according to a tone. But using one cancels the other. Some radio permit the use of both, hence the CROSS value in CHIRP. IMO. setting the ToneMode to Tone should have resulted in the UV5 /sending/ a tone. If it were earlier TSQL, and the Motorola were NOT sending a tone, then the UV5 would have not opened its squelch, and you would not receive the call. And yes the transmission is open to everyone to hear. All that TSQL does is tell your radio to ignore all transmissions it receives EXCEPT for those that also carry the CTCSS tone. Please note that if two radios are transmitting on the same freq, and one uses the tone to open your squelch, you will hear both transmissions simultaneously. Gotta go offline for the rest of the day...sorry. ~Rich~ On 2016-06-08 10:15:-0400, Jeffrey wrote: >Thanks Rick. > >I just tried setting Tone Mode to "Tone" with a tone of 67.0 it the UV5R was able to receive from the Motorola, but the Motorola could not receive from the UV5R. > >"Tone: A single CTCSS tone is transmitted, receive squelch is open or carrier-triggered. The tone used is that which is set in the Tone column.:" > >So, if I read this correctly, the Motorola radio transmission is open to everyone? And will filter out everything that does not transmit with the correct tone?� > >Tone mode as "Tone" should work if I have the correct tone, and the radio is sending it correctly. Right? > >Jeff > >On Wed, Jun 8, 2016 at 9:55 AM, Rich Messeder <<mailto:rich.messeder@gmail.com>rich.messeder(a)gmail.com> wrote: >I think this is a good question. I have recently acquired 2 BaoFeng UV-5RTP. I have programmed them "successfully", but not tested the results. > >Here is my take on it. > >I think that CHIRP allows the user to select TSQL, indicating that the ToneSql value is used for repeater access. It is unfortunate that we all don't use the same terms. I opine that CTCSS is the same thing as PL; one is a generic term and the other a vendor term. > >I understand that Tone in CHIRP is used for receive. If you have Tone selected, then the sender must use the agreed tone to open your squelch. For repeaters, I am not sure that all repeaters use tone (PL, CTCSS) on transmit, as they do on receive. A repeater first senses the carrier on the inbound freq, and then look for the PL tone. > >My impression is that many radios do not (can not) use PL codes /from/ a repeater that are different from the sending PL tone. > >Now to 2 radios. >The sending unit must send the same tone that the receiving unit is filtering on. So if you are both working simplex, and you both have tone squelch enabled and are using the same PL|CTCSS tones, it should work. I might try that later today or tomorrow if I have the time. > >From ><http://chirp.danplanet.com/projects/chirp/wiki/MemoryEditorColumns>http://chirp.danplanet.com/projects/chirp/wiki/MemoryEditorColumns >Tone >This sets the CTCSS tone to be transmitted if the Tone Mode is set to Tone. In Cross mode, it has additional meanings (see description of Cross Mode for more details). > >ToneSql >This sets the CTCSS tone to be transmitted and used for receiver squelch if the Tone Mode is set to TSQL. In Cross mode it has additional meanings (see description of Cross Mode for more details). > >I too have used TSQL for many entries, and now wonder if I should be using Tone, because I want to trigger the repeater with a PL tone, but then want the reply no matter what. > >~R~ NE1EE >Short email? No html? Here's why: <http://emailcharter.org/>http://emailcharter.org/ > >On 2016-06-08 09:26:-0400, Jeffrey wrote: >>Hey everyone, >> >>I'm pretty new to radios in general, and more so programming them, but I'll do my best to get the terminology right. >> >>I'm trying to use CHIRP to program a UV-5R so that it can communicate with a Motorola radio on a certain frequency.Â� The Motorola is set to use 151.9400 with a PL tone of 67.0 for both send and receive. >> >>PL is the same as CTCSS correct? >> >>On the UV-5R, I've got Tone Mode set as TSQL and ToneSql set to 67.0 - and it does not work? The two radios are not communicating.Â� Am I missing something? Something special about Motorola PL tones? Should be a standard right? >> >>Thanks for any advice. >> >>Jeff >>Jeffrey Fongemie Â� Â >>_______________________________________________ >>chirp_users mailing list >><mailto:chirp_users@intrepid.danplanet.com>chirp_users(a)intrepid.danplanet.com >>http://intrepid.danplanet.com/mailman/listinfo/chirp_users >>This message was sent to WeatheredSoul at <mailto:rich.messeder@gmail.com>rich.messeder(a)gmail.com >>To unsubscribe, send an email to <mailto:chirp_users-unsubscribe@intrepid.danplanet.com>chirp_users-unsubscribe(a)intrepid.danplanet.com > > >_______________________________________________ >chirp_users mailing list ><mailto:chirp_users@intrepid.danplanet.com>chirp_users(a)intrepid.danplanet.com >http://intrepid.danplanet.com/mailman/listinfo/chirp_users >This message was sent to <mailto:fongemie@gmail.com>fongemie(a)gmail.com at <mailto:fongemie@gmail.com>fongemie(a)gmail.com >To unsubscribe, send an email to <mailto:chirp_users-unsubscribe@intrepid.danplanet.com>chirp_users-unsubscribe(a)intrepid.danplanet.com > > > > >-- >______________ > >Jeffrey Fongemie � � > > >_______________________________________________ >chirp_users mailing list >chirp_users(a)intrepid.danplanet.com >http://intrepid.danplanet.com/mailman/listinfo/chirp_users >This message was sent to WeatheredSoul at rich.messeder(a)gmail.com >To unsubscribe, send an email to chirp_users-unsubscribe(a)intrepid.danplanet.com

3 2

[chirp_users] firmware
by digitdan 06 Jun '16

06 Jun '16

How can I find out what firmware is in my BaoFeng GT-2 Mark ll Dan

2 1

Re: [chirp_users] BaoFeng GT-3 Mark ll problem with channel name not uploading
by NP3AR 06 Jun '16

06 Jun '16

I don't have that specific radio but I have a Baofeng and there is an option in the menus to turn names on. Sent from my Samsung Galaxy Tab®4 -------- Original message -------- From: digitdan <digitdan(a)edifax.com> Date:06/06/2016 2:13 PM (GMT-04:00) To: chirp_users(a)intrepid.danplanet.com Subject: [chirp_users] BaoFeng GT-3 Mark ll problem with channel name not uploading I downloaded the most recent Chirp software to program a BaoFeng GT-3 Mark ll. I programed all the info for 12 channels, then read the radio then uploaded the program but when I check the radio the channel names did not show up. All the frequencies where there and the radio RX and TX fine but no channel names. I tried it in both channel and frequency modes. Can anyone help??? Dan H.

1 0

[chirp_users] BaoFeng GT-3 Mark ll problem with channel name not uploading
by digitdan 06 Jun '16

06 Jun '16

I downloaded the most recent Chirp software to program a BaoFeng GT-3 Mark ll. I programed all the info for 12 channels, then read the radio then uploaded the program but when I check the radio the channel names did not show up. All the frequencies where there and the radio RX and TX fine but no channel names. I tried it in both channel and frequency modes. Can anyone help??? Dan H.

2 1

[chirp_users] Problems programming ICOM IC-V82
by Larry Gagnon 06 Jun '16

06 Jun '16

Using Chirp v daily-20160301 on Linux and an ICOM IC-V82 VHF handheld. Was able to successfully connect and download from the radio. Added some channels, then uploaded. Upload seemed to go fine but with an error message at the end that reads: "Failed to communicate with the radio. Did not get clone result from radio." On rebooting the handheld all appears fine, new channels are there but all the channels that have offsets do not take, in other words it transmits/receives on same frequency, even though file is virtually identical to that uploaded from the radio and I have double checked to offset and duplex are correct. Any ideas appreciated. Larry VE7EA

4 4

Re: [chirp_users] Baofeng UV-5R firmware upgrade?
by Stormy 05 Jun '16

05 Jun '16

I think I open a new thread each reply, sorry, using yahoo mail, and not sure how to reply on same thread (I get the daily digest). I'm worried to get a "new" radio, but in fact seller sends old inventory , hence I'm checking the firmware before purchasing since as u say it is a one-time programming firmware :) Can someone confirm is getting anything from the last block on this list: http://www.miklor.com/uv5r/UV5R-Firmware.php Managed to find: N5R-2401 is this good enough? or should I try to get a higher number? like NR5R-3409? Thanks!!Stormy.

3 3

[chirp_users] New Daily Build
by Build System 04 Jun '16

04 Jun '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-20160604 A list of the changes included in this build (since the last daily) follows: Changes for Build #407 [Tom Hayward <tom(a)tomh.us>] [ui] Dismiss shift dialog with enter key. Fixes #3695 [Tom Hayward <tom(a)tomh.us>] [ui] Default memory editor view to 0-999 (was 0-25). Fixes #3629

1 0

Re: [chirp_users] Baofeng UV-5R firmware upgrade?
by Stormy 03 Jun '16

03 Jun '16

WOW, really appreciate your comprehensive reply, now it's archived, so others hopefully can benefit.. Is that really true that since 2014 there have been newer firmware but no detected changes? or this list is out of date: http://www.miklor.com/uv5r/UV5R-Firmware.php I'm trying to figure the best firmware to look for in a new purchase. Thanks.

4 3

Re: [chirp_users] Take me off your list
by Randy Rushing 02 Jun '16

02 Jun '16

As sent you an email on a earlier date I repeat it again ((((((Take me off your list))))))_) And stop sending the email/ Or I will report. this.

4 3

[chirp_users] Baofeng UV-5R firmware upgrade?
by Stormy 02 Jun '16

02 Jun '16

Hi, Newbie question, sorry :) Not sure where else to ask... Noticed here: http://www.miklor.com/uv5r/UV5R-Firmware.php it says firmwares are not changable on the Baofeng UV-5R radios.. but then reading some postings led to this directory: http://kc9hi.dyndns.org/uv5r/programming/CHIRPrecovery/ with list of firmwares.. and someone alluding to being able to switch or flush these? If I have a device with a given firmware, then for the life it cannot be changed? Thanks much. Stormy.

2 1

[chirp_users] Accessing Repeaterbook from chirp
by Scott Brewster 01 Jun '16

01 Jun '16

I am trying to get a list of 2m and 70cm repeaters for my area with no luck. Steps taken: Start ChirpFile: NewRadio: Query Data Source: Repeaterbook Initial dialog box comes up; I select Arizona for state; Maricopa for County and 2 Meters for Band. Clicking ok results in the "standard" busy mouse icon (small greenish blue circle). Data from Repeaterbook never shows up.Even though busy mouse icon is showing, I am able to click and use options within chirp. Attempts to use other sources appears to work (albeit I am not subscribed or premium with those other sources). Reading/writing from radio otherwise works, no other issues noticed. I have tried this with the last couple of windows daily builds - latest is today's - with no luck. Am I missing something? >From chirp about: Chirp daily - 20160531 OS: Windows 7.

7 9

[chirp_users] New Daily Build
by Build System 01 Jun '16

01 Jun '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-20160601 A list of the changes included in this build (since the last daily) follows: Changes for Build #406 [Pavel Milanes (CO7WT) <pavelmc(a)gmail.com>] [PATCH][QYT KT-8900R] Add support for a new variant, fixes #3547 A new variant of this radios was found, this patch adds support for it. All points that the previously found version was Generation 2 and this new one is from Generation 1 as the ID string shows, this patch also name the versions correctly. [Robert Morris <chirp.shopping(a)iloc.com>] Fix for Bug #3679 - Keyboard shortcuts are non-standard for Mac OS X. To improve standard cut/copy/paste UI conformity, re-mapped export shortcut to use <Ctrl>e. <Ctrl>x is for cut.

4 3

[chirp_users] Hello all Chirpers :-)
by neil - ee 31 May '16

31 May '16

Hi fellow Chirpers :) I got myself a baofeng uv5r radi and a cable. Was looking for a good program to edit its memorys. Found this one first and tried it and loved it. I then found the oem programmer for it, but chirp much better I then discovered that chirp will also do the settings of the radio, and also my other radio, yaesu 857d too. So both radios got a full memory makeover with the help of excel too. I have a few other radios, one to ask about is my icom e90 quadband handheld (6m,4m,2m,70cm) I have a icom cable and its own software. It works. But was wondering if chirp is likely to come along to support as well. My comments on the program itself that I love, are 1. Keyboard shoutcuts, not standardised, ie, alt f a for save as ; alt f o for open; silly little thing like that :) 2. Unsure if bug, but regarding cts codes, and the 2 coloums Tone and ToneSql - edit in chirp, ok. But if you export, edit both coloums in excel and re-import, ToneSql gets ignored on all lines back to 88.5 3. Anuther possible bug, when typing a frequency in, and you fluff it on enter, it pops a error up, Error setting memory: Frequency 0.000000 is out of supported range" as example. But then it dumps you back up to line 1, so in a long list, you got to scroll back down to as line 200 to find and fix it again. 4. When using a mouse, the roller on the mouse does not seem to use the same speed of page/line scroll as it does in other windows apps. Takes longer in chirp. 5. Maybe another silly comment..if I have a chrip img file open.when I open another, I expect it to show the new opened file. But it don't, it stays with the current opened one. Not the new one, I have to tab across. Not hard to do of course. Its just tweaks :) Hope all is ok with that above. 73's Ne

1 0

Re: [chirp_users] Accessing Repeaterbook from chirp
by jl_wilkerson＠att.net 31 May '16

31 May '16

Repeaterbook is free. ------ Original message------From: Jock via chirp_users Date: Tue, May 31, 2016 4:51 PMTo: chirp_users@intrepid.danplanet.com;Subject:Re: [chirp_users] Accessing Repeaterbook from chirp I believe Repeater Book requires a subscription. KC6IIH JockJock Soutar KC6IIH Sent via Samsung Galaxy S7 on AT&T 4G LTE Smartphone On Tuesday, May 31, 2016 Scott Brewster via chirp_users <chirp_users(a)intrepid.danplanet.com> wrote: I am trying to get a list of 2m and 70cm repeaters for my area with no luck. Steps taken: Start ChirpFile: NewRadio: Query Data Source: Repeaterbook Initial dialog box comes up; I select Arizona for state; Maricopa for County and 2 Meters for Band. Clicking ok results in the "standard" busy mouse icon (small greenish blue circle). Data from Repeaterbook never shows up.Even though busy mouse icon is showing, I am able to click and use options within chirp. Attempts to use other sources appears to work (albeit I am not subscribed or premium with those other sources). Reading/writing from radio otherwise works, no other issues noticed. I have tried this with the last couple of windows daily builds - latest is today's - with no luck. Am I missing something? From chirp about: Chirp daily - 20160531 OS: Windows 7. _______________________________________________ chirp_users mailing list chirp_users(a)intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Jock at kc6iih(a)aol.com To unsubscribe, send an email to chirp_users-unsubscribe(a)intrepid.danplanet.com

1 0

[chirp_users] pySerial
by Ryan Barber 31 May '16

31 May '16

Hi all, Are there plans to fix the depreciated calls to pySerial setBaudrate? -Ryan

2 3

Re: [chirp_users] New Daily Build
by Rich Messeder 31 May '16

31 May '16

I linked to the messages (see bottom of email), and saw some comments about the background for this mod. Here are my comments, just FYI, no complaints. Windows 10 Pro x64. 1. I am using the standalone version. Wish that there is an x64 version. 2. Copy | Paste of records and record blocks twixt 2 instances if CHIRP, using ctrl-c, -v, works for records now. 3. Twould be nice if the confirmation dialog showed up on the same display as the main program. I run CHIRP on a an extended display in Windows. 4. Ctrl-x does not work in a field. Delete does not work in a field. Ctrl-v does not work in a field. 5. RMC: Copy //does// work in a field, but then RMC: Paste is disabled in the 2nd instance. I /can/ RMC: Paste into a different file in a different tab in the same instance. 6. I use the standalone version because I find it more controllable than installing multiple versions of the same product, though I imagine that upgrading the installed version in place works fine. Not tested. I do this so that it is easy for me to roll back, if I wish. 7. I use multiple instances of the standalone version because I can alt-tab twixt them to copy | paste. Ctrl-tab does not work for me, though it does shift the focus from a memory to a tab. So I can't easily cut from one tab and paste to another. 8. I understand deprecating .chirp files, even if I don't know the history. If .csv files are the ne way of exporting, that works for me. 9. Still don't know why I can't save Kenwood TH-F6A .img in CHIRP, but can in Kenwood's Memory Control Program (MCP). MCP is not "live". I just did this test. While CHIRP was open, I ran MCP. I downloaded from the F6A. I modified a memory. I saved the file as .fx. I ended MCP. The F6A remained unchanged. I interpret this to mean that I could save the F6A in CHIRP as a .img file (which I can't). 10. It's nice that both MCP and CHIRP do not take control of the COM port; that is, they open it, use it, and release it. This allows me to run both programs at the same time. Currently, there are advantages and disadvantages to using both MCP and CHIRP with the F6A, so I use both. ~R~ NE1EE Short email? No html? Here's why: http://emailcharter.org/ On 2016-05-31 00:09:-0700, Build System wrote: >Greetings, >http://trac.chirp.danplanet.com/chirp_daily/daily-20160531 > >A list of the changes included in this build (since the last daily) follows: > >Changes for Build #405 >[Tom Hayward <tom(a)tomh.us>] [ui] Change clipboard target to support cross-process copy/paste on Windows. #3693 > >Clipboard target was PRIMARY, the X clipboard. Changed to CLIPBOARD, the >default clipboard, for better Windows support including the ability >to copy/paste between multiple instances of Chirp. > >http://intrepid.danplanet.com/pipermail/chirp_devel/2016-May/004018.html > >[Tom Hayward <tom(a)tomh.us>] [ui] Store clipboard outside of app, so paste works after quitting. #3691 > >[Tom Hayward <tom(a)tomh.us>] [ui] Deprecate .chirp file format by disabling export. #3689 > >The .chirp file format provides no additional features compared to .CSV and is >therefore redundant. .chirp is the more complex and less frequently used format >of the two, so to eliminate the redundancy it should be deprecated. > >This patch removes the ability to export as .chirp, leaving no way to generate >new .chirp files. It preserves the ability to open and import .chirp files, so >any existing .chirp files can still be opened, edited, and exported to other >formats. > >chirp_users mailing list >chirp_users(a)intrepid.danplanet.com >http://intrepid.danplanet.com/mailman/listinfo/chirp_users

2 2