Accelerometer not found on specified port

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

myersm1234

@droftarts Sounds good. Let me know how you make out!

droftarts

@myersm1234 I set up the bench test again, with the ribbon cable and 4-wire cable connected to the PanelDue this time. My accelerometer behaved perfectly!

One thing I noticed is that if you run the command to define the accelerometer M955 P0 C"spi.cs2+spi.cs1" I61, and it goes through okay, you can disconnect the accelerometer and M955 P0 will still report that the accelerometer is there. It's only by sending the full command again that it actually looks for it, and reports if it cannot find it.

So I'm not sure why you are having problems. Possibly a damaged PanelDue cable, or that it ran near something that generated a bit of interference, or something else on your board is causing noise on the board that having the PanelDue ribbon cable connected exacerbates enough to drown out the accelerometer.

If people are having problems with their accelerometers in the future, I'll certainly try and remember this as a possible solution!

Ian