<div dir="ltr">It may be too late for that? I just installed the "stable" version, and it worked. So this is an issue with the daily build version I was using, or so it would seem.<br><br>Basil<br></div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Thu, Jan 23, 2014 at 5:34 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">
Hi Basil<br>
I think there can be some useful info in the log, can you please reproduce the problem and send it?<br>
Here is how to collect debug log<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>
<div class="HOEnZb"><div class="h5"><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, 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>> wrote:<br>
> > > windows, with a final error message saying something about being 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>
</div></div></blockquote></div><br></div>