Developer

ArduIMU quadcopter part III

Hi all, I have a new drone in the family...

This tiny drone is able to do completely automatic flights, it can perform altitude hold (based on sonar sensor) and obstacle avoiding based on IR distance sensors (you could see the "black stange eyes" on the photo). It´s your personal droid...

Look at the video (the "tennis game" part it´s funny. Thanks to Ramon for the idea!!)

There are some new features in this thrid part... This is the list:

For outdoor configuration:

- GPS library support (actually UBLOX or NMEA)

- Position hold based on GPS

For indoor configuration:

- 4x IR distance sensors to detect obstacles (1.5m range)

- Obstacle avoiding (using distance sensors)

Common:

- Altitude hold based on Sonar (LV-EZ0)

- Automatic flight pattern (experimental).

--- Automatic takeoff

--- Position hold [outdoor] or obstacle avoiding [indoor] during a predefined time

--- Automatic descend

--- Automatic landing

- Added XBee for telemetry (and debug)

And some improvements in the code:

- New "radio test mode" to test radio equipment

- Revised control routines

Development

For the GPS position hold I had to implement the navigation algorithms for the quadcopter because it´s really different that the one used for planes...For this navigation it´s necesary to have the magnetometer to cancel the yaw drift in hover conditions. One thing I have observed is that you can only fly this tiny drone on very calm days because it´s too light for the wind... so it´s better suitted as an indoor drone. Then I started to think how to make a cheap way to navigate on indoor enviroments... I have one sharp IR disntace sensor so I start making some tests mounting the sensor in a servo to make a 180º scan. The idea was to mount 2 (or 4) of this sensors in the moving head.
On the tests I found that in this little machine the moving head caused some inestability, so I decided to mount 4 sensors in a fixed way. OK, this the cheap DIY version of an EXPENSIVE laser range finder, but it works...
there are many thing to improve and test, but it´s a promising start...


Details

Sonar module is an LV-EZ0. Because we don´t have any analog input available I use the PWM interface in a Port Change pin (PCINT20) to use an interrupt to read the sensor. (It´s recommended some solder skills to make this modification).

For the IR range finder (Sharp GP2Y0A02) I needed to use a separate Arduino Pro mini (again we don´t have any analog input free). This module connects to the ArduIMU via Serial port so we need to choose between GPS of range finder (outdoor-indoor decision).


On this III part, the hardware (ArduIMU) really show it´s limits... it´s not a problem of CPU power, it´s a problem of the limited I/O as I said before, so it´s time to move to the big brother, the new ArduPilot Mega Hardware... this new platform will be fantastic for this projects...


Behind the scenes

During the test of position hold I have some crashes (nothing important, only some broken propellers...) and there was a moment in that the quad performs not so good, so I start searching the reason. Again I suspect that it could be a vibrations problem so I decided to make a modified code to test the vibration on each motor.

As you can see I have problems on left motor, so I change this prop, also add a new layer of doubled sided foam tape to the ArduIMU and problem gone.

The code is here: Quad1_mini_test_motor_vibrations.zip (If you want to use it read the instrucctions)


Respect to the IR distance sensor, the first version was a moving head with a servo but this had some problems with vibrations that affect stability and also has a poor scanning rate, here is a photo of this prototype. Finally I decided to use 4 fixed sensors.

Codes

Some parts of this codes are still experimental but you can get it here:

Outdoor code (GPS): Quad_mini_1_27.zip . GPS libraries : GPS_libraries.zip

Indoor code (IR sensors): Quad_mini_1_29_rangefinder.zip External Arduino pro mini code: IR_distance1.zip


Old posts of this project: http://www.diydrones.com/profiles/blogs/arduimu-quadcopter-part-ii


Jose.




E-mail me when people leave their comments –

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

Join diydrones

Comments

  • Good job. I will try it on the ardupilotmega board.The PPM input pibn is different and the mega board has a pwm to ppm on board. I will let you know.!
    Earl
  • Admin
    Jose ,
    you inspire me to learn more and open my wallet :)
  • Developer
    @Jose Julio: Wonderful job!!! Man, you make it sound so easy. But I can imagine what nightmare is to joining this amount of variables. Until now I'm fighting to make an SPI connection, between the ArduIMU_V1 and the main board of my quadrotor. I achieved a nice serial integration with a modified version of Ardupilot's binary print, but I want to test SPI at high speed too (I want to leave UART to debug and I don't liked the results of NewSoftSerial). The hell is synchronize the boards to optimize the acquiring time. I'm being attacked by the interrupt errors on PCINT2 at the slave (ArduIMU). :(

    @Muot Vuong: Great idea! It would be nice. And adding a pressure sensor. I'm still missing it on that project (One more diabolic sensor to the Hell of PID's nightmare... :p).
  • Great job Jose! Now we need a custom shield with these sensors on it for the ardupilot mega. Call it QuadroShield! ;)
  • These IR distance sensors look like a huge improvement over previous indoor position sensors yet are end of life & don't seem to have a replacement. Wonder if they work near windows during daytime. 5 years ago, IR distance sensors were super expensive & had such short range they only worked on inverted pendulum robots. Theoretically you only needed 3 for obstacle avoidance.
  • Moderator
    Great Job Jose ... your platform is very nice and powerfull .... i'm working on your last version of software to support different kind of configuration ... quad hexa okto ecc
    Great Job .... !!!
  • What great fun.....really cool stuff...great video too...when do you find time to sleep? lol
This reply was deleted.