Miniterm fixed for Windows 10

[cefn]

I put together a modified version of Miniterm which addresses several issues which combine to explain problems people have using Miniterm on Windows Python, like this https://github.com/pyserial/pyserial/is ... -395713660

It is rollup of a fairly major fix for Windows terminal code-handling to translate input events received by the board, as well as some Windows 10-specific mode-setting logic which makes the console work properly since Windows 10 v1511 to handle received screen events on the client's side.

Thought it might be worth sharing given the issues around people successfully connecting and running a bug-free 'VT100' across platform, and be good to hear from people if it works for them.

I have republished the fixed version at https://github.com/vgkits/vgkits-vangua ... initerm.py until https://github.com/pyserial/pyserial/pull/351 gets considered or merged into PySerial.

If you have an ESP8266 board or any other running Micropython at 115200, this fixed version is already included in the latest vgkits-vanguard, so you should be able to test it out by just running

Code: Select all

vanguard shell

after installing the Vanguard tools following these instructions

Alternatively you can replace your local serial/tools/miniterm.py file and use the instructions to use Miniterm direct following https://vgkits.org/blog/connecting-with-miniterm/

[spektro]

Awsome job!
Those Putty and alike, semi-graphical terminals was driving me nuts! Somebody just needed to made it overcomplicated...
I made KISS batch file for starting miniterm from anywhere.
Save code from below as term.cmd in your path eg. python install dir or C:/Windows/system32.

Code: Select all

python -m serial.tools.miniterm --filter direct --eol CRLF --encoding utf-8 %1 %2

Usage is simple: just write "term" or "term COMXX baudrate" in cmd or PowerShell or even folder address bar...