Jump to content
I2Cdevlib Forums

dylanetaft

Members
  • Posts

    4
  • Joined

  • Last visited

Everything posted by dylanetaft

  1. I was actually coming here to ask the same question. I think it's tied to the DMP. If the DMP is on, it will output at 100hz by default. If it's off, I think you can do 8kHZ down to what you specified depending on if you have the lowpass filter on or off.
  2. https://www.invensense.com/wp-content/uploads/2015/02/MPU-6500-Register-Map2.pdf There we go, buried elsewhere on their site. Register 31. Not sure what mg is. mass * gravity maybe? 4 = m*1gforce I guess.
  3. Argh, it's a register not in the register map documentation, but it's in I2Cdevlib.
  4. initialize() sets the accelerometer range to +-2g In that case, you're looking at +-16384 for 2g. You might need to use setFullScaleAccelRange to raise the sensitivity to +-4g I'm not aware of any force-sensitive interrupt, are you? There's a few things that can trigger an interrupt, FIFO overflow, i2c interrupt, data ready. That said, you might just want to analyze values over time. The DMP outputs at 100hz if enabled. Otherwise the device is adjustible via a divider setting and lowpass filter setting. The DMP is kind of nice. You'll get 10ms between samples. So if you find one sample has a high g force, and the LSB difference between that and the next is >=2g, that's a shock, I think.
×
×
  • Create New...