[chirp_users] Tim at Yaesu Tech Support warns against Chirp, recommends RT Systems products

[Charles Stillman]

I'm just speculating here as to what (if any) problems people might have reported to Yaesu. It certainly is possible to do damage with an inappropriate cable for example. Some people are quite willing to try the "blue smoke test" prior to reading the manual!

Charlie KC1S


On Oct 17, 2013, at 3:09 PM, Tom Hayward <esarfl at gmail.com> wrote:

> On Thu, Oct 17, 2013 at 3:05 PM, Tom Hayward <esarfl at gmail.com> wrote:
>> On Thu, Oct 17, 2013 at 3:02 PM, Charles Stillman <datademon at aol.com> wrote:
>>> Tim at Yaesu tech support says that Chirp "burns out" EEPROMS on Yaesu radios. He says that results in the radios locking up. It was not clear whether he was saying that the EEPROM was destroyed or just programmed into a state that the radio would no longer work. I'm guessing that this might have been a problem during Chirp development and is no longer the case. I see that there are several steps involved in programming the Yaesu radios with Chirp. Does failure to follow the steps precisely create a risk to the usability of the radio? Sorry if this has been discussed before.
>> 
>> No radios have EVER been permanently damaged during Chirp development.
>> I bet he has absolutely zero evidence to support his claims.
> 
> By the way, if you use a program like portmon to monitor the data
> Chirp sends to the radio, you'll find it sends exactly the same thing
> as RT Systems software or a clone from an identical model radio.
> 
> Tom KD7LXL
> _______________________________________________
> chirp_users mailing list
> chirp_users at intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_users