X Endstop not being recognized

[BearcatTD]

Do I connect the multi to the switch like this?

(https://www.dropbox.com/s/z9etrgwa4jn8gkp/IMG_3410.jpg?dl=0)

[fcwilt]

Hi,

Are you sure you as using active high devices?

Please post you X axis homing file.

Frederick

[BearcatTD]

; homex.g
; called to home the X axis
;
; generated by RepRapFirmware Configuration Tool on Sat Sep 29 2018 12:21:45 GMT-0700 (Pacific Daylight Time)
G91 ; relative positioning
G1 Z2.5 F6000 S2 ; lift Z relative to current position
G1 S1 X-269 F1800 ; move quickly to X axis endstop and stop there (first pass)
G1 X5 F6000 ; go back a few mm
G1 S1 X-269 F360 ; move slowly to X axis endstop once more (second pass)
G1 Z-2.5 F6000 S2 ; lower Z again
G90 ; absolute positioning

[A Former User]

to verify if the firmware registers the endstops use the M119 command with the endstop triggerend and untriggered.

[fcwilt]

@BearcatTD

Your homing file looks ok but note that later versions of firmware are using H instead of S - check the documentation for the details.

Are you really using firmware 1.21 as mentioned in the config file?

And you are using active high end stop devices?

Thanks.

Frederick

[BearcatTD]

@bearer

This is what is returned for both triggered and untriggered.

Endstops - X: not stopped, Y: at min stop, Z: not stopped, Z probe: not stopped

[BearcatTD]

@fcwilt

Firmware: 2.04RC3 (2019-10-08b3)

How do I tell if I am using active high end stop devices. These are whatever came stock on the Ender.

Thanks!

[A Former User]

@BearcatTD so you get the same output when you run M119 while the endstop is triggered and not triggered? I.e. hold the switch while running M119

if so something is fishy, and your config looks ok.

active high/low has to do with the wiring and type of switch, normally closed vs normally open. if M119shows the X endstop as at stop if the switch is not triggered you may have to invert it, but for now that doesn't seem to be an issue if the previous post was correct.

[fcwilt]

@BearcatTD

Verify that your X endstop device is connected to the correct input.

Perhaps there is a break in one of the wires to the endstop device.

Also you can swap, as a test, the X and Y endstop connections and see what M119 reports.

Your endstop devices are likely active high assuming they are just micro switches and are using the suggested normally closed connection.

Frederick

[BearcatTD]

@bearer said in X Endstop not being recognized:

@BearcatTD so you get the same output when you run M119 while the endstop is triggered and not triggered? I.e. hold the switch while running M119

Yes indeed!

[BearcatTD]

@fcwilt

I'm headed out to a football game...will take a run at it when I get home later!

Thanks folks!

Pat

[A Former User]

@BearcatTD said in X Endstop not being recognized:

Yes indeed!

then check wiring as pr fcwilts suggestion, something fishy with the hardware (wiring, switch and/or board)

[Veti]

to check the endstop with a multimeter.

set it to measure ohm (resistance)

now the meter should show something that represents infinite. if you make the black and red probe of the multimeter touch it should show something close to 0 or 0.

now unplug the endstop from the duet. there should be two wires going into the molex connector.
each wire should have a small exposed metal area on the side of the connector. make the multimeter probes each touch one of those area.
depending on the switch the multimeter should read:
NO : infinite
NC : close to 0
then you then trigger the switch it should now switch to the other value.

if it does not toggle, measure directly on the switch itself. there are there wires comming out of the switch. use the 2 side ones.

if it now toggles, the wires or crimps in the cable are bad. if it does not, then the switch is broken.

[dc42]

@BearcatTD, is it a microswitch endstop, or some other type?

[Veti]

@dc42
he is setting up his ender 3 with a duet wifi.
the ender 3 is using micro switches as endstops.

[dc42]

@BearcatTD, please send M574 without parameters from the console and see what the response is. I want to check that the endstop configuration is as you specified in config.g.

If the configuration is correct and the hardware is working, it should read "stopped" when the LED is off and "not stopped" when the LED is on.

[BearcatTD]

@dc42

When I send the M574 command with the endstop triggered and untriggered I get the same response, " Endstop configuration: X; low end active high, Y; low end active high; Z; low end z probe.

When I trigger the endstop the led on the board goes out and comes back on when I release the endstop.

Thanks!

[dc42]

@BearcatTD said in X Endstop not being recognized:

@dc42

When I send the M574 command with the endstop triggered and untriggered I get the same response, " Endstop configuration: X; low end active high, Y; low end active high; Z; low end z probe.

When I trigger the endstop the led on the board goes out and comes back on when I release the endstop.

Thanks!

If you unplug the X endstop connector from the Duet completely, does M119 show it as triggered or not triggered? If it shows it as not triggered, that suggests a hardware fault on the Duet.

[BearcatTD]

Both triggered and untriggered shows the same response. Endstops -X:not stopped, Y: at min stop, Z not stopped, Z probe: not stopped.

Does it matter that the led on the board is responding when I engage the endstop?!

[BearcatTD]

If I unplug the connector I get:

"Endstops - X: at min stop, Y: at min stop, Z:not stopped, Z probe not stopped"