volconst

Do you see 'ok' for the G1 command. It is possible that the reading from the printer is broken. G1 could move the head even if we cannot read from...

You have to edit this code https://github.com/kliment/Printrun/blob/c451359a35d502a8e446702d3cf94cae9e50c0de/printrun/printcore.py#L253-L255

If you provide port in the constructor it is automatically opened and after that in the code it is opened again - remove the port parameter.

@euan2e5 raspbian stretch lite is console only, no GUI. You can run ./pronsole.py

https://github.com/kliment/Printrun/blob/82ed6302507eff93247e931c77f1c16b1a71f7fd/printrun/printcore.py#L349-L351 This is caused by UnicodeDecodeError. Put a print(line_bytes) before https://github.com/kliment/Printrun/blob/82ed6302507eff93247e931c77f1c16b1a71f7fd/printrun/printcore.py#L337 to see the bytes. It could be some compression algo, or non utf-8 text.

@a2k-hanlon , I think this is a hack to support the commented Tab uimodes if they are persisted in settings. Thus they are not advertised, but still supported.

You are welcome :) You can look at the 'Blame' view, to dig into history of the lines of interest.

@xtatorx you can test whether the artifacts at https://github.com/volconst/Printrun/actions/runs/1074748808 fix the problem. There are 2 exceptions and the fix is only for the last, but the other may be ok...

@xtatorx , Enable debug communication in the exe from https://github.com/volconst/Printrun/actions/runs/1074748808 and include the log together with the exception stack trace.

> Hi @volconst, > I just recognize the parameter **u**. Do printrun decode this parameter for PID tuning? > M303 E0 S200 **U1** I believe unknown parameters are forwarded transparently...