Accelerometer Usage

[dc42]

@ccs86 said in Accelerometer Usage:

So I could physically swap the wires, or update to M955 P0 C"twck0+twd0"?

yes.

[TheBasedDoge]

I am trying to setup the Adafruit LIS3DH Accelerometer with no luck so far. I have the Duet2 Wifi. I think that it is connected, light is on, and i didn't get an error in the log for it not being able to connect, but I am not getting any data. I am getting a drive error in the log:

[CCS86]

@dc42 said in Accelerometer Usage:

@ccs86 said in Accelerometer Usage:

So I could physically swap the wires, or update to M955 P0 C"twck0+twd0"?

yes.

[dc42]

@thebaseddoge use P0 in your M956 command (same as in your M955 command), not P124.0.

[dc42]

@ccs86 it's probably a wiring issue. A few days go I updated the wiring instructions at https://duet3d.dozuki.com/Wiki/Accelerometers#Section_Direct_SPI_connection_to_a_Duet_main_board. The first photo in that section is the 1m long cable that I used successfully to connect the Adafruit board to the Maestro.

You might like to try connecting the accelerometer to the Duet first using short jumper wires. When you have that working, you can try the same connections with a longer cable, taking care to keep the CS wire away from the other signal wires.

[CCS86]

@dc42 said in Accelerometer Usage:

@ccs86 it's probably a wiring issue. A few days go I updated the wiring instructions at https://duet3d.dozuki.com/Wiki/Accelerometers#Section_Direct_SPI_connection_to_a_Duet_main_board. The first photo in that section is the 1m long cable that I used successfully to connect the Adafruit board to the Maestro.

You might like to try connecting the accelerometer to the Duet first using short jumper wires. When you have that working, you can try the same connections with a longer cable, taking care to keep the CS wire away from the other signal wires.

Could you tell us what wires are considered signal wires?

I can try short jumpers, but I feel very good about my wiring. This was a fresh piece of CAT6 off the spool, all terminals crimped with a proper tool (EDM jaws), and it is the minimum length needed (shorter than 1 m).

Is the 1k resistor still benefiting my setup?

[tekstyle]

@ccs86

is there any reason to use VIN instead of the 3V pin on the LIs3DH module?

[CCS86]

@tekstyle said in Accelerometer Usage:

@ccs86

is there any reason to use VIN instead of the 3V pin on the LIs3DH module?

Yes, because that is a 3V output.

The V_in pin can take a 3-5V input.

[CCS86]

@dc42

All re-wired with short jumpers... same issue.

[dc42]

@ccs86 please connect all the jumpers to the appropriate pins on top of the temperature daughter board.

[CCS86]

@dc42 said in Accelerometer Usage:

@ccs86 please connect all the jumpers to the appropriate pins on top of the temperature daughter board.

I would need that pinout, since it does not match the mainboard pinout.

[dc42]

@ccs86 the pilot is the same as on the main board except for TWCK and TWD.

[CCS86]

@dc42 said in Accelerometer Usage:

@ccs86 the pilot is the same as on the main board except for TWCK and TWD.

@dc42 Do I have this right? The error persists.

[dc42]

@ccs86 I'll try that configuration here.

[dc42]

@ccs86 this arrangement is working for me, using the following command:

m955 p0 c"twck0+twd0"

I tried without enabling the PT100 channels, and also after enabling both channels. I normally connect the 3.3V wire to the 3.3V pin on the accelerometer, but I tried connecting it to the accelerometer VIN pin to match your setup, and it still works.

[CCS86]

@dc42 Thank you.

I'm having trouble making out some of your wire colors. Is this correct?

[dc42]

@ccs86 yes, the wiring is as you have indicated.

[CCS86]

@dc42 said in Accelerometer Usage:

@ccs86 yes, the wiring is as you have indicated.

Thanks for sticking with me, I finally got it working! Not sure if it had more to do with connecting to both the main board and the daughterboard, or if I had made an error somewhere.

I am running into quite a few overflow errors now, but don't see the rhyme or reason. Reducing the collection call to one axis and 500 samples still reported overflows. But after adding the S parameter to the M955 command, I got it to log all 3 axis for 1000 samples without an issue. That M955 S parameter behaves differently than I expected:

Sometimes I get overflow errors at 400 Hz, but not at 1344 Hz

[CCS86]

Also, is there anything I can do to reduce apparent noise in the accelerometer signal? These peaks seem like anomolies. This is with the printer at rest and steppers disabled. The peaks look very periodic.

[T3P3Tony]

@ccs86 could those peaks be from your fan?