ardupilot/libraries/AP_Scripting
Michael du Breuil 84c2b18e43 AP_Scripting: Support enum types, add millis() remove manual GCS wrapper
This introduces enum types for range checking/returns, adds a millis(() call
(this returns a uint32_t), and moves over to an auto generated version of the GCS binding
2019-05-11 18:25:43 -07:00
..
generator AP_Scripting: Support enum types, add millis() remove manual GCS wrapper 2019-05-11 18:25:43 -07:00
lua AP_Scripting: Reenable file IO 2019-04-26 08:07:19 +10:00
scripts AP_Scripting: Support enum types, add millis() remove manual GCS wrapper 2019-05-11 18:25:43 -07:00
AP_Scripting.cpp AP_Scripting: Add a debug level param 2019-04-11 23:03:20 -07:00
AP_Scripting.h AP_Scripting: Add a debug level param 2019-04-11 23:03:20 -07:00
README.md AP_Scripting: Support enum types, add millis() remove manual GCS wrapper 2019-05-11 18:25:43 -07:00
lua_bindings.cpp AP_Scripting: Support enum types, add millis() remove manual GCS wrapper 2019-05-11 18:25:43 -07:00
lua_bindings.h AP_Scripting: Enforce a time limit for a script 2018-11-14 01:41:35 +00:00
lua_boxed_numerics.cpp AP_Scripting: Support enum types, add millis() remove manual GCS wrapper 2019-05-11 18:25:43 -07:00
lua_boxed_numerics.h AP_Scripting: Support enum types, add millis() remove manual GCS wrapper 2019-05-11 18:25:43 -07:00
lua_generated_bindings.cpp AP_Scripting: Support enum types, add millis() remove manual GCS wrapper 2019-05-11 18:25:43 -07:00
lua_generated_bindings.h AP_Scripting: Support enum types, add millis() remove manual GCS wrapper 2019-05-11 18:25:43 -07:00
lua_scripts.cpp AP_Scripting: Add a debug level param 2019-04-11 23:03:20 -07:00
lua_scripts.h AP_Scripting: Add a debug level param 2019-04-11 23:03:20 -07:00

README.md

AP_Scripting

Enabling Scripting Support in Builds

To enable scripting the --enable-scripting flag must be passed to waf. The following example enables scripting and builds the ArduPlane firmware for the Cube.

$ waf configure --enable-scripting --board=CubeBlack

$ waf plane

To run SITL you can simply use the sim_vehicle.py script which will wrap the configuration, compilation, and launching of the simulation into one command for you.

$ Tools/autotest/sim_vehicle.py --waf-configure-arg --enable-scripting -v ArduPlane

Adding Scripts

The vehicle will automatically look for and launch any scripts that are contained in the scripts folder when it starts. On real hardware this should be inside of the APM folder of the SD card. In SITL this should be in the working directory (typically the main ardupilot directory).

An example script is given below:

function update () -- periodic function that will be called
  current_pos = ahrs:get_position()
  home = ahrs:get_home()
  if current_pos and home then
    distance = current_pos:get_distance(ahrs:get_home()) -- calculate the distance from home
    if distance > 1000 then -- if more then 1000 meters away
      distance = 1000;      -- clamp the distance to 1000 meters
    end
    servo.set_output_pwm(96, 1000 + distance) -- set the servo assigned function 96 (scripting3) to a proportional value
  end

  return update, 1000 -- request to be rerun again 1000 milliseconds (1 second) from now
end

return update, 1000 -- request to be rerun again 1000 milliseconds (1 second) from now