From 6cabac15bb432e5469df4d11fa769a6a7caddcb4 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Oliver=20K=C3=B6ster?= <36196269+knutwurst@users.noreply.github.com> Date: Sat, 29 May 2021 13:41:29 +0200 Subject: [PATCH] Updated FAQ (english) (markdown) --- FAQ-(english).md | 80 +++++++++++++++++++++++++++--------------------- 1 file changed, 45 insertions(+), 35 deletions(-) diff --git a/FAQ-(english).md b/FAQ-(english).md index a49b1be..7d242bc 100644 --- a/FAQ-(english).md +++ b/FAQ-(english).md @@ -1,71 +1,81 @@ # Frequently asked questions (FAQ): -> My printer freezes/hangs. It does not display an error message. What should I do? +## My printer freezes/hangs. It does not display an error message. What should I do? -Connect a PC via USB and start [Pronterface](http://www.pronterface.com) or Octoprint. Start a print and look at the console output. The error message is displayed here. There is no point in troubleshooting without looking at the message in the console. Therefore, this should always be the first step when an error occurs. +>Connect a PC via USB and start [Pronterface](http://www.pronterface.com) or Octoprint. Start a print and look at the console output. The error message is displayed here. There is no point in troubleshooting without looking at the message in the console. Therefore, this should always be the first step when an error occurs. -> My printer stops when printing starts. When I run Pronterface / Octoprint and look at the console output, it says 'Error: XXXXXX failed, system stopped! Heater_ID: X Error: Printer halted. kill() called!'. That was not so before. +## My printer stops when printing starts. When I run Pronterface / Octoprint and look at the console output, it says 'Error: XXXXXX failed, system stopped! Heater_ID: X Error: Printer halted. kill() called!'. That was not so before. -This is the [Thermal Runaway Protection](https://help.prusa3d.com/en/article/thermal-runaway-temperature-drops_2131) from Marlin, which struck in. Your nozzle or bed (heater 0 is the nozzle) has not reached or maintained the correct temperature in the given time. This leads to an error. The original Firmware did not have TRP and thus could not stop the printer. There are many reasons for such an error. Most of the time it is simply because someone forgot to set the original component cooler in the slicer to 70% (see above). At 100% it now cools too much and since it blows straight against the nozzle, the temperature drops too much, which looks like a failure for the printer. Another possibility could be a wobbly or defective thermistor or heating cartridge. It is also possible that the new [PID controller](https://en.wikipedia.org/wiki/PID_controller) heats the heater a little too carefully. This can be remedied by the PID tuning in the special menu. It also makes sense to install a silicone sock for the hotend, as this protects the nozzle from drafts. +>This is the [Thermal Runaway Protection](https://help.prusa3d.com/en/article/thermal-runaway-temperature-drops_2131) from Marlin, which struck in. Your nozzle or bed (heater 0 is the nozzle) has not reached or maintained the correct temperature in the given time. This leads to an error. The original Firmware did not have TRP and thus could not stop the printer. There are many reasons for such an error. Most of the time it is simply because someone forgot to set the original component cooler in the slicer to 70% (see above). At 100% it now cools too much and since it blows straight against the nozzle, the temperature drops too much, which looks like a failure for the printer. Another possibility could be a wobbly or defective thermistor or heating cartridge. It is also possible that the new [PID controller](https://en.wikipedia.org/wiki/PID_controller) heats the heater a little too carefully. This can be remedied by the PID tuning in the special menu. It also makes sense to install a silicone sock for the hotend, as this protects the nozzle from drafts. ->Knutwurst, why do you also make such a firmware? Aren't there so many already? +## Knutwurst, why do you also make such a firmware? Aren't there so many already? -Because I haven't seen any that don't contain the stupid bugs, such as that it crashes if you have files with special characters on the SD card. +>Because I haven't seen any that don't contain the stupid bugs, such as that it crashes if you have files with special characters on the SD card. ->Is it correct that you place more emphasis on SD card printing and others more on USB? +## Is it correct that you place more emphasis on SD card printing and others more on USB? -I do not attach "more importance to SD", but have simply fixed the numerous bugs to that effect. The small adjustments with the USB buffer etc are included anyway. But in my opinion they are so uninteresting that I don't mention them, because the really complicated thing is to control the proprietary display and the card reader correctly. Everything else is easy. +>I do not attach "more importance to SD", but have simply fixed the numerous bugs to that effect. The small adjustments with the USB buffer etc are included anyway. But in my opinion they are so uninteresting that I don't mention them, because the really complicated thing is to control the proprietary display and the card reader correctly. Everything else is easy. ->What is this "slowdown"? +## What is this "slowdown"? -The automatic slowdown is activated if the printer does not get data fast enough. Then it automatically slows down to 50%, tired of going on unmolested and then jerking and causing blobs. +>The automatic slowdown is activated if the printer does not get data fast enough. Then it automatically slows down to 50%, tired of going on unmolested and then jerking and causing blobs. ->Why is my printer suddenly louder than before? +## Why is my printer suddenly louder than before? -Your component fan is now running at full speed, which it didn't before. Simply set the speed in the slicer (e.g. Cura) to 70% and you have the old volume again. This modification is necessary if you want to replace the fan and many fans with the original duty cycle do not run or run poorly. +>Your component fan is now running at full speed, which it didn't before. Simply set the speed in the slicer (e.g. Cura) to 70% and you have the old volume again. This modification is necessary if you want to replace the fan and many fans with the original duty cycle do not run or run poorly. ->Is your firmware better than others? +## Is your firmware better than others? -No. But certainly not worse either. +>No. But certainly not worse either. ->Where are the downloads? +## Where are the downloads? -Under "releases" on the main page. +>Under "releases" on the main page. ->Do I have to turn the plugs with TMC drivers? +## Do I have to turn the plugs with TMC drivers? -Nope. Just download the correct version. +> Nope. Just download the correct version. ->Which TMC2208 motor drivers should I buy? Do you prefer the V2 or the Bigtreetech V3? +## Which TMC2208 motor drivers should I buy? Do you prefer the V2 or the V3? -Neither! There is no "V2" or "V3". The official final version of Trinamic is v1.2 and the two major primary manufacturers for the real SilentStepSticks are FYSETC and WATTERROTT. Just keep your hands off Bigtreetech. +> Neither! There is no "V2" or "V3". The official final version of Trinamic is v1.2 and the two major primary manufacturers for the real SilentStepSticks are FYSETC and WATTERROTT. Just keep your hands off Bigtreetech. ->I turned the plugs on my motors when I installed the TMC drivers. Do I have to flash the TMC version anyway? +## I turned the plugs on my motors when I installed the TMC drivers. Do I have to flash the TMC version anyway? -No. Just use the non-TMC version, otherwise the motors will run in the wrong direction again. +>No. Just use the non-TMC version, otherwise the motors will run in the wrong direction again. ->When I installed the drivers, my mainboard smoked in the middle right. Is that normal? +## When I installed the drivers, my mainboard smoked in the middle right. Is that normal? -No. You installed the drivers the wrong way round. Now the Zener diode (733A) is burned. There is a [repair guide](https://github.com/knutwurst/Marlin-2-0-x-Anycubic-i3-MEGA-S/wiki/TMC2xxx-troubleshooting-and-mainboard-repair-instructions) for this purpose. +>No. You installed the drivers the wrong way round. Now the Zener diode (733A) is burned. There is a [repair guide](https://github.com/knutwurst/Marlin-2-0-x-Anycubic-i3-MEGA-S/wiki/TMC2xxx-troubleshooting-and-mainboard-repair-instructions) for this purpose. ->Do I have to set the E-Steps as with other firmwares if I have a Mega S? +## Do I have to set the E-Steps as with other firmwares if I have a Mega S? -No, just download the correct version. Nevertheless, you should still calibrate the steps. +>No, just download the correct version. Nevertheless, you should still calibrate the steps. ->The mesh leveling seems to have no effect or the nozzle scratches the heating bed +## 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. +>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. +## 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. +>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? +## 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. \ No newline at end of file +>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 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. + +>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. + +>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. \ No newline at end of file