<div dir="ltr"><div>I've looked high and low around the chirp web site for how to formally report a bug, but see no way to do so. Help?<br><br></div>Basil<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">
On Thu, Jan 23, 2014 at 8:37 PM, Jens J. <span dir="ltr"><<a href="mailto:kd4tjx@yahoo.com" target="_blank">kd4tjx@yahoo.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div style="font-size:10pt;font-family:lucida console,sans-serif"><div>Hi Basil,</div><div>Please do report this bug, and be sure to include the debug.log, and a copy of radio image which was downloaded.</div><div><br>
</div><div style="font-style:normal;font-size:13px;background-color:transparent;font-family:'lucida console',sans-serif"><br></div><div><br></div> <div style="font-family:'lucida console',sans-serif;font-size:10pt">
<div style="font-family:HelveticaNeue,'Helvetica Neue',Helvetica,Arial,'Lucida Grande',sans-serif;font-size:12pt"> <div dir="ltr"> <hr size="1"> <font face="Arial"> <b><span style="font-weight:bold">From:</span></b> Basil Copeland <<a href="mailto:blcjr2@gmail.com" target="_blank">blcjr2@gmail.com</a>><div class="im">
<br> <b><span style="font-weight:bold">To:</span></b> Discussion of CHIRP <<a href="mailto:chirp_users@intrepid.danplanet.com" target="_blank">chirp_users@intrepid.danplanet.com</a>> <br> </div><b><span style="font-weight:bold">Sent:</span></b> Thursday, January 23, 2014 8:29 PM<div class="im">
<br> <b><span style="font-weight:bold">Subject:</span></b> Re: [chirp_users] Problems with Yaesu -- FT60 and FT-8800<br> </div></font> </div><div><div class="h5"> <div><br><div><div><div dir="ltr"><div><div><div><div><div>
<div><div>Okay, here are some results from a bit of testing with versions.<br clear="none"><br clear="none"></div>1) The error is replicated in 20140102 (which is the first version of CHIRP I used).<br clear="none"><br clear="none">
</div>
2) When I installed the current "stable" version, the error is not present, and the write to the FT-60 is successful.<br clear="none"><br clear="none"></div>3) When I reinstalled 20140102 "on top of" the stable version (i.e. without first doing a complete uninstall), it also worked! But when I did a complete uninstall, and reinstall of 20140102, the error returned.<br clear="none">
<br clear="none"></div>4) I went back to the 20131031 version. When this was installed "on top of" the stable version, same result as in 3), i.e. no error. But when I did a complete uninstall, and reinstalled 20131031, the error returned.<br clear="none">
<br clear="none"></div>5) Lastly, did a complete uninstall, and installed 20131002. This version worked, like the stable version. No error.<br clear="none"><br clear="none"></div>So, somewhere between 20131002 and 20131031, the error enters. I guess you could check change logs for the builds in October for any changes that would affect Yaesu radios. Incidentally, I notice that between 20131002 and 20131031, the read and write instructions (steps to set the radio for rx or tx) were added. Had I started with the "stable" build, or even 20131002, I wouldn't have known what to do (without further research) to set the radios for read or write.<br clear="none">
<br clear="none"></div>Basil<br clear="none"></div><div><div><br clear="none"><br clear="none"><div>On Thu, Jan 23, 2014 at 5:51 PM, IZ3GME Marco <span dir="ltr"><<a rel="nofollow" shape="rect" href="mailto:iz3gme.marco@gmail.com" target="_blank">iz3gme.marco@gmail.com</a>></span> wrote:<br clear="none">
<blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Good news!<br clear="none">
Can you please try again with the daily build to confirm is only a version problem?<br clear="none">
I can't test myself for a couple of days ...<br clear="none">
<div><br clear="none">
Tnx<br clear="none">
<br clear="none">
73 de IZ3GME Marco<br clear="none">
<br clear="none">
</div>On Thu, 23 Jan 2014 17:43:56 -0600<br clear="none">
<div><div>Basil Copeland <<a rel="nofollow" shape="rect" href="mailto:blcjr2@gmail.com" target="_blank">blcjr2@gmail.com</a>> wrote:<br clear="none">
<br clear="none">
> It may be too late for that? I just installed the "stable" version, and it<br clear="none">
> worked. So this is an issue with the daily build version I was using, or<br clear="none">
> so it would seem.<br clear="none">
><br clear="none">
> Basil<br clear="none">
><br clear="none">
><br clear="none">
> On Thu, Jan 23, 2014 at 5:34 PM, IZ3GME Marco <<a rel="nofollow" shape="rect" href="mailto:iz3gme.marco@gmail.com" target="_blank">iz3gme.marco@gmail.com</a>>wrote:<br clear="none">
><br clear="none">
> > Hi Basil<br clear="none">
> > I think there can be some useful info in the log, can you please reproduce<br clear="none">
> > the problem and send it?<br clear="none">
> > Here is how to collect debug log<br clear="none">
> ><br clear="none">
> > <a rel="nofollow" shape="rect" href="http://chirp.danplanet.com/projects/chirp/wiki/How_To_Report_Issues#Getting-your-debug-log" target="_blank">http://chirp.danplanet.com/projects/chirp/wiki/How_To_Report_Issues#Getting-your-debug-log</a><br clear="none">
> ><br clear="none">
> > tnx<br clear="none">
> > 73 de IZ3GME Marco<br clear="none">
> ><br clear="none">
> > On Thu, 23 Jan 2014 16:31:20 -0600<br clear="none">
> > Basil Copeland <<a rel="nofollow" shape="rect" href="mailto:blcjr2@gmail.com" target="_blank">blcjr2@gmail.com</a>> wrote:<br clear="none">
> ><br clear="none">
> > > Thanks for the prompt reply. At least with respect to the FT-60,<br clear="none">
> > Commander<br clear="none">
> > > was not open; at that point, it had not even been installed. IAC, I just<br clear="none">
> > > went through the whole process again with the FT-60. Same error.<br clear="none">
> > ><br clear="none">
> > > Seems curious to me that this would happen with two different cables<br clear="none">
> > > connected to two different radios. I really do not see how it could be a<br clear="none">
> > > cable issue. Driver issue, perhaps. That would be the only common<br clear="none">
> > > denominator. The driver is FTDI 2.8.30.0, dated 7/12/13, and installed<br clear="none">
> > > using COM4, as COM1/3 is reported "in use" (that would be for a Prolific<br clear="none">
> > > driver/USB cable used with the UV-5R).<br clear="none">
> > ><br clear="none">
> > > Basil<br clear="none">
> > > KE5GAE<br clear="none">
> > ><br clear="none">
> > ><br clear="none">
> > > On Thu, Jan 23, 2014 at 3:58 PM, Tom Hayward <<a rel="nofollow" shape="rect" href="mailto:esarfl@gmail.com" target="_blank">esarfl@gmail.com</a>> wrote:<br clear="none">
> > ><br clear="none">
> > > > On Thu, Jan 23, 2014 at 1:27 PM, Basil Copeland <<a rel="nofollow" shape="rect" href="mailto:blcjr2@gmail.com" target="_blank">blcjr2@gmail.com</a>><br clear="none">
> > wrote:<br clear="none">
> > > > > windows, with a final error message saying something about being<br clear="none">
> > unable<br clear="none">
> > > > to<br clear="none">
> > > > > "read echo" and then "bad cable?"<br clear="none">
> > > ><br clear="none">
> > > > This error means that Chirp tried to send something out over the<br clear="none">
> > > > serial port and didn't get a response. With Yaesu cables, everything<br clear="none">
> > > > sent should echo back to the serial port, because the tx and rx lines<br clear="none">
> > > > are connected together. The cause of this is usually, as reported, a<br clear="none">
> > > > faulty cable or driver. My only other idea is that another program may<br clear="none">
> > > > have been using the serial port when Chirp tried to access it. Was<br clear="none">
> > > > Commander still open?<br clear="none">
> > > ><br clear="none">
> > > > Tom KD7LXL<br clear="none">
> > > > _______________________________________________<br clear="none">
> > > > chirp_users mailing list<br clear="none">
> > > > <a rel="nofollow" shape="rect" href="mailto:chirp_users@intrepid.danplanet.com" target="_blank">chirp_users@intrepid.danplanet.com</a><br clear="none">
> > > > <a rel="nofollow" shape="rect" href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users" target="_blank">http://intrepid.danplanet.com/mailman/listinfo/chirp_users</a><br clear="none">
> > > ><br clear="none">
> > _______________________________________________<br clear="none">
> > chirp_users mailing list<br clear="none">
> > <a rel="nofollow" shape="rect" href="mailto:chirp_users@intrepid.danplanet.com" target="_blank">chirp_users@intrepid.danplanet.com</a><br clear="none">
> > <a rel="nofollow" shape="rect" href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users" target="_blank">http://intrepid.danplanet.com/mailman/listinfo/chirp_users</a><br clear="none">
> ><br clear="none">
_______________________________________________<br clear="none">
chirp_users mailing list<br clear="none">
<a rel="nofollow" shape="rect" href="mailto:chirp_users@intrepid.danplanet.com" target="_blank">chirp_users@intrepid.danplanet.com</a><br clear="none">
<a rel="nofollow" shape="rect" href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users" target="_blank">http://intrepid.danplanet.com/mailman/listinfo/chirp_users</a><br clear="none">
</div></div></blockquote></div><br clear="none"></div></div></div></div><br><div>_______________________________________________<br clear="none">chirp_users mailing list<br clear="none"><a shape="rect" href="mailto:chirp_users@intrepid.danplanet.com" target="_blank">chirp_users@intrepid.danplanet.com</a><br clear="none">
<a shape="rect" href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users" target="_blank">http://intrepid.danplanet.com/mailman/listinfo/chirp_users</a><br clear="none"></div><br><br></div> </div></div></div> </div>
</div></div><br>_______________________________________________<br>
chirp_users mailing list<br>
<a href="mailto:chirp_users@intrepid.danplanet.com">chirp_users@intrepid.danplanet.com</a><br>
<a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users" target="_blank">http://intrepid.danplanet.com/mailman/listinfo/chirp_users</a><br>
<br></blockquote></div><br></div>