Application Programming Interface (API)
Last updated
Was this helpful?
Last updated
Was this helpful?
We provide open source API for development with the Kerloud UAV series, and candidate API interfaces will support C++, python and other languages. Details will be updated continuously in this part. Note that we assume users are familiar with basic concepts about ROS, and those who don't meet the prerequisite are recommended to go through official tutorials in .
The API in ROS (Robot Operating System) is implemented based on the official from the PX4 community.
Our maintained repositories are:
mavros (dev_kerlouduav branch):
mavlink (dev_kerlouduav branch):
Note that the offboard control demo code is delivered only with Kerloud machines, hence is not open source. More programming details will be illustrated in the tutorial section . We present here topics and services that are commonly used with our Kerloud UAV case.
This topic can be subscribed to obtain current UAV state. The message type is defined . We can obtain the landed state accordingly, e.g. if the field landed_state equals LANDED_STATE_IN_AIR, then the uav is in air.
To illustrate, suppose we'd like to arm the vehicle, three steps are needed.
Step 1, we have to define the service client.
Step 2, we define the arm command as follows:
Step 3, we can call the service
Similar with the ROS API in C++, ROS python API is implemented on basis of our maintained mavros and mavlink packages as well. The only difference is that all those topics and services mentioned above should be utilized with python.
Our maintained repositories are:
move(x,y,z, BODY_FLU=False): request the vehicle to move to a desired position defined in either FLU frame or ENU frame.
turn(yaw_degree): request the vehicle to turn to a desired yaw angle during flight.
land(): request the vehicle to land.
hover(): request the vehicle to hover at current position.
arm(): request to arm the vehicle.
disarm(): request to disarm the vehicle on ground.
return_home(height): request the vehicle to return home.
This topic is used to publish the position setpoint in the local or global frame, and then guide the uav to the desired position. Note that the reference frame in the ROS level is the ENU frame, while that for the autopilot is the NED frame. The message type is or respectively.
These two topics are used to publish the velocity setpoint in the local frame for both rover and multicopter modes. The only difference between them is whether the velocity information is with a timestamp or not. The message type is .
This service is utilized to set various modes for the UAV, such as arm/disarm, set offboard mode, etc. The message type is .
mavros (dev_kerlouduav branch):
mavlink (dev_kerlouduav branch):
The offboard control demo code is delivered with Kerloud machines as well, and it's explained in the tutorial section . For brevity, the low level message communication is handled within the Px4Controller class, and the friendly API for user programming is wrapped within the Commander class, partially listed below: