wp/Marlin-2-0-x-Anycubic-i3-MEGA-S
1
0
Fork 0
Code Issues 28 Pull Requests 2 Actions Packages Projects Releases 30 Wiki Activity

Updated FAQ (english) (markdown)

Oliver Köster
2022-02-08 14:34:34 +01:00
parent 552b4634f7
commit bbb8165a9d
1 changed files with 1 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
FAQ-(english).md

@@ -78,18 +78,10 @@
>This error always occurs when an _attempt_ is made to activate mesh bed leveling, but no valid mesh is stored in the firmware. Activation is done with `M420 S1` in the start code, but this requires that the mesh bed leveling has also been done beforehand. You can easily check this by typing `M503` into the console and looking for several G29 commands. With `G29 S0` you can display the current mesh.
>
>Alternatively, you can also delete the line `M420 S1` from the start code so that mesh leveling is deactivated. But then there is no compensation for unevenness in the bed.
>Alternatively, you can also add the line `M420 S0` to the start code so that mesh leveling is deactivated. But then there is no compensation for unevenness in the bed.
>
>OctoPrint likes to report "_The firmware of your printer has reported an error._" and aborts the print immediately.
## The mesh leveling seems to have no effect or the nozzle scratches the heating bed
>You have to enter in your start code that the mesh should be loaded and activated. You do this by entering the lines **M420 S1** after **G28** in your start code in the slicer.
## I have M420 S1 in the startup code, but when I try to print an old gcode the printer ignores the mesh leveling.
>You have already answered the question yourself: You are using an _old_ gcode file that does not contain the M420 S1 code. Therefore the mesh is ignored. Either you open the file in an editor like Sublime or you have to reslice it.
## Why does the display not show any error messages and why does it still look exactly the same as before?
>Your mainboard (Trigorilla) can only control graphic displays like the 2004 or 12864. On them you would also see exactly what is really going on in the firmware - precisely because they show what the firmware says. Texts, error messages etc ...