[chirp_users] FT-817ND Writing problem

Kurt Savegnago ksaves2 at sbcglobal.net
Thu Jan 26 15:23:25 PST 2012


  I'll give it another try tonight with the linux version.  I think I have 
another cable and will give it a go too.  I will say that after I have Chirp read the ND, there is a delay, then a beep and then the screen on the ND says ERROR.  Thing is, even with this funky read process, all of the memories are appropriately read and displayed on the computer screen in chirp.  I'll see what a different cable does and try the write process from chirp to the ND with the debug command.

                              Kurt KC9LDH

--- On Thu, 1/26/12, Marco IZ3GME <iz3gme.marco at gmail.com> wrote:

> From: Marco IZ3GME <iz3gme.marco at gmail.com>
> Subject: Re: [chirp_users] FT-817ND Writing problem
> To: chirp_users at intrepid.danplanet.com
> Date: Thursday, January 26, 2012, 4:55 AM
> On 26/01/2012 04:25, Dan Smith
> wrote:
> >> I think the cable is fine because it works with
> HRD. Tried both Linux
> >> and Windows versions of Chirp. Weird because it
> reads the 817ND's
> >> memory just fine. No joy when it writes.
> >
> > Hmm, strange. Try running with CHIRP_DEBUG and grabbing
> the console
> > output to send to us. On linux:
> >
> > # CHIRP_DEBUG=y ./chirpw 2>&1 | tee debug.log
> >
> >
> > Maybe Marco has an idea?
> >
> Yes please, the debug output should help. Please do the
> clone out 
> immediately after the clone in so we are sure that there are
> no other 
> variables playing.
> I suspect a timing problem as Dan has already suggested but
> what is 
> really strange is that the radio should say if the clone
> operation was 
> completed or not ...
> BTW I developed the driver on my 817nd and never had to face
> such a deep 
> reset.
> 73 de IZ3GME Marco
> _______________________________________________
> chirp_users mailing list
> chirp_users at intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_users

More information about the chirp_users mailing list