November 2014 - Users - lists.chirpmyradio.com

[chirp_users] Followup on suggestion for Icom 51A comm
by Tim R. 17 Nov '14

17 Nov '14

John, I tried the newest daily build and changing the Smartscreen settings both had no effect. I did them one at a time. I can communicate just fine with my Icom ID-880H radios with both 0.4.1 and the daily build but not with the 51A. Thanks Tim K4RA Chirp community, I just bought a new computer that is running Windows ver 8.1. I loaded the newest release of Chirp, ver 0.4.1. I can't seem to get this computer with this version of Chirp to communicate with my Icom ID-51A. I have no problem using my XP computer with an older version of Chirp with the same 51A Any suggestions would be appreciated. Thanks Tim K4RA

1 0

[chirp_users] Radio did not ack programming mode with UV-B5
by Richard Hum 17 Nov '14

17 Nov '14

When I try to do "Download from radio" on my UV-B5 with chirp, I get a "Radio did not ack programming mode" error. I did some googling, but all the tips did not help. I discovered that using the programming software version 1.09 on Miklor did work, so it probably isn't a driver or cable issue. I have driver version 3.2.0.0. I get the error on both Linux and Windows 7. In Windows, I did some serial port captures to compare the traffic from the stock software and chirp. Below are those files generated by Serial Port Monitor by Eltima. The HTML files are exported versions so someone without the software could read the output. Here is a dropbox link to the files: https://www.dropbox.com/sh/hoj7428g4gnjq9x/AAAl8bjPi0vgNKWVm7w0hgyza?dl=0 Best Regards, Richard

3 5

[chirp_users] Problem in storing split configuration
by Maxxer 15 Nov '14

15 Nov '14

Hi. I'm using a Kenwood th-f7e with chirp 0.7.1, I'm trying to store a channel with split RX/TX but I always get "Radio refused ...". I stored it on the radio, but when I download it and try to edit I get the error. This is the download from console D7->PC: N PC->RADIO: MR 0,003 D7->PC: MR 0,003,00438637500,8,0,0,1,0,0,17,08,000,000000000,5,0 PC->RADIO: MNA 003 D7->PC: MNA 003, PC->RADIO: MR 1,003 D7->PC: MR 1,003,00429912500,8 If I update this record it works fine, and writes: PC->RADIO: MW 0,003,00438637500,5,0,0,1,0,0,17,08,000,000000000,5,0 but sometimes it doesn't even write it back, I still have to figure out when... Anyway it always fail I try to add a new record with split: D7->PC: N PC->RADIO: MW 0,003,00429912500,5,0,0,1,0,0,17,08,000,000000000,0,0 D7->PC: MW PC->RADIO: MNA 003, D7->PC: MNA 003, PC->RADIO: MW 1,003,00429912500,0 D7->PC: N Exception running RadioJob: Radio refused 3 -- Exception: -- Traceback (most recent call last): File "/usr/local/lib/python2.7/dist-packages/chirpui/common.py", line 111, in _execute result = func(*self.args, **self.kwargs) File "/usr/local/lib/python2.7/dist-packages/chirp/kenwood_live.py", line 234, in set_memory memory.number) InvalidDataError: Radio refused 3 ------ Job Args: (Memory[3],) Job KWArgs: {} Job Called from: File "/usr/local/bin/chirpw", line 154, in <module> gtk.main() File "/usr/local/lib/python2.7/dist-packages/chirpui/memedit.py", line 385, in edited job = common.RadioJob(self._set_memory_cb, "set_memory", mem) <MemoryEditor object at 0x7f1dd4a5b9b0 (chirpui+common+Editor at 0x1d64340)> changed Is this a problem with my radio or what? thanks!

1 0

Re: [chirp_users] chirp_users Digest, Vol 71, Issue 5
by herbsmyth 14 Nov '14

14 Nov '14

Unsubscribe On Nov 10, 2014 1:00 PM, <chirp_users-request(a)intrepid.danplanet.com> wrote: > Send chirp_users mailing list submissions to > chirp_users(a)intrepid.danplanet.com > > To subscribe or unsubscribe via the World Wide Web, visit > http://intrepid.danplanet.com/mailman/listinfo/chirp_users > or, via email, send a message with subject or body 'help' to > chirp_users-request(a)intrepid.danplanet.com > > You can reach the person managing the list at > chirp_users-owner(a)intrepid.danplanet.com > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of chirp_users digest..." > > > Today's Topics: > > 1. Re: Dstar ID-RP4000V Repeater (Jim Unroe) > 2. Osx 10 Yosemite for PL2303 cord (Milton) > 3. Re: FYI BF-F8HP programming (Michael Hilbert) > 4. Re: FYI BF-F8HP programming (Jim Unroe) > 5. Re: FYI BF-F8HP programming (Mike Hilbert) > 6. Re: FYI BF-F8HP programming (Jim Unroe) > 7. Re: FYI BF-F8HP programming (Mike Hilbert) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 9 Nov 2014 15:26:28 -0500 > From: Jim Unroe <rock.unroe(a)gmail.com> > Subject: Re: [chirp_users] Dstar ID-RP4000V Repeater > To: Discussion of CHIRP <chirp_users(a)intrepid.danplanet.com> > Message-ID: > <CADnO8U5Uj89GGN-aMytOyajAeGEn9iR_wxi4Lq= > kiWZmBA+_6w(a)mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > Bob, > > The CHIRP driver is idrp.py and for some reason it does not show up as > a choice in CHIRP (I believe it should be "ID-2000V/4000V/2D/2V"). > Most of the activity of this driver appears to be from 2009 to 2012. I > installed a daily build from May of 2012 and March of 2012 and there > was still not a selection for this Icom model. > > Jim KC9HI > > On Sat, Nov 8, 2014 at 11:35 PM, Robert Keeton <rkeeton(a)blarg.net> wrote: > > I have an ICOM , ID-RP4000V Dstar repeater. According to the Wiki page > both > > the VHF and UHF repeater is supported. When I check the daily build > list it > > is not shown as supported and I could not locate a *.py file for the > > repeater. I have been through the archives and found reference that > support > > for the ID-RP400V was added and it was working , but not much other info. > > When I run Chirp to try detect the repeater/radio I get an error message > ? > > An error has occurred Unable to get radio model?. I have tried both the > > most up to date windows version and a USB thumb drive with the Live CD > > loaded. Both versions operate fine , but with the error message. Any > > suggestions???? > > > > Bob K7MHJ > > > > > > _______________________________________________ > > chirp_users mailing list > > chirp_users(a)intrepid.danplanet.com > > http://intrepid.danplanet.com/mailman/listinfo/chirp_users > > > > > ------------------------------ > > Message: 2 > Date: Mon, 10 Nov 2014 08:56:30 -0500 > From: Milton <thecanesvenatici(a)gmail.com> > Subject: [chirp_users] Osx 10 Yosemite for PL2303 cord > To: Discussion of CHIRP <chirp_users(a)intrepid.danplanet.com> > Message-ID: > <CAChAUo= > 77d+ajEMJFDBeoTAE_azM2_zQAFz5XKft0K+EtPDHTg(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > I've installed the supposed updated driver from Sorceforge but no worky. > > > kextstat -b nl.bjaelectronics.driver.PL2303 is empty > > also > > Kext nl.bjaelectronics.driver.PL2303 not found for unload request. > Kext net.sourceforge.osx-pl2303 not found for unload request. > Kext com.prolific.driver.PL2303 not found for unload r > > > Any ideas? >

1 0

[chirp_users] Yaesu VX5 programming errors: tips for troubleshooting?
by David Hagood 14 Nov '14

14 Nov '14

I am trying to program a Yaesu VX5 using Chirp under Ubuntu, and I am not having any luck. I've tried 2 cables - one a USB to Yaesu cable, one a RS-232 to Yaesu cable (the latter both on a USB to RS-232 adapter, and on an honest UART based serial port). In all cases, I cannot download the data from the radio. Steps taken: 1 Verify serial device is readable/writable by my user (minicom, verify I see data looped back). 2 Start CHIRP (daily-20141112) 3 Select correct serial device (/dev/ttyUSB0), Vendor (Yaesu), and radio (VX-5) 4 Turn radio off, connect cable 5 Turn radio on holding Function (Radio shows "CLONE") 6 Radio->Download from radio. 7 Press OK 8 Press VFO key on radio. The radio shows "Clone TX" for about a second and a half, then shows CLONE ERROR. After a few seconds CHIRP reports a download error. Capturing the output of chirpw yields: (process:22085): Gtk-WARNING **: Locale not supported by C library. Using the fallback 'C' locale. CHIRP daily-20141112 on Linux - Ubuntu 14.04.1 LTS (Python 2.7.6) Registered Kenwood_TH-D7 = THD7Radio Registered Kenwood_TH-D7G = THD7GRadio Registered Kenwood_TM-D700 = TMD700Radio Registered Kenwood_TM-V7 = TMV7Radio Registered Kenwood_TM-G707 = TMG707Radio Registered Kenwood_TH-G71 = THG71Radio Registered Kenwood_TH-F6 = THF6ARadio Registered Kenwood_TH-F7 = THF7ERadio Registered Kenwood_TM-D710 = TMD710Radio Registered Kenwood_TH-D72_live_mode = THD72Radio Registered Kenwood_TM-V71 = TMV71Radio Registered Kenwood_TH-K2 = THK2Radio Registered Kenwood_TM-271 = TM271Radio Registered Kenwood_TM-281 = TM281Radio Registered Kenwood_TM-471 = TM471Radio Registered TYT_TH-UV3R = TYTUV3RRadio Registered Yaesu_FT-90 = FT90Radio Registered AnyTone_5888UV = AnyTone5888UVRadio Registered Intek_HR-2040 = IntekHR2040Radio Registered Polmar_DB-50M = PolmarDB50MRadio Registered Powerwerx_DB-750X = PowerwerxDB750XRadio Registered Icom_ID-800H_v2 = ID800v2Radio Registered Yaesu_FT-2800M = FT2800Radio Registered TYT_TH-9800 = TYTTH9800File Registered Icom_IC-2200H = IC2200Radio Registered TYT_TH-UVF1 = TYTTHUVF1Radio Registered Icom_IC-Q7A = ICQ7Radio Registered Icom_ID-31A = ID31Radio Registered Icom_ID-51A = ID51Radio Registered Yaesu_VX-7 = VX7Radio Registered Icom_IC-T8A = ICT8ARadio Registered Leixen_VV-898 = LeixenVV898Radio Registered Jetstream_JT270M = JetstreamJT270MRadio Registered Yaesu_VX-2 = VX2Radio Registered Icom_IC-T70 = ICT70Radio Registered Icom_7200 = Icom7200Radio Registered Icom_7000 = Icom7000Radio Registered Icom_746 = Icom746Radio Registered Yaesu_FT-60 = FT60Radio Registered Yaesu_FTM-350 = FTM350Radio Registered Icom_IC-T7H = ICT7HRadio Registered Kenwood_TK-7102 = KenwoodTK7102Radio Registered Kenwood_TK-8102 = KenwoodTK8102Radio Registered Kenwood_TK-7108 = KenwoodTK7108Radio Registered Kenwood_TK-8108 = KenwoodTK8108Radio Registered Baofeng_UV-5R = BaofengUV5R Registered Baofeng_F-11 = BaofengF11Radio Registered Baofeng_UV-82 = BaofengUV82Radio Registered Baofeng_UV-6 = BaofengUV6Radio Registered Intek_KT-980HP = IntekKT980Radio Registered Baofeng_BF-F8HP = BaofengBFF8HPRadio Registered Generic_CSV = CSVRadio Registered Commander_KG-UV = CommanderCSVRadio Registered RT_Systems_CSV = RTCSVRadio Registered Kenwood_ITM = ITMRadio Registered Yaesu_VX-8_R = VX8Radio Registered Yaesu_VX-8_DR = VX8DRadio Registered Yaesu_VX-8_GE = VX8GERadio Registered Baofeng_UV-3R = UV3RRadio Registered Icom_ID-880H = ID880Radio Registered Icom_ID-80H = ID80Radio Registered Icom_IC-2720H = IC2720Radio Registered Yaesu_FT-1802M = FT1802Radio Registered Icom_IC-2100H = IC2100Radio Registered Alinco_DR03T = DR03Radio Registered Alinco_DR06T = DR06Radio Registered Alinco_DR135T = DR135Radio Registered Alinco_DR235T = DR235Radio Registered Alinco_DR435T = DR435Radio Registered Alinco_DJ596 = DJ596Radio Registered Jetstream_JT220M = JT220MRadio Registered Alinco_DJ175 = DJ175Radio Registered Wouxun_KG-UVD1P = KGUVD1PRadio Registered Wouxun_KG-UV6 = KGUV6DRadio Registered Wouxun_KG-816 = KG816Radio Registered Wouxun_KG-818 = KG818Radio Registered Baofeng_BF-888 = H777Radio Registered Yaesu_FT-7800_7900 = FT7800Radio Registered Yaesu_FT-8800 = FT8800Radio Registered Yaesu_FT-8900 = FT8900Radio Registered Yaesu_VX-170 = VX170Radio Registered Icom_IC-2820H = IC2820Radio Registered Yaesu_FT-817 = FT817Radio Registered Yaesu_FT-817ND = FT817NDRadio Registered Yaesu_FT-817ND_US = FT817NDUSRadio Registered Icom_IC-V82_U82 = ICx8xRadio Registered TYT_TH-UVF8D = TYTUVF8DRadio Registered ARRL_Travel_Plus = TpeRadio Registered Icom_IC-208H = IC208Radio Registered Icom_IC-W32A = ICW32ARadio Registered Baofeng_UV-B5 = BaofengUVB5 Registered Generic_XML = XMLRadio Registered Icom_IC-91_92AD = IC9xRadio Registered Vertex_Standard_VXA-700 = VXA700Radio Registered Kenwood_HMK = HMKRadio Registered Yaesu_VX-5 = VX5Radio Registered Yaesu_VX-6 = VX6Radio Registered Yaesu_VX-3 = VX3Radio Registered Baojie_BJ-UV55 = BaojieBJUV55Radio Registered Kenwood_TH-D72_clone_mode = THD72Radio Registered Wouxun_KG-UV8D = KGUV8DRadio Registered KYD_NC-630A = NC630aRadio Registered Puxing_PX-777 = Puxing777Radio Registered Puxing_PX-2R = Puxing2RRadio Registered Yaesu_FT-857_897 = FT857Radio Registered Yaesu_FT-857_897_US = FT857USRadio Skipping existing stock config Skipping existing stock config Skipping existing stock config Skipping existing stock config Skipping existing stock config Skipping existing stock config Skipping existing stock config Skipping existing stock config User selected Yaesu VX-5 on port /dev/ttyUSB0 Clone thread started -- Exception: -- Traceback (most recent call last): File "/usr/lib/pymodules/python2.7/chirpui/clone.py", line 227, in run self.__radio.sync_in() File "/usr/lib/pymodules/python2.7/chirp/yaesu_clone.py", line 217, in sync_in self._mmap = _clone_in(self) File "/usr/lib/pymodules/python2.7/chirp/yaesu_clone.py", line 85, in _clone_in raise errors.RadioError("Failed to communicate with the radio: %s" % e) RadioError: Failed to communicate with the radio: No response from radio ------ Clone failed: Failed to communicate with the radio: No response from radio Clone thread ended --- Exception Dialog: Failed to communicate with the radio: No response from radio --- None ---------------------------- Is there anything I can do to get more information, such as a more verbose trace of what is going on?

1 0

[chirp_users] Wouxun kg-uv920p
by Mike Leighty 12 Nov '14

12 Nov '14

Anybody working on being able to program with chirp on the wouxun kg-uv920p?

2 1

[chirp_users] IC-208H programming question -- having difficulty
by Thomas Fancher 12 Nov '14

12 Nov '14

I am having difficulty getting my laptop to communicate with the IC-208H. It is easy to start the radio such that it displays "CLONE". Pressing the "SET*LOCK" button gives "CL OUT" but quickly clicking on the "download" in Chirp only gives an error message that there is a failure to communicate. John (kc2txv) was kind enough to send me a file that he has used with his Icom IC-208H. I modified the frequencies as applicable for my area and attempted to simply download the image file to the radio without having first accomplished an upload. That gives the message: "An error has occurred Failed to communicate with the radio: Unexpected response from radio." I verified that I have the "Prolific" USB cable set to the correct com port. However, I do not know of a good way to test the cable.

2 1

[chirp_users] New Daily Build
by Build System 12 Nov '14

12 Nov '14

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-20141112 A list of the changes included in this build (since the last daily) follows: Changes for Build #305 [Marco Filippi <iz3gme.marco(a)gmail.com>] Updated italian translation from Fabio Italian Translation - totally redone implement #2027 [Tom Hayward <tom(a)tomh.us>] [rfinder] Fix longitude formatting to work with single-digit longitudes. #2011

1 0

[chirp_users] Yaesu 7800
by ARSK0MBB＠aol.com 11 Nov '14

11 Nov '14

Hello everyone....Thanks to all who provide us less capable with the answers to program our radios. I have successfully programmed my BaoFeng UV-5re and would like to do the same with the Yaesu. I've seen comments that this is possible. Would someone be able to give me step by step instructions so I don't have to reinvent the wheel? I have the programming cable for the BaoFeng and can connect to the necessary pins of the data jack on the 7800 via a homemade adapter. Thanks, Phcyman KØMBB

1 0

[chirp_users] UV-82 C Issue with work mode
by Jamey Gettys 11 Nov '14

11 Nov '14

I have set up eight BAOFENG UV-82 C radios to use in my fire department. I have locked them down in CHIRP using the work mode settings. Here is what I have done: *Advanced Settings* -Dual Watch = Enabled -Dual Watch Priority = A -All menu's = Disabled -Single PTT= Enabled *Work Mode Settings* -Display =A -VFO/MR Mode = Channel -MR A Channel = 2 -MR B Channel =1 The result is that both the "A" channel and "B" channel show on screen as expected. The users can change channel "A" with the up/Down buttons. The users can not tab down and change the "B" channel. They can press the "Tab" button and the indicator arrow will go down to "B" and immediately return to the "A" channel. All this is perfect and what I wanted to happen. The problem/issue that I do not like is this: As radio traffic is being received on the "B" channel, the user can inadvertently press the up/down buttons and change the "B" channel. This is a huge issue because they can not change it back unless traffic is received on whatever channel they accidentally changed "B" to. The "B" channel should not be allowed to change under these circumstances. If this were corrected, it would be a perfect set-up for us. Any ideas or suggestions would greatly be appreciated.

2 2