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

[David Ranch]

I think Rob has an EXCELLENT idea there.. having a "cable test" feature 
in Chirp just to do some testing (data integrity tests, etc) would 
probably help a LOT of people troubleshoot.    If the test fails, Chirp 
could open a dialog box telling say Ubuntu people to make sure their 
username is in the dialout category, check the baud rates on their radio 
(list some common baud rates for some common manufacturers, etc).  Give 
a URL to a FAQ on bad Prolific drivers (windows, Mac, etc.)

With all that, the user is more empowered to fix things themselves, get 
less of this stuff on the email list, etc.

--David


> On 9/26/2012 3:00 PM, chirp.cordless at xoxy.net wrote:
>> What's next?
> Another thing you could try is to do a loop back test of your cable
> with the cable disconnected from the radio.
>
> IIRC some of the Yaesu cables share a pin for TxD and RxD so the computer
> will read back anything that it sends.   I don't know the FT-60 so you'll
> need to look up the wiring of the cable.
>
> If it isn't that type of cable, you can set up your own loop back test
> by shorting the cables TxD and RxD pins together.  Of course be careful
> not to short anything else.
>
> Once you've got TxD and RxD connected, you should be able to go into
> a terminal program and see anything you type echoed back.
>
> Just a thought.
> --Rob
>
>
> _______________________________________________
> chirp_users mailing list
> chirp_users at intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_users