Completely stumped after firmware update - X-axis wont move after home

noen

My Duet has been working fantastically, but I just returned to my printer after a few weeks away and decided to update to 1.17RC1.

Everything works as before except the x-axis (Drive 0).

I can home it using the homex or homeall script (and indeed, before homing, G1 X{-500…500} F600 S1 works).
But once it triggers the limit switch, the axis will not budge unless I manually move it off the limit switch.

This is a heavily modified RigidbotBig. And literally everything else works exactly as before the upgrade. Should I just do a manual firmware flash from my PC?

All pertinent parts of my config.g below:

[c]G21 ; Work in millimetres
G90 ; Send absolute coordinates…
M83 ; ...but relative extruder moves

; Axis and motor configuration
M569 P0 S0 ; Drive 0 goes backwards
M569 P1 S1 ; Drive 1 goes forwards
M569 P2 S1 ; Drive 2 goes forwards
M569 P3 S0 ; Drive 3 goes forwards
M569 P4 S0 ; Drive 4 goes forwards
M574 X1 Y1 Z1 S0 ; set endstop configuration (all endstops at high end, active high)
;*** The homed height is deliberately set too high in the following - you will adjust it during calibration
M666 X0 Y0 Z0 ; put your endstop adjustments here, or let auto calibration find them
M350 X16 Y16 E16:16 I1 ; Set 16x microstepping with interpolation
M92 X160 Y160 Z1600 ; Set axis steps/mm
;M906 X1600 Y1600 Z1650 E1330:1330 I60 ; Set motor currents (mA) and increase idle current to 60%
M906 X1360 Y1360 Z1300 E1130:1130 I60 ; Setting motor currents to 85% for temps.
M201 X1000 Y1000 Z100 E10000 ; Accelerations (mm/s^2)
M203 X20000 Y20000 Z180 E10000 ; Maximum speeds (mm/min)
M566 X500 Y500 Z24 E300 ; Maximum instant speed changes mm/minute
M208 X340 Y256 Z254 ; Extents for Bed
M208 X0 Y0 Z0 S1 ; Minimums for bed
M558 P0
M556 S78 X0 Y0 Z0 ; Axis compensation here
M208 S1 Z-0.2 ; set minimum Z
T0 ; select first hot end
M106 P2 S255[/c]

dc42

1. Does the rest of the printer still work after it triggers the limit switch, e.g. the Y and Z axes?

2. Does DuetWebControl or M119 show the X axis as homed after sending G28 X and it triggers the limit switch?

2a. Does DWC show the X coordinate as zero after homing?

3. Please post your entire config.g file as there may be other parts that are pertinent.

4. You can flash an older firmware version over the web interface if you want to revert the firmware. Which firmware were you using before?

5. Please post your homex.g and homeall.g files.

noen

Yep, all other axes and extruders and heaters work before and after triggering the x limit switch.
Yep shows as homed
2a) Yep shows as 0.0
http://pastebin.com/bf81AfTa
Will try flashing back to 1.15 and report back thanks!
[c]; Rigidbot homeall file for use with dc42 Duet firmware
; Adjust the bed upper and lower limits in config.g (M208 commands) to get the correct homing positions
G91
G1 Z4 F200 ; raise head to avoid dragging nozzle over the bed
G1 X-400 F3000 S1 ; move up to 240mm in the -X direction, stopping if the homing switch is triggered
G1 X4 F600 ; move slowly 4mm in the +X direction
G1 X-10 S1 ; move slowly 10mm in the -X direction, stopping at the homing switch
G1 Y-400 F3000 S1 ; move up to 240mm in the -Y direction, stopping if the homing switch is triggered
G1 Y4 F600 ; move slowly 4mm in the +Y direction
G1 Y-10 S1 ; move slowly 10mm in the -Y direction, stopping at the homing switch
G1 Z-300 F3000 S1 ; move up to 300mm in the -Z direction, stopping if the homing switch is triggered
G1 Z1 F600 ; move slowly 4mm in the +Z direction
G1 Z-5 S1 ; move slowly 10mm in the -Z direction, stopping at the homing switch
G90 ; back to absolute mode
[/c]

[c]; Rigidbot X axis homing file for dc42 Duet firmware
G91 ; relative mode
G1 Z4 F200 ; raise head to avoid dragging nozzle over the bed
G1 X-400 F3000 S1 ; move up to 240mm in the -X direction, stopping if the homing switch is triggered
G1 X4 F600 ; move slowly 4mm in the +X direction
G1 X-10 S1 ; move slowly 10mm in the -X direction, stopping at the homing switch
G1 Z-4 F200 ; lower the head again
G90 ; back to absolute mode
[/c]

dc42

Please run M208 with no parameters, to see what the firmware thinks your X axis limits are.

dc42

This bit of config.g is wrong:

; Tool definitions
M563 P0 D0 H1 F0 X22 Y2.1 ; Define tool 0
G10 P0 S0 R0 ; Set tool 0 operating and standby temperatures

The X and Y parameters are presumably tool offsets, and if you need them at all for tool 0 they should be in the G10 command. Using X22 on the M563 command means re-map the X axis to axis 22!

noen

Oh geeze, thanks! That got me sorted.

Just as an FYI, when reverting back to 1.15e, it worked even with my bodged config.g

Thank you so much, amazing how a second set of eyes can be so effective!

dc42

X mapping was introduced in 1.16 to support IDEX printers, so your X22 was ignored in earlier versions.