- Users - lists.chirpmyradio.com

[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