Stepper motor Noob Here
-
Noob here.
I just bought a DuetEth and all e3d steppers. On the website for each motor, it says 1.68A Phase. Does that mean the motor current should be set to 1680ma on the duet? I am just trying to test the motors at the default 1000ma, and the Duet keeps giving me an error about not homed. When I try to use GCode, I get an error (javascript, disconnected from duet to protect it self).
I am not sure if the wrong mA set is related to the errors, but I just want to move the corexy a few mm to make sure they are working. Still working on a proper mounting method for my optical end stops...Thanks!
-
The maximum realistic current you want to run the motor at is going to be more like 70-80% of what the motor is rated for. You want to make sure in addition to this the motor is not getting too hot, and in general that your drivers are capable of this. Its pretty common to run stepper motors well below their rated current, so you could consider going lower if they are performing well.
-
As @Emily says. 60 to 85% of rated motor current is common. If the motors are attached to the frame using printed PLA parts, you need to be careful that the motors don't get hot enough to soften the PLA.
-
@bluedust said in Stepper motor Noob Here:
Noob here.
..................... the Duet keeps giving me an error about not homed. ....................Thanks!
Use M564 H0 https://duet3d.dozuki.com/Wiki/GCode#Section_M564_Limit_axes. This will allow axis movement before the axes have been homed. But use with care because until the axes have been homed, there is nothing to stop them trying to move beyond their physical limits.
-
@deckingman
Thanks
Most G code I send to the printer gives me this error as did M564 S0 H0. I don't have a USB cable long enough to reach the printer right now to try and use a terminal emulator.
Any ideas?
Thank you all for your help!
-
Incase this helps with the above error... This is what my DuetEth is running on.
-
@bluedust said in Stepper motor Noob Here:
M564 S0 H0
I figured it out... I don't know what specifically caused the Gcode problems I have been having but I ran through the Gcode auto config tool again, and now it works. Thanks for your help guys! I really appreciate it!
-
@bluedust If JavaScript Error reappears go to
Settings -> List Itemsand delete every entry underDefault G-Codesthen hitApply Settingsand it should be working again.There is a bug in DWC that has been fixed in the latest version but this version is currently only fully compatible with the latest Beta version of RepRapFirmware.
-
Please try to upgrade to Duet Web Control 1.22.2: https://github.com/chrishamm/DuetWebControl/releases This version fixes the issue you're experiencing. Alternatively, as wilriker said, try to click on "Apply Settings" to restore the correct data type.
-
Thanks guys!