Type 'copyright', 'credits' or 'license()' for more information. #Echo the serial buffer bytes up to the CRLF back to screen #clear serial buffer to remove junk and noise It is most likely the mode or class (whatever that means) or environment I am running things in ? This is just to set up simple classroom demo scripts running IDLE and minimal hardware and basic concepts. These took weeks to pull out of the I imagine there will be an 'open' and 'close' command as well that would pretty much do the same thing and keep things tidy and under control. The read byte, read bytes and timeout functions have been 'discovered' already. Highly recommended when conversing and talking to picaxe etc. I imagine it would be somewhere between the port command and the port.readline() command I imagine.įor anyone interested the above port.readline() example works FAB with serial data arriving at the GPIO ad hoc / variable length and responds to the 13/10 LF/CR very nicely. Can someone indicate where and how such a clear buffer command would go in the above example so it runs once on startup.

#This sets up the serial port ttyAMA0 GPIOĢ/. Port = serial.Serial('/dev/ttyAMA0', baudrate=2400) Import serial, time #this imports the libraries needed This can be time consuming / messy esp if processing and forwarding data off the UART as we are doing to a web server etc. When (re)starting the program the Pi seems to have happily accumulated everything and anything seen on the UART Rx line.

Would be interested in how to clear the input serial buffer (and output ?) as the following program example starts.

Python flush serial port buffer