Re: Kossel 2020, possible auto level issue? August 01, 2015 02:07PM |
Registered: 9 years ago Posts: 606 |
Re: Kossel 2020, possible auto level issue? August 01, 2015 02:20PM |
Registered: 9 years ago Posts: 67 |
Re: Kossel 2020, possible auto level issue? August 01, 2015 02:55PM |
Registered: 9 years ago Posts: 606 |
Re: Kossel 2020, possible auto level issue? August 01, 2015 03:13PM |
Registered: 9 years ago Posts: 67 |
Quote
tadawson
You might be better served to try the spare driver first - motors are passive, and pretty hard to break . . .
Check DEFAULT_MAX_FEEDRATE as well as DEFAULT_STEPS_PER_UNIT for the extruder as well. Also note that Pronterface uses mm/*minute* for extruder speed, so you need a pretty big number to get much movement.
- Tim
Re: Kossel 2020, possible auto level issue? August 01, 2015 09:14PM |
Registered: 9 years ago Posts: 606 |
Re: Kossel 2020, possible auto level issue? August 02, 2015 07:33PM |
Registered: 9 years ago Posts: 67 |
Quote
tadawson
Pronterface can't directly control the towers - it just sends positions in X, Y, Z coordinates, and Marlin calculates the associated tower positions, and moves them accordingly. IE, for a Z move, all three should move vertically the same amount . . . if not, then either steps/mm for that tower or microstepping on it's driver is wrong.
And yes, the towers are referred to a X, Y, and Z, which is confusing, since they are not related to X, Y, and Z moves as sent in gcode via a job, Pronterface, or whatever . . .
- Tim