LIS3DSH on Duet 2 having trouble with the latest firmware
-
@Phaedrux 3.4.5 (the latest) I pulled down the git repository yesterday afternoon
-
I should add that I've hooked the device up to an Adruino and I'm getting 0x33 from WHO_AM_I and everything looks normal. I guess I could try wiring it up with some really short wires to see if I can get anything out of it. So far I've not had any luck.
-
The problem is entirely the cable. I'm not really excited about cutting up and adding connectors to another USB3 cable. The one I used was a pretty high quality one as well. I seem to remember reading something about connecting one of the wires to the insolation.
Any suggestions? This is on a heavily modified FT-5, with the duet on the back near the bottom, so I need around 3-4 ft. of cable. I'm considering moving the panel up to the top of the machine in order to fix this.
-
Wrapping the cable in aluminum foil did nothing.
-
@ericrane can you send a close up photo of the board, good enough for us to read the markings on the chip?
The WhoAmI register should return 0x3F for LIS3DSH and 0x33 for LIS3DH. These are checked in function LIS3DH::CheckPresent().
The issue I have seen with these accelerometers is that the CS pin is very sensitive to glitches, so it needs to be kept away from all the other signal wires. However, I have used a LIS3DH successfully with approx. 1m of unscreened 8-core cable and a Duet 2. I have also used one with 1m of ribbon cable, but I had the CS conductor at one end of the cable and a ground conductor between it and the next one.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@dc42 Sorry it took so long. I had a busy week. Thanks for taking a look!
-
Can you get one a little clearer of the black chip in the middle?
-
-
Thanks that's better. @dc42 should be able to make out what that is.
-
