<div dir="ltr"><div><div><div><div><div><div><div>Okay, here are some results from a bit of testing with versions.<br><br></div>1) The error is replicated in 20140102 (which is the first version of CHIRP I used).<br><br></div>
2) When I installed the current "stable" version, the error is not present, and the write to the FT-60 is successful.<br><br></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>
<br></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>
<br></div>5) Lastly, did a complete uninstall, and installed 20131002. This version worked, like the stable version. No error.<br><br></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>
<br></div>Basil<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Jan 23, 2014 at 5:51 PM, IZ3GME Marco <span dir="ltr"><<a href="mailto:iz3gme.marco@gmail.com" target="_blank">iz3gme.marco@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Good news!<br>
Can you please try again with the daily build to confirm is only a version problem?<br>
I can't test myself for a couple of days ...<br>
<div class="im"><br>
Tnx<br>
<br>
73 de IZ3GME Marco<br>
<br>
</div>On Thu, 23 Jan 2014 17:43:56 -0600<br>
<div class="HOEnZb"><div class="h5">Basil Copeland <<a href="mailto:blcjr2@gmail.com">blcjr2@gmail.com</a>> wrote:<br>
<br>
> It may be too late for that? I just installed the "stable" version, and it<br>
> worked. So this is an issue with the daily build version I was using, or<br>
> so it would seem.<br>
><br>
> Basil<br>
><br>
><br>
> On Thu, Jan 23, 2014 at 5:34 PM, IZ3GME Marco <<a href="mailto:iz3gme.marco@gmail.com">iz3gme.marco@gmail.com</a>>wrote:<br>
><br>
> > Hi Basil<br>
> > I think there can be some useful info in the log, can you please reproduce<br>
> > the problem and send it?<br>
> > Here is how to collect debug log<br>
> ><br>
> > <a 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>
> ><br>
> > tnx<br>
> > 73 de IZ3GME Marco<br>
> ><br>
> > On Thu, 23 Jan 2014 16:31:20 -0600<br>
> > Basil Copeland <<a href="mailto:blcjr2@gmail.com">blcjr2@gmail.com</a>> wrote:<br>
> ><br>
> > > Thanks for the prompt reply. At least with respect to the FT-60,<br>
> > Commander<br>
> > > was not open; at that point, it had not even been installed. IAC, I just<br>
> > > went through the whole process again with the FT-60. Same error.<br>
> > ><br>
> > > Seems curious to me that this would happen with two different cables<br>
> > > connected to two different radios. I really do not see how it could be a<br>
> > > cable issue. Driver issue, perhaps. That would be the only common<br>
> > > denominator. The driver is FTDI 2.8.30.0, dated 7/12/13, and installed<br>
> > > using COM4, as COM1/3 is reported "in use" (that would be for a Prolific<br>
> > > driver/USB cable used with the UV-5R).<br>
> > ><br>
> > > Basil<br>
> > > KE5GAE<br>
> > ><br>
> > ><br>
> > > On Thu, Jan 23, 2014 at 3:58 PM, Tom Hayward <<a href="mailto:esarfl@gmail.com">esarfl@gmail.com</a>> wrote:<br>
> > ><br>
> > > > On Thu, Jan 23, 2014 at 1:27 PM, Basil Copeland <<a href="mailto:blcjr2@gmail.com">blcjr2@gmail.com</a>><br>
> > wrote:<br>
> > > > > windows, with a final error message saying something about being<br>
> > unable<br>
> > > > to<br>
> > > > > "read echo" and then "bad cable?"<br>
> > > ><br>
> > > > This error means that Chirp tried to send something out over the<br>
> > > > serial port and didn't get a response. With Yaesu cables, everything<br>
> > > > sent should echo back to the serial port, because the tx and rx lines<br>
> > > > are connected together. The cause of this is usually, as reported, a<br>
> > > > faulty cable or driver. My only other idea is that another program may<br>
> > > > have been using the serial port when Chirp tried to access it. Was<br>
> > > > Commander still open?<br>
> > > ><br>
> > > > Tom KD7LXL<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>
> > _______________________________________________<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>
_______________________________________________<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>
</div></div></blockquote></div><br></div>