Hey, the MPU-9150 chip is obsolete, so I imagine you won't be able to make these anymore, is sparkfun planning to release an MPU-9250 version of this board?

I think it's time to inject some much needed information into this discussion.

I recently attended the Invensense Developer's Conference in San Francisco. While there I met a surprising number of fellow engineers with similar questions as I (and you) are asking. Namely, does the DMP function actually exist? I spoke directly with some of the Invensense technical team members and asked them this question.

So, can this IMU perform 9 axis sensor fusion? The short and final answer is NO. The IMU and breakout board here cannot do 9 axis sensor fusion. The hardware is not capable of doing it. And it's about time SparkFun finally corrects the information here and stops misleading its customers. I understand that the blame here largely rests with Invensense, who have been very cagey about releasing this information. But, it is out now, so the description should be fixed.

This IMU is identical to the 6150, in fact it IS the 6150 with the addition of a magnetometer. The DMP function on this IMU can do 6 axis sensor fusion if you can manage to initialize it properly and load the DMP code onto the chip. It can ONLY do 6 axis fusion. If you want 9 axis, it must be done on another MCU. Here you have a few options:

1) Get an MSP430 like the one on the MotionFit Wireless development board (out of stock on Invensense), log into the Invensense Developer's Corner, and download the MotionApps driver. Modify from there. This is more or less the only sure way to get 9 axis sensor fusion from Invensense directly. However, the TI development tool chain requires you use Code Composer, and if you want to use the Invensense library you will have to buy it as the free version has a code size limitation. It's about $400-500.

2) Port the code yourself to the MCU of your choice and integrate the magnetometer data yourself. They have, I believe, 3 versions in the aforementioned developer's corner. There is a version for the MSP430, a version for the Atmel UC3 development board, and a "general" version that is intended to be ported to various platforms. However, the only one that has full 9 axis sensor fusion is the one for the MSP430. The UC3 and general libraries are 6 axis only. You have to build the 9 axis functionality on top of this yourself, if you want it. This was confirmed by a developer at the conference. To get 9 axis you pretty much have to either use the TI toolchain with the MSP430 and Invensense code, or roll it yourself.

3) Code the sensor fusion algorithms yourself. Or find an open source version and adapt it to your application.

That's it! This breakout board, as it contains only the IMU and supporting circuitry, IS NOT PHYSICALLY CAPABLE of doing 9 axis sensor fusion. That can ONLY be done onboard an MCU. If you want 9 axis, it has to run on an external MCU. If you don't want to pay for the MSP430 toolchain, you can either find open source libraries or do it yourself. This is information coming directly from the Invensense team and exhibitors at the conference using the 9150 in their applications.

There is a 9250 planned, which will also not be capable of onboard 9 axis fusion. There is then a 9350 planned, with the same story. Only after the 9350 is there a possibility of the IMU performing full 9 axis sensor fusion onboard. But that is going to arrive late 2014, at the earliest.

Sparkfun, is this enough yet? Surely the text on this site is not carved into stone somewhere. The very first feature listed here is NOT a function that the 9150 can offer.

It would really be awesome if we could get Pete/Nick (or both) to do a tutorial or project with this breakout board. There seems to be a lot of unanswered questions. Keep up all the great work!!

OK, here is the deal with the DMP. Invensense isn't releasing a lot of information on how to use the DMP. You can signup on their dev site and get some drivers/applications, but you will not find a datasheet/register map explaining how to get DMP output. Bummer, so the only option is to work with what Invensense is going to give us. The 6 axis version of this chip, the MPU-6150 has DMP support, because the developers at i2cdevlib.com sniffed the I2C traffic from an MPU eval board and figured out how to program the DMP. The same should eventually get done for the MPU-9150. Someone has already sniffed the traffic for the 9DOF DMP. All of the I2C register information is there, all we need is someone to parse through it, which isn't an easy task. If you notice in the data dump, after the DMP is programmed, you can get 12 bytes of quaternion output (2-3 bytes per axis). Thank the devs at i2cdevlib.com for sharing how to do this!

I know this isn't ideal and we apologize that Invensense is not very clear about how to use the DMP when they overtly advertise it in the datasheets.

Strictly speaking, in terms of hardware, this chip has 3 sensors in one package and they are very high quality. We choose Invensense gyros for the UDB over a few other manufacturers due to their vibration tolerance for quad applications. Barring the DMP, this is a very useful and quality sensor, if you want to save space and cost.

Hmm..There doesn't seem to be any information on the DMP (digital motion processing) portion of this chip. I've even signed up for an account on the Invensense site to see what the developer section offers...nothing more on the MPU9150.

Perhaps we should try asking InvenSense? They only provide information on the MPU6050, and nothing really on the DMP...

I just did some googling and it looks like they finally released the registry map with descriptions!!!! YAY!!! http://www.invensense.com/mems/gyro/documents/RM-MPU-9150A-00v4_2.pdf Now we just need to turn it into a library. I'll be working on this in my free time. I'll post if I get anywhere.

I'm pretty disappointed that the breakout and example code won't allow us to do what the features say, and the DMP for this chip seems to be locked up secret info from invensense.

Top of the list is: "Digital-output 9-axis MotionFusion data in rotation matrix, quaternion, Euler Angle, or raw data format"

Sparkfun, can I suggest you either: * Provide info on how to enable the DMP for this chip (not another in the series) or * Either Remove the references to DMP features on your product page or put in a disclaimer that they aren't currently available.

I'm pretty cheesed that I purchased two of these breakout modules (specifically because they were supposed to do the heavy work on the DMP, not my microcontroller), and it looks like i would have been better off with another solution.

Having been disappointed by the lack of DMP usefulness on the ArduIMU, could someone point out where in the Invensense documentation quaternion or Euler angle output is even mentioned? I sure can't find it.

After I downloaded the 'example code' for this device, I noticed that the compass information was a bit strange. It turns out it is LOW ENDIAN, and not HIGH ENDIAN. So 'getMotion9' returns wrong information. OK you get what you pay for (free open source lib has bugs). Additionally, the code needs a serious review and re-factor. Hasn't anyone heard of "struct"? Using individual byte array indices is primitive and hard to read. And passing 9 integer pointers uses up a LOT of code on an Arduino. Try passing a structure pointer instead. You'll still need room for an SD library if you want to log data, after all, and the structure can be an integral part of the data you log. And using byte indices also obfuscates the fact that the magnetic values were incorrectly byte-swapped. And use 'protected', not 'private', so that people can easily derive a custom class without editing the library first ['private' should have NEVER been invented for C++]. OTHER THAN THIS, I'm happy with the 9150 (I'm doing some contract work related to that chip). It solves a lot of problems. And, of course, the breakout board lets you experiment with it. 'SO WHAT' if you need to write a program to integrate the information. At least you can collect the data without compensating for chip positions on the board. One thing worthy of note, is that it appears that the only way to get the motion interrupt to work is to EXACTLY follow the flowchart example in the data sheet. Otherwise you seem to get 'data ready' interrupts all the time. If you want to wake something up if it's moved, you'll need to use the low power accelerometer only mode with periodic wakeups, and tolerate one or two 'false hits' at the beginning of your sleep state. Then it works JUST fine. So thanks, Sparkfun, for making this available.

Great news everyone! It seems Pansenti has been gracious enough to create and Github-upload an Arduino library for the MPU-9150, including 9-axis fusion. Check the Github page for the library. Also this blog page.

For those that are not aware. I was getting pretty much garbage from the magnetometer. It drove me nuts. Then I found out that the magnetometer needs to be calibrated before the output is useful. You can roughly calibrate by rotating the magnetometer around each axis while logging the data to a file. Then plot raw values x vs y, z vs x, z vs y. Add an offset to each raw output value to center the circles on 0,0.. Hope helps someone else. There are more sophisticated ellipsoid fit methods but the above method will get you going..

Any update on getting DMP with i2c ?

Anyone succeed in getting the DMP output, using a bare microcontroller? It seemed to require uploading a binary blob over I2C.

I wish Sparkfun would make a hookup tutorial on this as well as how program your master. I can't figure out how to get it to work. I just get zeros on the serial port. I have GND, VCC, SDA, and SCL hooked up. Am I missing something?

EDIT:

Nevermind.

hi,

i'm looking for an arduino sketch which is working on arduino due and with sensor fusion . can anyone help me ?

thanks

rik

hi, i tryed to search in these comments a solution to not open another discussion and waste your time but i saw all the links below are giving me error

i'm just looking for an "arduino due" sketch to use this MPU9150 .. i'm using something that is giving me "raw data" but i need something else with a calibration algorithm inside to have "real data" obviously if you have something with even sensors fusion 6 or 9 will be appreciate

can anyone help me ?

thanks a lot

Hi, I did a 3d wireless mouse using a MPU9150, an atmega328 with arduino bootloader and RN42 v6.15 bluetooth module, and it had been working well, until a few days ago. It looks like the MPU9150 has stop sensing and now all that I get are zeros from gyro and accel. The sensor does not appear to be damage because the Who_I_Am register and mag responds well, and I dont get any I2C reaging errors. So if you have any idea of hoe to solve this I would appreciate it very much!!

Just a heads up for Sparkfun and everyone else: I was looking at this datasheet on the invensense website (rev 4.3) and they no longer show the clkout line on their pinout and description (it is still on the block diagram, though). Pin 22 on the 9150 is labeled as RESV (reserved, do not connect). Just FYI.

I have this connected to an arduino fio (3.3v), am running the newest sketch from github, but am getting a connection error and all zeros in the output.

Testing device connections... MPU6050 connection failed a/g/m: 0 0 0 0 0 0 0 0 0 a/g/m: 0 0 0 0 0 0 0 0 0

The wiring is really simple, as no resistors should be needed: 3v3 to vcc gnd to gnd a4 to sda a5 to scl

Using the i2c scanner, I detect the device on 0x68.

Any ideas?

There is a problem with description. "that combines two chips: the MPU-6050, which contains a 3-axis gyroscope, and 3-axis accelerometer." You are only describing the one chip that it contains. Also and contains the AK8975, a 3-axis digital compass

As of about a month and a half ago, Invensense release Embedded MotionDriver 6.1 which claims to be 9-axis solution. I am beginning to work on this, but will need some time. Anyone with any resources or input on this release be much appreciated!

I just wanted to say that the MPU9150 works great if you just want access to raw accelerometer, gyroscope, and magnetometer measurements to implement your own motion fusion algorithm on a micro controller. However, one of the main appeals of this chip and its sister, the MPU6050, is on-board data fusion. In short, Invensense (reluctantly) provided official support for on-board data fusion through their MotionDriver 5.1 library. The library is available through their developer corner, which is accessible through a free account.

I received an e-mail from Invensense on July 9th saying that they have released their MotionDriver 6.0, capable of doing 9DOF sensor fusion. I was under the impression that the library enabled on-board 9DOF sensor fusion. However, I came to the conclusion that the 6DOF motion fusion was handled on the chip, and fused with magnetometer sensor data using a pre-compiled library provided in the MotionDriver 6.0 software. This library only works with TI MSP430 and ARM Cortex Chips. This is the same approach that Pansenti (now Richards-Tech) took to enable 9DOF sensor fusion through his MPU9150 Arduino Library but with probably a slightly different motion fusion algorithm.

Working with Example code. Using AtMega328p to communicate. Thank you SparkFun!

SparkFun: Please isolate VLOGIC (pin 8) so that a separate supply can be fed in if desired. Something like a separate set of decoupling caps with a zero-ohm jumper to VDD. That way the zero-ohm can be depopulated and a flying lead attached with a 1.8V line.

I'm having a issue with this IMU. I'm connected to a Rabbit RCM4300. The maximum I2C speed I can read is about 80Hz. Any read operation takes 5-6 milliseconds for the IMU to respond to. I have a pair of ADXL345 accels and I can read those at greater than 100 Hz so I don't believe it's an issue with I2C comms. I was originally reading directly from the registers and also tried setting it up for FIFO using the same configuration as in the Richards Tech IMU library (https://github.com/richards-tech/RTIMULib), and then modified to update at 100Hz (their notes mention they have run this at close to 1000 Hz) and am having the same issue (not even trying to read from the mag right now). I also have a MPU-6050 breakout board and I'm having the same issue with that.

Any ideas why the MPU-9150/MPU-6050 is taking 5-6 ms to respond to a read request?

I wired one of these up with a PIC18 and an XBee to transmit to a PC, communicating to the MPU-9150 with I2C. I made the code available in a google code project. Here is a link to the youtube video and that links to a tutorial that links to the google code project:
https://www.youtube.com/watch?v=MJ3O1hsJ2XM

Raspberry Pi user with the MPU9150 here with a question.

I've been working with this and the MPU6050 for a long time now, probably around 4 different units so I'm sure the units are not defective as using different ones give me the same certain problem.

I'm taking readings from the MPU9150 (magnetometer and gyroscope), hooked up by jumper wires, and I occasionally get an error "IOError: [Errno 5] Input/output error" at one of the lines of code that either attempts to read or write to the device. It's exactly what would happen if I disconnected one of the jumper wires and the device disappeared. It only happens if I'm moving the device, not if it's just sitting still and taking sample readings. The jumper wires look like they're on securely. Thanks for any help.

I created a simple sketch using a modification of Jeff Rowberg's MPU6050 library that reads the MPU9150 gyroscope, accelerometer, and magnetometer data using the readAcceleration(), readRotation(), and readMag() functions checking for data updates using the data ready status register. For now it is at https://github.com/kriswiner/MPU-9150_Breakout. I hope it will soon be pulled to the Sparkfun repository. The sketch demos: * How to display output at a rate different from the sensor data update and fusion filter update rates * How to specify the accelerometer and gyro sampling and bandwidth rates * How to use the data from the MPU9150 to fuse the sensor data into a quaternion representation of the sensor frame orientation relative to a fixed Earth frame providing absolute orientation information for subsequent use. * How to use the quaternion data to generate standard aircraft orientation data in the form of Tait-Bryan angles representing the sensor yaw, pitch, and roll angles suitable for any vehicle stablization control application. Running the sketch on a 3.3 V 8 MHz Pro Mini Arduino microcontroller results in filter update rates of between 145 and 200 Hz for the open-source Madgwick and Mahony sensor fusion algorithms, respectively. This is about the same as one would get if a 9 DoF sensor fusion algorithm were functional in the on-board Digital Motion Processor, which it is not. Not too bad for the little Pro Mini!

I'm confused, does this chip have dmp or not? My reading is that it has dmp, but only 6 dof using the gyro and accelerometer. I've looked at the sparkfun, invensence, and some stm32f code that's on the internet. They all indicate to me that the same 6 dof dmp used on the mpu 6050 is on this chip. The data sheet indicates the same thing. I feel I wasted money on this item. Say it ain't so.

Does any body notice that SDA and SCL are inverted in the scematic ? On the PCB the SDA is pin 9 and SCL is pin 8. On the schematic SDA is pin 8 and SCL is pin 9.

Hi All: Is there any way to get either the delta t (time between measurements) or a time stamp for each data set (ie: XYZ gyro, XYZ Accel reading) out of the DMP as I need it for my application.

Hi There, I was wondering If anyone else found large offsets in the Z axis of the accelerometer before calibration? The tolerance levels for the chips are supposed to be +/- 15% but I am getting offsets around 30%. The X and Y axis are more or less okay but the Z axis accuracy is horrible. Anyone found a similar problem? Thanks!

Maybe someone can help... I'm having trouble reading anything else than 0's from the magnetometer... i2c bypass is enabled and I can read compass device id, but ASA registers come back and 0 (it's in fuse rom access mode) and hx, hy and hz are always 0. What am I missing?

We are trying to connect the MPU-9150 break board to arduino micro and we have used the example code suggested in the sparkfun document to read the raw data. Our Vcc was always 3.3V. And our Baud rate is 9600. Here is what serial port monitor shows.

a/g/m: 0 0 0 0 0 0 0 0 0 a/g/m: 0 0 0 0 0 0 0 0 0 a/g/m: 0 0 0 0 0 0 0 0 0 a/g/m: 0 0 0 0 0 0 0 0 0 a/g/m: 0 0 0 0 0 0 0 0 0 ...

When we use the code suggested in Arduino playground: http://playground.arduino.cc//Main/MPU-9150 Here is what we get:

-1 -1 -1 -1 -1 -1 -1 -1 -1 36.50 -1 -1 -1 -1 -1 -1 -1 -1 -1 36.50 -1 -1 -1 -1 -1 -1 -1 -1 -1 36.50 -1 -1 -1 -1 -1 -1 -1 -1 -1 36.50 -1 -1 -1 -1 -1 -1 -1 -1 -1 36.50 -1 -1 -1 -1 -1 -1 -1 -1 -1 36.50 -1 -1 -1 -1 -1 -1 -1 -1 -1 36.50 -1 -1 -1 -1 -1 -1 -1 -1 -1 36.50 -1 -1 -1 -1 -1 -1 -1 -1 -1 36.50 -1 -1 -1 -1 -1 -1 -1 -1 -1 36.50 -1 -1 -1 -1 -1 -1 -1 -1 -1 36.50 -1 -1 -1 -1 -1 -1 -1 -1 -1 36.50 -1 -1 -1 -1 -1 -1 -1 -1 -1 ...

We really have no idea where we are wrong. any comment would be appreciated.

Does anyone know how to sync the clock on this?

Does anyone know how much this IMU weighs? (preferably in grams)

Forgive my ignorance, but can anyone give comparison between the positional accuracy of 6 axis (without magneto) vs 9 axis? I plan to built motion capture glove (hand tracking), but I can't quite grasp whether absolute yaw (i.e magnetometer) is indeed essential for hand tracking. I'm going to use it for gripping VR objects. Thank

Does anyone have an interconnect schematic for this breakout and a ATMEGA 328P (with arduino boot loader)?

Why on earth is the Magnetometer X and Y axis flipped from the Accelerometer and Gyro's axis?

I am having problems communicating the MPU9150 to the Arduino Micro. I am using a logic level converter as the Arduino runs at 5V while the sensor runs at 3.3V. I read in some places that I might not need it but I thought it's just better to have one in place.

Logic Level Converter - https://www.sparkfun.com/products/8745 MPU9150 IMU Sensor - https://www.sparkfun.com/products/11486 Arduino Micro - http://arduino.cc/en/Main/arduinoBoardMicro

Here are my connections:

ARDUINO Logic Level Converter MPU9150 5V HV N/A 3.3V LV N/A GND GND (Both) N/A A4 Chan1 Tx SDA A5 Chan2 Tx SCL GND N/A GND 3.3V N/A VCC

I also have two 4.7k pull up resistors on the A4 and A5 on the Arduino connected to 5V and two 10k pull up resistors on the SCL and SDA on the IMU connected to 3.3V.

I have NOT connected anything on the IMU INT or AD0 pins.

I am running a standard I2C scanner code found here: http://playground.arduino.cc/Main/I2cScanner

My Arduino is unable to talk to the IMU I also tried this config with a friends IMU (which was confirmed to work) and it did not work with that either.

Is there something I am missing here? Please advise.

I managed to make the example code work on Arduino duo board. However, there is drifting in Quaternion readings. Anybody got this problem?

Could someone tell me how to make vibration noise reduction filter for this IMU, and how can i get the more accurate data possible

Just to clarify: this board does not need a logic level converter.

Forgive me if I'm wrong, but it works fine on the Uno's 3.3V

I'm considering purchase of this breakout, but I have two questions:

• as I'm more .Net, rather than micros, developer, I consider it for usage with .Net Gadgeteer mainboard, as it's I2C, seems natural to conect it to Gadgeteer I socket, but what about COUT, CIN, AD0, FSYNC, INT, shall they be just left unconnected or connected to some of the pins left available in socket?

• another thing, is it possible to calculate, with this breakout, speed and direction of movement over time? Calculating it on my micro, or doing it somewhat automagically using DMP?

Hi guys, Recently I buy the MPU9150 boards and want to get raw data from the on-board acc, gyro and compass. However the problem is that I am able to read acc and gyro data through primary I2C bus but cannot get any data from compass. Based on the datasheet, I first enabled the I2C bypass mode and then set the compass to single measurement mode. Also I have tried all slave addresses of magnetometer from 0x0C to 0x0E and tried to read many magnetometers' registers like WIA, INFO and HXL to HZH, but the compass never responded. Then instead of connecting to primary I2C, we tried to read magnetometer through Aux I2C bus(ESD, ESC), but didn't work. Then I used another MPU9150 board and tried the above methods again, but still compass never worked. Based on the above attempts, I was wondering that maybe something is missing in the compass setting. Our part of code related to magnetometer is shown below. Could you guys provide any suggestion? It's really in hurry! Many thanks for your kind help!

//Read Mag writeByte(add_slave, MPU6050_RA_USER_CTRL, 0x00); // clear I2C_MST_EN bit to drive Aux I2C bus line by the primary I2C bus msDelay(10); writeByte(add_slave, MPU6050_RA_INT_PIN_CFG, 0x02); //Enable I2C bypass mode to allow MCU to access Mag directly msDelay(10); writeByte(MPU9150_RA_MAG_ADDRESS, MPU9150_RA_MAG_CNTL, 0x01); //Enable Mag to single measurement mode msDelay(10); readBytes(MPU9150_RA_MAG_ADDRESS, MPU9150_RA_MAG_XOUT_L, 6, buffer2);

This is a nice sensor, but...

Sparkfun: Holy hell, are you ever going to do anything about your abso-ludicrous prices? This chip costs $17 straight from the manufacturer in single-unit quantities. That means that this tiny, 2-layer, simple breakout board (minus chip) costs $33!!! Even with (extremely minor) assembly THAT IS ABSOLUTELY INSANE. That is how much it costs per unit to pop over to Advanced Circuits and order several 2 layer boards with silkscreen and soldermask.

I really am having a hard time even comprehending the psychotic prices that you charge for breakout boards, especially this one. You seem to trying to demonstrate that the more expensive/complex the IC, the more expensive the breakout board must be? I hope you change your ways before people start to realize how ridiculous that is and leave you for your competitors.

Can anyone give a short summary of the challenges related to this board? Pros and cons vs. buying and assembling separate sensors?

Hi! Im working with MPU-9150 and have its working well on an Arduino Nano. Im using a library package "MPU9150Lib-master". Its a large package containing many libraries but it is working well. I`m in need of using two 9 degrees of freedom on one Arduino Nano board. Is that easy to accomplish? I know that wire library is used for I2C buss communication but it seams hard to find a solution because so many libraries are involved. Can any one please help me manage this in a pretty easy way? Regards Marcus

Somehow I made it work with Raspberry pi. http://veshnu.com/blogs/raspberrypi_mpu9150. But there is a lot of noise. How do u suppress it?

I'm interfacing this 9150 to a TI Stellaris Launchpad, which has a LM4F120. I'm trying to set the pull-ups for best results. This is my first time working with I2C buses and open-drain lines. I wasn't sure but the 10Kohm pull-ups on the breakout are not sufficient. And, when I engage the LM4F120's internal pull-ups, using either the weak or regular (I can't fine what the real difference is) I don't get good enough results to read data consistently. Through experimentation and use of a DSO, I've come upon a value of 500ohms place externally, i.e. essentially in parallel with, the 10K and I get what appears to be a very nice waveform on both data and clock. So the effective pull-up is a little lower than 500ohms. Any other experience out there on this? Does this seem right? Any suggestions on this process or else? Thanks

Pansenti over at

http://pansenti.wordpress.com/2013/03/06/an-arduino-driver-for-the-invensense-mpu-9150-what-fun/

says they have an Arduino driver for the 9150 that they will consider making available to the Sparkfun community "if there is enough interest". I suggest that you wander over that way and express interest.

When I run this example code, the gyro/accel work fine, but the magnetometer does not. I2Cdev reports that 0 bytes are read from the magnetometer. Any idea why this might happen? I've been checking and double-checking connections and code all day, and I'm all out of ideas.

I finally got the i2c working on a Xmega128a1U but I am trying to understand how I can read all 9 value at the same time? By same time I mean that the values were all clocked in from the ADC's at the same time. So I don't want values for another time interval. I will be reading the sensor data one right after another.ax->ay->az->gx->gy->gz->mx->my->mz(unless there is a better way please point out my errors)

I love the chip though I have not tried Sparkfun's breakout board. I have it as a part of a autopilot that I have developed. The DMP stuff was also interesting to me, and I joined the developers site and so forth, but found it easier to write my own sensor fusion stuff. I would love to pit my own 7 state Kalman against the MPU algorithms on my shaker table, however.

Yes, please please please do a tutorial!!!

Another request for either code/tutorial/example of using the DMP!

I'm having trouble understanding the app notes, and or how to read acceleration data from this device. Is this a simple request acceleration, response = acceleration data? How do you use the DMP?

Yes , but when trying dmp example it has no mag. and it has a drift...

I'm trying to connect this to an Arduino Uno. Here's what I've done but it's not working:

GND - Arduino GND
VCC - Arduino 3.3v
SDA - Arduino SDA (dedicated pin or Analog 4)
SCL - Arduino SCL (dedicated pin or Analog 5)
INT - Arduino digital pin 2

Everything else is disconnected. I'm just trying to get the sample arduino code to show sensor reads. With this configuration it's just returning "connection failed" and 0's for reads. Anybody know what's wrong?

does this chip work with 3.3v logic? datasheet says (VDD = 2.375V-3.465V, VLOGIC= 1.8V±5% or VDD) I'm guessing this means 3.3 logic(if VDD=3.3) or 1.8 logic.

Any thoughts on making an SPI version of this?

hi,

I am trying to connect this sensor with Ardupilot Mega, can someone help me with this?

Thanks in advance

Are SparkFun going to sell these ICs separate soon? I'd really like to have this guy in a project but needs it on my own board. Or is there another supplier?

Straight up questions- -does this sensor fusion stuff mean the chip puts out a stable yaw/roll/pitch referred to the local magnetic field vector? At the least can I get a stabilised roll/pitch referred to the local gravity vector? -is there a licence fee to be paid to get the sensor fusion stuff on board? If so how much -whats the rigmarole in getting sensor fusion onto the chip...can it come pre-fusioned, does each unit have to undergo a programming process? -with the sensor fusion....what's the update rate?

reason I ask is I've got a product that's currently got rate sensor/mag/acc sensors in three chips and logs all three. A post processing program downloads the sensor data and does the math. Two problems there....my math is buggy and I'd prefer to have it just working out of the chip and the other is that all the raw log data takes up memory....logging the yaw/roll/pitch only would save a lot.

Phil

5V VDD compatibility would have been nice...

How would you calculate velocity with this board?

Any Arduino code samples?

Is there a reason why you list: VDD Supply voltage range of 2.4V–3.46V; VLOGIC of 1.8V±5% or VDD

When the data sheet says: Supply Voltage, VDD -0.5V to +6V VLOGIC Input Voltage Level -0.5V to VDD + 0.5V

The datasheet doesn't seem to describe the registers, settings, etc, only how to talk with them over I2C.

We got this breakout and started testing it, namely the magnetometer. We compared the magnetometer in this chip with the HMC5883. You can check it out on our blog.

We also have performed a simple correction to the Example Code, that Sparkfun links here, in order to read the correct magnetometer values.

Feel free to give us your opinion and comments!

Cheers