Developer

3689432775?profile=originalHi there! Finally you can pre-order the ArduIMU V3 here.. You can find more info abut it in my last post here

The final version of the board for full production is here, I'm expecting to start shipping them this Friday or Monday. 

We are still working on documentation and giving the final cosmetic touches to the example code to have it ready before you have one in your hands and at the same time we are shipping samples to developers to do a full DCM integration.

 

From now on our new color will purple! All our new products will feature a Lilypad style look! 

 

(Note: this is a stand-alone IMU, and is not designed to be a replacement for the "Oilpan" IMU shield of ArduPilot Mega.)

E-mail me when people leave their comments –

You need to be a member of diydrones to add comments!

Join diydrones

Comments

  • How is magnetometer data normally fused?

    Is it just a matter of resetting the yaw/heading gyro data every n clock cycles? So gyro is only allowed to drift so far before it is re-"initialized" using tilt-compensated compass data?

    It would seem like Gyro would be given preference in the short term and Magnetometer over time.

  • agreed, thanks

  • Developer

    The same "slow" and bad quality magnetometer that I was referring to (for MPU-6000) is exactly the same sensor that will have to be used on the MPU-6050. Both sensors are identical. The only difference is that MPU-6050 is limited to i2c and MPU-6000 can be used with both protocols SPI and I2C (I don't even know why they ever released the MPU-6050, makes no sense if you can do the same with the MPU-6000, price maybe?).  

  • Yes that's what I thought thanks, This was a response to Logans earlier question suggesting 9DOF can only be achieved with 6050. So, it's not the case, both 6000 and 6050 support the same fusion options.

  • 3D Robotics

    The only difference between the MPU-6000 and MPU-6050 is that the first uses SPI and the second uses I2C. Lots of experience has taught us that SPI is the more robust interface for our purposes. The only reason Invensense released I2C is that lots of phones and consumer electronic devices use it, but it's not ideal for UAVs.

  • @Jordi Yep I know you use mpu6000, actually I was jut saying that Fabios FreeIMU uses mpu6050. I'm in no hurry for the V3 sensor fusion :) 

    From what you have said before the mag won't integrate to the 6000 fusion because the 6000 only supports slow mags. So if you have a mo, is there any difference between mag support on 6000 and 6050? I didn't think there was.

  • Developer
    Jackub use any one that says 328 with 16Mhz. Duemilanove should also work. If not you may have one without bootloader please contact costumer support for a free repair.
  • Developer
    @Fab we have sensor fusion on APM 2.0 and is heavily tested but we don't have a release date for ArduIMU v3.0, but can be easily imported from APM 2 code.
  • Hello,
    please, can you explain me which program can I use for ArduIMU V3 test? I know that I have to use Arduino for loading test code. After that which software will works with this test code?
    And the second question is which type of board I have to set in Arduino for test code loading? "Arduino Duemilanove or Nano w/ ATmega328" is the right?

    Thank you
    Jakub

  • Developer
    @Fab, seems like you are getting confused. We only use mpu6000 and it has sensor fusion.
This reply was deleted.