Hello and welcome to our community! Is this your first visit?
Register

Troubleshooting Guide

This page is a chapter in 'AeroQuad Manual'

This page shall provide users basic solutions to common problems. If you aren’t able to solve your individual issues with the steps provided here or they aren’t even listed here, please create a new thread describing your problem and all the steps you have done in the appropriate sub-forum or try to get help via our IRC channel!


Errors when compiling the software with the Arduino IDE

Problem:

Compiling the AeroQuad flight software via the Arduino IDE fails with a long list of errors saying “‘XXX’ was not declared in this scope” and "XXX: No such file or directory" like shown below.



Solution:

These error messages appear because you have copied the AeroQuad libraries to the wrong directory. Copy the whole content of the unzipped AeroQuad software to the sketchbook location of your Arduino IDE. This location can be found and/or changed under File » Preferences. Make sure to remove previous version of libraries which may already be there. After placing the files there, you’ll need to restart the Arduino IDE.

Arduino IDE Preferences - Here the sketchbook location can be checked and/or changed.Arduino IDE Preferences - Here the sketchbook location can be checked and/or changed.


In this case the sketchbook is located at C:\Users\"User name"\Documents\ArduinoIn this case the sketchbook is located at C:\Users\"User name"\Documents\Arduino

Connection issues to the Configurator

Problem:

Connecting the Configurator fails with a timeout error message.

Solution:

As this problem may have a huge number of causes, you’ll have to cycle through some basic steps to eliminate possible source of errors.

First of all, you’ll have to start with a minimum software setup. Thus you’ll need to upload the latest flight software again (at the moment: v3.2), this time replacing the with the software package provided UserConfiguration.h with this one. The only thing you have to modify there is the hardware configuration you are using. Moreover make sure that you don’t change anything else in the software like the baud rate (default value is 115200). If you are planning to use a wireless connection (e.g. XBee), please stick to a wired connection via USB first to reduce possible source of errors. In the next step upload the software to your flight controller board like described here.

After a successful upload, open the Serial Monitor from within the Arduino IDE by clicking on the “Magnifying glass” icon in the upper-right corner. Make sure to set the baud rate to 115200 in the upcoming window. Wait about 3 seconds to allow time for the flight software boot-up process to complete, the green LED should illuminate. Now, enter a ‘#’ (without the quotes) in the text box and hit “Send”. After that you should receive information about the software and hardware setup like shown below (or similar to this).

This (or similar to this, exact information doesn't matter) is what you should receive after sending '#'This (or similar to this, exact information doesn't matter) is what you should receive after sending '#'


If that’s the case, you may skip this paragraph. If you don’t receive anything, it means that the flight software has not finished initializing which is most likely caused by a hardware issue. To verify that your sensors are working correctly, please upload one by one the example sketches for all your installed sensors found in the Libraries folder (e.g. test sketch for gyro ITG-3200 is located at Libraries / AQ_Gyroscope / Examples / Test_ITG3200 / Test_ITG3200.ino). Each time after a successful upload open up the Serial Monitor and verify that you receive a continuous stream of valid sensor data.

Example output of the ITG-3200 sketchExample output of the ITG-3200 sketch


If you still don’t see anything, check your solder connections (shorts, cold solder joint etc.) and the orientation of your Logic Level Converter! Consider that one or more of your sensors may be damaged.

In the next step, ensure to use the latest suitable Configurator version (at the moment: v3.2 Windows / Mac)!
Open the Configurator and try setting the “Boot Delay” value to lower and/or higher values. Users of an AeroQuad32 board should choose 0 as the Boot Delay, all others should try values between 5 and 20 (choosing 10 solved connection issues of many users).

Now you are ready to give the connection to the Configurator another try! Ensure to choose the right com port and baud rate (115200). If connection is successful, enable one by one all your desired defines in the software to see if and where the issue comes up.

As there could arise a variety of different (individual) problems, please open up a new thread in our AeroQuad Configurator sub-forum describing all the steps you have done, if you are still not able to connect to the Configurator or need help to sort out a specific issue!

No sensor data visible in the Configurator

Problem:

There is no sensor data visible under the “Sensor Data” tab in the Configurator.

Solution:

This may be caused by a hardware issue with one or more of sensors. To verify that your sensors are working correctly, please upload one by one the example sketches for all your installed and not functional sensors found in the Libraries folder (e.g. test sketch for gyro ITG-3200 is located at Libraries / AQ_Gyroscope / Examples / Test_ITG3200 / Test_ITG3200.ino). Make sure that you set up the AeroQuad libraries properly as described here, otherwise you’ll get a bunch of compiling errors.

Each time after a successful upload open up the Serial Monitor by clicking on the “Magnifying glass” icon in the upper-right corner. Make sure to set the baud rate to 115200 in the upcoming window. Verify that you receive a continuous stream of valid sensor data.

Example output of the ITG-3200 sketchExample output of the ITG-3200 sketch


If you don’t see anything, check your solder connections, the traces on the shield and the orientation of your Logic Level Converter! Consider that one or more of your sensors may be damaged.

AUX1 channel moves with throttle channel

Problem:

When moving the throttle up and down the AUX 1 channel moves the same amount continuously switching between rate and attitude mode.

Solution:

When setting up your transmitter Heli mode was selected instead of Acro/Glider/Plane mode. Switch to Acro/Glider/Plane mode, rerun the transmitter calibration, and test again. If the problem still persists check if you have any mixes selected that is tying your AUX1 to your throttle. Last thing to try out would be to reset the model or change to a different model.

Tags:

This page has been seen 18,213 times.

    • Created by on
      Last updated by on