H-Bot Endstop problem

deckingman

Comments in bold.

G91 ; relative positioning - this is OK

G1 S2 Z5 F1800 ; lift Z relative to current position - this is OK too but you should use H2 here for the single Z motor

G1 S1 X-395 F1800 ; move quickly to X axis endstop and stop there (first pass) - this is OK but again, use H instead of S

G1 S2 X5 F9000 ; go back a few mm - before this move, the axis has already been homed so you don't need the S2 parameter - remove it.

G1 S1 X-395 F360 ; move slowly to X axis endstop once more (second pass) - this is OK.

G1 S2 Z-5 F1800 ; lower Z again - this should be OK but use H instead of S.

G90 ; absolute positioning - this Ok

Alternatively, you could put M564 H0 at the start of the homing file and take out all the S2 or H2 parameters. Then put M564 H1 at the end.

NL61

@deckingman
I changed everything as you wrote. It still crashes into the frame.

Veti

can you execute the commands from deckingman in the console one by one manually

NL61

@Veti
I did so. After G1 H1 X-395 F1800 it crashed.

droftarts

@NL61 Do you have a probe set up in config.g? Please post your whole config.g.

Ian

NL61

@droftarts

Here it is:

G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"Olli3" ; set printer name

M669 K1 ; switch to CoreXY mode

; Network
M552 S1 P172.21.163.110 ; enable network
M553 P255.255.255.0
M554 P 172.21.163.2

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

; Drives
M569 P0 S0 ; physical drive 0 goes forwards
M569 P1 S0 ; physical drive 1 goes forwards
M569 P2 S1 ; physical drive 2 goes backwards
M569 P3 S0 ; physical drive 3 goes forwards
M584 X0 Y1 Z2 E3 ; set drive mapping
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X32.00 Y32.00 Z640.00 E460.00 ; set steps per mm
M566 X900.00 Y900.00 Z12.00 E120.00 ; set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z180.00 E1200.00 ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z20.00 E250.00 ; set accelerations (mm/s^2)
M906 X1600 Y1600 Z500 E500 I30 ; 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 X390 Y290 Z100 S0 ; set axis maxima

; Endstops
M574 X1 Y1 Z2 S0 ; set active high endstops

; Z-Probe
M558 P0 H5 F120 T6000 ; disable Z probe but set dive height, probe speed and travel speed
M557 X15:215 Y15:195 S20 ; define mesh grid

; Heaters
M140 H-1 ; disable heated bed
M305 P1 T100000 B4725 C7.060000e-8 R4700 ; set thermistor + ADC parameters for heater 1
M143 H1 S280 ; set temperature limit for heater 1 to 280C

; 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

; 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
M911 S20 R22 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss

Veti

@NL61 said in H-Bot Endstop problem:

I did so. After G1 H1 X-395 F1800 it crashed.

this is VERY strange.
if M119 says the endstop is triggered the G1 H1 command should stop when the endstop is triggered.

The Firmware version is the correct one.

dc42

I agree, very strange. Typical causes of this type of problem would be:

Endstops pulling the input low enough to light the LED, but not low enough to register as a low input to the processor. But in that case, M119 wouldn't show the endstops as triggered when you test them.
X and Y endstop connections swapped
Axis movement incorrect (easy to do on a CoreXY machine), for example G1 H1 X-395 is actually moving the Y axis, or is moving X away from the endstop switch.

NL61

@dc42
thanks for answering,
I tried M119 serveral times for each axis, it always shows if triggered or not.
the endstops are not swapped and the movement goes to the correct direction.

deckingman

One thing that keeps leaping out at me from the config.g file, is the steps per mm for X and Y but I don't see what this would have bearing on the end stop triggering. But with a 16 tooth pulley, 2mm pitch, and 0.9 degree motors, the value is around 80 so having the steps per mm set to 32 would imply something like a 50 tooth pulley which is pretty huge. 32 steps @16x micro stepping is 2 full steps per mm or 100 mm per motor revolution using 1.8 degree motors.

dc42

@NL61 said in H-Bot Endstop problem:

@dc42
thanks for answering,
I tried M119 serveral times for each axis, it always shows if triggered or not.
the endstops are not swapped and the movement goes to the correct direction.

Can you confirm that the homex.g file looks exactly like the one you posted above when you open it in Duet Web Control?
If you try to home just X (by pressing the Home X button in Duet Web Control, or by sending G28 X), does movement stop if you trigger either the X or Y homing sensors manually?

Until you have homing working, you may wish to reduce the motor currents.

NL61

@dc42
once again the homex.g file:

; homex.g
; called to home the X axis
;
; generated by RepRapFirmware Configuration Tool v2.1.2 on Mon Nov 11 2019 14:44:06 GMT+0100 (Mitteleuropäische Normalzeit)
G91 ; relative positioning
G1 H2 Z5 F1800 ; lift Z relative to current position
G1 H1 X-395 F1800 ; move quickly to X axis endstop and stop there (first pass)
G1 X5 F1800 ; go back a few mm
G1 S1 X-395 F360 ; move slowly to X axis endstop once more (second pass)
G1 H2 Z-5 F1800 ; lower Z again
G90 ; absolute positioning

I tried to home X and triggered both, X and Y Endstop. No reaction

droftarts

Could you try swapping your NPN sensor for a microswitch, just to check it's working correctly?

Ian

NL61

@droftarts
hmm, the micro switch is working in X and Y.
The Sensors are MLM8-3002NA NPN, Schließer.
24 V and a BAT43 Diode at the signal output.
Why does the z-axis work? Its all the same setup.

I have to leave now. Thank you all for your answers, if there are any ideas whalt I can di to get those sensors working, I`ll try tomorrow.

dc42

Those sensors have a blue wire that must be connected to ground. Where on the Duet have you connected them?

NL61

@dc42
I connected 24V and Ground to the Power Supply.

NL61

I did some troubleshooting this morning. I connectet the X-Sensor to the Z-input and could stop the Z-axis with a piece of metal holding it to the X-Sensor. Same with the Y-Sensor. That tells me that the sensors work fine.
Then I connectet Z-Motor and Sensor to the Y-connectors on the duet. The LED triggered but the motor did not stop. M119 says Y-Axis homed.
Is it possible that there is a problem with the board?
Or does anyone have an idea?

dc42

Can you confirm that if you use a microswitch connected to the Y endstop input in place of the inductive sensor, the Y motor does stop when you trigger the microswitch?

If that's the case, then one possibility is that ground noise created by running the X and Y motors is affecting the input voltage at the endstop inputs. It may work better if you connect the blue wire to the ground pin on the endstop input, instead of to ground at the PSU.

NL61

@dc42
I connected microswitches to X and Y now, so I can run my first print. They are both working.
I already connected the ground wire to the input of the endstop but it also didn't work.

dc42

@NL61 said in H-Bot Endstop problem:

@dc42
I connected microswitches to X and Y now, so I can run my first print. They are both working.
I already connected the ground wire to the input of the endstop but it also didn't work.

If your Duet is revision 1.04, then you might get the inductive sensors working if you remove the diodes and connect the output directly to the endstop input. This disadvantage is that as you are using a 24V supply, if the ground wire to the sensor breaks then that will probably feed enough voltage into the endstop input to blow the indicator LED. The microcontroller itself is protected against excessive input voltage on the version 1.04 Duet.