Okay, so I've read all the examples regarding the MPU-6050 (acc/gyro/temp), which to me seem very complicated (this one for instance: Arduino Playground - MPU-6050), and not intuitive at all, they also seem to run slow (<10 unfiltered and unaveraged readings/sec). All I want to do is to take readings and print them, no need to define every single register in the datasheet or access every single function the chip has and so on, just getting gyro, acc and temp, that's it.
Is it just me or is I2C extremely difficult to use? Frustrating..
I2C isn't that bad, just find a good youTube video on it. And that sketch isn't really as complicated as it is long. Albeit, those devices ARE pretty complicated, and unless you find a really simple version with built in libraries to make things easier, dealing with the source code yourself will be difficult. Unfortunately, it doesn't seem that that device does any filtering or combing of the data and simply outputs all the raw values. Either you find the raw values that you need and then delete all the other stuff, or find a library that can make everything nice and simple for you.
Honestly, you can pretty much ignore most of the defines for the most part, they are excessive because they pretty much defined every single bit/byte in every single register that is used. If you skip down to the program part, you can see the structs that are actually used are quite small, also try google searching tutorials with the part number.
cypherrage:
I2C isn't that bad, just find a good youTube video on it. And that sketch isn't really as complicated as it is long. Albeit, those devices ARE pretty complicated, and unless you find a really simple version with built in libraries to make things easier, dealing with the source code yourself will be difficult. Unfortunately, it doesn't seem that that device does any filtering or combing of the data and simply outputs all the raw values. Either you find the raw values that you need and then delete all the other stuff, or find a library that can make everything nice and simple for you.
Honestly, you can pretty much ignore most of the defines for the most part, they are excessive because they pretty much defined every single bit/byte in every single register that is used. If you skip down to the program part, you can see the structs that are actually used are quite small, also try google searching tutorials with the part number.
I tried that approach to shred away all the stuff I didn't need, but the way it's structured with all the functions within other functions and all the pointers make it too hard to follow, at least for me that is. Also there's something about 'swapping' bytes, and lots of terms I've never used before such as '&', 'typedef', 'struct' and other stuff.
