(Forwarding to the list.)
-- 
Lloyd Kvam
Venix Corp
--- Begin Message ---
Ya know, you're right!... Wow, I feel good about
myself now..:) What I'll do is have the fist command
be ECHO OFF and see what happens...


Sorry about the waisted bandwidth, but thank you for
bringing me back to reality... It's the simple stuff
that will get ya! :)



-Joe

--- Python <[EMAIL PROTECTED]> wrote:

> The device at the far end of the serial connection
> is echoing what you
> write back to you.  This is a convenience for
> someone typing at a
> terminal, but a nuisance when you are programming.
> 
> The easier way out is to turn echoing off at the far
> device.  Failing
> that, you will want to provide a copy of your output
> to the read routine
> so that it can filter your output out of the data
> stream coming back to
> you.
> 
> Unfortunately there is no reliable error detection
> on a serial line, so
> line errors can complicate the task of matching the
> echoes to your
> output.
> 
> On Mon, 2005-11-14 at 17:04 -0800, Bennett, Joe
> wrote:
> > I have been working with pyserial. One question I
> have
> > is this. I have a loop that writes to the serial
> port
> > and then waits about 500ms and then reads from the
> > serial port. The first thing read from the serial
> port
> > is ALWAYS the data written to the serial port... I
> > must be missing something obvious, but I thuoght
> the
> > two buffers were separate...
> (snipped)
> > _______________________________________________
> > Tutor maillist  -  Tutor@python.org
> > http://mail.python.org/mailman/listinfo/tutor
> -- 
> Lloyd Kvam
> Venix Corp
> 
> 

--- End Message ---
_______________________________________________
Tutor maillist  -  Tutor@python.org
http://mail.python.org/mailman/listinfo/tutor

Reply via email to