I have Intel Aero Drone. I went over all the instructions and tried to arm the motor using the remote control but nothing happened. No response at all. I connected to drone AP using my phone and tried to control the drone using Qgroundcontrol app. I could change the flight mode but nothing more worked. The arm command always rejected.
I updated the OS, BIOS, FPGA and PX4 to lasted version but nothing changed.
How can I figure out whether the problem is in hardware or software?
Another question, In the released notes, you mentioned that dronekit is available in the OS. I tried to connect using dronekit but I got exceptions when I tried to execute:
vehicle = dronekit.connect('udpin:127.0.0.1:14550')
I got exceptions like :
Exception in message handler for HEARTBEAT. mode 65536 not available on mavlink definition. PREFLIGHT FAIL : MAG # 0 UNCALIBRATED. ......
But when I tried to connect using mavlink-routerd like :
mav = mavutil.mavlink_connection('udpin:127.0.0.1:14550')
It works perfectly and I get HEARTBEAT packets.
I am really confused why it cannot connect using dronekit. Is it possible to be related to the first issue so that dronekit cannot connect to drone?
I hope you can help me to solve that problem as soon as possible.
Thank you for your interest in the Intel® Aero Platform.
Did you make sure the orange LED on the remote control receiver located on the bottom side of the drone is on (like in 'paired' condition)? You should see a steady orange color. If the LED is blinking or is not illuminated at all you are not paired, in that case you should check the Troubleshooting section from the Getting Started Guide http://www.intel.com/content/dam/support/us/en/documents/boardsandkits/aero/intel-aero-rtf-drone-get... http://www.intel.com/content/dam/support/us/en/documents/boardsandkits/aero/intel-aero-rtf-drone-get..., "The orange LED on the remote control receiver is blinking".
I wouldn't be able to tell you if the dronekit issue is related to the connection issue, but it would be a good idea to first solve that issue and then proceed with the dronekit one.
how can I do full calibration? I could not find this option. When I connected with AP and open the application, a loading green line start moving and after it finishes, I can change the flighting mode. When I choose arm, it said "Arm Rejected" and no GPS information appears in the app.
lstrano, when you talk about calibrating the drone from within QGroundControl, do you refer to something like the information from these two links?
Please correct me if I'm wrong
I guess there is a problem in sensors. In Qgroundcenter, I have red small circles beside : Compass,Gyoscope and Accelermeter sensors and green circle beside Level Horizon.
How can I fix that?
Could you please provide the output of entering "get_aero_version.py"?
Also, the sensor can appear red in QGroundControl when they need calibration. Could you please try to calibrate each sensor individually by clicking on the sensor and following the instructions? The sensors should turn green after that, you should also be able to arm the drone after that (having them in red can cause the drone not to arm). Check this link for further instructions https://qgroundcontrol.gitbooks.io/qgc-user-guide/content/setup_sensors.html https://qgroundcontrol.gitbooks.io/qgc-user-guide/content/setup_sensors.html.
Any other error message that you can provide (if any) will be of great help!
I am so sorry to be late.
Yes, now it works using QgroundCenter but the remote controller sometime works and most of the time does not and I am not sure why.
It sounds like the remote is not paring to the receiver on your drone. When the drone is not arming from the remote, is the orange LED on the receiver solid or blinking? Please try the following steps to bind the remote and the receiver.
After the binding, try to power off the drone and the remote. Then power on the remote first and then power on the drone. The binding should happen automatically and you should be able to arm your drone.
Yes, It worked! Thank you.
Toady, when I was flying the drone, it dropped with ground because of my bad navigation. The access point does not work anymore and when I connect the drone with monitor and after "Intel Aero" logo, the screen goes black and nothing happens (the OS does not work). I tried to boot from external flash with ubuntu and after I chose try ubuntu the screen went black too. I have damaged the GPS antenna but It is still connected with the board. How can I solve this problem and figure out If I made and damage to the board itself?
another question related to last one, I have another board (I bough it individually without the drone). I changed the old one with the new. when I press power button, It works for few seconds and turn off automatically.
Could you please help me?
We're sorry to hear that. Have you tried to re-flash the Aero image and BIOS? Here you can find the instructions to perform it: https://github.com/intel-aero/meta-intel-aero/wiki/02-Initial-setup https://github.com/intel-aero/meta-intel-aero/wiki/02-Initial-setup.
The old board cannot continue booting at all. When I want to boot from flash and after choosing the boot partition, it just stuck and nothing happens. I guess it is damaged. The strange thing that when I changed the board to new one and tried to turn it on, it started to seconds and automatically turn off again. Is it possible that the power supply on the drone is damaged too?
I am confused.
We would like to know if the behavior is the same of the board when you have it sitting on your desk. We mean the coumpute board not connected to the drone.
We'll be waiting for your reply.