Re: [chirp_users] Truth or Fiction
Never bricked any of mine. Could it be the operator rather than the radio?
On Tuesday, May 21, 2019 Dennis Wage chirp_users@intrepid.danplanet.com wrote: Chirp has bricked Yeasu radios? I know what I think. What's the real truth? Dennis M. Wage (W9BOQ)
245 Corum Hill Road Castalian Springs, TN 37031 (615) 310-4242 Cell (615) 562-5128 Home http://hammondb3organ.net http://overdubs.net _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Jock at kc6iih@aol.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
Most of the people I've heard this from have a vested interest in selling another brand of software.
On Wed, May 22, 2019 at 12:20 AM JOCK SOUTAR via chirp_users < chirp_users@intrepid.danplanet.com> wrote:
Never bricked any of mine. Could it be the operator rather than the radio?
On Tuesday, May 21, 2019 Dennis Wage chirp_users@intrepid.danplanet.com wrote: Chirp has bricked Yeasu radios?
I know what I think. What's the real truth?
Dennis M. Wage (W9BOQ)
245 Corum Hill Road Castalian Springs, TN 37031 (615) 310-4242 Cell (615) 562-5128 Home http://hammondb3organ.net http://overdubs.net _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Jock at kc6iih@aol.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to W5NNH at kemkerj3@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
Or perhaps a "cockpit error". Chirp is just a Python script so at the worst can only corrupt a radio's configuration. I'm a retired Embedded Systems and Software Engineer with 40 years of experience. Almost every electronic device I've encountered in that time had a reset mechanism to return the device to a default configuration. I addition to those with a vested interest, some may give up and refuse to use simple troubleshooting techniques to resolve such issues. A "factory rest" would probably have "unbricked" the radio, but they chose to blame Chirp rather than solving the actual problem.
Larry AC8YE
On Wed, May 22, 2019 at 7:09 AM John Kemker kemkerj3@gmail.com wrote:
Most of the people I've heard this from have a vested interest in selling another brand of software.
On Wed, May 22, 2019 at 12:20 AM JOCK SOUTAR via chirp_users < chirp_users@intrepid.danplanet.com> wrote:
Never bricked any of mine. Could it be the operator rather than the radio?
On Tuesday, May 21, 2019 Dennis Wage chirp_users@intrepid.danplanet.com wrote: Chirp has bricked Yeasu radios?
I know what I think. What's the real truth?
Dennis M. Wage (W9BOQ)
245 Corum Hill Road Castalian Springs, TN 37031 (615) 310-4242 Cell (615) 562-5128 Home http://hammondb3organ.net http://overdubs.net _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Jock at kc6iih@aol.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to W5NNH at kemkerj3@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
-- --John E Kemker III _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to larry.howell.47@gmail.com at larry.howell.47@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
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 pmcclosky@earthlink.net n7iy@arrl.net http://home.earthlink.net/~pmcclosky/
On May 22, 2019, at 4:07 AM, John Kemker kemkerj3@gmail.com wrote:
Yeasu
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 pmcclosky@earthlink.net 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 pmcclosky@earthlink.net n7iy@arrl.net http://home.earthlink.net/~pmcclosky/
On May 22, 2019, at 4:07 AM, John Kemker kemkerj3@gmail.com wrote:
Yeasu
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to W5NNH at kemkerj3@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
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 kemkerj3@gmail.com 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 pmcclosky@earthlink.net 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 pmcclosky@earthlink.net n7iy@arrl.net http://home.earthlink.net/~pmcclosky/
On May 22, 2019, at 4:07 AM, John Kemker kemkerj3@gmail.com wrote:
Yeasu
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to W5NNH at kemkerj3@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
-- --John E Kemker III _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to TheX1le at thex1le@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
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 thex1le@gmail.com 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 kemkerj3@gmail.com 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 < pmcclosky@earthlink.net> 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 pmcclosky@earthlink.net n7iy@arrl.net http://home.earthlink.net/~pmcclosky/
On May 22, 2019, at 4:07 AM, John Kemker kemkerj3@gmail.com wrote:
Yeasu
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to W5NNH at kemkerj3@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
-- --John E Kemker III _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to TheX1le at thex1le@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to W5NNH at kemkerj3@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
In the SW world, there are only three knobs to turn: fast, good, and cheap. However, increasing fast decreases good. Increasing cheap decreases good. But, fast and cheap can be increased at the expense of good. The rest is left as an exercise to the student. 😊
From: chirp_users-bounces@intrepid.danplanet.com chirp_users-bounces@intrepid.danplanet.com On Behalf Of John Kemker Sent: Friday, May 24, 2019 3:10 PM To: Discussion of CHIRP chirp_users@intrepid.danplanet.com Subject: Re: [chirp_users] Truth or Fiction
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 <thex1le@gmail.com mailto:thex1le@gmail.com > 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 <kemkerj3@gmail.com mailto:kemkerj3@gmail.com > 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 <pmcclosky@earthlink.net mailto:pmcclosky@earthlink.net > 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 pmcclosky@earthlink.net mailto:pmcclosky@earthlink.net n7iy@arrl.net mailto:n7iy@arrl.net http://home.earthlink.net/~pmcclosky/
On May 22, 2019, at 4:07 AM, John Kemker <kemkerj3@gmail.com mailto:kemkerj3@gmail.com > wrote:
Yeasu
_______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com mailto:chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to W5NNH at kemkerj3@gmail.com mailto:kemkerj3@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com mailto:chirp_users-unsubscribe@intrepid.danplanet.com
I've always heard that stated as "Fast, reliable, and Cheap. Pick two."
Tom Henderson
On 5/24/19 3:16 PM, jz@zeevi.org wrote:
In the SW world, there are only three knobs to turn: fast, good, and cheap. However, increasing fast decreases good. Increasing cheap decreases good. But, fast and cheap can be increased at the expense of good. The rest is left as an exercise to the student. 😊
*From:* chirp_users-bounces@intrepid.danplanet.com chirp_users-bounces@intrepid.danplanet.com *On Behalf Of *John Kemker *Sent:* Friday, May 24, 2019 3:10 PM *To:* Discussion of CHIRP chirp_users@intrepid.danplanet.com *Subject:* Re: [chirp_users] Truth or Fiction
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 <thex1le@gmail.com mailto:thex1le@gmail.com> 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 <kemkerj3@gmail.com <mailto:kemkerj3@gmail.com>> 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 <pmcclosky@earthlink.net <mailto:pmcclosky@earthlink.net>> 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 pmcclosky@earthlink.net <mailto:pmcclosky@earthlink.net> n7iy@arrl.net <mailto:n7iy@arrl.net> http://home.earthlink.net/~pmcclosky/ On May 22, 2019, at 4:07 AM, John Kemker <kemkerj3@gmail.com <mailto:kemkerj3@gmail.com>> wrote: Yeasu _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com <mailto:chirp_users@intrepid.danplanet.com> http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to W5NNH at kemkerj3@gmail.com <mailto:kemkerj3@gmail.com> To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com <mailto:chirp_users-unsubscribe@intrepid.danplanet.com> -- --John E Kemker III _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com <mailto:chirp_users@intrepid.danplanet.com> http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to TheX1le at thex1le@gmail.com <mailto:thex1le@gmail.com> To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com <mailto:chirp_users-unsubscribe@intrepid.danplanet.com> _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com <mailto:chirp_users@intrepid.danplanet.com> http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to W5NNH at kemkerj3@gmail.com <mailto:kemkerj3@gmail.com> To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com <mailto:chirp_users-unsubscribe@intrepid.danplanet.com>--
--John E Kemker III
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Tom KM4UQB at tom@henderson4.us To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
There's at least 4 ways to say that. I'd guess more...😀
Josef Sent from a phone with a tiny screen
On May 24, 2019, at 5:22 PM, Tom Henderson Tom@henderson4.us wrote:
I've always heard that stated as "Fast, reliable, and Cheap. Pick two."
Tom Henderson
On 5/24/19 3:16 PM, jz@zeevi.org wrote: In the SW world, there are only three knobs to turn: fast, good, and cheap. However, increasing fast decreases good. Increasing cheap decreases good. But, fast and cheap can be increased at the expense of good. The rest is left as an exercise to the student. 😊
From: chirp_users-bounces@intrepid.danplanet.com chirp_users-bounces@intrepid.danplanet.com On Behalf Of John Kemker Sent: Friday, May 24, 2019 3:10 PM To: Discussion of CHIRP chirp_users@intrepid.danplanet.com Subject: Re: [chirp_users] Truth or Fiction
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 thex1le@gmail.com 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 kemkerj3@gmail.com 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 pmcclosky@earthlink.net 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 pmcclosky@earthlink.net n7iy@arrl.net http://home.earthlink.net/~pmcclosky/
On May 22, 2019, at 4:07 AM, John Kemker kemkerj3@gmail.com wrote:
Yeasu
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to W5NNH at kemkerj3@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
-- --John E Kemker III _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to TheX1le at thex1le@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to W5NNH at kemkerj3@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
-- --John E Kemker III
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Tom KM4UQB at tom@henderson4.us To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Josef Zeevi at jz@zeevi.org To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
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 kemkerj3@gmail.com 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 thex1le@gmail.com 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 kemkerj3@gmail.com 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 < pmcclosky@earthlink.net> 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 pmcclosky@earthlink.net n7iy@arrl.net http://home.earthlink.net/~pmcclosky/
On May 22, 2019, at 4:07 AM, John Kemker kemkerj3@gmail.com wrote:
Yeasu
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to W5NNH at kemkerj3@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
-- --John E Kemker III _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to TheX1le at thex1le@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to W5NNH at kemkerj3@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
-- --John E Kemker III _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Chance at chance.fulton@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
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 chance.fulton@gmail.com 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 kemkerj3@gmail.com 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 thex1le@gmail.com 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 kemkerj3@gmail.com 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 < pmcclosky@earthlink.net> 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 pmcclosky@earthlink.net n7iy@arrl.net http://home.earthlink.net/~pmcclosky/
On May 22, 2019, at 4:07 AM, John Kemker kemkerj3@gmail.com wrote:
Yeasu
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to W5NNH at kemkerj3@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
-- --John E Kemker III _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to TheX1le at thex1le@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to W5NNH at kemkerj3@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
-- --John E Kemker III _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Chance at chance.fulton@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
-- Chance Fulton chance.fulton@gmail.com 810.441.5795 _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Dan Clemmensen at danclemmensen@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
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.
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.
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.
On Fri, May 24, 2019 at 5:19 PM Dan Clemmensen danclemmensen@gmail.com wrote:
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 chance.fulton@gmail.com 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 kemkerj3@gmail.com 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 thex1le@gmail.com 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 kemkerj3@gmail.com 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 < pmcclosky@earthlink.net> 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 pmcclosky@earthlink.net n7iy@arrl.net http://home.earthlink.net/~pmcclosky/
On May 22, 2019, at 4:07 AM, John Kemker kemkerj3@gmail.com wrote:
Yeasu
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to W5NNH at kemkerj3@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
-- --John E Kemker III _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to TheX1le at thex1le@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to W5NNH at kemkerj3@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
-- --John E Kemker III _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Chance at chance.fulton@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
-- Chance Fulton chance.fulton@gmail.com 810.441.5795 _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Dan Clemmensen at danclemmensen@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to W5NNH at kemkerj3@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
"Shouldn't" but apparently might.
Josef Sent from a phone with a tiny screen
On May 24, 2019, at 5:27 PM, John Kemker kemkerj3@gmail.com wrote:
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.
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.
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.
On Fri, May 24, 2019 at 5:19 PM Dan Clemmensen danclemmensen@gmail.com wrote: 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 chance.fulton@gmail.com 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 kemkerj3@gmail.com 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 thex1le@gmail.com 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 kemkerj3@gmail.com 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 pmcclosky@earthlink.net 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 > pmcclosky@earthlink.net > n7iy@arrl.net > http://home.earthlink.net/~pmcclosky/ > >> On May 22, 2019, at 4:07 AM, John Kemker kemkerj3@gmail.com wrote: >> >> Yeasu > > _______________________________________________ > chirp_users mailing list > chirp_users@intrepid.danplanet.com > http://intrepid.danplanet.com/mailman/listinfo/chirp_users > This message was sent to W5NNH at kemkerj3@gmail.com > To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
-- --John E Kemker III _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to TheX1le at thex1le@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to W5NNH at kemkerj3@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
-- --John E Kemker III _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Chance at chance.fulton@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
-- Chance Fulton chance.fulton@gmail.com 810.441.5795 _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Dan Clemmensen at danclemmensen@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to W5NNH at kemkerj3@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
-- --John E Kemker III _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Josef Zeevi at jz@zeevi.org To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
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.
If the big names do not want to open up to us, I say do not buy them.
George
On Fri, May 24, 2019 at 4:36 PM Josef Zeevi jz@zeevi.org wrote:
"Shouldn't" but apparently might.
Josef Sent from a phone with a tiny screen
On May 24, 2019, at 5:27 PM, John Kemker kemkerj3@gmail.com wrote:
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.
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.
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.
On Fri, May 24, 2019 at 5:19 PM Dan Clemmensen danclemmensen@gmail.com wrote:
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 chance.fulton@gmail.com 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 kemkerj3@gmail.com 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 thex1le@gmail.com 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 kemkerj3@gmail.com 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 < pmcclosky@earthlink.net> 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 > pmcclosky@earthlink.net > n7iy@arrl.net > http://home.earthlink.net/~pmcclosky/ > > On May 22, 2019, at 4:07 AM, John Kemker kemkerj3@gmail.com wrote: > > Yeasu > > > _______________________________________________ > chirp_users mailing list > chirp_users@intrepid.danplanet.com > http://intrepid.danplanet.com/mailman/listinfo/chirp_users > This message was sent to W5NNH at kemkerj3@gmail.com > To unsubscribe, send an email to > chirp_users-unsubscribe@intrepid.danplanet.com
-- --John E Kemker III _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to TheX1le at thex1le@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to W5NNH at kemkerj3@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
-- --John E Kemker III _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Chance at chance.fulton@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
-- Chance Fulton chance.fulton@gmail.com 810.441.5795 _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Dan Clemmensen at danclemmensen@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to W5NNH at kemkerj3@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
-- --John E Kemker III
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Josef Zeevi at jz@zeevi.org To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to ghalejr@gmail.com at ghalejr@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
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.
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.
73 de W5NNH
On Fri, May 24, 2019 at 7:18 PM George Hale Jr. ghalejr@gmail.com wrote:
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.
If the big names do not want to open up to us, I say do not buy them.
George
On Fri, May 24, 2019 at 4:36 PM Josef Zeevi jz@zeevi.org wrote:
"Shouldn't" but apparently might.
Josef Sent from a phone with a tiny screen
On May 24, 2019, at 5:27 PM, John Kemker kemkerj3@gmail.com wrote:
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.
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.
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.
On Fri, May 24, 2019 at 5:19 PM Dan Clemmensen danclemmensen@gmail.com wrote:
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 chance.fulton@gmail.com 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 kemkerj3@gmail.com 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 thex1le@gmail.com 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 kemkerj3@gmail.com 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 < > pmcclosky@earthlink.net> 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 >> pmcclosky@earthlink.net >> n7iy@arrl.net >> http://home.earthlink.net/~pmcclosky/ >> >> On May 22, 2019, at 4:07 AM, John Kemker kemkerj3@gmail.com >> wrote: >> >> Yeasu >> >> >> _______________________________________________ >> chirp_users mailing list >> chirp_users@intrepid.danplanet.com >> http://intrepid.danplanet.com/mailman/listinfo/chirp_users >> This message was sent to W5NNH at kemkerj3@gmail.com >> To unsubscribe, send an email to >> chirp_users-unsubscribe@intrepid.danplanet.com > > > > -- > --John E Kemker III > _______________________________________________ > chirp_users mailing list > chirp_users@intrepid.danplanet.com > http://intrepid.danplanet.com/mailman/listinfo/chirp_users > This message was sent to TheX1le at thex1le@gmail.com > To unsubscribe, send an email to > chirp_users-unsubscribe@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to W5NNH at kemkerj3@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
-- --John E Kemker III _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Chance at chance.fulton@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
-- Chance Fulton chance.fulton@gmail.com 810.441.5795 _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Dan Clemmensen at danclemmensen@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to W5NNH at kemkerj3@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
-- --John E Kemker III
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Josef Zeevi at jz@zeevi.org To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to ghalejr@gmail.com at ghalejr@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to W5NNH at kemkerj3@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
Benton,
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.
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.
On Fri, May 24, 2019 at 7:30 PM John Kemker kemkerj3@gmail.com wrote:
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.
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.
73 de W5NNH
On Fri, May 24, 2019 at 7:18 PM George Hale Jr. ghalejr@gmail.com wrote:
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.
If the big names do not want to open up to us, I say do not buy them.
George
On Fri, May 24, 2019 at 4:36 PM Josef Zeevi jz@zeevi.org wrote:
"Shouldn't" but apparently might.
Josef Sent from a phone with a tiny screen
On May 24, 2019, at 5:27 PM, John Kemker kemkerj3@gmail.com wrote:
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.
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.
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.
On Fri, May 24, 2019 at 5:19 PM Dan Clemmensen danclemmensen@gmail.com wrote:
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 chance.fulton@gmail.com 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 kemkerj3@gmail.com 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 thex1le@gmail.com 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 kemkerj3@gmail.com 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 < >> pmcclosky@earthlink.net> 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 >>> pmcclosky@earthlink.net >>> n7iy@arrl.net >>> http://home.earthlink.net/~pmcclosky/ >>> >>> On May 22, 2019, at 4:07 AM, John Kemker kemkerj3@gmail.com >>> wrote: >>> >>> Yeasu >>> >>> >>> _______________________________________________ >>> chirp_users mailing list >>> chirp_users@intrepid.danplanet.com >>> http://intrepid.danplanet.com/mailman/listinfo/chirp_users >>> This message was sent to W5NNH at kemkerj3@gmail.com >>> To unsubscribe, send an email to >>> chirp_users-unsubscribe@intrepid.danplanet.com >> >> >> >> -- >> --John E Kemker III >> _______________________________________________ >> chirp_users mailing list >> chirp_users@intrepid.danplanet.com >> http://intrepid.danplanet.com/mailman/listinfo/chirp_users >> This message was sent to TheX1le at thex1le@gmail.com >> To unsubscribe, send an email to >> chirp_users-unsubscribe@intrepid.danplanet.com > > _______________________________________________ > chirp_users mailing list > chirp_users@intrepid.danplanet.com > http://intrepid.danplanet.com/mailman/listinfo/chirp_users > This message was sent to W5NNH at kemkerj3@gmail.com > To unsubscribe, send an email to > chirp_users-unsubscribe@intrepid.danplanet.com
-- --John E Kemker III _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Chance at chance.fulton@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
-- Chance Fulton chance.fulton@gmail.com 810.441.5795 _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Dan Clemmensen at danclemmensen@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to W5NNH at kemkerj3@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
-- --John E Kemker III
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Josef Zeevi at jz@zeevi.org To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to ghalejr@gmail.com at ghalejr@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to W5NNH at kemkerj3@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
-- --John E Kemker III
El 24/5/19 a las 19:16, George Hale Jr. escribió:
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.
Motorola... a proprietary protocol to talk to the radios and "Cease and Desist" letter to anyone to attempt to try that way...
John, you say that the firmware should not accept an invalid write, and you are absolutely correct: it "should" not. However, it does. Really, at least for many radios. Therefore, if the computer software sends the wrong write command, the radio just accepts it and happily writes to a dangerous spot. I am a relative newcomer to Ham radios and to CHIRP, but I know from reading here and from my own work on the ft4.py driver that many radios show this behaviour. For the ft4 and its siblings, the computer software can check the radio type. If this check matches, the software can then write into areas that the computer software developer has determined by experiment are the "correct" areas. The command to write into an area is simply a 16-bit number we empirically call an "address" followed by data that the radio writes at that location. If the computer software commands a write of the wrong data into the wrong location, the this radio (apparently) simply writes that data in that location. The is no other protocol. The only commands are "read data from location" and "write data to location". This is the behaviour I would expect from a program written in assembly language in 1975 to run in one kilobyte of memory, not the behaviour I expect of a 21st century product, but this is the observed behaviour.
On Fri, May 24, 2019 at 3:28 PM John Kemker kemkerj3@gmail.com wrote:
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.
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.
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.
On Fri, May 24, 2019 at 5:19 PM Dan Clemmensen danclemmensen@gmail.com wrote:
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 chance.fulton@gmail.com 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 kemkerj3@gmail.com 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 thex1le@gmail.com 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 kemkerj3@gmail.com 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 < pmcclosky@earthlink.net> 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 > pmcclosky@earthlink.net > n7iy@arrl.net > http://home.earthlink.net/~pmcclosky/ > > On May 22, 2019, at 4:07 AM, John Kemker kemkerj3@gmail.com wrote: > > Yeasu > > > _______________________________________________ > chirp_users mailing list > chirp_users@intrepid.danplanet.com > http://intrepid.danplanet.com/mailman/listinfo/chirp_users > This message was sent to W5NNH at kemkerj3@gmail.com > To unsubscribe, send an email to > chirp_users-unsubscribe@intrepid.danplanet.com
-- --John E Kemker III _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to TheX1le at thex1le@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to W5NNH at kemkerj3@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
-- --John E Kemker III _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Chance at chance.fulton@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
-- Chance Fulton chance.fulton@gmail.com 810.441.5795 _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Dan Clemmensen at danclemmensen@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to W5NNH at kemkerj3@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
-- --John E Kemker III _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Dan Clemmensen at danclemmensen@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
El 24/5/19 a las 18:27, John Kemker escribió:
I find it hard to believe that they don't have as good a software standard as less-expensive brands.
I was not eager to take a side here, but...
I'm developing a driver (CHIRP) for an old Yaesu/Vertex Radio family right now (FTL 1011/2011/7011) and there a BUG in the firmware, they DON'T Validate the radio info once I pass to the program space...
I can program a 2011 like if a 7011 and vice versa... there is an old hack to convert any of them from 4 to 8 to 12 channels on SOFTWARE, etc..
"less-expensive brands?"
I developed the driver for Commercial Grade Kenwood TK-x60/x70 & TK-x60G/x70G families (for CHIRP) and there is a lack of validation out there in the same aspect...
In fact for YEARS fleet/ham operators knows that ANY of the in that familly can be programed like a x78 and you will get features that ONLY that radio has... yes I can program a TK-760G and get all the features of a TK-768G (A key for low power, true reverse, etc...) and the radios are happy with that...
[The OEM software HIDE the key features for particular radios but the functions are there, I have given ACCESS to that functions in CHIRP, once you know that all of them uses the same firmware, literally: the same firmware...]
The TK-790 is another monster [never completed the driver for it...], better programmed, locks on the important things, a separate mode for firmware, but has a quirk or two also...
As many of the previous OM said: Fast, Reliable, Cheap; pick just two of them.
Cheers, Pavel CO7WT.
On 2019-05-24 12:22, John Kemker 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 bought the RTS sw/cable from HRO because I needed the cable to program my FT-60. The SW did me no good because it's for Windows and I'm a linux guy.
Chirp worked fine with my HT and several others that I programmed for friends until it came to one of Yaesu's water-resistant models. Don't remember which one specifically, but we needed to unscrew a cap to get to the port. Found the cable wouldn't fit into the port mechanically -- the plastic overmolding was just too wide to fit down into the hole. So there I was -- bought SW I couldn't use to get a cable that I couldn't use. (On that radio.) I'd have been really torqued if I'd bought it specifically for that model.
If RTS is the 'officially supported' SW because it doesn't 'brick,' does that imply that Yaesu has shared with RTS which areas are safe to touch and which aren't? And wouldn't it be doing their customers a good deed to share that info with the Chirp community, too?
Benton 24may19 -- NX7O benton@siletzbay.com
I helped write the Yaesu VX-3R driver https://chirp.danplanet.com/projects/chirp/repository/entry/chirp/drivers/vx...
About a year after that, (and using the radio a good bit) the radio appeared to lose power while I was writing to it. The battery was tested and charged, still no love. I sent it to Yaesu and the replaced some minor part (*not* the flash) but sadly I don't have the documentation on what anymore. After they sent it back to me I didn't use it as much (I had more radios by this point). About a year ago I started using it more heavily and 6 months ago the same thing happened (with the writing and the dying).
In no way do I "blame chirp". In fact, I'd more likely blame a problem with the cheap cable possibly having voltage spikes and the radio not being designed to handle a small voltage spike over the serial and shorting something out. That said, twice my vx-3r has died while writing to it from chirp.
Thanks, Rick
PS> I don't sell anything, I don't work on radios for a living, and I love chirp. I don't believe there is any possible way someone could suggest I'm biased aside from unlucky personal experience.
On Wed, May 22, 2019 at 12:22 AM JOCK SOUTAR via chirp_users chirp_users@intrepid.danplanet.com wrote:
Never bricked any of mine. Could it be the operator rather than the radio?
On Tuesday, May 21, 2019 Dennis Wage chirp_users@intrepid.danplanet.com wrote: Chirp has bricked Yeasu radios?
I know what I think. What's the real truth?
Dennis M. Wage (W9BOQ)
245 Corum Hill Road Castalian Springs, TN 37031 (615) 310-4242 Cell (615) 562-5128 Home http://hammondb3organ.net http://overdubs.net _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Jock at kc6iih@aol.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com_______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Rick Farina at sidhayn@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
Since your CHIRP driver almost certainly send exactly the same that the Yaesu software would send, It's likely that you woold have seen the same reslult if you had been using the Yaesu software. This is speculation on my part. A spike on a USB-to-serial cable is not very likely unless you somehow had a ground loop?
On Fri, May 24, 2019 at 7:39 PM Sid Hayn sidhayn@gmail.com wrote:
I helped write the Yaesu VX-3R driver
https://chirp.danplanet.com/projects/chirp/repository/entry/chirp/drivers/vx...
About a year after that, (and using the radio a good bit) the radio appeared to lose power while I was writing to it. The battery was tested and charged, still no love. I sent it to Yaesu and the replaced some minor part (*not* the flash) but sadly I don't have the documentation on what anymore. After they sent it back to me I didn't use it as much (I had more radios by this point). About a year ago I started using it more heavily and 6 months ago the same thing happened (with the writing and the dying).
In no way do I "blame chirp". In fact, I'd more likely blame a problem with the cheap cable possibly having voltage spikes and the radio not being designed to handle a small voltage spike over the serial and shorting something out. That said, twice my vx-3r has died while writing to it from chirp.
Thanks, Rick
PS> I don't sell anything, I don't work on radios for a living, and I love chirp. I don't believe there is any possible way someone could suggest I'm biased aside from unlucky personal experience.
On Wed, May 22, 2019 at 12:22 AM JOCK SOUTAR via chirp_users chirp_users@intrepid.danplanet.com wrote:
Never bricked any of mine. Could it be the operator rather than the radio?
On Tuesday, May 21, 2019 Dennis Wage chirp_users@intrepid.danplanet.com
wrote:
Chirp has bricked Yeasu radios?
I know what I think. What's the real truth?
Dennis M. Wage (W9BOQ)
245 Corum Hill Road Castalian Springs, TN 37031 (615) 310-4242 Cell (615) 562-5128 Home http://hammondb3organ.net http://overdubs.net _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Jock at kc6iih@aol.com To unsubscribe, send an email to
chirp_users-unsubscribe@intrepid.danplanet.com_______________________________________________
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Rick Farina at sidhayn@gmail.com To unsubscribe, send an email to
chirp_users-unsubscribe@intrepid.danplanet.com _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Dan Clemmensen at danclemmensen@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
I would wager that my driver sends the same everything as well. Honestly never checked, never bought the RT systems software.
The cable voltage issue is a wild guess, which at least made more sense to me than anything else.
On Fri, May 24, 2019, 22:54 Dan Clemmensen danclemmensen@gmail.com wrote:
Since your CHIRP driver almost certainly send exactly the same that the Yaesu software would send, It's likely that you woold have seen the same reslult if you had been using the Yaesu software. This is speculation on my part. A spike on a USB-to-serial cable is not very likely unless you somehow had a ground loop?
On Fri, May 24, 2019 at 7:39 PM Sid Hayn sidhayn@gmail.com wrote:
I helped write the Yaesu VX-3R driver
https://chirp.danplanet.com/projects/chirp/repository/entry/chirp/drivers/vx...
About a year after that, (and using the radio a good bit) the radio appeared to lose power while I was writing to it. The battery was tested and charged, still no love. I sent it to Yaesu and the replaced some minor part (*not* the flash) but sadly I don't have the documentation on what anymore. After they sent it back to me I didn't use it as much (I had more radios by this point). About a year ago I started using it more heavily and 6 months ago the same thing happened (with the writing and the dying).
In no way do I "blame chirp". In fact, I'd more likely blame a problem with the cheap cable possibly having voltage spikes and the radio not being designed to handle a small voltage spike over the serial and shorting something out. That said, twice my vx-3r has died while writing to it from chirp.
Thanks, Rick
PS> I don't sell anything, I don't work on radios for a living, and I love chirp. I don't believe there is any possible way someone could suggest I'm biased aside from unlucky personal experience.
On Wed, May 22, 2019 at 12:22 AM JOCK SOUTAR via chirp_users chirp_users@intrepid.danplanet.com wrote:
Never bricked any of mine. Could it be the operator rather than the radio?
On Tuesday, May 21, 2019 Dennis Wage <
chirp_users@intrepid.danplanet.com> wrote:
Chirp has bricked Yeasu radios?
I know what I think. What's the real truth?
Dennis M. Wage (W9BOQ)
245 Corum Hill Road Castalian Springs, TN 37031 (615) 310-4242 Cell (615) 562-5128 Home http://hammondb3organ.net http://overdubs.net _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Jock at kc6iih@aol.com To unsubscribe, send an email to
chirp_users-unsubscribe@intrepid.danplanet.com_______________________________________________
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Rick Farina at sidhayn@gmail.com To unsubscribe, send an email to
chirp_users-unsubscribe@intrepid.danplanet.com _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Dan Clemmensen at danclemmensen@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Rick Farina at sidhayn@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
All of the above just goes to confirm why I will NOT buy Yaesu. They sold boat load of C4FM repeaters most of which are doing analog because they are not connected to the net. Yes you can use a MMDVM and build your own, but go buy a non-yeasu radio that supports their closed protocol.
I purchased a D-Star handheld from HRO in Portland back in 2008, it was years before I got to use it on D-Star and it is an open protocol but no manufacturer wanted to support it. Even now only Kenwood is producing radios that do D-Star.
I have had to deal with RT-Systems and I did not care for their "our way or the highway " attitude.
In amateur radio we are SUPPOSED to open things up change them use other bits and pieces on them, those who demand a walled garden should not get our money. Yaesu is outstanding in that way. Indeed I have always associated them with box operators, not nitty gritty hams who want to dig into the technical side of things.
On Fri, May 24, 2019 at 10:03 PM Sid Hayn sidhayn@gmail.com wrote:
I would wager that my driver sends the same everything as well. Honestly never checked, never bought the RT systems software.
The cable voltage issue is a wild guess, which at least made more sense to me than anything else.
On Fri, May 24, 2019, 22:54 Dan Clemmensen danclemmensen@gmail.com wrote:
Since your CHIRP driver almost certainly send exactly the same that the Yaesu software would send, It's likely that you woold have seen the same reslult if you had been using the Yaesu software. This is speculation on my part. A spike on a USB-to-serial cable is not very likely unless you somehow had a ground loop?
On Fri, May 24, 2019 at 7:39 PM Sid Hayn sidhayn@gmail.com wrote:
I helped write the Yaesu VX-3R driver
https://chirp.danplanet.com/projects/chirp/repository/entry/chirp/drivers/vx...
About a year after that, (and using the radio a good bit) the radio appeared to lose power while I was writing to it. The battery was tested and charged, still no love. I sent it to Yaesu and the replaced some minor part (*not* the flash) but sadly I don't have the documentation on what anymore. After they sent it back to me I didn't use it as much (I had more radios by this point). About a year ago I started using it more heavily and 6 months ago the same thing happened (with the writing and the dying).
In no way do I "blame chirp". In fact, I'd more likely blame a problem with the cheap cable possibly having voltage spikes and the radio not being designed to handle a small voltage spike over the serial and shorting something out. That said, twice my vx-3r has died while writing to it from chirp.
Thanks, Rick
PS> I don't sell anything, I don't work on radios for a living, and I love chirp. I don't believe there is any possible way someone could suggest I'm biased aside from unlucky personal experience.
On Wed, May 22, 2019 at 12:22 AM JOCK SOUTAR via chirp_users chirp_users@intrepid.danplanet.com wrote:
Never bricked any of mine. Could it be the operator rather than the radio?
On Tuesday, May 21, 2019 Dennis Wage <
chirp_users@intrepid.danplanet.com> wrote:
Chirp has bricked Yeasu radios?
I know what I think. What's the real truth?
Dennis M. Wage (W9BOQ)
245 Corum Hill Road Castalian Springs, TN 37031 (615) 310-4242 Cell (615) 562-5128 Home http://hammondb3organ.net http://overdubs.net _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Jock at kc6iih@aol.com To unsubscribe, send an email to
chirp_users-unsubscribe@intrepid.danplanet.com_______________________________________________
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Rick Farina at sidhayn@gmail.com To unsubscribe, send an email to
chirp_users-unsubscribe@intrepid.danplanet.com _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Dan Clemmensen at danclemmensen@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Rick Farina at sidhayn@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Chuck Hast at kp4djt@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
Check out Icom's line of digital radios. They're supporting D-Star.
Only reason I bought the Yaesu is it was on sale and I figured I'd try it out. It's not a bad radio, just don't like the closed architecture.
On Sat, May 25, 2019 at 8:42 AM Chuck Hast kp4djt@gmail.com wrote:
All of the above just goes to confirm why I will NOT buy Yaesu. They sold boat load of C4FM repeaters most of which are doing analog because they are not connected to the net. Yes you can use a MMDVM and build your own, but go buy a non-yeasu radio that supports their closed protocol.
I purchased a D-Star handheld from HRO in Portland back in 2008, it was years before I got to use it on D-Star and it is an open protocol but no manufacturer wanted to support it. Even now only Kenwood is producing radios that do D-Star.
I have had to deal with RT-Systems and I did not care for their "our way or the highway " attitude.
In amateur radio we are SUPPOSED to open things up change them use other bits and pieces on them, those who demand a walled garden should not get our money. Yaesu is outstanding in that way. Indeed I have always associated them with box operators, not nitty gritty hams who want to dig into the technical side of things.
On Fri, May 24, 2019 at 10:03 PM Sid Hayn sidhayn@gmail.com wrote:
I would wager that my driver sends the same everything as well. Honestly never checked, never bought the RT systems software.
The cable voltage issue is a wild guess, which at least made more sense to me than anything else.
On Fri, May 24, 2019, 22:54 Dan Clemmensen danclemmensen@gmail.com wrote:
Since your CHIRP driver almost certainly send exactly the same that the Yaesu software would send, It's likely that you woold have seen the same reslult if you had been using the Yaesu software. This is speculation on my part. A spike on a USB-to-serial cable is not very likely unless you somehow had a ground loop?
On Fri, May 24, 2019 at 7:39 PM Sid Hayn sidhayn@gmail.com wrote:
I helped write the Yaesu VX-3R driver
https://chirp.danplanet.com/projects/chirp/repository/entry/chirp/drivers/vx...
About a year after that, (and using the radio a good bit) the radio appeared to lose power while I was writing to it. The battery was tested and charged, still no love. I sent it to Yaesu and the replaced some minor part (*not* the flash) but sadly I don't have the documentation on what anymore. After they sent it back to me I didn't use it as much (I had more radios by this point). About a year ago I started using it more heavily and 6 months ago the same thing happened (with the writing and the dying).
In no way do I "blame chirp". In fact, I'd more likely blame a problem with the cheap cable possibly having voltage spikes and the radio not being designed to handle a small voltage spike over the serial and shorting something out. That said, twice my vx-3r has died while writing to it from chirp.
Thanks, Rick
PS> I don't sell anything, I don't work on radios for a living, and I love chirp. I don't believe there is any possible way someone could suggest I'm biased aside from unlucky personal experience.
On Wed, May 22, 2019 at 12:22 AM JOCK SOUTAR via chirp_users chirp_users@intrepid.danplanet.com wrote:
Never bricked any of mine. Could it be the operator rather than the radio?
On Tuesday, May 21, 2019 Dennis Wage <
chirp_users@intrepid.danplanet.com> wrote:
Chirp has bricked Yeasu radios?
I know what I think. What's the real truth?
Dennis M. Wage (W9BOQ)
245 Corum Hill Road Castalian Springs, TN 37031 (615) 310-4242 Cell (615) 562-5128 Home http://hammondb3organ.net http://overdubs.net _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Jock at kc6iih@aol.com To unsubscribe, send an email to
chirp_users-unsubscribe@intrepid.danplanet.com_______________________________________________
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Rick Farina at sidhayn@gmail.com To unsubscribe, send an email to
chirp_users-unsubscribe@intrepid.danplanet.com _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Dan Clemmensen at danclemmensen@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Rick Farina at sidhayn@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Chuck Hast at kp4djt@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
-- Chirp + Editcp + MD380Tools on Linux Celestial!!! Chuck -- KP4DJT _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to W5NNH at kemkerj3@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
Yes, I should have said Icom D-Star.... I have an ID -5100 in the vehicle too, but not much D-Star here in central OK. Building a MMDVM repeater based on a Mastr III, makes a great digital box. Since it has the data ports on it for EDACS use. First I will turn on DMR then D-Star.
On Sat, May 25, 2019 at 1:29 PM John Kemker kemkerj3@gmail.com wrote:
Check out Icom's line of digital radios. They're supporting D-Star.
Only reason I bought the Yaesu is it was on sale and I figured I'd try it out. It's not a bad radio, just don't like the closed architecture.
On Sat, May 25, 2019 at 8:42 AM Chuck Hast kp4djt@gmail.com wrote:
All of the above just goes to confirm why I will NOT buy Yaesu. They sold boat load of C4FM repeaters most of which are doing analog because they are not connected to the net. Yes you can use a MMDVM and build your own, but go buy a non-yeasu radio that supports their closed protocol.
I purchased a D-Star handheld from HRO in Portland back in 2008, it was years before I got to use it on D-Star and it is an open protocol but no manufacturer wanted to support it. Even now only Kenwood is producing radios that do D-Star.
I have had to deal with RT-Systems and I did not care for their "our way or the highway " attitude.
In amateur radio we are SUPPOSED to open things up change them use other bits and pieces on them, those who demand a walled garden should not get our money. Yaesu is outstanding in that way. Indeed I have always associated them with box operators, not nitty gritty hams who want to dig into the technical side of things.
On Fri, May 24, 2019 at 10:03 PM Sid Hayn sidhayn@gmail.com wrote:
I would wager that my driver sends the same everything as well. Honestly never checked, never bought the RT systems software.
The cable voltage issue is a wild guess, which at least made more sense to me than anything else.
On Fri, May 24, 2019, 22:54 Dan Clemmensen danclemmensen@gmail.com wrote:
Since your CHIRP driver almost certainly send exactly the same that the Yaesu software would send, It's likely that you woold have seen the same reslult if you had been using the Yaesu software. This is speculation on my part. A spike on a USB-to-serial cable is not very likely unless you somehow had a ground loop?
On Fri, May 24, 2019 at 7:39 PM Sid Hayn sidhayn@gmail.com wrote:
I helped write the Yaesu VX-3R driver
https://chirp.danplanet.com/projects/chirp/repository/entry/chirp/drivers/vx...
About a year after that, (and using the radio a good bit) the radio appeared to lose power while I was writing to it. The battery was tested and charged, still no love. I sent it to Yaesu and the replaced some minor part (*not* the flash) but sadly I don't have the documentation on what anymore. After they sent it back to me I didn't use it as much (I had more radios by this point). About a year ago I started using it more heavily and 6 months ago the same thing happened (with the writing and the dying).
In no way do I "blame chirp". In fact, I'd more likely blame a problem with the cheap cable possibly having voltage spikes and the radio not being designed to handle a small voltage spike over the serial and shorting something out. That said, twice my vx-3r has died while writing to it from chirp.
Thanks, Rick
PS> I don't sell anything, I don't work on radios for a living, and I love chirp. I don't believe there is any possible way someone could suggest I'm biased aside from unlucky personal experience.
On Wed, May 22, 2019 at 12:22 AM JOCK SOUTAR via chirp_users chirp_users@intrepid.danplanet.com wrote:
Never bricked any of mine. Could it be the operator rather than the radio?
On Tuesday, May 21, 2019 Dennis Wage <
chirp_users@intrepid.danplanet.com> wrote:
Chirp has bricked Yeasu radios?
I know what I think. What's the real truth?
Dennis M. Wage (W9BOQ)
245 Corum Hill Road Castalian Springs, TN 37031 (615) 310-4242 Cell (615) 562-5128 Home http://hammondb3organ.net http://overdubs.net _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Jock at kc6iih@aol.com To unsubscribe, send an email to
chirp_users-unsubscribe@intrepid.danplanet.com_______________________________________________
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Rick Farina at sidhayn@gmail.com To unsubscribe, send an email to
chirp_users-unsubscribe@intrepid.danplanet.com _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Dan Clemmensen at danclemmensen@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Rick Farina at sidhayn@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Chuck Hast at kp4djt@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
-- Chirp + Editcp + MD380Tools on Linux Celestial!!! Chuck -- KP4DJT _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to W5NNH at kemkerj3@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
-- --John E Kemker III _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Chuck Hast at kp4djt@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
participants (15)
-
Ben Smith -
benton＠siletzbay.com -
Chance Fulton -
Chuck Hast -
Dan Clemmensen -
George Hale Jr. -
JOCK SOUTAR -
John Kemker -
Josef Zeevi -
jz＠zeevi.org
-
Larry Howell -
Pavel Milanes Costa -
Peter J. McClosky -
Sid Hayn -
Tom Henderson