ardupilot/libraries/AP_Scripting
Tom Pittenger b5e2f9aa0a AP_Scripting: change some _INFO msgs to _CRITICAL/ERROR 2023-11-22 00:07:05 -08:00
..
applets AP_Scripting: added more params to revert script 2023-11-17 07:23:28 +11:00
docs AP_Scripting: add success status to serialLED:send and serialLED:set_RGB 2023-11-20 19:22:20 +11:00
drivers AP_Scripting: added HobbyWing DataLink lua driver 2023-11-06 07:12:35 +11:00
examples AP_Scripting: add bindings for fence 2023-11-07 07:52:14 +11:00
generator AP_Scripting: add success status to serialLED:send and serialLED:set_RGB 2023-11-20 19:22:20 +11:00
lua
modules/MAVLink
tests
.gitignore
AP_Scripting.cpp AP_Scripting: change some _INFO msgs to _CRITICAL/ERROR 2023-11-22 00:07:05 -08:00
AP_Scripting.h AP_Scripting: add support for dependencty on manual methods, remove handling of mission commands without AP_Mission 2023-10-17 10:23:20 +11:00
AP_Scripting_CANSensor.cpp AP_Scripting: don't include CAN support on periph if there is only one CAN port 2023-10-17 10:23:20 +11:00
AP_Scripting_CANSensor.h AP_Scripting: don't include CAN support on periph if there is only one CAN port 2023-10-17 10:23:20 +11:00
AP_Scripting_config.h AP_Scripting: require a file system 2023-10-17 10:23:20 +11:00
AP_Scripting_helpers.cpp
AP_Scripting_helpers.h
README.md
lua_bindings.cpp AP_Scripting: add support for dependencty on manual methods, remove handling of mission commands without AP_Mission 2023-10-17 10:23:20 +11:00
lua_bindings.h AP_Scripting: add basic print 2023-10-04 18:34:08 +11:00
lua_boxed_numerics.cpp
lua_boxed_numerics.h
lua_common_defs.h
lua_repl.cpp
lua_scripts.cpp AP_Scripting: change some _INFO msgs to _CRITICAL/ERROR 2023-11-22 00:07:05 -08:00
lua_scripts.h
wscript

README.md

AP_Scripting

Enabling Scripting Support in Builds

Scripting is automatically enabled on all boards with at least 1MB of flash space. The following example enables scripting, builds the ArduPlane firmware for the Cube, and uploads it.

$ waf configure --board=CubeBlack

$ waf plane

$ waf plane --upload

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 -v ArduPlane

Once you have a vehicle flashed with scripting you need to set the SCR_ENABLE parameter to 1 to enable scripting and reboot.

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
  local current_pos = ahrs:get_location() -- fetch the current position of the vehicle
  local home = ahrs:get_home()            -- fetch the home position of the vehicle
  if current_pos and home then            -- check that both a vehicle location, and home location are available
    local distance = current_pos:get_distance(home) -- calculate the distance from home in meters
    if distance > 1000 then -- if more then 1000 meters away
      distance = 1000;      -- clamp the distance to 1000 meters
    end
    SRV_Channels:set_output_pwm(96, 1000 + distance) -- set the servo assigned function 96 (scripting3) to a proportional value
  end

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

return update, 1000   -- request "update" to be the first time 1000 milliseconds (1 second) after script is loaded

Examples

See the code examples folder

Working with bindings

Edit bindings.desc and rebuild. The waf build will automatically re-run the code generator.