It's back.
Power cycled the printer.
M955 P0 C"spi.cs4+spi.cs3"
Error: M955: Accelerometer not found on specified port
This is maddening.
It's back.
Power cycled the printer.
M955 P0 C"spi.cs4+spi.cs3"
Error: M955: Accelerometer not found on specified port
This is maddening.
Well hot dog.
Flashed back to 3.4.1 final and all 4 boards are working.
3.4.1RC1 -> 3.4.1 no go
3.4.1RC1 -> 3.4.1 -> 3.4.1RC1 no go
3.4.1RC1 -> 3.4.1 -> 3.4.1RC1 -> 3.4.1 working
Thank you @Phaedrux !!
I hooked up a LIS3DSH board a few months ago, configured input shaping, and all was well. (Duet 2 Wifi 1.0 board w/ DueX5). Using the default recommended connection to Temp_DB pins
This past week I updated firmware to 3.4.1 and immediately noticed ringing back on my first test print.
Now, despite two days of troubleshooting I only get "Error: M955: Accelerometer not found" when calling M955.
I have 4 LIS3DSH boards - all exhibit the same behavior.
I continuity checked the ribbon cable, it's good. Even so, just to rule it out, used 6" individual 22awg jumper cables to manually connect to the Temp_DB pins. No dice.
Short of taking the board to an EE with an oscilloscope, I'm baffled what has happened, or what to try. The only system change was moving to 3.4.1
config.g that was known good prior to firmware update:
; Configure lis3dsh accelerometer using Hemera Mount on Duet2Wifi
M955 P0 C"spi.cs4+spi.cs3"
; Set input shaping mode to zvd with center frequency of 40hz.
M593 P"zvd" F40
Any help would be greatly appreciated.
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!
[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]
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]
Order #130 here, would be happy to take one of the Black on Blue boards.