[chirp_users] Programming of Baofeng UV-5RA transceiver

Jim Unroe rock.unroe at gmail.com
Mon Mar 11 18:02:23 PDT 2013


Check back though the messages for the last 2 or 3 days. Someone described
how they setup their Win 8 computer. I believe this is it.

http://groups.yahoo.com/group/baofeng_uv5r/message/23154

Jim KC9HI

On Mon, Mar 11, 2013 at 8:39 PM, Don <dbwjr1949 at verizon.net> wrote:

> Is there a programming fix for the Baofeng UV-5RA transceiver with
> firmware BFB297?  I ordered the programming cable and cd from amazon.com,
> but was sent the cd for the UV-5R transceiver which does not work (I
> guess).  I have windows 8 so I really could not try this cd for obvious
> reasons.  Any help will be greatly appreciated.
>
> Thank you,
>
> Don, KB3ZUF
>
>
> On 03/11/13, chirp_users-request at intrepid.danplanet.com wrote:
>
> Send chirp_users mailing list submissions to
> chirp_users at 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 at intrepid.danplanet.com
>
> You can reach the person managing the list at
> chirp_users-owner at 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: Yaesu FT-7900R driver needed. I think :) (Tom Hayward)
> 2. win xp (jim)
> 3. Re: Yaesu FT-7900R driver needed. I think :)
> (chirp.cordless at xoxy.net)
> 4. Re: win xp (Bry Carling)
> 5. Re: win xp (Alan Hill)
> 6. Re: Yaesu FT-7900R driver needed. I think :) (Apple //GS)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 11 Mar 2013 12:18:54 -0700
> From: Tom Hayward esarfl at gmail.com>
> Subject: Re: [chirp_users] Yaesu FT-7900R driver needed. I think :)
> To: Discussion of CHIRP <chirp_users at intrepid.danplanet.com>
> Message-ID:
> <CAFXO5Z3MZNLC5G-_aLEjzpJQmZTtphVd9=Bvcr9JTXJX-R9a4A at mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> On Mon, Mar 11, 2013 at 11:52 AM, M.F. apple2gs at sbcglobal.net> wrote:
> > Hi Tom,
> >
> > I an in Windows mode right now, and I did download the FTDI-FT-Device: 0
> >
> > Now what? I feel so dumb, but I have no idea what to do. I am sorry to
> all
> > of you for asking what must be simple stuff.
>
> I don't remember exactly what it looks like, but in FT_Prog, select
> the Vendor ID and reset to default, then select the Product ID and
> reset to defaults. Note that this will make the cable incompatible
> with RT Systems software. You can, however, reverse the process by
> typing the original Vendor and Product IDs back into FT_Prog.
>
> Tom KD7LXL
>
>
> ------------------------------
>
> Message: 2
> Date: Mon, 11 Mar 2013 12:23:48 -0400
> From: jim jmsrandazzo at gmail.com>
> Subject: [chirp_users] win xp
> To: chirp_users at intrepid.danplanet.com
> Message-ID: <513E0514.90509 at gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> To any one out there .. that have Windows XP i have Windows XP with
> service
> pack 3 and i do not have any problems with XP what i have found out about
> chrip is find the right cable or drivers and you well not have any
> problems
> at all i have used chrip with win 7 win 8 win xp come on out there study
> your Radio or radios you are going to buy get the right stuff and and use
> chrip you well not have any problems with this program..
>
>
>
> ------------------------------
>
> Message: 3
> Date: Mon, 11 Mar 2013 12:28:54 -0700
> From: chirp.cordless at xoxy.net
> Subject: Re: [chirp_users] Yaesu FT-7900R driver needed. I think :)
> To: chirp_users at intrepid.danplanet.com
> Message-ID: <54E08EEA-104A-40B1-A698-AEBED03D11B1 at cox.net>
> Content-Type: text/plain; charset=us-ascii
>
> Not quite my experience. Note I'm the author of the second link
> below, under "Modify OS X driver". That's what I _ENDED UP_ doing,
> because it amused me, and there were some small benefits, as that
> post explains.
>
> However, go back to earlier in that same thread, here:
> http://intrepid.danplanet.com/pipermail/chirp_users/2012-September/002585.
> html
>
> You can get this working in a turnkey manner by loading the Mac
> driver that RT systems provides. And BTW, I don't know where you
> got your RT Systems cable, but it likely comes with a CD with the
> Windows driver you need.
>
> In the middle of that post is the link you want for the Mac driver:
> http://www.rtsystemsinc.com/kb_results.asp?ID=9
> and if you search around on that same support site, I think
> you'll find the windows drivers. Here:
> http://www.rtsystemsinc.com/kb_results.asp?ID=15
>
> If you want more details, please read those two posts, and maybe
> some more of that same thread.
>
> -dan
>
> On Mar 11, 2013, at 10:30 AM, "Tom Hayward - esarfl at gmail.com" wrote:
> > On Mon, Mar 11, 2013 at 10:20 AM, Apple //GS apple2gs at sbcglobal.net>
> wrote:
> >> Hello Dan :)
> >>
> >> The cable is CT29B Radio Cable:
> >>
> >> CT29B Radio Cable:
> >>
> >> Product ID: 0x9e54
> >> Vendor ID: 0x2100
> >> Version: 6.00
> >> Serial Number: RTWA39NN
> >> Speed: Up to 12 Mb/sec
> >> Manufacturer: RT Systems
> >> Location ID: 0xfa123000 / 8
> >> Current Available (mA): 500
> >> Current Required (mA): 90
> >
> > RT Systems cables are designed to work *only* with RT Systems
> > software. There are two options for getting this cable to work with
> > any other programming software: modify your OS X driver, or modify
> > your cable. I modified my cable (this is a firmware mod, no soldering
> > required).
> >
> > Modify the cable's FTDI firmware:
> > http://intrepid.danplanet.com/pipermail/chirp_users/2013-January/002988.
> html
> >
> > Modify OS X driver:
> > http://intrepid.danplanet.com/pipermail
> /chirp_users/2012-September/002612.html
>
>
>
>
> ------------------------------
>
> Message: 4
> Date: Mon, 11 Mar 2013 16:45:56 -0400
> From: "Bry Carling" bcarling at cfl.rr.com>
> Subject: Re: [chirp_users] win xp
> To: chirp_users at intrepid.danplanet.com
> Message-ID: <513E4284.1172.3B2C10 at bcarling.cfl.rr.com>
> Content-Type: text/plain; charset="us-ascii"
>
> This makes it sound easy but it wasn't at all.
>
> The program failing to start has noting to do with the cable or the radio.
>
> It has to do with the fact that Chirp requires SP3 and Windows XP is not
> something
> that upgrades easily to SP3 from SP1 or SP2. If you don't believe me, read
> the hundreds of
> horror stories all over the web. If it was just me that would be one
> thing. In the case of my
> laptop, Chirp would not start at all, so I know it hasn't checked what
> radio, drivers or cable is
> connected.
>
> On 11 Mar 2013 at 12:23, jim wrote:
>
> > To any one out there .. that have Windows XP i have Windows XP with
> > service
> > pack 3 and i do not have any problems with XP what i have found out
> > about
> > chrip is find the right cable or drivers and you well not have any
> > problems
> > at all i have used chrip with win 7 win 8 win xp come on out there
> > study
> > your Radio or radios you are going to buy get the right stuff and
> > and use
> > chrip you well not have any problems with this program..
> >
> > _______________________________________________
> > chirp_users mailing list
> > chirp_users at intrepid.danplanet.com
> > http://intrepid.danplanet.com/mailman/listinfo/chirp_users
> >
> >
> > -----
> > No virus found in this message.
> > Checked by AVG - www.avg.com
> > Version: 2013.0.2904 / Virus Database: 2641/6164 - Release Date:
> > 03/11/13
> >
>
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: http://intrepid.danplanet.com/pipermail
> /chirp_users/attachments/20130311/ed8bbe33/attachment-0001.html
>
> ------------------------------
>
> Message: 5
> Date: Mon, 11 Mar 2013 13:54:27 -0700
> From: Alan Hill alan.r.hill at gmail.com>
> Subject: Re: [chirp_users] win xp
> To: Brian Carling AF4K bcarling at cfl.rr.com>, Discussion of CHIRP
> <chirp_users at intrepid.danplanet.com>
> Message-ID:
> w==KZQxco6mGAygpkoE2g at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> I've found that you have to run it as administrator to work. It will not
> show menus until it can access the serial i/o.
> 73,
> Alan - W6ARH
> P.S. It doesn't work at all with my Yeasu radios under 32 bit Win 7. It
> does work on the same computer with the live CD.
>
>
>
>
> On Mon, Mar 11, 2013 at 1:45 PM, Bry Carling bcarling at cfl.rr.com> wrote:
>
> > **
> > This makes it sound easy but it wasn't at all.
> >
> > The program failing to start has noting to do with the cable or the
> > radio.
> >
> > It has to do with the fact that Chirp requires SP3 and Windows XP is not
> > something
> > that upgrades easily to SP3 from SP1 or SP2. If you don't believe me,
> read
> > the hundreds of horror stories all over the web. If it was just me that
> > would be one thing. In the case of my laptop, Chirp would not start at
> all,
> > so I know it hasn't checked what radio, drivers or cable is connected.
> >
> > On 11 Mar 2013 at 12:23, jim wrote:
> >
> > *> To any one out there .. that have Windows XP i have Windows XP with*
> > *> service*
> > *> pack 3 and i do not have any problems with XP what i have found out*
> > *> about*
> > *> chrip is find the right cable or drivers and you well not have any*
> > *> problems*
> > *> at all i have used chrip with win 7 win 8 win xp come on out there *
> > *> study*
> > *> your Radio or radios you are going to buy get the right stuff and *
> > *> and use*
> > *> chrip you well not have any problems with this program..*
> > *> *
> > *> _______________________________________________*
> > *> chirp_users mailing list*
> > *> chirp_users at intrepid.danplanet.com*
> > *> http://intrepid.danplanet.com/mailman/listinfo/chirp_users*
> > *> *
> > *> *
> > *> -----*
> > *> No virus found in this message.*
> > *> Checked by AVG - www.avg.com*
> > *> Version: 2013.0.2904 / Virus Database: 2641/6164 - Release Date:*
> > *> 03/11/13*
> > *> *
> >
> >
> >
> > _______________________________________________
> > chirp_users mailing list
> > chirp_users at intrepid.danplanet.com
> > http://intrepid.danplanet.com/mailman/listinfo/chirp_users
> >
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: http://intrepid.danplanet.com/pipermail
> /chirp_users/attachments/20130311/27186d76/attachment-0001.html
>
> ------------------------------
>
> Message: 6
> Date: Mon, 11 Mar 2013 18:27:00 -0400
> From: Apple //GS <apple2gs at sbcglobal.net>
> Subject: Re: [chirp_users] Yaesu FT-7900R driver needed. I think :)
> To: Discussion of CHIRP <chirp_users at intrepid.danplanet.com>
> Message-ID: <D0CC7AAD-6D55-4AAE-B409-835FDA90E1D0 at sbcglobal.net>
> Content-Type: text/plain; charset=windows-1252
>
> Okay.
>
> First thank you all so very much trying to help me
> CHIRP now has " /dev/cu.usbserial-RTWA39NN " in the pull down menu.
> I picked both the 7800 and the 8900 to test to see if one of them would
> work.
>
> This is what it said to be on both tries:
> Failed to communicate with radio: Failed to read header (0)
>
>
> ??.. :(
>
> -Mark
>
>
>
> On Mar 11, 2013, at 3:28 PM, chirp.cordless at xoxy.net wrote:
>
> > Not quite my experience. Note I'm the author of the second link
> > below, under "Modify OS X driver". That's what I _ENDED UP_ doing,
> > because it amused me, and there were some small benefits, as that
> > post explains.
> >
> > However, go back to earlier in that same thread, here:
> > http://intrepid.danplanet.com/pipermail
> /chirp_users/2012-September/002585.html
> >
> > You can get this working in a turnkey manner by loading the Mac
> > driver that RT systems provides. And BTW, I don't know where you
> > got your RT Systems cable, but it likely comes with a CD with the
> > Windows driver you need.
> >
> > In the middle of that post is the link you want for the Mac driver:
> > http://www.rtsystemsinc.com/kb_results.asp?ID=9
> > and if you search around on that same support site, I think
> > you'll find the windows drivers. Here:
> > http://www.rtsystemsinc.com/kb_results.asp?ID=15
> >
> > If you want more details, please read those two posts, and maybe
> > some more of that same thread.
> >
> > -dan
> >
> > On Mar 11, 2013, at 10:30 AM, "Tom Hayward - esarfl at gmail.com" wrote:
> >> On Mon, Mar 11, 2013 at 10:20 AM, Apple //GS apple2gs at sbcglobal.net>
> wrote:
> >>> Hello Dan :)
> >>>
> >>> The cable is CT29B Radio Cable:
> >>>
> >>> CT29B Radio Cable:
> >>>
> >>> Product ID: 0x9e54
> >>> Vendor ID: 0x2100
> >>> Version: 6.00
> >>> Serial Number: RTWA39NN
> >>> Speed: Up to 12 Mb/sec
> >>> Manufacturer: RT Systems
> >>> Location ID: 0xfa123000 / 8
> >>> Current Available (mA): 500
> >>> Current Required (mA): 90
> >>
> >> RT Systems cables are designed to work *only* with RT Systems
> >> software. There are two options for getting this cable to work with
> >> any other programming software: modify your OS X driver, or modify
> >> your cable. I modified my cable (this is a firmware mod, no soldering
> >> required).
> >>
> >> Modify the cable's FTDI firmware:
> >> http://intrepid.danplanet.com/pipermail
> /chirp_users/2013-January/002988.html
> >>
> >> Modify OS X driver:
> >> http://intrepid.danplanet.com/pipermail
> /chirp_users/2012-September/002612.html
> >
> >
> > _______________________________________________
> > chirp_users mailing list
> > chirp_users at intrepid.danplanet.com
> > http://intrepid.danplanet.com/mailman/listinfo/chirp_users
>
>
>
> ------------------------------
>
> _______________________________________________
> chirp_users mailing list
> chirp_users at intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
>
>
> End of chirp_users Digest, Vol 51, Issue 24
> *******************************************
>
> _______________________________________________
> chirp_users mailing list
> chirp_users at intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20130311/6b85f7f8/attachment-0001.html 


More information about the chirp_users mailing list