Page 1 of 1

Pyserial3 and miniterm

Posted: Mon Oct 10, 2016 5:30 pm
by marfis
For those who are using pyserial's miniterm... it took me a while to figure this out:

Since pyserial v3 the escape sequence are not processed by default. uPy makes heavy use of escape sequence so the repl is basically unusable - except you pass the

Code: Select all

-f direct
parameter to the miniterm call.

Thanks to the pyserial maintainer for this tip...

Re: Pyserial3 and miniterm

Posted: Tue Aug 22, 2017 5:52 pm
by cefn
Curious if this is the same as the --raw flag which I use.

Re: Pyserial3 and miniterm

Posted: Wed Aug 23, 2017 7:13 am
by pythoncoder
Thanks for that :D

[EDIT]
Later. Both these are an improvement but they aren't perfect, at least with my ESP32. Attempting to recall and edit a previously entered line doesn't work at all reliably.

Re: Pyserial3 and miniterm

Posted: Wed Aug 23, 2017 7:49 am
by Roberthh
Hi @pythoncoder. Why don't you use a serial terminal intended for that purpose, like picocom, minicom or even screen? I thought you did.

Re: Pyserial3 and miniterm

Posted: Wed Aug 23, 2017 4:06 pm
by pythoncoder
I use rshell almost exclusively which I find awesome for MicroPython.

There are odd occasions when I need a dumb terminal. As miniterm is in Python I hacked it to do a few things like keyboard macros so I use it on occasion. But I'll use any terminal application available including screen.

Re: Pyserial3 and miniterm

Posted: Wed Aug 23, 2017 5:30 pm
by dhylands
Under linux, I use usb-ser-mon.py when I don't use rshell: https://github.com/dhylands/usb-ser-mon ... ser-mon.py

Rather than specify a port (like /dev/ttyACM0) it uses attributes from the usb device, like the manufacturer name, etc to connect. The --list option will show all of your connected USB srial devices.

Re: Pyserial3 and miniterm

Posted: Thu Apr 19, 2018 7:52 am
by Kelly Petersen
In working with macros, rshell is simply irreplaceable