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

  • Gerard, thanks!

  • Developer

    @Gerard,

         I'm quite certain that I'm right now.  I tried connecting the optical flow sensor to the 3v side of the level converter (see pic below) and the MPU6000's values were no longer garbled.  I think you could try the same thing with your existing sensor and you'd see the problem will go away.  I used a jumper wire on just the MISO line and touched it to the 3rd pin down on the right side of the level converter.

    3692340006?profile=original

  • i am getting shifted heading angles on IMU , 90deg turn of compass is not real 90 at my output , can i get your codes (harry), thanks in advance, regards.  

  • Hi,

    I've been working on a custom software for the ArduIMU v3 for logging airplane attitude (MPU-6000 & Magnetometer), speed (MPX7002), height (BMP085), position (MTK GPS) and current (Attopilot sensor). I've had quiet a lot of problems to upload to the board. I tried several cables and computers. Somehow I managed to find a working solution using my Laptop.

    So far so good. However, some days ago, when coding the software for the magnetometer, uploading stopped working without any clear reason. Until then, Arduino uploaded the code, but on a regular basis it reported errors. The uploaded code seemed to work anyway. Suddenly I had to make several attempts until the code was uploaded and then it stopped working completely: "programmer not responding". When I power the board the green LED turns on, the yellow X-LED blinks once and after that it starts blinking brightly with a couple of Hz (this did not happen before).

    Does someone have an idea what happend?  Did the bootloader get corrupted? Is it worth to get an ISP programmer and upload the bootloader again?

    I do not know if the board belongs to the first batch with corrupted bootloaders (I bough it here in Germany at Lipoly). The date on the back of the board is 11/08/2011. 

    Thanks in advance,

    Andrés

  • @Randy: Haven't received it yet, but will let you know my results here. Perhaps both the chips have issues, otherwise your analysis seems something to look into. I do know for sure that the ethernet breakout is incorrect, so let's hope thats it.

    @Kirill: see page 10.

  • Jordi,

    do you have any new information about a new code for arduimu v3?

    thank you

  • That's strange... What board should I select? Arduino Duemilanove 328?

    I try to load the test code, compiling is done successfuly, but uploading results in crash (no messages about that it's Done and no any error messages at the same time, it's just waiting for something...). I'm uploading via FTDI cable (the cable is workable, checked with many other boards). All settings are set as said in wiki.

  • 3D Robotics

    Kirill: It has the bootloader already loaded.

  • Does it has Arduino bootloader by default? Or I have to burn it by myself?

  • Developer

    Gerard,

         I've seen the same issue but on the APM2 (which uses the same MPU6000 and also the same level converter).  The difference is that I'm attempting to attach the optical flow sensor instead of the W5100 chip.

    I  may be wrong but I think the MPU6000 messages become garbled because the level converter gets confused about the MISO line.  I think it's not sure which sensor is talking (i.e. doesn't know if it's the mpu6000 or external sensor) so it switches back and forth while the MPU6000 is trying to talk to the APM.

         You can see the problem in the picture I've attached below.  I attached a logic analyser while reading information from the APM2's barometer. 
                  Top picture: optical flow sensor is not attached.  the green box shows a good clean signal from the barometer.
                  Bottom picture: optical flow sensor is attached.  the red box shows false dips.
     
    So, I don't want to bias your testing, but I think that the new sensor you've ordered won't fix the problem.  I think you'll still see garbled messages from the MPU6000.  Looking forward to hearing from you once you get the sensor though, and I hope it does work!
    3692337351?profile=original
This reply was deleted.