ardupilot/libraries/AP_Scripting
Andrew Tridgell bae5859a92 AP_Scripting: added copter_loiter_brake script
for automatic BRAKE mode when flying in LOITER in steep terrain
2024-05-07 19:39:39 +10:00
..
applets AP_Scripting: added copter_loiter_brake script 2024-05-07 19:39:39 +10:00
docs AP_Scripting: Docs: fix all type errors 2024-05-07 09:51:53 +10:00
drivers AP_Scripting: allow for 0x00 for 2nd checksum byte in INF_Inject driver 2024-05-04 07:43:39 +10:00
examples AP_Scripting: lua range finder driver that returns distances to a simulated sea floor for testing ArduSub surface tracking modes 2024-04-08 11:18:23 -03:00
generator AP_Scripting: generator: add return count to manual bindings 2024-05-07 09:51:53 +10:00
lua AP_Scripting: allow loading moduels from ROMFS 2024-02-27 10:17:43 +11:00
modules/MAVLink
tests AP_Scripting: tests: enforce correct types in docs 2024-05-07 09:51:53 +10:00
.gitignore
AP_Scripting.cpp AP_Scripting: Only try to make scripts directory if file write and directory is enabled 2024-03-12 08:52:38 +11:00
AP_Scripting.h AP_Scripting: fixed memory leak in sendfile() 2024-01-08 13:01:02 +11:00
AP_Scripting_CANSensor.cpp
AP_Scripting_CANSensor.h
AP_Scripting_config.h
AP_Scripting_helpers.cpp
AP_Scripting_helpers.h
README.md
lua_bindings.cpp AP_Scripting: CAN: `get_device` and `get_device2` return nil if no driver is configure with the correct protocol 2024-05-07 09:48:10 +10:00
lua_bindings.h
lua_boxed_numerics.cpp
lua_boxed_numerics.h
lua_common_defs.h AP_Scripting: allow loading moduels from ROMFS 2024-02-27 10:17:43 +11:00
lua_repl.cpp
lua_scripts.cpp AP_Scripting: only try to load from ROMFS if `HAL_HAVE_AP_ROMFS_EMBEDDED_LUA` is defined 2024-02-27 11:09:08 +11: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.