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
2021-12-03 12:58:08 +01:00
parent 75fe3b4cf9
commit 4c83f3f1f3
1 changed files with 15 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
FAQ-(english).md

@@ -63,21 +63,21 @@
## Why does the display not show any error messages and why does it still look exactly the same as before? ## 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 ... >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 ...
>
>It looks different with your (and all other) touch display. The touch display is just a pretty presentation and internally translates the actual commands into something that the mainboard understands. It's just a "mask" for the actual firmware. >It looks different with your (and all other) touch display. The touch display is just a pretty presentation and internally translates the actual commands into something that the mainboard understands. It's just a "mask" for the actual firmware.
>
>There is a 1-to-1 mapping between the commands that the mainboard can implement (set temperature to value x, move motor 10 mm to the right, etc.). If you set the temperature in the display to 200 ° C, you are actually only sending a Gcode such as "M104 T1 S200", which must already be in the display. >There is a 1-to-1 mapping between the commands that the mainboard can implement (set temperature to value x, move motor 10 mm to the right, etc.). If you set the temperature in the display to 200 ° C, you are actually only sending a Gcode such as "M104 T1 S200", which must already be in the display.
>
>With this mapping, you have to rely on the functions you want to use also being available in the display. And unfortunately there isn't much in it. The file list is the only one (!) Over which you have some control, as it is displayed dynamically. Unfortunately, you have to accept these stupid quirks, such as the fact that after a confirmation / update the list is rebuilt and thus starts at the top. >With this mapping, you have to rely on the functions you want to use also being available in the display. And unfortunately there isn't much in it. The file list is the only one (!) Over which you have some control, as it is displayed dynamically. Unfortunately, you have to accept these stupid quirks, such as the fact that after a confirmation / update the list is rebuilt and thus starts at the top.
## I get layer shifts and/or the Extruder stop working after installing TMC2208 stepper drivers - HELP! ## I get layer shifts and/or the Extruder stop working after installing TMC2208 stepper drivers - HELP!
>This is a common problem when the motor drivers overheat or fail to deliver the required power to the motors at high temperatures. >This is a common problem when the motor drivers overheat or fail to deliver the required power to the motors at high temperatures.
>
>I generally recommend operating the TMC2208 with at least 1 volt Vref, otherwise layer shifts will occur. With the Y-axis you can go up to 1.3V, as more power is needed here. >I generally recommend operating the TMC2208 with at least 1 volt Vref, otherwise layer shifts will occur. With the Y-axis you can go up to 1.3V, as more power is needed here.
>
>These fan ducts with axial fans are also extremely counterproductive. Axial fans cannot build up air pressure (only radial fans can do that) and so the air suppresses itself. That is why a fan cools much worse than the original fan. As a result, TMC drivers can also overheat and layer shifts occur. >These fan ducts with axial fans are also extremely counterproductive. Axial fans cannot build up air pressure (only radial fans can do that) and so the air suppresses itself. That is why a fan cools much worse than the original fan. As a result, TMC drivers can also overheat and layer shifts occur.
>
>The fact that the layer shift always occurs in the same layer is simply due to the fact that at this very moment the bed has to change direction at an unfavorable angle and time and this is where too much power is being demanded from the motors. >The fact that the layer shift always occurs in the same layer is simply due to the fact that at this very moment the bed has to change direction at an unfavorable angle and time and this is where too much power is being demanded from the motors.
## When I start auto leveling with BLTouch, the nozzle rises, but then stops and a melody sounds. "**STOP called because of BLTouch error - restart with M999**" appears in the serial terminal. ## When I start auto leveling with BLTouch, the nozzle rises, but then stops and a melody sounds. "**STOP called because of BLTouch error - restart with M999**" appears in the serial terminal.
@@ -87,3 +87,11 @@
## When I auto-level with BLTouch, the first (or more) measuring point(s) is/are approached, but before the auto-leveling is completed, the nozzle stops and the message "**Error: BLTouch Probing Failed**" appears in the terminal. ## When I auto-level with BLTouch, the first (or more) measuring point(s) is/are approached, but before the auto-leveling is completed, the nozzle stops and the message "**Error: BLTouch Probing Failed**" appears in the terminal.
> This is a typical error if either the bed was manually leveled very imprecisely or if the Z-offset is incorrect. This error message is triggered by an excessive deviation between the measured value and Z=0. In this case, it helps to first level the bed with 4-Point-Easy-Leveling so that the nozzle lightly touches the bed at all 4 corners. If it is still not possible to take a complete measurement, the Z-offset must be readjusted, as it indicates the distance between the nozzle and the sensor when it is triggered. > This is a typical error if either the bed was manually leveled very imprecisely or if the Z-offset is incorrect. This error message is triggered by an excessive deviation between the measured value and Z=0. In this case, it helps to first level the bed with 4-Point-Easy-Leveling so that the nozzle lightly touches the bed at all 4 corners. If it is still not possible to take a complete measurement, the Z-offset must be readjusted, as it indicates the distance between the nozzle and the sensor when it is triggered.
## When I move the axes using the touchscreen, all end stops are ignored.
>Since Marlin 2.0 (Knutwurst Hybrid Firmware v1.0.1), the limit switches are only evaluated once when moving to the home position (G28) and then replaced by software endstops that prevent the nozzle from moving outside the specified ranges. Without prior homing, the position of the limit switches is unknown and there are only two options:
>1. Prohibit all movement until homing has been performed.
>2. Allow any movement outside of the end stops.
>
>I opted for the second option, because manual driving often means you know exactly what you are doing and can keep an eye on the nozzle. The prerequisite for homing would cause more problems if there is still a component on the print bed.