February 2014 - Users - lists.chirpmyradio.com

[chirp_users] Virginia Beach frequencies
by Dan A 03 Feb '14

03 Feb '14

does anyone by chance have a chirp file with all the Virginia Beach, VA frequencies ? I am looking to program all available 2m & 70cm frequencies Thanks DA -- --------------------------------------------------------------------- Electronic Privacy Notice. This e-mail, and any attachments, contains information that is, or may be, covered by electronic communications privacy laws, and is also confidential and proprietary in nature. If you are not the intended recipient, please be advised that you are legally prohibited from retaining, using, copying, distributing, or otherwise disclosing this information in any manner. Instead, please reply to the sender that you have received this communication in error, and then immediately delete it. Thank you in advance for your cooperation. ---------------------------------------------------------------------

4 3

[chirp_users] FT-60 Upload "Bad Cable" Issue
by Hamilton, William 03 Feb '14

03 Feb '14

I am able to upload to my FT-60 (Windows & RT cable) if I first download and then immediately upload my image. If I attempt to only upload, I get the same error message.

3 2

[chirp_users] General inquiry on adding "settings"
by chirp.cordless＠xoxy.net 02 Feb '14

02 Feb '14

Before I start, this is less a request to give me something for free, more an inquiry whether doing part of the job is enough to get someone else to finish it, and how that might work. I haven't seen this kind of development meta-discussion, so here goes: I'm inquiring about adding Chirp control of feature settings as has been done on a few radios. I can see it's a separate significant project for each radio, but there's some general infrastructure in place since it's been done for some, and presumably the first one was the hardest. Since I'll get asked, my interest is my radios, Yaesu FT-60 & FT-8800. I'm an old unix C hacker, with a bunch of shell and a healthy exposure to a number of others, but I retired before OOLs became needed to use on a regular basis. I can sort of read the Chirp Python source, but I'm thinking there's too much to learn to contribute code. I expect that the first step is to map out the settings in the data stream. For example, the FT-60 seems to have 56 set parameters, most of which can take from 2 to a half dozen or so values. A few, such as repeater shift or tone value seem to be multi-bit data fields that one hopes are encoded binary values that be reverse-engineered with a few samples, and described. I guess the process would be to change a setting via the radio's buttons, read into chirp. and record what changed in the data stream. Rinse and repeat. If someone (me, for example) were to do that and provide the map, would that likely be enough to have someone else pick it up and code it into Chirp? And if so, what form should the 'map' take? Several hundred complete radio images seems less than optimal to me, for several reasons, most obviously that it still needs interpretation to code from. I could probably do a Python const data structure or equivalent if pointed to an example. Just looking to understand this aspect of the development process. Thanks and regards, -dan

2 1

Re: [chirp_users] Baofeng CT-3 programs as ur5 SOMETIMES
by David S. Calef 01 Feb '14

01 Feb '14

Jim (KC9HI): Yes, the GT-3 is referenced, not CT. The Prolific driver 3.3.2.105 dated 10/27/2008 works great on the GT-3 FTDI driver 2.8.30.0 dated 7/12/2013 does NOT work on the GT-3 Jim, the reason I use the FTDi cable and driver is that on my main HP DV7 Windows 7 laptop I use, It refuses to take the older Prolific drivers no matter what I do. I originally had it working and something blew it away. I have used several driver versions that "remove" the Prolific driver before re-installing, but no dice it would not install the older driver. I once removed each driver file component by hand and got it working, but it got blown away again. So I gave up and went to the FTDi series. I love the FTDI cables and drivers. Just disappointed the GT-3 does not work David ND1Q I assume that you meant GT-3. Interesting. We usually recommend FTDI based programing cables to avoid issues like this. Please tell us which driver version does not work and which driver version does. Jim KC9HI

2 1

Re: [chirp_users] Baofeng CT-3 programs as ur5 SOMETIMES
by David S. Calef 01 Feb '14

01 Feb '14

Yes, John, they use the same cable. No, John, the Radio did not respond error is not one described on the miklor site. My plug is trimmed and installed all the way in. The radio was turned on. The FTDi device driver is compatible with the programming cable, works fine on 6 various models of the UR5. The FTDi Programming cable is not defective, works fine on 6 various models of the UR5. So, I appreciate your thoughts, but no, standard errors we have all worked through is not the issue here. Thats why my naïve statement was that it must be a timing issue not seen on the older prolific driver but is seen by the FTDi driver. But then, I am not a developer working on Chirp software. David ND1Q The GT-3 and UV5R use the same programming cable. Is it possible the error could be one of the following described at: http://www.miklor.com/HT/HT-ErrorMess.php John K3NXU

1 0

[chirp_users] Baofeng CT-3 programs as ur5 SOMETIMES
by David S. Calef 01 Feb '14

01 Feb '14

Yes, if you have a Baofeng CT-3, you can program it as a ur5 IF you are using the older prolific driver. I use cables with the FTDI chip and drivers as my main programming cables. These do not work on the CT-3. Work great on 6 various ur5 models I have with no problems at all. The CT-3 will go into error saying the radio did not respond. Must be a timing issue I would guess. David ND1Q

4 3

[chirp_users] Chirp & FT-8800
by Andy 31 Jan '14

31 Jan '14

I've been using the latest build for programming the FT-8800 over the last two weeks. No problem at all. For windows the only issue I've ever had is drivers being updated automatically for the programming cable. Do not allow Windows to do this! Regards, Andy - G8NTH

5 7