Correct Blimpduino LED/motor/servo behavior
The correct Blimpduino behavior modes are as follows.
First power-up of board, straight from the factory:
| Red Power LED: | On |
| Four green LEDs | Flashing in sequence, then altogether, then in sequence again: |
Blimpduino code loaded, RC receiver plugged in. Power on/calibration sequence:
| Red Power LED: | On |
| Four green LEDs | 1st: flashing in sequence. Then: North LED only while reading RC. Then: alternate N&S, E&W to signal RC control |
| Vectoring servo: | Responds to RC stick control |
| Motors: | Speed up when channel 2 stick is pushed up, slow down when pushed down. Channel 1 stick controls which motor spins faster |
Autonomous mode (RC not connected) startup:
| Red Power LED: | On |
| Four green LEDs | Flashing in sequence |
| Vectoring servo: | Moves up, level and then down while calibrating US sensor. Then tilting up or down for altitude hold depending on whether the board is above or below initial height |
| Motors: | Should spin. Direction/speed depends on what the sensors are seeing |
Autonomous mode (RC not connected); beacon present and visible to board:
| Red Power LED: | On |
| Four green LEDs | Light up in direction of beacon |
| Vectoring servo: | Then tilting up or down for altitude hold depending on whether the board is above or below initial height |
| Motors: | Should spin. Direction/speed depends on what the sensors are seeing |
Autonomous mode (RC not connected); beacon not present and or not seen by board:
| Red Power LED: | On |
| Four green LEDs | Off |
| Vectoring servo: | Stationary, usually titled down |
| Motors: | Should spin. Direction/speed depends on altitude |
Battery low:
| Red Power LED: | On |
| Four green LEDs | All flashing |
| Vectoring servo: | Stationary |
| Motors: | Off |
-
Comment by Mitch Patenaude on June 20, 2009 at 8:47am -
Just to clarify, until the blimpduino code is loaded using the FTDI cable, the RC mode will not work with the code that is loaded at the "factory". Is that correct?
-
3D Robotics Comment by Chris Anderson on June 20, 2009 at 9:17am -
Correct
-
Comment by david williamson on July 22, 2009 at 2:17am
-
because most domestic environments are very cluttered, wouldn't the ultrasonic eye be better employed using the ceiling as a height datum? What about unsoldering the ultrasound transducer & putting it on top of the blimp facing upwards then removing the altitude moter & sticking it back on upside-down?
-
Comment by Neal McBurnett on January 9, 2010 at 12:03am -
That's a real problem and a clever idea, but I bet it is a hassle (and unattractive) to put the sensor on top and run all the necessary wires.. I also wonder if e.g. my ceiling (with bumpy textured plaster) would be a good enough surface to measure against.
Comment
Social Networking
Top Content
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
-
Terrain/Surface Mapping
118 members
-
Queensland
4 members
-
ArduPlane User Group
682 members
-
Documentation Editors
51 members
-
Moderators
24 members
Advertisement
© 2013 Created by Chris Anderson.
Powered by
You need to be a member of DIY Drones to add comments!
Join DIY Drones