<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body dir="auto"><div dir="auto">Yes. There is a certain non-Yaesu handheld which must have a certain chip in it replaced periodically due it only being able to accept a limited number of memory changes.</div><div dir="auto"><br></div><div dir="auto">I cannot remember the exact unit, but it was detailed on youtube, both the problem involved and how to change the chip.</div><div dir="auto"><br></div><div dir="auto">I think it was Wouxan (sp?). In any case, I own one.</div><div dir="auto"><br></div><div dir="auto">Ken W7EKB</div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto"><br></div><div id="composer_signature" dir="auto"><div style="font-size:12px;color:#575757" dir="auto">Sent via the Samsung Galaxy S21 5G, an AT&T 5G smartphone</div></div><div dir="auto"><br></div><div><br></div><div align="left" dir="auto" style="font-size:100%;color:#000000"><div>-------- Original message --------</div><div>From: Ken Hansen <ken@n2vip.org> </div><div>Date: 5/16/23 08:38 (GMT-08:00) </div><div>To: Discussion of CHIRP <chirp_users@intrepid.danplanet.com> </div><div>Subject: Re: [chirp_users] Yaesu FT8800 </div><div><br></div></div>Yaesu claims it happened, but it happened to a very particular radio for a very particular reason that doesn't apply to the vast of current Yaesu radios.<br><br>IIRC, the issue had to do with rewriting a part of the radio memory that Yaesu implemented with a chip that had a low update count/life (making up an example, the part in question could only be updated, say, 200 times before the part would fail), but Yaesu would simply avoid updating that memory space while chirp did, and thus 'wore out' a particular part - and Yaesu was unable to secure replacement parts for the part in question, thus 'bricked' radios.<br><br>I believe that is a fair description of what happened, I recall a post (here?) not to long ago that explained the situation in greater detail. <br><br>Ken, N2VIP<br><br>> On May 16, 2023, at 05:41, Henry Mensch <henry@n6hcm.com> wrote:<br>> <br>> yaesu pushes this sort of. nonsense to get their customers t use yaesu-approved solutions.<br>> <br>> This attitude, in turn, is why I no longer buy yaesu radio gear.<br>> <br>> - Henry / N6HCM<br>> <br>>> On May 15, 2023 15:03:54 "Nigel A. Gunn G8IFF/W8IFF" <nigel@ngunn.net> wrote:<br>>> <br>>> Just a rumour. I've never known Chirp to damage a radio.<br>>> <br>>> <br>>>>> On 15/05/2023 18:28 GMT Don Farrow <ve3ulf@cogeco.ca> wrote:<br>>>> <br>>>> <br>>>> Greeting everyone . I am look to see if anyone is familiar with<br>>>> Programing the Yaesu FT8800 using the Chirp Software , i have read some<br>>>> posts that chirp could damage your radio.<br>>>> <br>>>> 73s Thanks Don VE3ULF<br>>>> <br>>>> _______________________________________________<br>>>> chirp_users mailing list<br>>>> chirp_users@intrepid.danplanet.com<br>>>> http://intrepid.danplanet.com/mailman/listinfo/chirp_users<br>>>> This message was sent to Nigel Gunn, W8IFF at nigel@ngunn.net<br>>>> To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com<br>>>> To report this email as off-topic, please email chirp_users-owner@intrepid.danplanet.com<br>>>> Searchable archive: https://www.mail-archive.com/chirp_users@intrepid.danplanet.com<br>>> <br>>> Nigel A. Gunn, ///shoulders.outwards.resolutions tel +1-937-971-0366<br>>> Amateur Radio G8IFF W8IFF and GMRS WRBV701, e-mail nigel@ngunn.net www http://www.ngunn.net<br>>> _______________________________________________<br>>> chirp_users mailing list<br>>> chirp_users@intrepid.danplanet.com<br>>> http://intrepid.danplanet.com/mailman/listinfo/chirp_users<br>>> This message was sent to Henry Mensch at henry@n6hcm.com<br>>> To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com<br>>> To report this email as off-topic, please email chirp_users-owner@intrepid.danplanet.com<br>>> Searchable archive: https://www.mail-archive.com/chirp_users@intrepid.danplanet.com<br>> <br>> <br>> <br>> _______________________________________________<br>> chirp_users mailing list<br>> chirp_users@intrepid.danplanet.com<br>> http://intrepid.danplanet.com/mailman/listinfo/chirp_users<br>> This message was sent to Ken Hansen at ken@n2vip.org<br>> To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com<br>> To report this email as off-topic, please email chirp_users-owner@intrepid.danplanet.com<br>> Searchable archive: https://www.mail-archive.com/chirp_users@intrepid.danplanet.com<br>_______________________________________________<br>chirp_users mailing list<br>chirp_users@intrepid.danplanet.com<br>http://intrepid.danplanet.com/mailman/listinfo/chirp_users<br>This message was sent to Ken Gordon W7EKB at kgordon2006@frontier.com<br>To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com<br>To report this email as off-topic, please email chirp_users-owner@intrepid.danplanet.com<br>Searchable archive: https://www.mail-archive.com/chirp_users@intrepid.danplanet.com</body></html>