Z axis wont home

dc42

Does the red LED on the sensor light up when the sensor is triggered i.e. close to the bed, and stay off otherwise? If yes and you are getting those readings around 900 then that suggests a faulty connection between the sensor output pin and the Duet.

elmoret

Just FYI David, I think he's using an Aus3D sensor.

elmoret

Brian, you are not configuring properly for a Z-endstop:

M574 Z0 S0 ; Define active low and unused microswitches no need for this so have changed Z1 to Z0 to indicate no endstop
M574 X1 Y1 S1 ; Define active high microswitches

That does not set up a Z-endstop in firmware. You'd need to get rid of the first line and change the second line to:

M574 X1 Y1 Z1 S1 ; Define active high microswitches

Assuming all three endstops are active high.

Please do that and re-run the M119 tests.

brian

@dc42:

Does the red LED on the sensor light up when the sensor is triggered i.e. close to the bed, and stay off otherwise? If yes and you are getting those readings around 900 then that suggests a faulty connection between the sensor output pin and the Duet.

No it doesnt. It flashes twice on start up only.

dc42

That's not right. If you have connected it correctly then it should flash 4 times at startup. Perhaps you have connected the sensor output wire to the MOD pin of the Z probe connector instead of to the IN pin?

brian

Z-endstop engaged = @ not stopped * this changed
Z-endstop released = @ min stop
Z-probe activated (bed close enough to trigger it) = @ min stop
Z-probe released (bed far enough away to not trigger it) = @ min stop

brian

@dc42:

That's not right. If you have connected it correctly then it should flash 4 times at startup. Perhaps you have connected the sensor output wire to the MOD pin of the Z probe connector instead of to the IN pin?

I've connected sensor duetwifi
power to 3.3v
grnd to mod
–-- grnd
analogue probe in

Looks like i've got Grnd on sensor going to Mod on duet.

elmoret

@brian:

Z-endstop engaged = @ not stopped * this changed
Z-endstop released = @ min stop
Z-probe activated (bed close enough to trigger it) = @ min stop
Z-probe released (bed far enough away to not trigger it) = @ min stop

This is a step in the right direction, but it seems as though that switch is active low, not active high. I assumed all three endstop switches were the same but is seems that is not the case. Try changing this:

M574 X1 Y1 Z1 S1 ; Define active high microswitches

to:

M574 Z1 S0 ; Define active low microswitches
M574 X1 Y1 S1 ; Define active high microswitches

That should set the firmware up to expect an active low microswitch on Z. The above code also assumes your endstop is at the Z-minimum, if it is at the Z-maximum then change to Z2 instead of Z1.

dc42

Tim, thanks for that. Brian, you had better talk to aus3d if you are using their sensor. It's my sensor (also so!d by Duet3D and Filastruder) that should flash 4 times at startup when connected to a Duet.

brian

@dc42:

Tim, thanks for that. Brian, you had better talk to aus3d if you are using their sensor. It's my sensor (also so!d by Duet3D and Filastruder) that should flash 4 times at startup when connected to a Duet.

I think i have found the error, as i've mount the duet upside down, and with small print its hard to see clearly. I'll check until i'm convinced i see it right.

brian

I changed the ground on the sensor to the next position on the duet .

It still only flashes twice on start up, but when bed approches the sensor a red led lights up until bed is moved away.

brian

Now the home z only moves the bed down a bit, but the home all works!!!

brian

Finally got the z probe offset to work, it resisted a lot, but is good now.

Just want to thank dc42, elmoret, and CaLviNx for getting me thru this.

fcwilt

Just love a happy ending.

Frederick