Gyro/Acceler. connections

[Faldor]

Hello, can any body tell me what we would connect the gyro/accelerometer to?

Thanks

EDIT: oh and the wires too, please?

[jtdowney]

They connect to the analog module on the cRio. Once connected you can use the built in support to draw meaningful values from the two included sensors. http://usfirst.org/uploadedFiles/Com...ual%20RevA.doc is the link to the manual on the included sensors. Hope this helps.

[viper110110]

I think the accelerometer connects to the digital sidecar, but the gyro definitely connects to the analog module

[Faldor]

Thank you both you guys have helped

[WGRAY]

You can check Labview Gyro example for a wiring diagram, however it is not available for the accelerometer vi even though they do have a specific vi for the ADXL345 12C, Maybe if enough people request it labview engineers will supply it.

[jtdowney]

viper110110 is right I hadn't read the accelerometer part of the sensor guide yet, this years gyro is an I2C/SPI gyro so it would connect to the digital sidecar.

[Faldor]

Thank you jt, but could you also tell me what cables i would be using, and exactly where on the digital sidecar, or the analogue module it would connect?

Thanks again

[Alan Anderson]

Originally Posted by Faldor

Thank you jt, but could you also tell me what cables i would be using, and exactly where on the digital sidecar, or the analogue module it would connect?

Read the Sensor Manual. It should give you lots of answers, but if you still have questions afterward, go ahead and ask them.

[Faldor]

I am still having issues as to where exactly on the digital sidecar they connect. So if anyone can help much appreciated.

[jhersh]

Originally Posted by Faldor

I am still having issues as to where exactly on the digital sidecar they connect. So if anyone can help much appreciated.

I2C is easiest. You can just hook the 4 I2C wires to the digital sidecar's I2C pins.

[Faldor]

thank you very much, you have helped me muchley

Kudos to you!

[PortugazD.Ace]

can anyone tell me where exactly the accelerometer connects to the cRIO or the analog breakout? and does anyone have any schematics?

[fiferdc]

Originally Posted by jtdowney

viper110110 is right I hadn't read the accelerometer part of the sensor guide yet, this years gyro is an I2C/SPI gyro so it would connect to the digital sidecar.

The gyro has a three pin connection (ground, power, signal), so how would it connect to the I2C, which has four connections? Connecting it to a digital I/O port also seems odd because you don't want a reading of either 1 or 0 for a heading. Team 3176 is still trying to get their gyro up and working. We have it connected to the analog breakout, but we're having problems getting a reading, so I'm not sure if that is due to a bad connection, or just a programming problem.

[Joe Ross]

Originally Posted by fiferdc

The gyro has a three pin connection (ground, power, signal), so how would it connect to the I2C, which has four connections? Connecting it to a digital I/O port also seems odd because you don't want a reading of either 1 or 0 for a heading. Team 3176 is still trying to get their gyro up and working. We have it connected to the analog breakout, but we're having problems getting a reading, so I'm not sure if that is due to a bad connection, or just a programming problem.

I2C is a serial bus, so you send and receive messages that contain multiple bits, giving you the range and resolution you need for the accelerometer.

[Alan Anderson]

Originally Posted by fiferdc

The gyro has a three pin connection (ground, power, signal), so how would it connect to the I2C, which has four connections?

There has been some confusion in the answers given. People talking about I2C and SPI are really referring about the accelerometer board, even though they might have slipped up and called it a gyro. The yaw rate sensor ("gyro") board provides a pair of analog outputs.

We have it connected to the analog breakout, but we're having problems getting a reading, so I'm not sure if that is due to a bad connection, or just a programming problem.

I don't know what you mean by "problems" here. What kind of reading do you get, and what are you expecting?

Do you see an appropriate battery voltage display on the Driver Station?