Professional Documents
Culture Documents
1, JANUARY 2009
43
I. INTRODUCTION
44
Weight (g)
60.5
55.0
10.5
39.0
35.0
200.0
Fig. 1.
turbofan gondola at its base. Balloon size was 52. The vertical motor
controls altitude and the side motors control horizontal movements.
45
B. Ultrasonic sensors
Two ultrasonic sensors provided the autonomous blimp with
information on the environment. An ultrasonic, lightweight
SRF05 sensor (with a resolution of 1 mm and a very narrow
beam) was mounted facing downwards at the bottom of the
gondola to measure the distance from the blimp to other
objects. Sensor measurements were integrated by means of a
Kalman filter which sequentially estimated blimp altitude. The
other ultrasonic sensor, located in the forward-facing part of
the balloon, was used by the obstacle avoidance controller. In
this case, we selected a lightweight SRF10 ultrasonic sensor
with an operating range of up to 6 meters that could be
connected to the microcontroller via a standard I2C bus
interface.
C. Electronic components
An electronic board was custom-designed for this
application because no commercial board met with our
requirements (Figure 2). An appropriate communication
system was also designed and implemented. The main reasons
motivating this approach were the following:
A new motor speed control was necessary, firstly, because
the blimp could not be controlled using the original circuit,
which only worked at maximum speeds, and secondly,
because we could not control the new vertical motor with
the original board.
Good wireless communication coverage with a lightweight
circuit was desirable, so lighter components for
communications between the vehicle and the PC ground
station were selected, given that a wireless access point or
a wireless router could not be used because of the limited
payload capability.
A bidirectional communication link to send and receive
data from the blimp was required in order to be able to
send data to and from the blimp and the PC ground station
(in other words, we needed to close the control loop).
For the above reasons, two specific boards were designed: a
gondola onboard card and a PC interface card.
Gondola onboard card. This board included all the
electronic components necessary to control the three motors
46
The ground computer could both write and read from the
WCU using these functions. The design of the function
interface was such that the programmer was not required to
deal with serial port characteristics and the communication
protocol between the blimp and the computer. The interface
had ten user-friendly functions so that the programmer could
develop software to move the blimp in few minutes.
D. Onboard software
The onboard software processed the sensor measurements
and sent them to the PC ground station. These data were
received by the PC ground station and used to compute new
control signals for the gondola micromotors. The WCU in the
PC interface card sent control data to the onboard WCU,
which were used by the microcontroller to set the
corresponding commands for the micromotors.
IV. BLIMP NAVIGATION SOFTWARE
The navigation software provided limited autonomous
operation of our blimp due to:
The lack of odometry.
Misalignment caused by wind gusts and temperature
changes.
The non-linear nature of propeller action.
Blimp operation in three dimensions.
The control system for our autonomous blimp was designed
basically to keep the blimp moving in a straight line if its path
was clear, maintaining the desired horizontal speed and
reference altitude. When a head-on obstacle was detected the
control system attempted to maintain a certain distance from it.
Assuming a low speed, the control problem could be
decoupled in two sub-systems describing motions in both
vertical and horizontal planes [11].
Although some blimp control approaches are based on the
vehicle mathematical model (see [11] and [12], for example),
we preferred not to implement an analytical controller because
the blimp has complex dynamics due to its nonlinear
characteristics and environmental influences (air gusts,
temperature, altitude references, etc). We implemented both
de(t )
dt
(1)
47
a)
b)
Fig 4. Behavior of the PID altitude controller when the altitude
reference is set to 1 meter. a) Experiments in environment 1. b)
Experiments in environment 2.
48
49
b)
Fig. 11. Behavior of the fuzzy altitude controller when the altitude
reference is set to 1 meter. a) Experiments in environment 1. b)
Experiments in environment 2.
Fig. 10. Behavior of the fuzzy altitude controller when the blimp
descends.
a)
50
sensors were used for navigation; the small payload also did
not permit inclusion of an inertia sensor or miniature wireless
camera usually used for global position calculation [6].
We also implemented onboard and PC programs to control
the blimp with the PC ground station, with the communication
software module capable of receiving onboard sensor data and
sending commands to the blimp (as well as facilitating future
application developments).
Two different controllers were implemented. An altitude
controller maintained the blimp at a certain distance from the
floor and a second controller avoided obstacles in the path of
the blimp. The altitude controller was implemented using two
different approaches: PID and fuzzy logic. A first experiment
was designed to compare the two controllers operating in the
same conditions, so as to determine which controller was
better suited to controlling blimp altitude.
In the first scenario, both controllers were tested on an
alternating basis in one environment (a corridor), an
experiment that was repeated eight times. Similarly, the blimp
was tested in a second environment (a computer room) with
the same perturbations on the blimp for both controllers.
Comparative results show that the fuzzy logic controller
produced balanced behavior in either of the two environments.
The PID altitude controller performed slightly better than the
fuzzy logic controller in environment 1 (see Figure 14a) but its
performance in environment 2 was significantly poorer than
that of the fuzzy logic controller. A better PID controller in
other environments would require online adjustment of PID
parameters. Using a fuzzy logic controller, on the other hand,
does not affect the behavior of the blimp too much and the
controller parameters do not require modification.
A second fuzzy logic controller, designed to avoid head-on
collision with obstacles while the vehicle was navigating in the
indoor environment, showed good experimental performance.
Fig. 14. Behavior of the blimp in a corridor. The blue line is the safety
distance from the floor.
V. CONCLUSIONS
In this paper we have described the construction of a small
blimp based on a commercial kit, with the main goal of
designing and implementing different control navigation
techniques. It was necessary to change the vertical motor of
the commercial blimp and develop onboard control hardware,
including a wireless radio connection with a PC ground
station. Due to the vehicles small payload only two distance
a)
51
[2]
[3]
[4]
[5]
b)
Fig. 13. Comparative results for the PID and fuzzy logic controllers. a)
Experiments in environment 1. b) Experiments in environment 2.
A. Elfes, S. Siquiera, M. Bergerman, and J. Guimaraes, A semiautonomous robotic airship for environmental monitoring missions, in
Proceedings of the 1998 IEEE. International Conference on Robotics
and
Automation,
1998.
[6]
[7]
[8]
[9]
[10]
[11]
[12]
[13]
52