Duet 3 mini 5+ sensorless homing will not work
-
@Veti did you even look in the homeX? if you did you will see i have 100.
-
only on one axis.
you have a corexy where 2 motors are involved -
@Veti changedf still no dice. After i run the homex macro it for some reason go to y home. Which it should not do acording to homex.
-
Why is is so dam hard? It took me 2 minutes to set this crap up ion a duet wifi. Here is a video and a new homeall file. Why does it do like it does? It even goes the wrong way on Y axis. Something is wrong cause it wont matter if is et motor current % to 1 or 100. makes no difference.
-
@droftarts does not tell me a dam thing sadly. I am soon to give up on this board and throw in my duet 2 card in it again. I bought 2 cards and will just sell this and use the other with endstops in my voron.
-
Sensorless homing is literally just listening to the driver for a backEMF spike caused when the motor is unable to move anymore. The key to sensorless homing is finding the lowest motor current that still provides reliable movement, and using a speed fast enough to generate a strong backEMF spike. It's also compounded in a corexy belt arrangement by the belt stretch, so try and choose your location to stall the print head such that the belt length back to the motor is as direct as possible.
In your homex you have only dropped the current to 90% and you're only dropping the X motor. In a corexy both motors are involved in movement, so drop both.
M913 X90 ; drop motor current to 90%
First step will be to find how long you can drop the motor current and still have the axis move. That could be 30 or 40%
G1 H2 Z5 F1200 ; lift Z G1 H1 X-255 F2500 ; move quickly to X axis endstop and stop there (first pass) G1 X5 F1200 ; go back a few mm G1 H1 X-10 F2500 ; move slowly to X axis endstop once more (second pass) G1 X10 F1200 ; go back a few mm G1 H2 Z-5 F1200 ; lower Z M400 ; wait for current moves to finishNext, since you're using a hard stall as the endstop, you don't need to back off slowly and approach again for more accuracy. That's only relevant for endstop switches. I would increase the homing speed on the first move and that's it. Remove the other moves entirely.
-
@Phaedrux read the updated homeall instead. I tried 1% and it still moves. It will not accept M913. Also have a look at the video.
-
So you're saying you have sent the commands M913 X1 Y1 and are still able to move the motors by jogging?
-
@Phaedrux I have tried mah between 400-1400. I used to run at 900mah on my old duet card. I tried M915 s-64 to 64 no difference. M569 V1 and numbers in-between to 2000 no difference. Always behaves like in the video i posted. If i force stop it with my hand it wont detect anything either.
So il take back my old card and throw this in a box or sell it cause i spent over 8hours on it today and gotten no where..here is the cleaned up homeall homeall (1).g
-
@Alucardi said in Duet 3 mini can't configure sensorless homing + missing extruder:
So il take back my old card and throw this in a box or sell it cause i spent over 8hours on it today and gotten no where..
Alright. Take a banana break and when you want to take another crack at it come on back.
-
@Phaedrux if yo have anything to help please tell me. I Dont know what to do. Issue is that it does not detect the stall it just sits there.
-
Well let's start with finding the motor current limits.
Here's how I do it.
Set M906 to the rated max of the motor. In my case M906 X2000 Y2000.
Then I use M913 to reduce it to whatever I need it to be for regular usage. 85% for printing, 50% for homing. 20% for idle, etc. That way I know that the M913 percentage is the percentage of the motor max current.Do all of this with no M915 active.
So start with 85% current and jog the print head around. Reduce it to 70% and jog around, 60% and jog around, 50, 40, 30, 20, 10, 5. At some point in there your motors won't move. When you find that point increase the M913 by 1% until it moves again reliably.
Now that you've found the lowest current needed to have the motors move you can use that amount for sensorless homing and the motors should stall quite easily when blocked.
Once you have that the rest should get easier.
https://forum.duet3d.com/topic/20622/duet-3-mini-5-sensorless-homing-configuration/3?_=1610961629552
This thread has some valuable and specific information on sensorless homing with the mini5+. It's worth reading.
-
@Phaedrux I have read that thread a million times and still don't understand. I found out that 303 mah works. But still no dice. Sensitivity is -64 which is as sensitive as it goes and will NOT work, i tried 3.3 which i had before but wont work. It detects a stop after a while i think but it is not working as it should, i get error But the then i get error "G28
Error: Insufficient axes homed for bed probing
Error: G0/G1: insufficient axes homed"
So either i have a broken card, a card that will not work with my steppers even though a duet wifi did or i am missing something else. Just to prove it il add a video.
video -
Of the million times did you catch this post?
You need to run the stealthChop tuning procedure first. You can do this is the homing files.This is what I suggest:
Execute a tiny move (1 or 2 microsteps) away from the homing direction.
Pause for 100ms using G4.
Execute a small move away from the homing direction, e.g. 10mm.
Execute the homing move.
Don't forget to reduce current for the homing move (M913). -
@Phaedrux i must be stupid but i don't understand it and others that have gotten it to work do NOT have that in their homeall.
-
@Phaedrux Figured it out but no affect.
M400 ; finishes all current moves and and thus clears the buffer M913 X34 Y34 ; drop motor current to 33% M569 P0.0 P0.1 D3 V100 ; reduce V to ensure stealthChop is enabled M915 P0.0 P0.1 S-64 R0 F0 H400 ; sensitivity, don’t take action, don’t filter M400 ; finishes all current moves and and thus clears the buffer G91 ; relative positioning G1 H2 Z10 F6000 ; lift Z relative to current position G1 H1 X0.1 G4 P100 G1 H1 X20 G1 H1 X-335 F7000 ; move to X G1 H1 Y0.1 G4 P100 G1 H1 Y20 G1 H1 Y-348 F7000 ; move to Y G30 P0 G1 X167.5 Y167.5 ; home Z by probing the bed G90 ; absolute positioning M400 ; finishes all current moves and and thus clears the buffer M569 P0.0 P0.1 D2 ; restore default for motor M913 X100 Y100 ; return current to 100% M400 ; finishes all current moves and and thus clears the buffer -
I don't have my mini5 in a corexy and I use endstops in the cartesian I do have it in, but I can go through setting it up and I can see if I hit any sticking points.
CoreXY is going to be different, but hopefully it's not a deal breaker.
@Alucardi said in Duet 3 mini can't configure sensorless homing + missing extruder:
i must be stupid
Do you need another banana break? Don't despair.
-
@Phaedrux why does this not work? is it cause other drivers cause it worked fine on my wifi. I need the printer but i wont redesign it for endstops. So if I cannot get this to work before end of this week il make sure to post a video on how to set fire to a mini 5+ lol (that isa promise)
Also i do believe something is broken since it will NOT detect a stall even if i pick -64. -
played around with different move types and all i could find. Still no go.
M400 ; finishes all current moves and and thus clears the buffer M913 X50 Y34 ; drop motor current to 33% M569 P0.0 D3 V60 ; reduce V to ensure stealthChop is enabled M569 P0.1 D3 V60 ; reduce V to ensure stealthChop is enabled M915 P0.0 S-54 R0 F0 H400 ; sensitivity X, don’t take action, don’t filter M915 P0.1 S30 R0 F0 H400 ; sensitivity Y, don’t take action, don’t filter M400 ; finishes all current moves and and thus clears the buffer G91 ; relative positioning G1 H2 Z10 F6000 ; lift Z relative to current position G1 H2 X1 G4 P200 G1 H2 X20 F8000 G1 H3X-335 F7000 ; move to X G1 H2 X5 F7000 G1 H2 Y1 G4 P200 G1 H2 Y20 F8000 G1 H3 Y-348 F7000 ; move to Y G30 P0 G1 X167.5 Y167.5 ; home Z by probing the bed G90 ; absolute positioning M400 ; finishes all current moves and and thus clears the buffer M569 P0.0 P0.1 D2 ; restore default for motor M913 X100 Y100 ; return current to 100% M400 ; finishes all current moves and and thus clears the buffer -
@Alucardi I realize this sounds like madness, but can you try setting the stall detection threshold to +63 (so S63 on the M915 for both motors) and see if it detects the stall then.
