Communication error while printing ECOR_TOWER with fw3.2.1
Hi all!
I have the latest firmware for my MK3 (3.2.1) and I am trying to print the ECOR_TOWER for linearity correction calibration. I am printing it through Octoprint (normal USB connection, not direct Einsy connection) and the print failed twice with a communication error: "too many consecutive timeouts."
I haven't tried printing anything else with the new firmware yet, so I can't confirm if it's a general problem, but I just wanted to know if this happened to anybody else.
Cheers,
Francesco
Re: Communication error while printing ECOR_TOWER with fw3.2.1
Issue will be fixed with around next week or so.
Git pull #744 did not make it into the master yet.
https://github.com/prusa3d/Prusa-Firmware/pull/744/commits/c59e9bd6bec45ddd5a5c2d2ad8c96b8f9d240c4b
Re: Communication error while printing ECOR_TOWER with fw3.2.1
Awesome, thanks! Just two more questions then:
1) Printing ECOR_TOWER from SD would work (presumably yes as it seems a serial-comm-related bug)?
2) Does this bug affect all files or just ECOR_TOWER?
Re: Communication error while printing ECOR_TOWER with fw3.2.1
Awesome, thanks! Just two more questions then:
1) Printing ECOR_TOWER from SD would work (presumably yes as it seems a serial-comm-related bug)?
2) Does this bug affect all files or just ECOR_TOWER?
1 - yep, move it to SD and it works.
2 - not entirely related to this bug, but it affects undocumented gcodes or gcodes that are too new. OctoPrint halts everything (safety measure) when it senses the printer is doing something and takes way too long to respond.
OctoPrint has a 'long running commands' setting, where people can add things like the mesh bed leveling command or temp calibration command, but the Prusa dev team often introduces new special gcodes that throw OctoPrint off.
I once was up to date with these long running commands on the MK2, but on the MK3 they introduced so much special stuff with no documentation that just bugs OctoPrint left and right.
gcodes generated from Slic3r S3D Cura KissSlicer work fine in OctoPrint, Prusa's special whacky gcodes for special printer settings not so.