this time I printed the calibration pyramid, and watched the extruider motor the entire time. It seemed like it simply got weaker up to about the middle of the print where it just stopped alltogether (including retraction). I took pictures of the results...
Today I tried printing some Gcobe that I spliced a few weeks ago (right after I finished building the um) and the issue is the same, which proves atleast that the gcode is not the problem.so if it is not the driver or the gcode that leaves the controller board or the motor it self
does anyone know if there is a way to test the motor with out switching it out?
how do I controll the second extruder slot via gcode?
You might try swapping your Pololu drivers to troubleshoot and see if that's the issue... Make sure you have completely disconnected the power before swapping them!
thanks for the suggestion, though I have allread tried that (see above). I wanted to switch the motors, but I notice that the extruder is not completely cicular, so that isnt an option :(
Recommended Posts
bob 0
Today I tried printing some Gcobe that I spliced a few weeks ago (right after I finished building the um) and the issue is the same, which proves atleast that the gcode is not the problem.
so if it is not the driver or the gcode that leaves the controller board or the motor it self
does anyone know if there is a way to test the motor with out switching it out?
how do I controll the second extruder slot via gcode?
Link to post
Share on other sites