This application was designed to help you test your ArduIMU V2 by showing graphically and numerically all of the data being output from the IMU.

You can download the Setup here: ArduIMUTest Setup (3 MB)

This version of the Test App uses the MSCOMM control, so the max COM port number is 16 (unfortunately a limitation set forth my Microsoft).

Before starting the application, make sure your ArduIMU is sitting flat with the serial cable towards yourself. When the application starts, it will automatically try to find the right COM port and it defaults to 38,400 baud.

To reset the ArduIMU, click Disconnect and Connect again on the application. It takes about 10 seconds for the ArduIMU to boot up and start sending serial messages so please be patient.

No need for LabView runtime! Yay! However, it now requires DirectX 8 runtime :)

EDIT: A special thanks to Michal for providing the 3DS file and texture map! Thank you Michal!!!

Views: 3059

Tags: Application, ArduIMU, HappyKillmore, Test, VB6

Comment by Paul Mather on November 26, 2009 at 9:14pm
I added the DX8VB.dll that apparently isn't a part of the DirectX install anymore (which is something I need to consider for future developments!)
Comment by Krzysztof Bosak on March 9, 2010 at 6:17pm
Here it is, the thread.
My test:
http://vimeo.com/10049131
Comment by Paul Mather on March 9, 2010 at 7:37pm
Ok, v1.1.8 should have the yaw smoothed out. Do you think I should have a scaling factor for the accelerometers? That way it might be more useful if your output is only small movements. I'll also look into the naming of the fields.
Comment by Krzysztof Bosak on March 10, 2010 at 11:02am
I don't think the different scalings are necessary.
This is what I have typed on vimeo:
No way you can jump off scale if your G rating of accelerometers is 1.5, 3, 6 or 11G...
In practice in autonomous flight G scales are 1..2G in Z, -1..1 in the remaining axis. With manual flying you get -2..4G on Z and -1.5..1.5 on X and Y.
All values typical for agile, overpowered EasyStar but also other high-wingers/trainers.

Therefore I would suggests something close to EasyStar ranges mentioned.
Above 4G home-made toy aircrafts start to bend and decompose anyway.
Comment by Krzysztof Bosak on March 10, 2010 at 12:26pm
Ehh, something went wrong during reinstall (sounding like Sonic something plugins)
and cannot access the app anymore, even it Hyperterm can see things.
+++RLL:0.2,PCH:-0.5,YAW:59.2,AN0:0.0,AN1:0.0,AN2:-0.0,AN3:2.9,AN4:4.2,AN5:102.6,***
Probably I have changed something but don't remember what.
Comment by Krzysztof Bosak on March 10, 2010 at 12:30pm
Got it. The terminal window IS NOT showing the RECEIVED strings, but PARSED strings.
big difference when debugging. So the protocol needs !!!.
Now the funny part. Ardu GS fast message (roll/pitch) needs +++, while Ardu GS slow message (lat/lon) needs !!!.
On the other hand IMU test fast message needs !!! for roll/pitch
What a mess.
Comment by DODY on March 10, 2010 at 12:41pm
very nice DODY

Developer
Comment by Mark Colwell on March 10, 2010 at 12:44pm
Well, throw in some binary to and that's what in dealing with...
Comment by Paul Mather on March 10, 2010 at 1:10pm
I didn't make the protocol...

3D Robotics
Comment by Chris Anderson on March 10, 2010 at 1:28pm
Krzy, we're cleaning up the protocols across the board for Mega. Thanks for the constructive feedback.

Comment

You need to be a member of DIY Drones to add comments!

Join DIY Drones

Social Networking

Contests

Season Two of the Trust Time Trial (T3) Contest has now begun. The fourth round is an accuracy round for multicopters, which requires contestants to fly a cube. The deadline is April 14th.

A list of all T3 contests is here

Groups

Advertisement

© 2013   Created by Chris Anderson.   Powered by

Badges  |  Report an Issue  |  Terms of Service