[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Paparazzi-devel] I2C Questions

From: Christophe De Wagter
Subject: Re: [Paparazzi-devel] I2C Questions
Date: Wed, 1 Dec 2010 08:08:01 +0100

Hi Kurtis,

You can use many devices on the same I2C_DEV "=wires" but it is not recommended to use too many high-bandwidth devices.

The AIRSPEED_ETS_I2C_DEV points to which processor PINS you use. The LPC2148 has only 2 I2C devices, so there is certainly no i2c2 and further. This is something different from the I2C slave address which is a byte to address something connected on a bus. I believe the ArduIMU and EagleTree have different slave addresses and can be used on the same wires (e.g. I2C0)

But an IMU is important enough to give it a dedicated I2C_DEV if possible. 


On Wed, Dec 1, 2010 at 1:20 AM, Kurtis Kraemer <address@hidden> wrote:
I just received an ArduIMU that I would like to integrate into my Tiny2.11. I also have Eagle Tree Airspeed and Altitude sensors that I have not yet integrated.
Each of these sensors uses I2C, but I am uncertain whether or not I can use all of these sensors simultaneously through the single I2C bus on the Tiny/TWOG.
From what I can tell from the wiki (, I can set a particular I2C address for each module:
<param name="AIRSPEED_ETS_I2C_DEV" value="i2c1"/>
However, is there a limit to how many can be used? i.e. "i2c0", "i2c1", "i2c2", etc. Also, what is the parameter name for setting the ArduIMU address?
Is there anything else that I need to change to get them to work together?
As for wiring, do I just connect the SDA and SCL of each sensor in parallel with each other, or in series?
- Kurtis

Paparazzi-devel mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]