<div dir="ltr">Benton,<div><br></div><div>I agree. I mentioned to the Yaesu tech that they should publish a standard for anyone to follow, but I got the typical closed architecture excuses of not wanting to give away their work. Apple was mentioned as an example, but when I mentioned that Apple is based upon BSD, an open source OS, and Red Hat was just bought by IBM and the majority of the Internet runs on Linux, that line of argument quickly died.</div><div><br></div><div>Who maintains most of the Yaesu modules for CHIRP? Has anyone ever tried to reach out to Yaesu to "work with" them to get the Yaesu seal of approval? If Yaesu is willing to cooperate without charging a huge fee, that is.</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, May 24, 2019 at 7:30 PM John Kemker <<a href="mailto:kemkerj3@gmail.com">kemkerj3@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">George, I agree 100%. If I'd realized that this would be an issue, I probably would not have bought not one, but two, Yaesu radios in the last 6 months. Unless I see a serious change in their openness, these will probably be the only two Yaesu radios I ever buy.<div><br></div><div>I encourage all of you to let others know. Some folks won't care, as they see nothing wrong with what Yaesu is doing. That's fine. But, for those of us who do care, we need to be informed before we buy.</div><div><br></div><div>73 de W5NNH</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, May 24, 2019 at 7:18 PM George Hale Jr. <<a href="mailto:ghalejr@gmail.com" target="_blank">ghalejr@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>I find it sad that a big name radio maker would fight to keep programming propriety. Perhaps it is a way to help dealers to continue receiving revenue after the sale. As far back as I can remember, the Ham radio hobby was aimed at the amateur, and electronics enthusiast. Several of these big name companies have always tried to keep the electronic fiddlers out of their boxes. Its been other hams that have built better ways to use those boxes, building interfaces for allowing computers to have a place in the ham shacks, and the big names have reluctantly followed along, but tried to put boulders in the path. I still have a crystal radio I made at a ham feast back in the early 70's. Its that do it yourself flavor of the hobby that has kept me in it. Most of my equipment has been modded in one form or another. Sadly, that is what keeps me away from the big name radios. Yea, I miss Heathkits.</div><div><br></div><div>If the big names do not want to open up to us, I say do not buy them.</div><div><br></div><div>George<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, May 24, 2019 at 4:36 PM Josef Zeevi <<a href="mailto:jz@zeevi.org" target="_blank">jz@zeevi.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto">"Shouldn't" but apparently might. <br><br><div id="gmail-m_8579653619489175087gmail-m_-8993825770841542479gmail-m_-7047100689816192864AppleMailSignature" dir="ltr"><span style="background-color:rgba(255,255,255,0)">Josef</span><div><span style="background-color:rgba(255,255,255,0)">Sent from a phone with a tiny screen </span></div></div><div dir="ltr"><br>On May 24, 2019, at 5:27 PM, John Kemker <<a href="mailto:kemkerj3@gmail.com" target="_blank">kemkerj3@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div dir="ltr"><div dir="ltr">We're not talking about writing a new image of the firmware. We're talking about sending parameters to fit into a memory slot. The memory slot shouldn't leak over into another slot, the firmware shouldn't accept just any kruft that's sent to it, and it should ALWAYS allow a reset to factory defaults by the front panel. Anything else is just poor programming practice.<div><br></div><div>As far as good vs. fast vs. cheap, Yaesu is not the cheapest out there. I find it hard to believe that they don't have as good a software standard as less-expensive brands.</div><div><br></div><div>Dan, I understand your 3 requirements. I'm assuming that CHIRP is performing at least some basic checks to make sure that the radio is the one that they're expecting. That leaves 1 and 3, or a combination of both.</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, May 24, 2019 at 5:19 PM Dan Clemmensen <<a href="mailto:danclemmensen@gmail.com" target="_blank">danclemmensen@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>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.</div><div><br></div><div>This would require:</div><div> 1)clueless software in the radio</div><div> 2)no checking by the computer software that it's the correct radio type for the software</div><div> 3)no checking by the computer operator that the software matches the radio.</div><div><br></div><div>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.<br></div><div><br></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, May 24, 2019 at 2:00 PM Chance Fulton <<a href="mailto:chance.fulton@gmail.com" target="_blank">chance.fulton@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div dir="auto">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.</div></div><div dir="auto">73</div><div dir="auto">AD8CJ</div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, May 24, 2019 at 4:13 PM John Kemker <<a href="mailto:kemkerj3@gmail.com" target="_blank">kemkerj3@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">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.<div><br></div><div>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?</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, May 24, 2019 at 3:33 PM Ben Smith <<a href="mailto:thex1le@gmail.com" target="_blank">thex1le@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto">I love chirp but there are some know bugs with yeasu radios. Doesn't mean you shouldn't use it though.<div dir="auto"><a href="https://chirp.danplanet.com/issues/1735" target="_blank">https://chirp.danplanet.com/issues/1735</a><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, May 24, 2019, 12:25 John Kemker <<a href="mailto:kemkerj3@gmail.com" target="_blank">kemkerj3@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">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.<div><br></div><div>That's the second time I've heard the same propaganda from that particular vendor's sales team.</div><div><br></div><div>73 de W5NNH</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, May 22, 2019 at 9:54 AM Peter J. McClosky <<a href="mailto:pmcclosky@earthlink.net" rel="noreferrer" target="_blank">pmcclosky@earthlink.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>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). <div><br></div><div>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.<div><br></div><div>I find that lack of understanding how to use Chirp leads to problems in using it. </div><div><br></div><div>(Also, and contrary to most rumors, I have never found a programming cable that did not work.)</div><div><br></div><div>Peter, N7IY</div><div><br></div><div>P.S, Before anyone says anything, the way I program Baofengs, they will not transmit outside of the amateur radio bands.</div><div><div><div>
<div style="color:rgb(0,0,0);font-family:Helvetica;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">-----</div><div style="color:rgb(0,0,0);font-family:Helvetica;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">Peter J. McClosky, N7IY<br>Eugene, Oregon<br><a href="mailto:pmcclosky@earthlink.net" rel="noreferrer" target="_blank">pmcclosky@earthlink.net</a><br><a href="mailto:n7iy@arrl.net" rel="noreferrer" target="_blank">n7iy@arrl.net</a><br><a href="http://home.earthlink.net/~pmcclosky/" rel="noreferrer" target="_blank">http://home.earthlink.net/~pmcclosky/</a></div>
</div>
<br><div><blockquote type="cite"><div>On May 22, 2019, at 4:07 AM, John Kemker <<a href="mailto:kemkerj3@gmail.com" rel="noreferrer" target="_blank">kemkerj3@gmail.com</a>> wrote:</div><br class="gmail-m_8579653619489175087gmail-m_-8993825770841542479gmail-m_-7047100689816192864gmail-m_2357984566551695743gmail-m_5039172728093010839m_5858939534540335777gmail-m_2253011044091612338m_4251631412743921844gmail-m_1501479249370278283Apple-interchange-newline"><div><span style="font-family:monospace,monospace;font-size:18px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline">Yeasu</span></div></blockquote></div><br></div></div></div></div>_______________________________________________<br>
chirp_users mailing list<br>
<a href="mailto:chirp_users@intrepid.danplanet.com" rel="noreferrer" target="_blank">chirp_users@intrepid.danplanet.com</a><br>
<a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users" rel="noreferrer noreferrer" target="_blank">http://intrepid.danplanet.com/mailman/listinfo/chirp_users</a><br>
This message was sent to W5NNH at <a href="mailto:kemkerj3@gmail.com" rel="noreferrer" target="_blank">kemkerj3@gmail.com</a><br>
To unsubscribe, send an email to <a href="mailto:chirp_users-unsubscribe@intrepid.danplanet.com" rel="noreferrer" target="_blank">chirp_users-unsubscribe@intrepid.danplanet.com</a></blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail-m_8579653619489175087gmail-m_-8993825770841542479gmail-m_-7047100689816192864gmail-m_2357984566551695743gmail-m_5039172728093010839m_5858939534540335777gmail-m_2253011044091612338m_4251631412743921844gmail_signature"><div dir="ltr">--John E Kemker III</div></div>
_______________________________________________<br>
chirp_users mailing list<br>
<a href="mailto:chirp_users@intrepid.danplanet.com" rel="noreferrer" target="_blank">chirp_users@intrepid.danplanet.com</a><br>
<a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users" rel="noreferrer noreferrer" target="_blank">http://intrepid.danplanet.com/mailman/listinfo/chirp_users</a><br>
This message was sent to TheX1le at <a href="mailto:thex1le@gmail.com" rel="noreferrer" target="_blank">thex1le@gmail.com</a><br>
To unsubscribe, send an email to <a href="mailto:chirp_users-unsubscribe@intrepid.danplanet.com" rel="noreferrer" target="_blank">chirp_users-unsubscribe@intrepid.danplanet.com</a></blockquote></div>
_______________________________________________<br>
chirp_users mailing list<br>
<a href="mailto:chirp_users@intrepid.danplanet.com" target="_blank">chirp_users@intrepid.danplanet.com</a><br>
<a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users" rel="noreferrer" target="_blank">http://intrepid.danplanet.com/mailman/listinfo/chirp_users</a><br>
This message was sent to W5NNH at <a href="mailto:kemkerj3@gmail.com" target="_blank">kemkerj3@gmail.com</a><br>
To unsubscribe, send an email to <a href="mailto:chirp_users-unsubscribe@intrepid.danplanet.com" target="_blank">chirp_users-unsubscribe@intrepid.danplanet.com</a></blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail-m_8579653619489175087gmail-m_-8993825770841542479gmail-m_-7047100689816192864gmail-m_2357984566551695743gmail-m_5039172728093010839m_5858939534540335777gmail_signature"><div dir="ltr">--John E Kemker III</div></div>
_______________________________________________<br>
chirp_users mailing list<br>
<a href="mailto:chirp_users@intrepid.danplanet.com" target="_blank">chirp_users@intrepid.danplanet.com</a><br>
<a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users" rel="noreferrer" target="_blank">http://intrepid.danplanet.com/mailman/listinfo/chirp_users</a><br>
This message was sent to Chance at <a href="mailto:chance.fulton@gmail.com" target="_blank">chance.fulton@gmail.com</a><br>
To unsubscribe, send an email to <a href="mailto:chirp_users-unsubscribe@intrepid.danplanet.com" target="_blank">chirp_users-unsubscribe@intrepid.danplanet.com</a></blockquote></div></div>-- <br><div dir="ltr" class="gmail-m_8579653619489175087gmail-m_-8993825770841542479gmail-m_-7047100689816192864gmail-m_2357984566551695743gmail-m_5039172728093010839gmail_signature">Chance Fulton<br><a href="mailto:chance.fulton@gmail.com" target="_blank">chance.fulton@gmail.com</a><br>810.441.5795</div>
_______________________________________________<br>
chirp_users mailing list<br>
<a href="mailto:chirp_users@intrepid.danplanet.com" target="_blank">chirp_users@intrepid.danplanet.com</a><br>
<a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users" rel="noreferrer" target="_blank">http://intrepid.danplanet.com/mailman/listinfo/chirp_users</a><br>
This message was sent to Dan Clemmensen at <a href="mailto:danclemmensen@gmail.com" target="_blank">danclemmensen@gmail.com</a><br>
To unsubscribe, send an email to <a href="mailto:chirp_users-unsubscribe@intrepid.danplanet.com" target="_blank">chirp_users-unsubscribe@intrepid.danplanet.com</a></blockquote></div>
_______________________________________________<br>
chirp_users mailing list<br>
<a href="mailto:chirp_users@intrepid.danplanet.com" target="_blank">chirp_users@intrepid.danplanet.com</a><br>
<a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users" rel="noreferrer" target="_blank">http://intrepid.danplanet.com/mailman/listinfo/chirp_users</a><br>
This message was sent to W5NNH at <a href="mailto:kemkerj3@gmail.com" target="_blank">kemkerj3@gmail.com</a><br>
To unsubscribe, send an email to <a href="mailto:chirp_users-unsubscribe@intrepid.danplanet.com" target="_blank">chirp_users-unsubscribe@intrepid.danplanet.com</a></blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail-m_8579653619489175087gmail-m_-8993825770841542479gmail-m_-7047100689816192864gmail_signature"><div dir="ltr">--John E Kemker III</div></div>
</div></blockquote><blockquote type="cite"><div dir="ltr"><span>_______________________________________________</span><br><span>chirp_users mailing list</span><br><span><a href="mailto:chirp_users@intrepid.danplanet.com" target="_blank">chirp_users@intrepid.danplanet.com</a></span><br><span><a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users" target="_blank">http://intrepid.danplanet.com/mailman/listinfo/chirp_users</a></span><br><span>This message was sent to Josef Zeevi at <a href="mailto:jz@zeevi.org" target="_blank">jz@zeevi.org</a></span><br><span>To unsubscribe, send an email to <a href="mailto:chirp_users-unsubscribe@intrepid.danplanet.com" target="_blank">chirp_users-unsubscribe@intrepid.danplanet.com</a></span></div></blockquote></div>_______________________________________________<br>
chirp_users mailing list<br>
<a href="mailto:chirp_users@intrepid.danplanet.com" target="_blank">chirp_users@intrepid.danplanet.com</a><br>
<a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users" rel="noreferrer" target="_blank">http://intrepid.danplanet.com/mailman/listinfo/chirp_users</a><br>
This message was sent to <a href="mailto:ghalejr@gmail.com" target="_blank">ghalejr@gmail.com</a> at <a href="mailto:ghalejr@gmail.com" target="_blank">ghalejr@gmail.com</a><br>
To unsubscribe, send an email to <a href="mailto:chirp_users-unsubscribe@intrepid.danplanet.com" target="_blank">chirp_users-unsubscribe@intrepid.danplanet.com</a></blockquote></div>
_______________________________________________<br>
chirp_users mailing list<br>
<a href="mailto:chirp_users@intrepid.danplanet.com" target="_blank">chirp_users@intrepid.danplanet.com</a><br>
<a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users" rel="noreferrer" target="_blank">http://intrepid.danplanet.com/mailman/listinfo/chirp_users</a><br>
This message was sent to W5NNH at <a href="mailto:kemkerj3@gmail.com" target="_blank">kemkerj3@gmail.com</a><br>
To unsubscribe, send an email to <a href="mailto:chirp_users-unsubscribe@intrepid.danplanet.com" target="_blank">chirp_users-unsubscribe@intrepid.danplanet.com</a></blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail-m_8579653619489175087gmail_signature"><div dir="ltr">--John E Kemker III</div></div>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr">--John E Kemker III</div></div>