Jump to content
I2Cdevlib Forums

Search the Community

Showing results for tags 'I2C communication'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • I2Cdevlib Web Tools
    • I2C Protocol Analyzer
    • I2C Device Entry Interface
    • I2C Device Library API
  • I2Cdev Platform Discussion
    • Arduino (ATmega)
    • Arduino Due (ARM Cortex M3)
    • MSP430
    • Other Platforms
  • I2C Device Discussion
    • AD7746 capacitance-to-digital converter (Analog Devices)
    • ADS1115 16-bit A/D converter (Texas Instruments)
    • ADXL345 3-axis accelerometer (Analog Devices)
    • AK8975 3-axis magnetometer (AKM Semiconductor)
    • BMA150 3-axis accelerometer (Bosch Sensortec)
    • BMP085 pressure sensor (Bosch Sensortec)
    • DS1307 real-time clock (Maxim)
    • HMC5843 3-axis magnetometer (Honeywell)
    • HMC5883L 3-axis magnetometer (Honeywell)
    • iAQ-2000 indoor air quality sensor (AppliedSensor)
    • IQS156 ProxSense capacitive touch sensor (Azoteq)
    • ITG-3200 3-axis gyroscope (InvenSense)
    • L3G4200D 3-axis accelerometer (STMicroelectronics)
    • MPL3115A2 Xtrinsic Smart Pressure Sensor (Freescale)
    • MPR121 12-bit capacitive touch sensor (Freescale)
    • MPU-6050 6-axis accelerometer/gyroscope (InvenSense)
    • MPU-9150 9-axis accelerometer/gyroscope/magnetometer (InvenSense)
    • PanelPilot multi-screen digital meter (Lascar Electronics)
    • SSD1308 128x64 OLED/PLED driver (Solomon Systech)
    • TCA6424A 24-bit I/O expander (Texas Instruments)

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 2 results

  1. Hey everyone, I want first to thank a lot Jeff Rowberg for his work, because without him my project might not be so advanced. I will first present outlines of my project: The idea is to track arm position in 3D space, this by using 3 GY-521connected on a Teensy 2.0 board. All sensors are connected on the two I2C pins of the board and each of them is connected from one digital pin to the ADO of the sensor. Because sensors have only 2 addresses, I have created a loop that will change the ADO to HIGH for one sensor and 2 others to LOW. In that way, I will query data from only the sensor that is HIGH and at the end stock it in an array. When the 3 sensors have send their data I print the results and return in initial condition. Everything is going well, I have good results but their is still one thing that I can't fix: my second sensor, the one in the middle is delayed and this is really annoying. The point that is really confusing, is that others sensors work very well, if the problem might be due to the delay of querying result, the 3rd one should be worst, but it is not the case... Also It is not a sensor problem because I have already replace it twice... I Also have try to call only the second sensor without the two others and the delay persist. Is someone have any suggestion of how fixing this problem, I will be really grateful to him.
  2. Hey everyone, I want first to thank a lot Jeff Rowberg for his work, because without him my project might not be so advanced. I will first present outlines of my project: The idea is to track arm position in 3D space, this by using 3 GY-521connected on a Teensy 2.0 board. All sensors are connected on the two I2C pins of the board and each of them is connected from one digital pin to the ADO of the sensor. Because sensors have only 2 addresses, I have created a loop that will change the ADO to HIGH for one sensor and 2 others to LOW. In that way, I will query data from only the sensor that is HIGH and at the end stock it in an array. When the 3 sensors have send their data I print the results and return in initial condition. Everything is going well, I have good results but their is still one thing that I can't fix: my second sensor, the one in the middle is delayed and this is really annoying. The point that is really confusing, is that others sensors work very well, if the problem might be due to the delay of querying result, the 3rd one should be worst, but it is not the case... Also It is not a sensor problem because I have already replace it twice... I Also have try to call only the second sensor without the two others and the delay persist. Is someone have any suggestion of how fixing this problem, I will be really grateful to him.
×
×
  • Create New...