Collision detection troubleshooting on new printer
Hi, new Mk3 owner, I built the printer a few days ago (it is NOT the new S version).
I did a few prints from the SD card, everything looked and worked great.
I sliced a part using Slic3rPE, and when I printed it from the SD card, the printer told me there is a firmware update, I assume it gets this info from the gcode file.
I updated the printer to 3.5.1.
Since updating the firmware, I get collision detected on Y axis, and sometimes X axis, about 1xX and 10xY per 10 hour print.
I read last night that there is now a 3.5.2 firmware, I updated to 3.5.2, hoping it may be a firmware issue, same problem.
Per google, I verified the belt offset positions, no problem.
Per google, I did loosen the extruder cover screws a bit, loosening the cover screws did make the X-axis move more easily, and I've not had X-axis collisions in the last print, but still Y-axis collisions.
The bed does move reasonably easily, not super smooth, but no sticking per my hand movement.
Per google, I read that I need to remove the heat bed and loosen the u-bolt screws, I'll do that when the current print finishes.
I am wondering though, the problem only started happening after I updated to 3.5.1, could it be a firmware problem, maybe too sensitive, or is it just a timing related with the printer wearing in or wearing out, and not firmware related?
How do I go about troubleshooting?
E.g. if the printer can detect "collisions" can it help tell me how "smooth" the axis movement is?
Re: Collision detection troubleshooting on new printer
I can't answer your real question, but it's my understanding all collisions are sensed by detecting currents to the motors, and I have read somewhere v3.5 did change how the motors were driven (unverified by me, though). You can change back to 3.4 and see if the issue persists, or not. It could be the printer has flexed enough some wart has popped up and it's only a coincidence it showed up with 3.5 upgrade.
You can avoid the FW upgrade spam by changing the custom gcode on the Printer tab:
M115 U3.4.0 ; tell printer latest fw version (I'm happy with what I am using, a modified 3.5 something)
Re: Collision detection troubleshooting on new printer
Last night I loosened the u-bolts a bit, the bed still moves freely, but with less noise.
I switched to using OctoPrint, and from Amazon Basics PETG to PLA Prusament, I know, I am changing too many variables.
I changed to OctoPrint for convenience, but I noticed that when printing from OctoPrint, the print fail stats are not reset.
I noticed this after an 11 hour print, and this morning I was disappointed to see that I again had collision failures, but the total count did not change:
https://github.com/prusa3d/Prusa-Firmware/issues/676
The reason I changed from Amazon Basics PETG to Prusament PLA is because google showed some results where collisions can be the result of the extruder temporarily not detecting filament, and this apparently happens with translucent filament, and I was using translucent pink.
I hope the real issue was the translucent filament, something the MK3S extruder should fix.
I hoped too soon, I started printing a vase, and even with the silver prusament, and loosened u-bolts, I'm still getting crashes 🙁