- Users - lists.chirpmyradio.com

[chirp_users] Alinco DJ-C7
by RavenMaster 31 May '13

31 May '13

Hi Anyone knows if this scanner/transmitter is readable/programmable via Chirp? I only ask cause it's not on the supported devices but... we never know :) I'm waiting for the programming cable, so soon I'll be able to test it. Regards, RavenMaster

1 0

[chirp_users] New Daily Build
by Build System 30 May '13

30 May '13

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-20130530 A list of the changes included in this build (since the last daily) follows: Changes for Build #204 [Tom Hayward <tom(a)tomh.us>] Make settings less verbose. #891 [Marco Filippi <iz3gme.marco(a)gmail.com>] [ic208] Correct upper valid_bands check fix #887

1 0

[chirp_users] Ft-1900
by Glenn C Werner 29 May '13

29 May '13

Has anyone had success programming an FT-1900 or FT-2900 ??? Thanks, Glenn K1PCB

2 1

Re: [chirp_users] radio still does not respond
by Madison Jones 29 May '13

29 May '13

Thanks to all for your suggestions. None of them worked, though I appreciate your diligent efforts. Even worse, during my thrashing around in attempting yet another fix, the radio locked up in Memory mode, and nothing I attempted worked except the Mono button which somehow kicked the receiver into the frequency for a local hard rock station. Let not your hearts be troubled, however: using and old XP machine and making sure I had the proper Prolific driver, I went to the Baofeng UV-5R user group and looked up Hard Reset. None of the tips worked, either, until I guessed that perhaps loading the Baofeng software might influence things. After doing that and interpreting something that was mentioned in passing on one of the posts and giving it a whirl by inserting a new file [an .img file, perhaps? This concept is not explained anywhere I could find but I think it is what I did], the whole thing came alive! I have concluded that my radio works with the Baodeng software only and that the cloning cable works in XP [using the XP driver] rather than in Windows 7 using the Vista driver. I have programmed a half dozen repeaters into memory and saved it so the next time at least I won't have to start from scratch. In summary, the software [beta, gamma, delta ??] from Baofeng is useable, XP is OK, and I am happy. Thanks again and best of luck. Regards, Madison W5MJ -----Various Responses----- From: km9m-zig(a)comcast.net Subject: Re: [chirp_users] Radio still does not respond . . . try plugging the programming cable into a different usb port. . . . . . . Welcome to the world of windows hidden files and the hardware hive. Too bad its been this way for generations. W6ARH . . . If you change com ports, the correct driver needs to be reloaded to the new port. I believe that?s what you are experiencing. John K3NXU

1 0

[chirp_users] Radio still does not respond
by Madison Jones 29 May '13

29 May '13

To review my problem: Win7, Prolific 3.2.0.0 7/31/2007 [installed and reinstalled and reinstalled] on com 3, CHIRP 0.3.1, plug end filed down and pushed in HARD, and still get "radio did not respond" when I attempt to download from the radio. The miklor.com page has no suggestions for this error msg other than to file down the cable. Anything else in anyone's bag of tricks? Regards, Madison Jones W5MJ

4 4

[chirp_users] "radio did not respond"
by Madison Jones 29 May '13

29 May '13

I am a new user to the Baofeng F-11 so I might not be getting things correct, though I have reinstalled the cloning cable driver [it is on Com 3] using the Win7 procedure outlined by Wouxun and reinstalled Chirp. When I initially obtained the radio, I pulled up the stock channel program, changed it around a little and uploaded it to the radio using Chirp. A few days later I manually programmed several of the memories and deleted most of the stock memories. Now, when going to the Radio tab on the Chirp software and attempting to Download from Radio, I get an error message which says "radio did not respond." I get the same error message when attempting to upload to the radio from Chirp. Suggestions? Madison Jones W5MJ

3 2

Re: [chirp_users] chirp_users Digest, Vol 53, Issue 42
by N4AOF 28 May '13

28 May '13

This SPAM was partly the fault of the ignorant twit who invited the mail list address to Linked In, and largely the fault of Linked In itself. A few years ago, Linked In used to be a serious professional networking site, but more recently it has become more of a MySpace wannabe. When a person joins Linked In now, every time he logs in he will be pestered by a screen asking him to give linked in access to his email client program so that it can find people he knows on Linked In, but that come on is largely a lie. What Linked In actually does is import every email address in the person's contacts and then it offers to "invite" those addresses to join his "professional network" -- it does not tell the person that most of those addresses are NOT already on Linked In, and it is formatted in such a way that most people never even see the addresses that they are about to "invite" - but by doing so, the person agrees to a set of conditions that allows Linked In to spam every address it found in his contacts. Linked In will then spam those addresses, and about a month later it will spam all the addresses that haven't joined Linked In a second time. Linked In claims that people can opt out of being spammed by their members, but you have to join Linked In before you can opt out. Personally, on the mail lists that I manage, I treat Linked In invitations exactly the same way I treat Grouply invitations -- I immediately ban the individual from that mail list and from all the other mail lists that I manage. Doing so may not be "fair" but it cuts way down on the problems of managing recurring spam caused by ignorant fools. -----Original Message----- 1. Invitation to connect on LinkedIn (Tomas Mesta) 2. Re: Invitation to connect on LinkedIn (Bear Albrecht) 3. Re: Invitation to connect on LinkedIn (The Silver Fox)

1 0

[chirp_users] UV-B5 Limiting frequency entry
by nv7v nv7v 28 May '13

28 May '13

With the UV-5R you can enter frequency limits with CHIRP so the user can't enter anything outside those limits manually in VFO mode. You can still program in frequencies outside those limits with CHIRP and upload them to the radio. This is very useful as you can set the radio up for a Ham that may also have need to use the radio on other services for which they are authorized without worrying he may inadvertently transmit or enter and transmit on a frequency he should not. If I enter in frequency limits in the "settings" section in CHIRP for the UV-B5, however, it then will not allow any frequencies outside those frequency limits to be programmed into memories using CHIRP or manually in VFO mode. Is this a limit of the radio or is it possible CHIRP could be changed to work like it does with the UV-5R? Thanks so much for your excellent work!! Steve NV7V

2 2

[chirp_users] Invitation to connect on LinkedIn
by Tomas Mesta 28 May '13

28 May '13

LinkedIn ------------ Discussion, I'd like to add you to my professional network on LinkedIn. - Tomas Tomas Mesta Retail Professional Modesto, California Area Confirm that you know Tomas Mesta: https://www.linkedin.com/e/c4xhnw-hh9q7jj3-58/isd/13679634333/yM1ZKmZO/?hs=… -- You are receiving Invitation to Connect emails. Click to unsubscribe: http://www.linkedin.com/e/c4xhnw-hh9q7jj3-58/XqXhe0G_4hwIZ3_xoQuVTfT_syuI36… (c) 2012 LinkedIn Corporation. 2029 Stierlin Ct, Mountain View, CA 94043, USA.

3 4

[chirp_users] Yaesu FT-60 upload fails but download works
by Marcia Stockton 28 May '13

28 May '13

I could use some help figuring out how to make this work. I have tried everything I could think of for 2 days before asking for help. In summary, Chirp 0.3.1 and 0.1.12 will receive configuration data from the Yaesu FT-60 radio, but will not send chirp image data back to the radio to configure it. Permissions on the serial device /dev/ttyS0 are correct: crw-rw---- allowing the dialout group to read/write the serial port, and my userid is a member of the dialout group. The steps I tried are listed below. (Pardon me for the length of the problem-solving narrative but I decided to include a number of false steps and time-consuming problems due to incomplete or erroneous or confusing documentation, in case these are fixable issues, so that others might avoid these troubles.) Thanks for any help you can give. 73, Marcia NU6N ----------------Tried to Solve the Problem Myself------------------ OS = Linux Mint 12 First, installed chirp package from Ubuntu ppa repository (Linux Mint is a Ubuntu derivative and Ubuntu packages almost always work fine): | sudo apt-add-repository ppa:ubuntu-hams-updates/ppa sudo apt-get update sudo apt-get install chirp| What I got was a downlevel chirp 0.1.12. Tested it and chirp 0.1.12 successfully read from the radio. The problem occurs repeatably whenever I try to upload from chirp to the radio. The cable should be OK because it was purchased from Yaesu and has worked before in both directions with Yaesu-provided rig programming software on the same laptop, back when we ran Windows on this laptop. The serial port on the laptop works fine when communicating with the HF rig. And one should try the latest version before asking for help, as the Yaesu FT-60 support might be more complete in the current version, based on differences in the test reports for the two versions ("Test report for CHIRP version 0.1.12" (http://chirp.danplanet.com/download/0.1.12/Test_Report.html shows all functions supported on FT-60 except "clone"; whereas clone is listed as supported on the current beta release 0.3.1 http://chirp.danplanet.com/download/0.3.1/Model_Support.html). I downloaded the 0.3.1 tarball and manually installed it (|sudo python setup.py install)|. I presumed that the necessary libraries were already present as a result of the previous installation of chirp 0.1.12. The manual installation ||produced error messages and chirpw would not run (i.e. was not installed in a way that allowed it to be run from any directory or menu.) However, per the instructions, running chirp 0.3.1 directly from the directory it was unzipped to, via ./chirpw command, worked OK ... except that upload to radio still didn't work. To rule out the possibility of a conflict with code that could have been left over from the 0.1.12 install, I removed chirp 0.1.12 using apt-get remove chirp. Then I manually deleted all files and directories that had been created by the attempted manual install of chirp 0.3.1. || So at this point I am starting over attempting a clean manual install of chirp 0.3.1 from the downloaded tarball. Following the instructions at http://chirp.danplanet.com/projects/chirp/wiki/Running_Under_Linux to ensure all prerequisite libraries are present, sudo apt-get install python-gtk python-serial python-libxml2 produced an error message: Package 'python-gtk' has no installation candidate. I ran apt-get update but still no python-gtk. I then ran a complete sudo apt-get upgrade on my system to ensure all my repository-provided software is up to date. After web research I learned there is no longer a python-gtk but there is a python-gtk2, and it is already installed on my system, and is the newest version. I unpacked chirp 0.3.1 and again ran chirp from inside the directory where it was unpacked. (Did not attempt to run the python installer this time.) Again chirp 0.3.1 ran, with the same results as before: Chirp can receive data from the FT-60 radio, but when data from chirp cannot be sent to the radio. Note that I carefully followed the special sequence instructions required for Yaesu radios, always putting the receiving device into receive mode first, before initiating transmit on the other device. Thus, when attempting to send a couple of memories from chirp to the radio, I did the following, which I believe was correct: a. Put the FT-60 into clone mode with the cable connected to the mic/sp port, by powering on while holding the MONI button. Turn the large knob until 'F8 CLONE' appears. Press F/W key. Radio restarts displaying CLONE. Put radio into Rx mode by pressing MONI. Radio displays ---Rx--- and waits to receive data from chirp. b. On Chirp, select Radio then Upload to Radio. The port, vendor and model are set to the same values that work for receiving data from the radio, i.e.: /dev/ttyS0, Yaesu, FT-60. Click OK to begin transmitting to the radio. c. Chirp's prompt appears showing that Chirp is attempting to transmit to the radio. After a short timeout, error message appears: "An error has occurred. Failed to communicate with radio: Radio did not respond." (Note that the radio still displays ---Rx--- ). Chirp Help, About shows the following: Chirp 0.3.1 GTK 2.24.6 PyGTK 2.24.0 Python 2.7.2+ ---------------------------------------------------------------------------------------------------------

5 11