- Users - lists.chirpmyradio.com

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 16 Jul '16

16 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