How Can We Help?

INAV Programming Framework

You are here:
< All Topics

Framework

INAV Programming Framework (IPF) is a mechanism that allows you to to create custom functionality in INAV. You can choose for certain actions to be done, based on custom conditions you select.

Logic conditions can be based on things such as RC channel values, switches, altitude, distance, timers, etc. The conditions you create can also make use of other conditions you’ve entered previously. The results can be used in:

  • Servo mixer to activate/deactivate certain servo mix rulers
  • To activate/deactivate system overrides

INAV Programming Framework consists of:

  • Logic Conditions – each Logic Condition can be understood as a single command, a single line of code. Each logic condition consists of:
    • an operator (action), such as “plus” or “set vtx power”
    • one or two operands (nouns), which the action acts upon. Operands are often numbers, such as a channel value or the distance to home.
    • “activator” condition – optional. This condition is only active when another condition is true
  • Global Variables – variables that can store values from and for Logic Conditions and servo mixer
  • Programming PID – general purpose, user configurable PID controllers

IPF can be edited using INAV Configurator user interface, or via CLI. To use COnfigurator, click the tab labeled “Programming”. The various options shown in Configurator are described below.

Logic Conditions

CLI

logic <rule> <enabled> <activatorId> <operation> <operand A type> <operand A value> <operand B type> <operand B value> <flags>

  • <rule> – ID of Logic Condition rule
  • <enabled>0 evaluates as disabled, 1 evaluates as enabled
  • <activatorId> – the ID of LogicCondition used to activate this Condition. Logic Condition will be evaluated only then Activator evaluates as true. -1 evaluates as true
  • <operation> – See Operations paragraph
  • <operand A type> – See Operands paragraph
  • <operand A value> – See Operands paragraph
  • <operand B type> – See Operands paragraph
  • <operand B value> – See Operands paragraph
  • <flags> – See Flags paragraph

Operations

Operation IDNameNotes
0TRUEAlways evaluates as true
1EQUALEvaluates false if false or 0
2GREATER_THANtrue if Operand A is a higher value than Operand B
3LOWER_THANtrue if Operand A is a lower value than Operand B
4LOWtrue if <1333
5MIDtrue if >=1333 and <=1666
6HIGHtrue if >1666
7ANDtrue if Operand A and Operand B are the same value or both true
8ORtrue if Operand A and/or OperandB is true
9XORtrue if Operand A or Operand B is true, but not both
10NANDfalse if Operand A and Operand B are both true
11NORtrue if Operand A and Operand B are both false
12NOTThe boolean opposite to Operand A
13StickyOperand A is the activation operator, Operand B is the deactivation operator. After the activation is true, the operator will return true until Operand B is evaluated as true
14Basic: AddAdd Operand A to Operand B and returns the result
15Basic: SubtractSubstract Operand B from Operand A and returns the result
16Basic: MultiplyMultiply Operand A by Operand B and returns the result
17Basic: DivideDivide Operand A by Operand B and returns the result
18Set GVARStore value from Operand B into the Global Variable addressed by
Operand A. Bear in mind, that operand Global Variable means: Value stored in Global Variable of an index! To store in GVAR 1 use Value 1 not Global Variable 1
19Increase GVARIncrease the GVAR indexed by Operand A (use Value 1 for Global Variable 1) with value from Operand B
20Decrease GVARDecrease the GVAR indexed by Operand A (use Value 1 for Global Variable 1) with value from Operand B
21Set IO PortSet I2C IO Expander pin Operand A to value of Operand B. Operand A accepts values 0-7 and Operand B accepts 0 and 1
22OVERRIDE_ARMING_SAFETYAllows the craft to arm on any angle even without GPS fix. WARNING: This bypasses all safety checks, even that the throttle is low, so use with caution. If you only want to check for certain conditions, such as arm without GPS fix. You will need to add logic conditions to check the throttle is low.
23OVERRIDE_THROTTLE_SCALEOverride throttle scale to the value defined by operand. Operand type 0 and value 50 means throttle will be scaled by 50%.
24SWAP_ROLL_YAWbasically, when activated, yaw stick will control roll and roll stick will control yaw. Required for tail-sitters VTOL during vertical-horizonral transition when body frame changes
25SET_VTX_POWER_LEVELSets VTX power level. Accepted values are 0-3 for SmartAudio and 0-4 for Tramp protocol
26INVERT_ROLLInverts ROLL axis input for PID/PIFF controller
27INVERT_PITCHInverts PITCH axis input for PID/PIFF controller
28INVERT_YAWInverts YAW axis input for PID/PIFF controller
29OVERRIDE_THROTTLEOverride throttle value that is fed to the motors by mixer. Operand is scaled in us. 1000 means throttle cut, 1500 means half throttle
30SET_VTX_BANDSets VTX band. Accepted values are 1-5
31SET_VTX_CHANNELSets VTX channel. Accepted values are 1-8
32SET_OSD_LAYOUTSets OSD layout. Accepted values are 0-3
33Trigonometry: SineComputes SIN of Operand A value in degrees. Output is multiplied by Operand B value. If Operand B is 0, result is multiplied by 500
34Trigonometry: CosineComputes COS of Operand A value in degrees. Output is multiplied by Operand B value. If Operand B is 0, result is multiplied by 500
35Trigonometry: TangentComputes TAN of Operand A value in degrees. Output is multiplied by Operand B value. If Operand B is 0, result is multiplied by 500
36MAP_INPUTScales Operand A from [0 : Operand B] to [0 : 1000]. Note: input will be constrained and then scaled
37MAP_OUTPUTScales Operand A from [0 : 1000] to [0 : Operand B]. Note: input will be constrained and then scaled
38RC_CHANNEL_OVERRIDEOverrides channel set by Operand A to value of Operand B. Note operand A should normally be set as a “Value”, NOT as “Get RC Channel”
39SET_HEADING_TARGETSets heading-hold target to Operand A, in degrees. Value wraps-around.
40ModuloModulo. Divide Operand A by Operand B and returns the remainder
41LOITER_RADIUS_OVERRIDESets the loiter radius to Operand A [0 : 100000] in cm. If the value is lower than the loiter radius set in the Advanced Tuning, that will be used.
42SET_PROFILESets the active config profile (PIDFF/Rates/Filters/etc) to Operand A. Operand A must be a valid profile number, currently from 1 to 3. If not, the profile will not change
43Use Lowest ValueFinds the lowest value of Operand A and Operand B
44Use Highest ValueFinds the highest value of Operand A and Operand B
45FLIGHT_AXIS_ANGLE_OVERRIDESets the target attitude angle for axis. In other words, when active, it enforces Angle mode (Heading Hold for Yaw) on this axis (Angle mode does not have to be active). Operand A defines the axis: 0 – Roll, 1 – Pitch, 2 – Yaw. Operand B defines the angle in degrees
46FLIGHT_AXIS_RATE_OVERRIDESets the target rate (rotation speed) for axis. Operand A defines the axis: 0 – Roll, 1 – Pitch, 2 – Yaw. Operand B defines the rate in degrees per second
47EDGEMomentarily true when triggered by Operand A. Operand A is the activation operator [boolean], Operand B (Optional) is the time for the edge to stay active [ms]. After activation, operator will return true until the time in Operand B is reached. If a pure momentary edge is wanted. Just leave Operand B as the default Value: 0 setting.
48DELAYDelays activation after being triggered. This will return true when Operand A is true, and the delay time in Operand B [ms] has been exceeded.
49TIMERA simple on – off timer. true for the duration of Operand A [ms]. Then false for the duration of Operand B [ms].
50DELTAThis returns true when the value of Operand A has changed by the value of Operand B or greater within 100ms.
51APPROX_EQUALtrue if Operand B is within 1% of Operand A.
52LED_PIN_PWMValue Operand A from [0 : 100] starts PWM generation on LED Pin. See LED pin PWM. Any other value stops PWM generation (stop to allow ws2812 LEDs updates in shared modes)

Operands

Operand TypeNameNotes
0VALUEValue derived from value field
1GET_RC_CHANNELvalue points to RC channel number, indexed from 1
2FLIGHTvalue points to flight parameter table
3FLIGHT_MODEvalue points to flight modes table
4LCvalue points to other logic condition ID
5GVARValue stored in Global Variable indexed by value. GVAR 1 means: value in GVAR 1
5PIDOutput of a Programming PID indexed by value. PID 1 means: value in PID 1

FLIGHT

Operand ValueNameNotes
0ARM_TIMERin seconds
1HOME_DISTANCEin meters
2TRIP_DISTANCEin meters
3RSSI
4VBATin Volts * 100, eg. 12.1V is 1210
5CELL_VOLTAGEin Volts * 100, eg. 12.1V is 1210
6CURRENTin Amps * 100, eg. 9A is 900
7MAH_DRAWNin mAh
8GPS_SATS
9GROUD_SPEEDin cm/s
103D_SPEEDin cm/s
11AIR_SPEEDin cm/s
12ALTITUDEin cm
13VERTICAL_SPEEDin cm/s
14TROTTLE_POSin %
15ATTITUDE_ROLLin degrees
16ATTITUDE_PITCHin degrees
17IS_ARMEDboolean 0/1
18IS_AUTOLAUNCHboolean 0/1
19IS_ALTITUDE_CONTROLboolean 0/1
20IS_POSITION_CONTROLboolean 0/1
21IS_EMERGENCY_LANDINGboolean 0/1
22IS_RTHboolean 0/1
23IS_LANDINGboolean 0/1
24IS_FAILSAFEboolean 0/1
25STABILIZED_ROLLRoll PID controller output [-500:500]
26STABILIZED_PITCHPitch PID controller output [-500:500]
27STABILIZED_YAWYaw PID controller output [-500:500]
283D HOME_DISTANCEin meters, calculated from HOME_DISTANCE and ALTITUDE using Pythagorean theorem
29CROSSFIRE LQCrossfire Link quality as returned by the CRSF protocol
30CROSSFIRE SNRCrossfire SNR as returned by the CRSF protocol
31GPS_VALIDboolean 0/1. True when the GPS has a valid 3D Fix
32LOITER_RADIUSThe current loiter radius in cm.
33ACTIVE_PROFILEinteger for the active config profile [1..MAX_PROFILE_COUNT]
34BATT_CELLSNumber of battery cells detected
35AGL_STATUSboolean 1 when AGL can be trusted, 0 when AGL estimate can not be trusted
36AGLinteger Above The Groud Altitude in cm
37RANGEFINDER_RAWinteger raw distance provided by the rangefinder in cm
38ACTIVE_MIXER_PROFILEWhich mixers are currently active (for vtol etc)
39MIXER_TRANSITION_ACTIVECurrently switching between mixers (quad to plane etc)
40ATTITUDE_YAWcurrent heading (yaw) in degrees
41FW Land Sateinteger 15, indicates the status of the FW landing, 0 Idle, 1 Downwind, 2 Base Leg, 3 Final Approach, 4 Glide, 5 Flare

FLIGHT_MODE

The flight mode operands return true when the mode is active. These are modes that you will see in the Modes tab. Note: the USER* modes are used by camera switchers, PINIO etc. They are not the Waypoint User Actions. See the Waypoints section to access those.

Operand ValueNameNotes
0FAILSAFEtrue when a Failsafe state has been triggered.
1MANUALtrue when you are in the Manual flight mode.
2RTHtrue when you are in the Return to Home flight mode.
3POSHOLDtrue when you are in the Position Hold or Loiter flight modes.
4CRUISEtrue when you are in the Cruise flight mode.
5ALTHOLDtrue when you the Altitude Hold flight mode modifier is active.
6ANGLEtrue when you are in the Angle flight mode.
7HORIZONtrue when you are in the Horizon flight mode.
8AIRtrue when you the Airmode flight mode modifier is active.
9USER1true when the USER 1 mode is active.
10USER2true when the USER 2 mode is active.
11COURSE_HOLDtrue when you are in the Course Hold flight mode.
12USER3true when the USER 3 mode is active.
13USER4true when the USER 4 mode is active.
14ACROtrue when you are in the Acro flight mode.
15WAYPOINT_MISSIONtrue when you are in the WP Mission flight mode.

WAYPOINTS

Operand ValueNameNotes
0Is WPBoolean 0/1
1Current Waypoint IndexCurrent waypoint leg. Indexed from 1. To verify WP is in progress, use Is WP
2Current Waypoint Actiontrue when Action active in current leg. See ACTIVE_WAYPOINT_ACTION table
3Next Waypoint Actiontrue when Action active in next leg. See ACTIVE_WAYPOINT_ACTION table
4Distance to next WaypointDistance to next WP in metres
5Distance from WaypointDistance from the last WP in metres
6User Action 1true when User Action 1 is active on this waypoint leg [boolean 0/1]
7User Action 2true when User Action 2 is active on this waypoint leg [boolean 0/1]
8User Action 3true when User Action 3 is active on this waypoint leg [boolean 0/1]
9User Action 4true when User Action 4 is active on this waypoint leg [boolean 0/1]
10Next Waypoint User Action 1true when User Action 1 is active on the next waypoint leg [boolean 0/1]
11Next Waypoint User Action 2true when User Action 2 is active on the next waypoint leg [boolean 0/1]
12Next Waypoint User Action 3true when User Action 3 is active on the next waypoint leg [boolean 0/1]
13Next Waypoint User Action 4true when User Action 4 is active on the next waypoint leg [boolean 0/1]

ACTIVE_WAYPOINT_ACTION

ActionValue
WAYPOINT1
HOLD_TIME3
RTH4
SET_POI5
JUMP6
SET_HEAD7
LAND8

Flags

All flags are reseted on ARM and DISARM event.

bitDecimalFunction
01Latch – after activation LC will stay active until LATCH flag is reset
12Timeout satisfied – Used in timed operands to determine if the timeout has been met

Global variables

CLI

gvar <index> <default value> <min> <max>

Programming PID

pid <index> <enabled> <setpoint type> <setpoint value> <measurement type> <measurement value> <P gain> <I gain> <D gain> <FF gain>

  • <index> – ID of PID Controller, starting from 0
  • <enabled>0 evaluates as disabled, 1 evaluates as enabled
  • <setpoint type> – See Operands paragraph
  • <setpoint value> – See Operands paragraph
  • <measurement type> – See Operands paragraph
  • <measurement value> – See Operands paragraph
  • <P gain> – P-gain, scaled to 1/1000
  • <I gain> – I-gain, scaled to 1/1000
  • <D gain> – D-gain, scaled to 1/1000
  • <FF gain> – FF-gain, scaled to 1/1000

Examples- Programming Tab

When more than 100 meters away, increase VTX power

screenshot of vtx home distance

When more than 600 meters away, engage return-to-home by setting the matching RC channel

screenshot of rth home distance

Dynamic THROTTLE scale

logic 0 1 0 23 0 50 0 0 0

Limits the THROTTLE output to 50% when Logic Condition 0 evaluates as true

Set VTX power level via Smart Audio

logic 0 1 0 25 0 3 0 0 0

Sets VTX power level to 3 when Logic Condition 0 evaluates as true

Invert ROLL and PITCH when rear facing camera FPV is used

Solves the problem from #4439

logic 0 1 0 26 0 0 0 0 0
logic 1 1 0 27 0 0 0 0 0

Inverts ROLL and PITCH input when Logic Condition 0 evaluates as true. Moving Pitch stick up will cause pitch down (up for rear facing camera). Moving Roll stick right will cause roll left of a quad (right in rear facing camera)

Cut motors but keep other throttle bindings active

logic 0 1 0 29 0 1000 0 0 0

Sets throttle output to 0% when Logic Condition 0 evaluates as true

Set throttle to 50% and keep other throttle bindings active

logic 0 1 0 29 0 1500 0 0 0

Sets throttle output to about 50% when Logic Condition 0 evaluates as true

Set throttle control to different RC channel

logic 0 1 0 29 1 7 0 0 0

If Logic Condition 0 evaluates as true, motor throttle control is bound to RC channel 7 instead of throttle channel

Set VTX channel with a POT

Set VTX channel with a POT on the radio assigned to RC channel 6

logic 0 1 -1 15 1 6 0 1000 0
logic 1 1 -1 37 4 0 0 7 0
logic 2 1 -1 14 4 1 0 1 0
logic 3 1 -1 31 4 2 0 0 0

Steps:

  1. Normalize range [1000:2000] to [0:1000] by substracting 1000
  2. Scale range [0:1000] to [0:7]
  3. Increase range by 1 to have the range of [1:8]
  4. Assign LC#2 to VTX channel function

Set VTX power with a POT

Set VTX power with a POT on the radio assigned to RC channel 6. In this example we scale POT to 4 power level [1:4]

logic 0 1 -1 15 1 6 0 1000 0
logic 1 1 -1 37 4 0 0 3 0
logic 2 1 -1 14 4 1 0 1 0
logic 3 1 -1 25 4 2 0 0 0

Steps:

  1. Normalize range [1000:2000] to [0:1000] by substracting 1000
  2. Scale range [0:1000] to [0:3]
  3. Increase range by 1 to have the range of [1:4]
  4. Assign LC#2 to VTX power function

Common issues / questions about IPF

One common mistake involves setting RC channel values. To override (set) the value of a specific RC channel, choose “Override RC value”, then for operand A choose value and enter the channel number. Choosing “get RC value” is a common mistake, which does something other than what you probably want.

screenshot of override an RC channel with a value
Table of Contents