Error: failed to enable endstops
Piyush Panse last edited by
I have a router which does not have endstops. In my config.g file generator I had selected no endstops. Now when I upload a gcode file in Jobs it gives out an error 'Failed to enable endstops'.I want to use duet 3 without endstops how can I do it.....
heres my config file:
; Configuration file for Duet 3 (firmware version 3.3)
; executed by the firmware on start-up
; generated by RepRapFirmware Configuration Tool v3.3.10 on Fri Apr 29 2022 11:01:24 GMT+0200 (Central European Summer Time)
; General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"Duet 3" ; set printer name
M569 P0.0 S1 ; physical drive 0.0 goes forwards
M569 P0.1 S1 ; physical drive 0.1 goes forwards
M569 P0.2 S1 ; physical drive 0.2 goes forwards
M569 P0.3 S1 ; physical drive 0.3 goes forwards
M584 X0.0 Y0.1 Z0.2 E0.3 ; set drive mapping
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z400.00 E305.00 ; set steps per mm
M566 X900.00 Y900.00 Z60.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 X800 Y800 Z800 E800 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout
; Axis Limits
M208 X-150 Y-150 Z0 S1 ; set axis minima
M208 X150 Y150 Z200 S0 ; set axis maxima
; WARNING: No endstops configured
M558 P0 H5 F120 T6000 ; disable Z probe but set dive height, probe speed and travel speed
M557 X-135:135 Y-135:135 S20 ; define mesh grid*********
M308 S0 P"temp0" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin temp0
M950 H0 C"out0" T0 ; create bed heater output on out0 and map it to sensor 0
M307 H0 B1 S1.00 ; enable bang-bang mode for the bed heater and set PWM limit
M140 H0 ; map heated bed to heater 0
M143 H0 S120 ; set temperature limit for heater 0 to 120C
M308 S1 P"temp1" Y"thermistor" T100000 B4138 ; configure sensor 1 as thermistor on pin temp1
M950 H1 C"out1" T1 ; create nozzle heater output on out1 and map it to sensor 1
M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
M143 H1 S280 ; set temperature limit for heater 1 to 280C
M950 F0 C"out4" Q500 ; create fan 0 on pin out4 and set its frequency
M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"out5" Q500 ; create fan 1 on pin out5 and set its frequency
M106 P1 S1 H-1 ; set fan 1 value. Thermostatic control is turned off
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
jay_s_uk last edited by
@piyush-panse you'd basically need G92 X0 etc in each homing file.
but questions such as are you going to leave the motors a X0 etc before you power down? or will you be needing to jog them into position before setting 0?
You could always echo their location into a file before powerdown to enable you to reinstate that position at power up but obviously things such as an emergency stop would affect that. motors can also jump up to 4 full steps when energised.
Ultimately, when the motors aren't energised, RRF has no way of knowing where those motors are
droftarts administrators last edited by droftarts
@piyush-panse I expect the uploaded gcode has a command to home the axes, ie G28. I guess you are setting the router position with G92, but the homing command is overriding this, and calling home[axis/all].g, which is then (in its default form) not finding any endstops to home against, and generating the error.
EDIT: Ideally, remove any G28 homing command from the gcode. You should be able to do this in the software that is generating the gcode; there's usually a 'start gcode' (and 'end gcode') section that gets inserted into the generated gcode file.
You could change homeall.g (and the other homing macros) to pick up the current value of X, Y and Z and set it again.