13-18 code with no sensor trip?

Snapmaker Artisan
1

Has anyone narrowed down these random 13-18’s and 13-12’s that occur when there is no tension on the filament and the sensor is not being pulled up?

For example it will throw a 13-18 after a successful purge as the gantry is starting to head downward but the nozzle hasn’t even reached the bed.

How would one test the sensor to see if it is bad?

Are there certain firmware versions that are known to have this problem?

Thanks

2

Have a look at the wiki page, have you done anything to avoid it so far?
https://wiki.snapmaker.com/en/snapmaker_artisan/troubleshooting/error_code_13-12_13-18

3

the wiki page mentions nothing about the code being thrown randomly for no reason. I’m not sure what I can do to avoid that besides replacing a sensor that they do not sell, and/or downgrading firmware.

4

If you need a sensor, shoot a ticket by emailing to support@snapmaker.com or
https://snapmaker.formcrafts.com/support-ticket

You could also disable the runout sensor by

  • Disable filament runout detection.
M412 S0

Or see the runout status by

M412

https://wiki.snapmaker.com/en/Snapmaker_Luban/manual/artisan_supported_gcode_references

5

thank you for trying to assist me :slight_smile:

what is the correlation between the runout sensor and the calibration sensor? why would disabling the runout help prevent 13-18’s?

6

Sorry I missed that, I thought it’s about runout…

Anyway, you should be able to adjust the sensor as written in the wiki:
The purpose of adjusting the leveling plate’s position is to reduce its sensitivity and minimize the chances of receiving error messages about the extruders being pulled up.

If you are in warranty, reach out to support and let us know what they suggest.

7

I have been dealing with these errors. The steps that have helped me the most so far are:

  1. Use the printable in the wiki to print roller bearings for the filament spools.
  2. The documentation says more or less nothing about how to install the bowden tubes that I could find (not hard to miss things since the docs are scattered all over between videos and documents). Make sure that the bowden tube is extended relatively close to the spool. Mine was too far and it caused excess tension.
  3. Flip the spools so that as they turn, the filament is angled towards the tube. The documentation says “clockwise” which doesn’t really make sense given it causes it to be almost a 90 degree angle to what the tube’s natural curve is.
  4. Unload the filament, and then reload it.
  5. Run an auto bed level set to 9x9 rather than the default 5x5.
  6. Switch from the PEI textured glass plate to the smooth glass plate.

Together all of this helped me a bit. I was consistently getting 13-18 errors, and after switching to new filament, i kept getting 13-12 which would flash for a moment before the 13-18 error popped up.

1 Like
8

Thank you. Are you referring to adjusting the sensor by following the short that shows to use tweezers to create a gap? I find that video to be completely useless since the gap gets closed the second you retighten the screws, as the holes are too tight of a tolerance with the screws. You literally have to make the round holes oblong with a small round file or endmill if you want the gap to remain after you retighten.

9

I eliminated all the bowden tubing completely so that’s not even a factor. The sensor requires approximately 9.4N of force pulling up on the filament to trip and my filament requires less than 1N to pull into the extruder, so it’s definitely not that.

4, 5, and 6 did seem to help, but the complete randomness of this (works fine sometimes, is 5mm high other times, and throws the code sometimes before the thing ever moves) would lead me to believe that the board that reads the sensor is defective, because I believe it is a simple binary photoelectric sensor that is incapable of complex data (such as some other pressure sensors that may give a variable value). It is essentially a photoelectric momentary switch; I’m not sure how that could go bad and be responsible for such randomness in its error throws- I would think it would fail completely or not at all. Right?

Thanks!