Endstop error

lacs2711

End stop problem

I have a duet wifi 2 which I am installing with an Ender 5. everything has gone well.
but i have a problem with my endstops, everything seems to work but the steppe motor does not stop when it reaches the endstop. It does not detect that it should stop. so it crashe.

I have in frustration come to put the wires wrong, so also fear that I may have shorted something.

Sorry about my English, I'm using google translet.

Veti

please read

https://duet3d.dozuki.com/Wiki/Connecting_endstop_switches

and look at the testing part.

also post your config

lacs2711

; Configuration file for Duet WiFi (firmware version 2.03)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v2.1.2 on Thu Nov 07 2019 17:27:04 GMT+0100 (Centraleuropæisk normaltid)

; General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"Ender5" ; set printer name
M918 P1 E4 F2000000 ; configure direct-connect display

; Network
M552 S1 ; enable network
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable Telnet

; Drives
M569 P0 S1 ; physical drive 0 goes forwards
M569 P1 S1 ; physical drive 1 goes forwards
M569 P2 S0 ; physical drive 2 goes backwards
M569 P3 S0 ; physical drive 3 goes backwards
M584 X0 Y1 Z2 E3 ; set drive mapping
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z400.00 E93.00 ; set steps per mm
M566 X1200.00 Y1200.00 Z24.00 E300.00 ; set maximum instantaneous speed changes (mm/min)
M203 X9000.00 Y9000.00 Z180.00 E6000.00 ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z100.00 E5000.00 ; set accelerations (mm/s^2)
M906 X800 Y800 Z800 E1000 I50 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout

; Axis Limits
M208 X0 Y0 Z0 S1 ; set axis minima
M208 X250 Y250 Z300 S0 ; set axis maxima

; Endstops
M574 X1 Y1 S1 ; set active high endstops
M574 Z1 S2 ; set endstops controlled by probe

; Z-Probe
M307 H4 A-1 C-1 D-1 ; disable heater on PWM channel for BLTouch
M558 P9 H5 F120 T3000 ; set Z probe type to bltouch and the dive height + speeds
M558 H30 ;*** Remove this line after delta calibration has been done and new delta parameters have been saved
G31 P500 X41 Y9 Z2.5 ; set Z probe trigger value, offset and trigger height
M557 X15:230 Y15:230 S20 ; define mesh grid

; Heaters
M305 P0 T100000 B4092 R4700 ; set thermistor + ADC parameters for heater 0
M143 H0 S150 ; set temperature limit for heater 0 to 150C
M305 P1 T100000 B4092 R4700 ; set thermistor + ADC parameters for heater 1
M143 H1 S275 ; set temperature limit for heater 1 to 275C

; Fans
M106 P0 S0 I0 F500 H-1 ; set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
M106 P1 S1 I0 F500 H1 T45 ; set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on
M106 P2 S1 I0 F500 H1:0 T45 ; set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned on

; Tools
M563 P0 D0 H1 F0 ; 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

; Custom settings are not defined

; Miscellaneous
M501 ; load saved parameters from non-volatile memory
M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss

lacs2711

I have tested endstop in machine probeties, and they go from no to yes when i enable them.

Veti

use a multimeter and measure the resistance on the connector. triggered and untriggerd.

lacs2711

OK I have measured on endstop with multimeter 20k, they go from 0.00 to -8.30 when activated.
hope it makes sense

Veti

-8.3 makes not much sense. there is no negative resistance. but there seems to be a change.

config looks fine.

please post the output of.
M119 when press x and when pressed y endstop.

also you are aware that your board is not a genuine duet board?

dc42

We'll also need to see your homing files.

lacs2711

here's what it writes when I send M119
the first is triggered, the second is not triggered:

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

2: 21.28.22M119
Endstops - X: not stopped, Y: not stopped, Z: not stopped, Z probe: not stopped

Did not now that it was not a duet I had bought, but can see that it says on the back that it is a copy.
sorry if i have wrongly asked for help.

lacs2711

; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool v2.1.2 on Thu Nov 07 2019 17:27:04 GMT+0100 (Centraleuropæisk normaltid)
G91 ; relative positioning
G1 H2 Z4 F3000 ; lift Z relative to current position
G1 H1 X-240 Y-240 F1500 ; move quickly to X and Y axis endstops and stop there (first pass)
G1 H2 X5 Y5 F3000 ; go back a few mm
G1 H1 X-240 Y-240 F120 ; move slowly to X and Y axis endstops once more (second pass)
G90 ; absolute positioning
G1 H2 X-26 Y6 F3000 ; go to first bed probe point and home Z
G30 ; home Z by probing the bed

; Uncomment the following lines to lift Z after probing
;G91 ; relative positioning
;G1 S1 Z4 F50 ; lift Z relative to current position
;G90 ; absolute positioning

lacs2711

; homex.g
; called to home the X axis
;
; generated by RepRapFirmware Configuration Tool v2.1.2 on Thu Nov 07 2019 17:27:04 GMT+0100 (Centraleuropæisk normaltid)
G91 ; relative positioning
G1 H2 Z5 F3000 ; lift Z relative to current position
G1 S1 X-255 F1500 ; move quickly to X axis endstop and stop there (first pass)
G1 H2 X5 F3000 ; go back a few mm
G1 H1 X-255 F120 ; move slowly to X axis endstop once more (second pass)
G1 H2 Z-5 F3000 ; lower Z again
G90 ; absolute positioning

dc42

Are you sure that you don't have the X and Y endstop connections swapped, or the X and Y motor connections swapped?

Veti

@lacs2711 said in Endstop error:

1: 21.28.07M119
Endstops - X: at min stop, Y: at min stop, Z: not stopped, Z probe: not stopped
2: 21.28.22M119
Endstops - X: not stopped, Y: not stopped, Z: not stopped, Z probe: not stopped

this means they trigger correcly.
can you test x and y seperatly. you might have swapped them around.

lacs2711

I'm pretty sure they are not swapped, here M119 along with a picture

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

Veti

what firmware version did they supply the duet with?

dc42

Let' start with homing X by itself. Your homex.g file is this:

; homex.g
; called to home the X axis
;
; generated by RepRapFirmware Configuration Tool v2.1.2 on Thu Nov 07 2019 17:27:04 GMT+0100 (Centraleuropæisk normaltid)
G91 ; relative positioning
G1 H2 Z5 F3000 ; lift Z relative to current position
G1 S1 X-255 F1500 ; move quickly to X axis endstop and stop there (first pass)
G1 H2 X5 F3000 ; go back a few mm
G1 H1 X-255 F120 ; move slowly to X axis endstop once more (second pass)
G1 H2 Z-5 F3000 ; lower Z again
G90 ; absolute positioning

The line starting G1 S1 should really start G1 H1, but unless you have accidentally set the Duet to laser mode, it doesn't matter. Try changing it to G1 H1 anyway.

You've already checked that the X endstop switch reads correctly in M119. When you try to home just X (using the web interface, or by sending G28 X), does it move the carriage towards the X endstop switch?

lacs2711

when I try to home X it says

22.06.50G28 X
Error: G0/G1: insufficient axes homed

dc42

@lacs2711 said in Endstop error:

when I try to home X it says

22.06.50G28 X
Error: G0/G1: insufficient axes homed

As @Veti already asked, please tell us what firmware version you are using. Send M115 to find out.

lacs2711

firmware version 2,03

lacs2711

sorry
M115
22.10.39M115
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 2.0(RTOS) ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2018-06-05b3