I'm keep getting Serial error after updating to Octopi Version 0.18.0 OctoPrint Version 1.7.3. It stops on the same place on the print. Tried another file and it stops on the same place with the other file as well. It will stop but still keep the the heatbed and hotend on the temps from the gcode file.
What did you already try to solve it?
Tried different gcode files.
Tried 2 other usb cables
Tried safe mode
Tried fresh installation
For this is a Creality printer, first you can try with/without SC card in the printer slot.
Also this:
To the serial log:
At a certain point the printer gets busy processing the commands (from line N1012 on).
It takes up to 2 seconds to process a line. Up to the point there is no response from the printer any more.
So I tried the 5v pin mod and same result. Went out and bought another usb cable. Printed a little longer. See bundle octoprint-systeminfo-20220126091219.zip (1.0 MB)
Then tried my raspberry pi 3 running Octoprint Version 1.7.2 Octopi Version 0.18.0 with the same result. I know about the under voltage error because it is not the original power supply.
see bundle octoprint-systeminfo-20220126095527.zip (65.4 KB)
Anything else I could try? Any suggestions will be welcome.
I plugged back the PI 4. Loaded an old gcode file to print that was created last year. So far it is printing for 11min without any issue. So this might be a slicer(Cura) issue. Will update.
Okey the above file finished printing( Hollow 20x20 cube ). I uninstalled Cura and all the profiles. Downloaded a new copy and installed. Set my setting and sliced the new stl. Started print, failed on same place as my first print. Even went as far as flashing the firmware on the ender 3 pro. See systeminfo octoprint-systeminfo-20220127000525.zip (701.2 KB)
Started the print again and it again stopped on the same place.
I don't know what else to do. Any other suggestions?
I had another look on the serial logs.
After about 1000 lines, the printer seems to have trouble processing G0 (rapid move) commands that are faster than 1800 mm/min. This appears after command lines with F2400 or F4800.
You may reduce the maximum travel speed to 1800 mm/min to observe if issue is still there.
It also may be, that the firmware has some trouble with the G0 command.