z motor not driving when connected to leadscrew
-
@Ian-Miller said in z motor not driving when connected to leadscrew:
Each motor is only rated to 0.33 amps.
Those are quite small motors. How much does the gantry weigh? How much compliance is there in the gantry? When they aren't perfectly even they are likely binding a bit and the motors aren't very powerful. I think they may not be suitable for your Z axis. Do you have the specs for them?
-
I tried wiring them in parallel and now neither motor activates whatsoever, but I will work on that.
As for the motor specs I will post them below. The entire gantry the 2 motors are lifting is between 2.5 and 3 pounds.
-
I can't make anything out on that blurry image.
-
are you aware that you have bought a cloned board?
those motors are not suitable for 3d printers
https://images-na.ssl-images-amazon.com/images/I/A1N+z7VtiNL.pdf
see
https://duet3d.dozuki.com/Wiki/Choosing_and_connecting_stepper_motorsAvoid motors with rated voltage (or product of rated current and phase resistance) > 4V or inductance > 4mH.
-
I did not realize that those motors were not ok with 3d printers, I'm using them for driving every other axis on this machine and they all 5 seem to be working well. Do you recommend I just get new motors for that axis or is there anything else I can try?
Btw thank you guys for all the tips and ideas, I'm only 15 and this is my first fully custom printer build.
-
@Ian-Miller said in z motor not driving when connected to leadscrew:
M350 X16 Y16:16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X80.00 Y80.00:80.00 Z1600.00 E420.00 ; set steps per mm
M566 X900.00 Y900.00:900.00 Z60.00 E120.00 ; set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00:600.00 Z180.00 E1200.00 ; set maximum speeds (mm/min)
M201 X500.00 Y500.00:500.00 Z20.00 E250.00 ; set accelerations (mm/s^2)
M906 X800 Y800:800 Z800 E800 I30 ; set motor currents (mA) and motor idle factor in per centthis is incorrect, y does not allow for double settings.
delete the second y entry.
also if your motors are 0.33A you are running them with 0.8A, you might have damaged to motors.
-
I would be reluctant to use those motors. Return them if you can. They may be alright for the other axis at low speeds, but the weight of the Z axis is likely a problem for them.
https://duet3d.dozuki.com/Wiki/Choosing_and_connecting_stepper_motors
Use that link for choosing motors to try and determine what you need.Here's a filtered search result that has some good options. Determine if you want/need 0.9 degree motors and how much torque.
-
I'm using 4 of them on the y and 1 on the x and they are providing plenty of power and seem to be accurate. It was only 30$ for 10 so its not a big deal to get new motors. And here is the latest version of the config for those who were concerned with errors.
; Drives
M569 P0 S1 ; physical drive 0 goes forwards
M569 P1 S1 ; physical drive 1 goes forwards
M569 P2 S0 ; physical drive 2 goes forwards
M569 P3 S0 ; physical drive 3 goes forwards
M569 p4 s1
M584 X0 Y1 Z2 ; set drive mapping
M584 E3:4
M92 X80 Y80 Z400
M92 E429.85:99 ; Set steps per mm
M350 X16 Y16 Z16 E16:16 I1 ; configure microstepping with interpolation
M566 X1200 Y1200 Z24 E300 ; Set maximum instantaneous speed changes (mm/min)
M203 X30000 Y30000 Z600 E3000:3000 ; Set maximum speeds (mm/min)
M201 X500 Y500 Z100 E25:250 ; Set accelerations (mm/s^2)
M906 X800 Y800 Z800 E800:800 I30 ; Set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout ; Set idle timeout; Axis Limits
M208 X0 Y0 Z0 S1 ; set axis minima
M208 X300 Y300 Z360 S0 ; set axis maxima; Endstops
M574 X1 Y1 Z1 S1 ; Define active high microswitches
M558 P5 H5 F500 T4000 X0 Y0 Z1 ; Set Z probe type/mode 5. Not using on XY, but using it on Z.
G31 P25 X29 Y-23 Z2.45 ; Z probe trigger value, offset in relation to nozzle. And trigger height adjustment
M557 x50:250 Y50:250 s30
; BLTouch - Heaters
M307 H7 A-1 C-1 D-1 ; Disable the 7th Heater to free up PWM channel 5 on the Duex bo; Heaters
M143 S265 ; Set maximum heater temperature to 265C
M305 P0 T100000 B4138 C0 R4700 ; Set thermistor + ADC parameters for heater 0
M305 P1 T100000 B4138 C0 R4700 ; Set thermistor + ADC parameters for heater 1
M305 P2 T100000 B4138 C0 R4700; Fans
M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency
M106 P0 C"Controll box fan" S1 ; set fan 0 name and value. Thermostatic control is turned off
M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency
M106 P1 C"Extruder fans" S1 H1:2 T45 ; set fan 1 name and value. Thermostatic control is turned on
M950 F2 C"fan2" Q500 ; create fan 2 on pin fan2 and set its frequency
M106 P2 C"Part cooling fans" S1 H1:2 T45 ; set fan 2 name and value. Thermostatic control is turned off; Tools
M563 P0 S"Hotend 0" D0 H2 F2 ; define tool 0
G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets
G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C
M563 P1 S"Hotend 1" D1 H1 F2 ; define tool 1
G10 P1 X23.2 Y0 Z0 ; set tool 1 axis offsets
G10 P1 R0 S0 ; set initial tool 1 active and standby temperatures to 0C; Custom settings
m552 s1 -
-
stepper online sells good steppers.
they are both used in the blv design.
https://www.blvprojects.com/blv-mgn-cube-3d-printer
and the voron 2.4
https://vorondesign.com/sourcing_guide?model=V2.4M305 P0 T100000 B4138 C0 R4700 ; Set thermistor + ADC parameters for heater 0
M305 P1 T100000 B4138 C0 R4700 ; Set thermistor + ADC parameters for heater 1
M305 P2 T100000 B4138 C0 R4700your thermistor config is wrong. find the correct beta value in your thermistor documentation.
-
@Ian-Miller said in z motor not driving when connected to leadscrew:
Do you think these motors would be good?
https://www.amazon.com/RTELLIGENT-Stepper-Bipolar-42x42x38mm-42A02C-Dupont/dp/B0817T5SRH/ref=sr_1_17?dchild=1&keywords=42x42x40%2Bmm%2Bnema%2Bmotor&qid=1609188975&sr=8-17&th=1Those would be more suitable, yes. But it's hard to say what you really get from amazon and below.
It can help to try and understand what kinds of speeds and accelerations you hope to attain and how much mass you're going to be moving around. This would also be a good time to learn how stepper motors work. A little bit of knowledge now will go a long way to avoiding disappointment and frustrations later. Though that's a good way to learn too.
-
@Ian-Miller said in z motor not driving when connected to leadscrew:
I'm using 4 of them on the y and 1 on the x
if the link from Veti is the same motors then they have a very high inductance, which will severely limit the speed you can operate at with a 12v supply, and this becomes a bigger problem when you have two in series on the Z driver .. which explains the error "motor phase A may be disconnected"
You'd probably want to take Phaedrux's advice and concider replacing them, but you could lower the current a little and/or increase the 12v supply (but that might create issues with heaters) and also reduce the speed, jerk and acceleration to try to make them work.
-
@Phaedrux since they are driving leadscrews that are holding a gantry that is about 3 pounds they need to be relatively strong but don't need to be extremely fast. I will pick up some new motors from stepperonline. Thanks for all your help guys.
-
I picked up the new steppers and wired them up to the board. When I try to run them they just seem to be vibrating whether under load or not. When I use the provided jst connectors and run the motor there is nothing at all but when I use the setup for the previous motors they just vibrate. I'm pretty sure this is a wring issue but I'm not exactly sure what it is. I have them set to 1.5 amps witch is their rated current and they are wired in parallel to a single set of pins.
-
-
I checked using a multimeter that the pins on the motor were ABAB and wired to the board as AABB. But I'm getting no response whatsoever from the motor. I have tested at both 0.8 and 1.5 amps and also I am running just a single motor to test with no load. The motor doesn't even activate and can be easily turned by hand.
When the motor was vibrating and also not keeping its position while idle, it was wired ABAB on the board. -
Are you getting any errors from the Duet after wiring them correctly? unfortunately incorrectly wiring can potentially destroy the drivers.
-
Can you post the results of M122 after trying to move the motor?
Do you get any errors in the console?
-
@Phaedrux no errors in the console
m122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.03beta3 running on Duet WiFi 1.02 or later
Board ID: 0JD0M-9P61A-J8PSJ-6J9F6-3S06R-KUQ2S
Used output buffers: 1 of 20 (17 max)
=== RTOS ===
Static ram: 25632
Dynamic ram: 93800 of which 0 recycled
Exception stack ram used: 412
Never used ram: 11228
Tasks: NETWORK(ready,652) HEAT(blocked,1236) MAIN(running,3816) IDLE(ready,196)
Owned mutexes:
=== Platform ===
Last reset 00:01:10 ago, cause: software
Last software reset time unknown, reason: User, spinning module GCodes, available RAM 11264 bytes (slot 3)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 89.5ms, max retries 0
MCU temperature: min 34.9, current 35.2, max 35.4
Supply voltage: min 12.0, current 12.1, max 12.2, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, SG min/max 421/873
Driver 1: standstill, SG min/max not available
Driver 2: standstill, SG min/max 0/5
Driver 3: standstill, SG min/max not available
Driver 4: standstill, SG min/max not available
Date/time: 1970-01-01 00:00:00
Cache data hit count 244424298
Slowest loop: 2.08ms; fastest: 0.08ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0
=== Move ===
Hiccups: 0, FreeDm: 169, MinFreeDm: 168, MaxWait: 64222ms
Bed compensation in use: none
Bed probe heights: 0.000 0.000 0.000 0.000 0.000
=== MainDDARing ===
Scheduled moves: 5, completed moves: 5, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== AuxDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
=== GCodes ===
Segments left: 0, aux move: no
Stack records: 1 allocated, 0 in use
Movement lock held by null
http is idle in state(s) 0
telnet is idle in state(s) 0
file is idle in state(s) 0
serial is idle in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty. -
@bearer is there a certain reason that that would occur? also how does it destroy the drivers?