You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are using the onboard SDK with the A3 to control an industrial drone.
The Onboard SDK is running on an intel atom single board computer (Minnowboard x86 Ubuntu 14.04 LTS server), we are able to successfully take control of the aircraft using both the DJI OSDK sample application (Linux) and our own application.
Both in the simulator and actual flight we can takeoff and land using the interactive sample
When we try to do the sample "square" live (flying), the aircraft immediately turns due north and starts climbing. We stop the climb at about 15 meters height because the aircraft is on a tether.
The aircraft does not start the square.
In the simulator, the sample works correctly. That is the aircraft starts the square without turning or climbing first.
I don't know if this is relevant but I reviewed the telemetry and noticed that the altitude (z) indicated about -120m.
We confirmed that the flight controller was in P mode, GPS fix was obtained before takeoff
This behavior was identical on two different A3 flight controllers, two different single board computers.
Can you suggest some corrections? We need to be able to command precise movement.
Tariq
The text was updated successfully, but these errors were encountered:
Hello
We are using the onboard SDK with the A3 to control an industrial drone.
The Onboard SDK is running on an intel atom single board computer (Minnowboard x86 Ubuntu 14.04 LTS server), we are able to successfully take control of the aircraft using both the DJI OSDK sample application (Linux) and our own application.
Both in the simulator and actual flight we can takeoff and land using the interactive sample
When we try to do the sample "square" live (flying), the aircraft immediately turns due north and starts climbing. We stop the climb at about 15 meters height because the aircraft is on a tether.
The aircraft does not start the square.
In the simulator, the sample works correctly. That is the aircraft starts the square without turning or climbing first.
I don't know if this is relevant but I reviewed the telemetry and noticed that the altitude (z) indicated about -120m.
We confirmed that the flight controller was in P mode, GPS fix was obtained before takeoff
This behavior was identical on two different A3 flight controllers, two different single board computers.
Can you suggest some corrections? We need to be able to command precise movement.
Tariq
The text was updated successfully, but these errors were encountered: