News:
-Repetitivety Is ok, tested with a dial indicator
-I've change the nut. Some improvements but the error doesn't disappear.

Other advices?

this was exactly what i was looking for! thank you!

@deckingman unfortunately T-0 (or any negative value ) doesn't work. At this point I'll leave "T0", as others say there is no difference for me. thank you all!

@Veti yeah, I've noticed. Thank you for the info

@Rushmere3D yeah, it's true, it was only to see "off"
thank you

Removing T0 at the end of config.g the hotend is no more active but in standby. Is there any way to shut it down?

Hi,
I've just updated to RRF3 and I've noticed that the hotend (hetear 1) is already active when I turn on the printer (even if the power supply is off). Look at the picture

This is my config file:

; Drives
M569 P0 S1 ; physical drive 0 goes forwards
M569 P1 S0 ; physical drive 1 goes forwards
M569 P2 S1 ; physical drive 2 goes forwards
M569 P3 S1 ; physical drive 3 goes forwards
M584 X1 Y0 Z2 E3 ; set drive mapping
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z400.00 E408.50 ; 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 Z1500.00 E3600.00 ; set maximum speeds (mm/min)
M201 X2500.00 Y2500.00 Z50.00 E1500.00 ; set accelerations (mm/s^2)
M906 X1200 Y1200 Z1200 E1200 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 X310 Y315 Z265 S0 ; set axis maxima

; Endstops
M574 X1 S1 P"xstop" ; configure active-high endstop for low end on X via pin xstop
M574 Y1 S1 P"ystop" ; configure active-high endstop for low end on Y via pin ystop
M574 Z1 S2 ; configure Z-probe endstop for low end on Z

; Stall Detection
;M915 X Y S7 F0 H200 R2 ; X and Y motor stall detection

; Z-Probe
M558 P1 C"zprobe.in" H5 F250 T6000 ; set Z probe type to unmodulated and the dive height + speeds
G31 P500 X0 Y0 Z1.20 ; set Z probe trigger value, offset and trigger height
M557 X50:260 Y20:230 S105 ; define mesh grid

; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin bedtemp
M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0
M307 H0 B0 S1.2 ; disable bang-bang mode for the bed heater and set PWM limit
M140 H0 ; map heated bed to heater 0
M143 H0 S100 ; set temperature limit for heater 0 to 100C
M308 S1 P"e0temp" Y"thermistor" T100000 B4138 ; configure sensor 1 as thermistor on pin e0temp
M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat 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

; Fans
M950 F0 C"fan0" Q1000 ; create fan 0 on pin fan0 and set its frequency
M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"fan1" Q1000 ; create fan 1 on pin fan1 and set its frequency
M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on
M950 F2 C"fan2" Q1000 ; create fan 2 on pin fan2 and set its frequency
M106 P2 S0 H-1 ; set fan 2 value. Thermostatic control is turned off

; Tools
M563 P0 S"Hotend" D0 H1 F0:2 ; 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

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

I've already checked the onboard leds: 3.3V is on, 5V is on, e0 Heat as well as Bed Heat are off.
I've also tried to add "M104 S0" in confing.g but it doesn't work.

Any advice is welcome. Thanks.

Hi,
Is there any way to display DWC-style messages instead "M291 messages"? I think they look much better than standard messages.
If so, how can I use them?

Thanks

@dc42 your solution seems work.

I was wondering if M112 has an "automatic reboot", infact when I press the emergency button and wait few seconds DWC seems already rebooted.

@Nathan actually I've had small issues with fans, but now is all ok, so I will try in the next days.

In my opinion there should be a sort of interaction between the two macros for this reason:
Let's suppose the emergency button has been pushed, then the printer is switched off before the emergency button has been released. When the printer is restarted (switched on) there may be some problems due to the emergency button state.

I'm a PLC programmer, and usually, to solve this kind of problems, we use rising edge (or falling edge). But for me g-code is completely new and I don't know how to use properly commands ( like M581). For now it's ok, I will try with dc42's solution.

@dc42 thank you, I'll try with this solution tomorrow.