Endstop issue after updating firmware

[man_mar]

Hello everyone, "I Am Once Again Asking for Your Financial Technical Support" LOL

I'll get straight to the point.
Basic configuration is an old 3D SYSTEMS CUBE pro trio, so :
X axis with single nema17
Y axis with dual nema17
Z axis with single nema23

Endstops are 3 bare microswitches, normally open, at the origin of the axis:

M574 X1 S1 P"!io0.in"          
M574 Y1 S1 P"!io1.in"          
M574 Z1 S1 P"!io2.in"

The issue: with RRF3.0final everything was ok, but DWC wouldn't allow to manually extrude and I had to use console so I did a "sudo apt update sudo apt upgrade" and proceeded to upgrade to 3.2.2

To my suprise there's no more endstop status displayed, well it's a bit unconvenient but I can use M119! Everything seems in order, I try to do an HOME X and...doesn't do it.
Well specifically it doesn't execute this line of the homex.g:

G1 H1 X-215 F1800

I try to do an HOME Z and this works as intended!

I tried to switch endstops and IO_x, but no luck. Homing Z works, homing X or Y doesn't.
With the previous firmware I didn't have this issue

Any other movement works: I placed the extruder in the center of the build area, I did a G92 setting coordinates and then I did a G1 something and it worked as smoothly as ever.

I am out of options here, so here's the config.g:

; Configuration file for Duet 3 (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Tue Mar 30 2021 19:47:51 GMT+0200 (Ora legale dell’Europa centrale)
 
; General preferences
G90                            ; send absolute coordinates...
M83                            ; ...but relative extruder moves
M550 P"Duet 3"                 ; set printer name
 
; Drives
M569 P0.0 S1                   ; physical drive 0.0 goes forwards
M569 P0.1 S0                   ; physical drive 0.1 goes backwards
M569 P0.2 S0                   ; physical drive 0.2 goes backwards
M584 X0.0 Y0.1 Z0.2            ; set drive mapping
M350 X16 Y16 Z16 I1            ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z400.00      ; set steps per mm
M566 X900.00 Y900.00 Z60.00    ; set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z180.00 ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z20.00    ; set accelerations (mm/s^2)
M906 X1800 Y1800 Z1800 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 X210 Y210 Z250 S0         ; set axis maxima
 
; Endstops
M574 X1 S1 P"!io0.in"           ; configure active-high endstop for low end on X via pin inverted io0.in
M574 Y1 S1 P"!io1.in"           ; configure active-high endstop for low end on Y via pin inverted io1.in
M574 Z1 S1 P"!io2.in"           ; configure active-high endstop for low end on Z via pin inverted io2.in
 
; Z-Probe
M558 P0 H5 F120 T6000          ; disable Z probe but set dive height, probe speed and travel speed
M557 X15:195 Y15:195 S20       ; define mesh grid
 
; Heaters
 
; Fans
 
; Tools
 
; Custom settings are not defined
 

Thanks

[Phaedrux]

The endstop status will make a comeback as a plugin. See here.

https://github.com/Duet3D/DSF-Plugins/tree/master/EndstopsMonitor

How were your endstops defined in config.g before?

When you say you try home x but it doesn't do it, but what happens? Does it mark the axis as homed?

What do you have in homex?

What does M119 report as the endstop status?

[Alex.cr]

@man_mar said in Endstop issue after updating firmware:

M574 Y1 S1 P"!io1.in"

I have a CubePro as well.

While I don't think this is the issue, Y axis endstops home to max( unless you have changed them).
The line quoted above should be a "Y2".

[man_mar]

Update: Today I just changed the X endstop with one bare microswitch with NC pin available, as suggested in the documentation. I admit I didn't change endstops just because at first they were working just fine, but I guess I was wrong and at least this could be helpfull for future reference.
This new one has the classic 3 pins: COM, NO, NC; the original one has only COM and NO.
This resolved the issue on the X axis, but now the issue has "transferred" to the other axis LOL.
I measured with a multimeter the Ohms between the contacts, and got like 280kOhms instead of "open circuit". I guess i better throw these original microswitches in the trash ASAP.

@phaedrux said in Endstop issue after updating firmware:

The endstop status will make a comeback as a plugin. See here.

https://github.com/Duet3D/DSF-Plugins/tree/master/EndstopsMonitor

1) How were your endstops defined in config.g before?

2) When you say you try home x but it doesn't do it, but what happens? Does it mark the axis as homed?

3) What do you have in homex?

4) What does M119 report as the endstop status?

Thanks for the reply! I'll go in order, but keep in mind the following was the situations as of yesterday:

1. same identical configuration, after the firmware upgrade i just shutted down the system and turned on the following day.
2. I click "home x", the carriage does an imperceptible negative movement (like it starts doing the X-200) but immediately stops (as if the endstop was already triggered), and then proceeds to do the X5 movement. After this it doesn't do the "double check", the DWC shows the X axis as "homed" (X = 0.00). If I do multiple "home x" one after the other it just ends up doing 5mm movements but DWC keeps telling X = 0.00: if I do 10 times "home x" the carriage ends up at X = 50 in real life, but DWC says X = 0.00.
3. homex.g is as follows:

; homex.g
; called to home the X axis
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Wed Mar 31 2021 14:11:36 GMT+0200 (Ora legale dell’Europa centrale)
G91               ; relative positioning
G1 H2 Z5 F6000    ; lift Z relative to current position
G1 H1 X-215 F1800 ; move quickly to X axis endstop and stop there (first pass)
G1 H2 X5 F6000    ; go back a few mm
G1 H1 X-215 F360  ; move slowly to X axis endstop once more (second pass)
G1 H2 Z-5 F6000   ; lower Z again
G90               ; absolute positioning
 

4)M119 when no endstop is triggered says what it should:

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

when an endstop is triggered it says "at min stop" (don't mind the Z probe, it is disabled by config.g)

@alex-cr said in Endstop issue after updating firmware:

@man_mar said in Endstop issue after updating firmware:

M574 Y1 S1 P"!io1.in"

I have a CubePro as well.

While I don't think this is the issue, Y axis endstops home to max( unless you have changed them).
The line quoted above should be a "Y2".

I configured it as Y1, because the endstop is physically placed near the origin of the axis, and I saw the Dyze conversion blog, and they actually they configured it as Y2 aswell but yes, it isn't the issue unfortunately.

[Phaedrux]

Yes it would appear that your endstops are failing as triggered. If you can replace them with NC switches all the better.