I don't understand your question. The guy who writes the upload software that resides in the radio "determines" (i.e., controls) what it is possible to write. The design and implementation team that designs and implents the radio hardware and software "determine" what they think you are "supposed to" write. They will have some level of trust (ranging from totally paranoid to totally accepting) of the uploader software and the data being sent from the computer. Clearly, If the radio performs no checking and the softwrae performs no checking, then the uploading computer software can send data that the radio's software can use to brick the radio.
This would require: 1)clueless software in the radio 2)no checking by the computer software that it's the correct radio type for the software 3)no checking by the computer operator that the software matches the radio. When you say "I've seen bricks", can you provide examples? What exactly happened? if it's was a Radio-computer mismatch, then was taht a way thta the computrer could have identified the mismatch in advance? If there is no way to identify a mismatch, then you must either avoid using that software or you must accept responsibility as the operator to avoid the mismatch. On Fri, May 24, 2019 at 2:00 PM Chance Fulton <[email protected]> wrote: > Who determines what you are supposed to write to and what you’re not? I’ve > seen bricks when you write the wrong image on image based radios. > 73 > AD8CJ > > On Fri, May 24, 2019 at 4:13 PM John Kemker <[email protected]> wrote: > >> Just got off the phone with Yaesu tech support. I wanted to know if it >> was a Yaesu policy to tell people not to use CHIRP. >> >> They say they've seen bricked radios caused by CHIRP. Said it's because >> CHIRP wrote to areas they're not supposed to write to. Said that RT >> Systems "works with Yaesu" and that's why they support RT Systems. Who >> would write the internal software for a radio where the programming >> software could brick it? >> >> On Fri, May 24, 2019 at 3:33 PM Ben Smith <[email protected]> wrote: >> >>> I love chirp but there are some know bugs with yeasu radios. Doesn't >>> mean you shouldn't use it though. >>> https://chirp.danplanet.com/issues/1735 >>> >>> On Fri, May 24, 2019, 12:25 John Kemker <[email protected]> wrote: >>> >>>> Just got off the phone with a national amateur radio vendor, asking if >>>> they had the cable for my FTM3200DR for sale. I was told they have the >>>> cable with the RT-Systems ADMS software, but not the cable by itself. I >>>> told the salesperson that I didn't need the software, that I had used CHIRP >>>> for years and he proceeded to tell me "You know, you're not supposed to use >>>> CHIRP with Yaesu radios...." I cut him off before he got finished with his >>>> statement and told him that it was an old wives' tale and not true. >>>> >>>> That's the second time I've heard the same propaganda from that >>>> particular vendor's sales team. >>>> >>>> 73 de W5NNH >>>> >>>> On Wed, May 22, 2019 at 9:54 AM Peter J. McClosky < >>>> [email protected]> wrote: >>>> >>>>> While I have only programed 1 Yeasu (successful), I have programed >>>>> over 150 Baofengs and Wouxuns, all but 2 successfully on the first try. (I >>>>> am the unofficial "programer” for my club). >>>>> >>>>> I made a simi-brick out of 2 Baofengs. It look a while, but I was >>>>> successful in restoring both of these to full use. >>>>> >>>>> I find that lack of understanding how to use Chirp leads to problems >>>>> in using it. >>>>> >>>>> (Also, and contrary to most rumors, I have never found a programming >>>>> cable that did not work.) >>>>> >>>>> Peter, N7IY >>>>> >>>>> P.S, Before anyone says anything, the way I program Baofengs, they >>>>> will not transmit outside of the amateur radio bands. >>>>> ----- >>>>> Peter J. McClosky, N7IY >>>>> Eugene, Oregon >>>>> [email protected] >>>>> [email protected] >>>>> http://home.earthlink.net/~pmcclosky/ >>>>> >>>>> On May 22, 2019, at 4:07 AM, John Kemker <[email protected]> wrote: >>>>> >>>>> Yeasu >>>>> >>>>> >>>>> _______________________________________________ >>>>> chirp_users mailing list >>>>> [email protected] >>>>> http://intrepid.danplanet.com/mailman/listinfo/chirp_users >>>>> This message was sent to W5NNH at [email protected] >>>>> To unsubscribe, send an email to >>>>> [email protected] >>>> >>>> >>>> >>>> -- >>>> --John E Kemker III >>>> _______________________________________________ >>>> chirp_users mailing list >>>> [email protected] >>>> http://intrepid.danplanet.com/mailman/listinfo/chirp_users >>>> This message was sent to TheX1le at [email protected] >>>> To unsubscribe, send an email to >>>> [email protected] >>> >>> _______________________________________________ >>> chirp_users mailing list >>> [email protected] >>> http://intrepid.danplanet.com/mailman/listinfo/chirp_users >>> This message was sent to W5NNH at [email protected] >>> To unsubscribe, send an email to >>> [email protected] >> >> >> >> -- >> --John E Kemker III >> _______________________________________________ >> chirp_users mailing list >> [email protected] >> http://intrepid.danplanet.com/mailman/listinfo/chirp_users >> This message was sent to Chance at [email protected] >> To unsubscribe, send an email to >> [email protected] > > -- > Chance Fulton > [email protected] > 810.441.5795 > _______________________________________________ > chirp_users mailing list > [email protected] > http://intrepid.danplanet.com/mailman/listinfo/chirp_users > This message was sent to Dan Clemmensen at [email protected] > To unsubscribe, send an email to > [email protected]
_______________________________________________ chirp_users mailing list [email protected] http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to [email protected] at [email protected] To unsubscribe, send an email to [email protected]
