[chirp_users] Help needed, can't write to Yaesu FT-60

[Harrison Cooper]

Guess I'll step in (it) here as well

Seems to me there are a couple of issues going on

First, comm ports...ie....is the computer even talking to the cable.  Cable meaning the USB UART, and in this case the drivers looking for the prolific chips.  You can use a number of utilities available, at least on a  PC (sorry Mac and Linux users..but im sure the Linux community has similar things) to go out and query a device on the USB to get its VID and PID.  
So if in the hardware manager, you have a banged (for win7) or unknown device connected, that simply means the driver is not loaded and then you can check the USB.org listing of VID numbers.  For win7, those can also be found under the properties.  Bottom line..you can identify what USB UART you have sitting there.  Once you get the correct driver, it should work as the software simply says...push data in and out of com port N.   Correct me if I'm wrong authors, but you could care less what device is there, just as long as the OS knows it's a com port and it can set it up.   FYIW, the VID and PID are located in the driver .inf file, so you can open that up and check to see if your VID and PID are listed.  That's typically why a driver wont work (or be found).  Word of caution...DONT edit that file if your on win7, as then it will no longer be a signed driver...and win7 insists on that.  XP...you ok to edit (why would you tho?).

So now you have a valid driver, and really what you have is a USB UART serial interface.  USB one side, TTL (5V or 3.3V) serial on the other.  I haven't looked close enough to see if the big pin is tx or rx, and polarity but the circuits are on the web.  

Using a com program (putty, Xterm, etc) you can do two things.

First tie the tips together (assuming they are the hot signals) and you ought to have a loop back.  Just type and it should come back on the screen.

Second, if someone who is an author can chime in...whats the typical baud rate, etc for the port setup and how do you put it into the command mode?  You should be able to check it that way as well.  FYIW, I have the UV5R, connecting to TeraTerm I didn't see anything coming out.  Rather surprised, I would have thought it would have sent a string but since it's the mic connector as well...maybe you have to send it something first.

So that's my 2cents worth.

-----Original Message-----
From: chirp_users-bounces at intrepid.danplanet.com [mailto:chirp_users-bounces at intrepid.danplanet.com] On Behalf Of IZ3GME Marco
Sent: Thursday, September 27, 2012 12:24 PM
To: Discussion of CHIRP
Subject: Re: [chirp_users] Help needed, can't write to Yaesu FT-60

On 27/09/2012 20:09, Tom Hayward wrote:
> - A cable test as Rob suggested involves shorting two pins on the 
> cable--not something Chirp can do for you.

But we have some radio, like the FT60 itself, that use cables with tx and rx shorted.
Right now we simply throw away the echoed char in those drivers as far as I know.

Starting with them can be better than nothing ...

just my two cents ....

73 de IZ3GME Marco
_______________________________________________
chirp_users mailing list
chirp_users at intrepid.danplanet.com
http://intrepid.danplanet.com/mailman/listinfo/chirp_users

This e-mail (and any attachments) is confidential and may be privileged.  Any unauthorized use, copying, disclosure or dissemination of this communication is prohibited.  If you are not the intended recipient,  please notify the sender immediately and delete all copies of the message and its attachments.