Closed whymarrh closed 8 years ago
@EasternEdgeRobotics/developers this is up for grabs is anyone wants to take it
@whymarrh Currently working on this item.
The best library to use seems to be:
Sample code of interest:
Though they'll share the underlying communication protocol, is this different from the thruster stuff (#9)?
The thrusters are run through an I2C interface. The design decision to move i2c functions to the rasprime requires that the arduino communication (in system-manager branch) be translated to java.
I was considering using PI4J for this.
Ah, I completely misread this. After basic code for i2c communication is added, the IMU portion of the task can be handed off.
Current status of AltIMU-10 v3 components:
Device details:
Sensor | Address low | Address high (default) |
---|---|---|
L3GD20H gyroscope | 1101010b | 1101011b |
LSM303D accelerometer & magnetometer | 0011110b | 0011111b |
LPS331AP barometer | 1011100b | 1011101b |
Output format (I²C):
Sensitivity range:
Note that the AltIMU devices use predefined I²C addresses. We're going to use the grounded (low) addresses, however, we should avoid re-using any of these addresses to avoid future conflicts.
Reserved Addresses: 0x6A, 0x6B, 0x1E, 0x1F, 0x5C, 0x5D
The amount of time required to make IMU output useful to us is greater than the amount of time we have.
The IMU communication is via I2C