You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you are using an Original Prusa printer, there is a possible issue in the firmware 3.0.12 (linear advance update) that causes lock-ups and, in the very worst case, out of order gcode execution when using Octolapse. I don't recommend using octoprint whith linear advance enabled for the time being.
I've been albe to work around this bug by by avoiding the Linear Advance profile within Slic3r prusa edition. I'm not sure if it's necessary, but I also changed the custom filament gcode found in Filament Settings->Custom G-Code to: M900 K0
I've heard that this bug has been fixed for the Mk3 in the latest release candidate firmware. See the release notes.
The text was updated successfully, but these errors were encountered:
@Sebastianv650 has released a fix for this bug!! Not only is it a fix, but I consider it an upgrade. I hope I can get around to testing this update soon on my mmu. Here is a link. MAKE SURE you read the docs, since your K values MUST CHANGE. The k values now actually make sense! Thanks @Sebastianv650 ! I can't wait to use LA again, this time without all that extruder grinding!
If you are using an Original Prusa printer, there is a possible issue in the firmware 3.0.12 (linear advance update) that causes lock-ups and, in the very worst case, out of order gcode execution when using Octolapse. I don't recommend using octoprint whith linear advance enabled for the time being.
I've been albe to work around this bug by by avoiding the Linear Advance profile within Slic3r prusa edition. I'm not sure if it's necessary, but I also changed the custom filament gcode found in Filament Settings->Custom G-Code to: M900 K0
I've heard that this bug has been fixed for the Mk3 in the latest release candidate firmware. See the release notes.
The text was updated successfully, but these errors were encountered: