Problems with Duet 3 Mini 5+ WiFi
-
@phaedrux Is that why I'm getting an error?
-
Do you have motors connected to all of the drivers when you test?
What is the exact error you're getting?
-
I see you have sensorless homing set for X and Y. Do you have endstop switches as well? That can simplify things during initial setup.
-
@phaedrux I have senseless homing set in the config but not calibrated. 8 don't have any endstop switches.
-
@unforgivenll G1 H2 X10 makes the motor lock up and whine.
-
Ok, so sensorless homing is going to take some configuring to get working. I would suggest that you put that off until you've done some more testing and commissioning.
You can also force the axis to be homed by sending
G92 X0 Y0 Z0for example which would make the firmware think that the current position is at the low end for each axis. This can be useful for testing.Basically we need to test movement without homing (or sensorless homing in this case)
The same can be done by using G1 H2 commands to ignore the homed state and just move the motor.
Do you get the errors when trying those means of moving the motor?
-
M906 X650 Y650 Z650 E650 I30 ; set motor currents (mA) and motor idle factor in per centAre your motor currents set correctly for the motors?
Aim to set M906 to ~60% to 80% of the max rated for the motor.
-
@phaedrux The extruder seems to work perfectly (LGX). The max current on the sheet says 0.65 a. I hope the whole build doesn't go like this.
-
@unforgivenll the extruder is on the tool board (If that's means anything.)
-
@unforgivenll said in Problems with Duet 3 Mini 5+ WiFi:
The max current on the sheet says 0.65 a
That's the Moons motor whose data sheet you posted earlier?
If they are max 650ma and you have the current set to 650ma in M906 you're giving them 100% power. An easy way to test finding the right current is to add an M913 command after your M906. M913 is used to alter the motor current by a percentage. For example:
M906 X650 Y650 Z650 M913 X60 Y60 Z60Would reduce the current to 60% of the rated max, which is a good value to start with.
Do you have other motors to test with or are they all the same?
Have you tried the extruder motor on the main board? What max current does it take?
When you change motors make sure you're also updating the config to match the settings they need. In this case the extruder motor seems to work and will take 650ma so you should be safe to try it on X and Y. Just make sure to power off before unplugging.
-
@phaedrux The extruder is mounted and wired already. I bought 4 Moons motors as I plan to have dual Z, one on EO on the mainboard (A problem I'll have in the future I'm sure.). So 390ma for the motors? That's not too low?
-
@unforgivenll The Extruder is a different (LDO) motor and wired differently.
-
@unforgivenll said in Problems with Duet 3 Mini 5+ WiFi:
So 390ma for the motors? That's not too low?
Test it and find out.
650ma seems very low to begin with. How did you determine these motors were suitable in the first place? The rated inductance values from that sheet is very high. 15mH It's not recommended to use motors with an inductance above 4mH
https://docs.duet3d.com/en/User_manual/Connecting_hardware/Motors_choosing
I think the phase errors are due to back EMF already exceeding the supply voltage even at low homing speeds.
Can you try this command?
G1 H2 X10 F600
That is a much slower move than the default F6000 and it may be able to complete it.
-
@phaedrux They were recommended for my original printer. I basically rebuilt my Tevo Tornado. There isn't anything original left on it except the extrusion.
-
@unforgivenll Tried the new settings and the same thing happens. The motor just whines.
-
What voltage is your power supply?
-
Did you try that lower speed command?
-
@phaedrux I did try that and it didn't work. I tried my old Tevo motor at 850ma. It worked fine. The $200 worth of Moons motors are literally days old. I did see a discussion somewhere where they might have an incompatibility with the steppers. I think it was Stealth Chop in particular. I have no idea how to test that. I'm not an expert by any means but I generally make my way through electronics projects just fine. This is maybe the 3rd or fourth time asking for help ever. I'm just not having much positive movement with this Duet build. I'm not blaming anything, or anyone. It's probably my fault. Just putting it out there.
-
I believe they should be in spread cycle by default instead of stealthchop but we can force it by adding
D2to the M569 command for X Y Z.M569 P0.0 S1 ; physical drive 0.0 goes forwards M569 P0.1 S1 ; physical drive 0.1 goes forwards M569 P0.2 S1 ; physical drive 0.2 goes forwardsAdd the D2 after the S1
-
@phaedrux Unfortunately it didn't change anything.
