[chirp_users] Problems with Yaesu -- FT60 and FT-8800

Sat Jan 25 06:10:52 PST 2014

Thanks.  I've filed a bug report.

Basil

On Sat, Jan 25, 2014 at 12:22 AM, Jens J. <kd4tjx at yahoo.com> wrote:

>
>
> http://chirp.danplanet.com/projects/chirp/wiki/How_To_Report_Issues#Getting-your-debug-log
>
> Sent from Yahoo Mail on Android<https://overview.mail.yahoo.com/mobile/?.src=Android>
>
>  ------------------------------
> * From: * Basil Copeland <blcjr2 at gmail.com>;
> * To: * Jens J. <kd4tjx at yahoo.com>; Discussion of CHIRP <
> chirp_users at intrepid.danplanet.com>;
> * Subject: * Re: [chirp_users] Problems with Yaesu -- FT60 and FT-8800
> * Sent: * Sat, Jan 25, 2014 2:40:20 AM
>
>   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?
>
> Basil
>
>
> On Thu, Jan 23, 2014 at 8:37 PM, Jens J. <kd4tjx at yahoo.com> wrote:
>
>> Hi Basil,
>> Please do report this bug, and be sure to include the debug.log, and a
>> copy of radio image which was downloaded.
>>
>>
>>
>>   ------------------------------
>>  *From:* Basil Copeland <blcjr2 at gmail.com>
>>
>> *To:* Discussion of CHIRP <chirp_users at intrepid.danplanet.com>
>> *Sent:* Thursday, January 23, 2014 8:29 PM
>>
>> *Subject:* Re: [chirp_users] Problems with Yaesu -- FT60 and FT-8800
>>
>> Okay, here are some results from a bit of testing with versions.
>>
>> 1) The error is replicated in 20140102 (which is the first version of
>> CHIRP I used).
>>
>>  2) When I installed the current "stable" version, the error is not
>> present, and the write to the FT-60 is successful.
>>
>> 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.
>>
>> 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.
>>
>> 5) Lastly, did a complete uninstall, and installed 20131002.  This
>> version worked, like the stable version.  No error.
>>
>> 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.
>>
>> Basil
>>
>>
>> On Thu, Jan 23, 2014 at 5:51 PM, IZ3GME Marco <iz3gme.marco at gmail.com>wrote:
>>
>> Good news!
>> Can you please try again with the daily build to confirm is only a
>> version problem?
>> I can't test myself for a couple of days ...
>>
>> Tnx
>>
>> 73 de IZ3GME Marco
>>
>> On Thu, 23 Jan 2014 17:43:56 -0600
>> Basil Copeland <blcjr2 at gmail.com> wrote:
>>
>> > 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.
>> >
>> > Basil
>> >
>> >
>> > On Thu, Jan 23, 2014 at 5:34 PM, IZ3GME Marco <iz3gme.marco at gmail.com
>> >wrote:
>> >
>> > > Hi Basil
>> > > I think there can be some useful info in the log, can you please
>> reproduce
>> > > the problem and send it?
>> > > Here is how to collect debug log
>> > >
>> > >
>> http://chirp.danplanet.com/projects/chirp/wiki/How_To_Report_Issues#Getting-your-debug-log
>> > >
>> > > tnx
>> > > 73 de IZ3GME Marco
>> > >
>> > > On Thu, 23 Jan 2014 16:31:20 -0600
>> > > Basil Copeland <blcjr2 at gmail.com> wrote:
>> > >
>> > > > Thanks for the prompt reply.  At least with respect to the FT-60,
>> > > Commander
>> > > > was not open; at that point, it had not even been installed.  IAC,
>> I just
>> > > > went through the whole process again with the FT-60.  Same error.
>> > > >
>> > > > Seems curious to me that this would happen with two different cables
>> > > > connected to two different radios.  I really do not see how it
>> could be a
>> > > > cable issue.  Driver issue, perhaps.  That would be the only common
>> > > > denominator.  The driver is FTDI 2.8.30.0, dated 7/12/13, and
>> installed
>> > > > using COM4, as COM1/3 is reported "in use" (that would be for a
>> Prolific
>> > > > driver/USB cable used with the UV-5R).
>> > > >
>> > > > Basil
>> > > > KE5GAE
>> > > >
>> > > >
>> > > > On Thu, Jan 23, 2014 at 3:58 PM, Tom Hayward <esarfl at gmail.com>
>> wrote:
>> > > >
>> > > > > On Thu, Jan 23, 2014 at 1:27 PM, Basil Copeland <blcjr2 at gmail.com
>> >
>> > > wrote:
>> > > > > > windows, with a final error message saying something about being
>> > > unable
>> > > > > to
>> > > > > > "read echo" and then "bad cable?"
>> > > > >
>> > > > > This error means that Chirp tried to send something out over the
>> > > > > serial port and didn't get a response. With Yaesu cables,
>> everything
>> > > > > sent should echo back to the serial port, because the tx and rx
>> lines
>> > > > > are connected together. The cause of this is usually, as
>> reported, a
>> > > > > faulty cable or driver. My only other idea is that another
>> program may
>> > > > > have been using the serial port when Chirp tried to access it. Was
>> > > > > Commander still open?
>> > > > >
>> > > > > Tom KD7LXL
>> > > > > _______________________________________________
>> > > > > chirp_users mailing list
>> > > > > chirp_users at intrepid.danplanet.com
>> > > > > http://intrepid.danplanet.com/mailman/listinfo/chirp_users
>> > > > >
>> > > _______________________________________________
>> > > chirp_users mailing list
>> > > chirp_users at intrepid.danplanet.com
>> > > http://intrepid.danplanet.com/mailman/listinfo/chirp_users
>> > >
>> _______________________________________________
>> chirp_users mailing list
>> chirp_users at intrepid.danplanet.com
>> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
>>
>>
>>
>> _______________________________________________
>> chirp_users mailing list
>> chirp_users at intrepid.danplanet.com
>> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
>>
>>
>>
>> _______________________________________________
>> chirp_users mailing list
>> chirp_users at intrepid.danplanet.com
>> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20140125/3766a4e2/attachment.html 