Trouble with Mk4 IS Firmware and Slicer 2.6
 
Notifications
Clear all

Trouble with Mk4 IS Firmware and Slicer 2.6  

  RSS
Brian Amato
(@brian-amato)
Active Member
Trouble with Mk4 IS Firmware and Slicer 2.6

I've posted this over on the subreddit as well, so apologies to anyone that this might be a duplicate issue on.  But I've been struggling to get any print to complete with the alpha firmware on my mk4.  Originally, I thought it was an octoprint issue, as the print head would just stop moving mid print.  So I loaded my USB stick with some test prints and starting going.  The first print I canceled because the bridging on the temp tower failed pretty early on.  My second print was a low poly evee model.  After about ten minutes I noticed the print head was no longer extruding, so I canceled the print and tried again.  This time I hovered over the machine and watched the print settings around when it failed the first time.  Which I then noticed the bed stopped heating, shortly followed by the hot end.  When I checked messages screen, I saw "bed timed out" and "tool0 timed out".  Not sure the cause of this.

Opublikowany : 26/06/2023 8:58 pm
Walter Layher
(@walter-layher)
Prominent Member
RE: Trouble with Mk4 IS Firmware and Slicer 2.6

I have had good success printing gcode generated with IS from the USB stick and using just the webcam in OctoPrint to monitor the print. It even works if I have processed the files with the Arc-Welder plugin in OctoPrint first. Printing IS gcode files (with or without Arc-Welder) via OctoPrint can cause random problems. Printing non-IS gcode with the 5.0.0-alpha firmware from OctoPrint also has a higher success rate for me. To save time printing with IS -> use USB. 🙂
When I have several big prints that require settings that have no IS profile (different nozzle sizes or layer heights) I switch to the stable firmware to avoid problems with the 5.0.0-alpha firmware.

Opublikowany : 27/06/2023 9:23 am
Share: