Accelerometer not found on specified port

droftarts

@myersm1234 when you send M955 P0 C"spi.cs2+spi.cs1" I61 in the console, what does it actually report? And when you send M955 P0 after?

Ian

myersm1234

@droftarts This is what I get
M955 P0
Error: M955: Accelerometer not found

; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.5.0-rc.4+1 on Sat Apr 13 2024 14:49:41 GMT-0400 (Eastern Daylight Time)

; General
G90 ; absolute coordinates
M83 ; relative extruder moves
M550 P"My Printer" ; set hostname
M911 S12 R12.5 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss

; Accessories
M575 P1 S0 B57600 ; configure PanelDue support

; Network
M552 S1 ; configure WiFi adapter
M586 P0 S1 ; configure HTTP

; Accelerometers
M955 P0 C"spi.cs2+spi.cs1" I61 ; configure accelerometer on board #0

; Smart Drivers
M569 P0 S0 D2 ; driver 0 goes backwards (X axis)
M569 P1 S0 D2 ; driver 1 goes backwards (Y axis)
M569 P4 S1 D2 ; driver 4 goes forwards (extruder 0)
M569 P6 S1 D2 ; driver 6 goes forwards (Y axis)
M569 P7 S0 D2 ; driver 7 goes backwards (Z axis)
M569 P8 S0 D2 ; driver 8 goes backwards (Z axis)
M569 P9 S0 D2 ; driver 9 goes backwards (Z axis)

; Motor Idle Current Reduction
M906 I30 ; set motor current idle factor
M84 S30 ; set motor current idle timeout

; Axes
M584 X0 Y1:6 Z7:8:9 ; set axis mapping
M671 X7:320:500 Y145:500:145 S99
M350 X16 Y16 Z16 I1 ; configure microstepping with interpolation
M906 X1200 Y1200 Z1200 ; set axis driver currents
M92 X106.67 Y106.67 Z400 ; configure steps per mm
M208 X0:500 Y0:500 Z0:450 ; set minimum and maximum axis limits
M566 X900 Y900 Z12 ; set maximum instantaneous speed changes (mm/min)
M203 X18000 Y18000 Z180 ; set maximum speeds (mm/min)
M201 X600 Y600 Z200 ; set accelerations (mm/s^2)

; Extruders
M584 E4 ; set extruder mapping
M350 E16 I1 ; configure microstepping with interpolation
M906 E1200 ; set extruder driver currents
M92 E282.94 ; configure steps per mm
M566 E120 ; set maximum instantaneous speed changes (mm/min)
M203 E3600 ; set maximum speeds (mm/min)
M201 E250 ; set accelerations (mm/s^2)

; Kinematics
M669 K0 ; configure Cartesian kinematics

; Probes
M558 K0 P9 C"^zprobe.in" H5 F6000:120:120 T18000 ; configure BLTouch probe via slot #0
G31 P500 X0 Y0 Z3.6 ; set Z probe trigger value, offset and trigger height
M950 S0 C"duex.pwm1" ; create servo #0 for BLtouch

; Endstops
M574 X1 P"xstop" S1 ; configure X axis endstop
M574 Y1 P"ystop" S1 ; configure Y axis endstop
M574 Z1 S2 ; configure Z axis endstop

; Mesh Bed Compensation
M557 X25:475 Y25:475 S50:50 ; define grid for mesh bed compensation

; Sensors
M308 S0 P"bedtemp" Y"thermistor" A"Heated Bed" T100000 B4725 C7.06e-8 ; configure sensor #0
 ; configure sensor #1

; Heaters
M950 H0 C"bedheat" T0 ; create heater #0
M143 H0 P0 T0 C0 S140 A0 ; configure heater monitor #0 for heater #0
M307 H0 R2.43 D5.5 E1.35 K0.56 B1 ; configure model of heater #0
M950 H1 C"e0heat" T1 ; create heater #1
M143 H1 P0 T1 C0 S285 A0 ; configure heater monitor #0 for heater #1
M307 H0 R0.418 K0.0323:0.000 D1.35 E1.35 S1.00 B0 ; configure model of heater #1

; Heated beds
M140 P0 H0 ; configure heated bed #0

; Fans
M950 F0 C"fan0" ; create fan #0
M106 P0 S0 L0 X1 B1 ; configure fan #0
M950 F1 C"fan1" ; create fan #1
M106 P1 S0 B1 H1 T45 ; configure fan #1
M950 F2 C"fan2" ; create fan #2
M106 P2 S0 L0 X1 B1 ; configure fan #2

; Tools
M563 P0 S"Micro Swiss" D0 H1 F1 ; create tool #0
M568 P0 R0 S0 ; set initial tool #0 active and standby temperatures to 0C

; Miscellaneous
T0 ; select first tool

droftarts

@myersm1234 Can you send M98 P"config.g" and post the response? This should run config.g and show any errors.

It may be worth trying with the ribbon cable between the Duet and Duex disconnected, too.

I should be getting a Duet3D accelerometer in the next couple of days, I'll set it up as you have and test.

Ian

myersm1234

@droftarts Thank you sir, I will get this done tomorrow night.

myersm1234

@droftarts said in Accelerometer not found on specified port:

This is with the Duex5 disconnected.
M98 P"config.g"
HTTP is enabled on port 80
Error: Accelerometer not found on specified port
Error: Driver 6 does not support mode 'spreadCycle'
Error: Driver 7 does not support mode 'spreadCycle'
Error: Driver 8 does not support mode 'spreadCycle'
Error: Driver 9 does not support mode 'spreadCycle'
Warning: Heater 0 predicted maximum temperature at full power is 321°C
Warning: Sensor number 1 has not been defined
Warning: Heater 0 predicted maximum temperature at full power is 691°C
Error: Heater 1 not switched on due to bad model

droftarts

@myersm1234 I have replicated your setup on my bench, with a Duet 2 WiFi and Duex, using RRF 3.5.0-rc.3 and a copy of your config.g

I tested with the accelerometer plugged into the Duet directly first, then the Duex. I plugged in a PT100 board and a thermocouple board, and tested with the accelerometer in those, too, updating the accelerometer configuration in all positions:

18/04/2024, 13:54:43 	M115
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.5.0-rc.3 ELECTRONICS: Duet WiFi 1.02 or later + DueX5v0.11 FIRMWARE_DATE: 2024-01-24 17:56:24
18/04/2024, 13:55:19 	M955 P0
Accelerometer 0 type LIS2DW with orientation 61 samples at 1600Hz with 14-bit resolution, SPI frequency 2000000
18/04/2024, 13:59:40 	M955 P0 C"spi.cs6+spi.cs5" I61
18/04/2024, 13:59:45 	M955 P0
Accelerometer 0 type LIS2DW with orientation 61 samples at 1600Hz with 14-bit resolution, SPI frequency 2000000
18/04/2024, 14:00:32 	G92 X0 Y0 Z0
18/04/2024, 14:00:41 	G4 S1
Error: Attempt to move motors when VIN is not in range
18/04/2024, 14:03:56 	M955 P0 C"spi.cs4+spi.cs3" I61
18/04/2024, 14:04:01 	M955 P0
Accelerometer 0 type LIS2DW with orientation 61 samples at 1600Hz with 14-bit resolution, SPI frequency 2000000
18/04/2024, 14:04:14 	M955 P0 C"spi.cs2+spi.cs1" I61
Error: M955: Accelerometer not found on specified port
18/04/2024, 14:05:08 	M955 P0 C"spi.cs8+spi.cs7" I61
18/04/2024, 14:05:14 	M955 P0
Accelerometer 0 type LIS2DW with orientation 61 samples at 1600Hz with 14-bit resolution, SPI frequency 2000000

As you can see, it was recognised when plugged in in all places! I was able to record motion profiles in the Input Shaping plugin in DWC and view them; these are the 'Error: Attempt to move motors when VIN is not in range' messages, as obviously I don't have any motors connected. I could wave the accelerometer around and it picked up the movement.

So I don't think this is a firmware or configuration issue, and looks like a hardware fault. I think the chances of both your Duet and Duex Temp_DB inputs failing is remote, especially as you have run temperature daughterboards in the past, and that either the cable or the accelerometer is faulty. If you have a multimeter, you could check the cable for continuity of each wire.

However, I think it would be best to swap your accelerometer for a new one. Where and when did you purchase it?
Please send an email to warranty@duet3d.com and CC your reseller. Include a link to this forum thread and the details of your original purchase. You'll receive a reply with a form to fill out.

Ian

myersm1234

@droftarts Thanks Ian, I really appreciate your help with this.
Thanks again! Mike

myersm1234

@droftarts Looks like I bought it at Spool3d on Oct.20/23, but just getting to install it now...lol. Probably not worth the effort for warranty, for the cost of a new one.

droftarts

@myersm1234 Up to you! But it would be good to get it back and find out why it's not working.

Ian

myersm1234

@droftarts Hello I received a new accelerometer. Unfortunately I'm having the same issue. Could it be the Duet 2 board? Everything else seems to work with the board though.

Phaedrux

Can you take the board out of the printer and test it on a bench setup with nothing else connected?

Also, 3.5.1 firmware is out now, have you updated?

myersm1234

@Phaedrux No I haven't done the update. I will do this before I put it on the bench

myersm1234

@Phaedrux Same thing with the update. If I just unplug everything from the board in place, this should give the same result as on the bench correct?

myersm1234

@Phaedrux With everything unplugged it is recognized on both boards. I guess I'll start plugging things back.

myersm1234

@Phaedrux I found the problem. When the Panel Due 7 is plugged in it will not recognize the accelerometer

droftarts

@myersm1234 said in Accelerometer not found on specified port:

@Phaedrux I found the problem. When the Panel Due 7 is plugged in it will not recognize the accelerometer

@Phaedrux highlighted this to @dc42. He replied:

That's an odd one! It could be a hardware problem e.g. a short between two pins on the MCU causing the PD to drive one of the accelerometer connections, or a software issue e.g. the polling that PD does interfering with the accelerometer being read. They could try putting PD on the Setup page and then rebooting the Duet with the reset button or M999 or emergency stop from DWC. If that allows the accelerometer to work, but it stops working if they switch to a different page on PD, that would point to a software problem.

I redid the setup of a Duet 2 WiFi (RRF 3.5.0-rc.3), Duex, and accelerometer, this time with a Paneldue 5i (firmware 3.5.0-rc6-5.0i), powered by USB and using your config.g again. I did the test as David suggested, but the accelerometer was always visible, in DWC and on the PanelDue.

DWC console:

02/05/2024, 10:15:51 	M955 P0 C"spi.cs2+spi.cs1" I61
02/05/2024, 10:15:54 	M955 P0
Accelerometer 0 type LIS2DW with orientation 61 samples at 1600Hz with 14-bit resolution, SPI frequency 2000000
02/05/2024, 10:24:22 	M115
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.5.0-rc.3 ELECTRONICS: Duet WiFi 1.02 or later + DueX5v0.11 FIRMWARE_DATE: 2024-01-24 17:56:24

I think check your Duet and Duex for any possible shorts, eg make sure there's nothing touching the back of the boards when installed, and give the boards a good clean to make sure no metal filings are causing shorts.

What firmware is the PanelDue running (see the Setup screen on the PanelDue)? Is the PanelDue connected to the Duet via the ribbon connector or the 4-wire cable?

Ian

myersm1234

@droftarts I don't see anything that looks like it could be shorting. Firmware is 3.5.0-rc9-v3-7.0 and I have both the ribbon and 4-wire connected.

droftarts

@myersm1234 there’s no reason to use both cables to the PanelDue, unless your Duet is an old version (v1.01 or earlier). Please try with just one cable connected. Use just the ribbon cable if you need the SD card. Are you using a particular long ribbon cable to the PanelDue? The ribbon cable is on the same SPI bus as the accelerometer, so the extra capacitive load of the cable may be causing the problem.

Ian

myersm1234

@droftarts I am using just the 4-wire and everything is working fine. Not sure why I had both connections in use, I must have miss read something when I was building this printer years ago. The 10 pin was 130cm long.
Any way sorry for the trouble and thanks again for the help!
Mike

droftarts

@myersm1234 No, it's fine, I'll dig out the test setup again next week and see if I can replicate it with both plugged in.

Ian