Tips & Common Problems

"Script panic not enough memory" or "Script syntax error not enough memory" errors:

Be sure you're following the INAV Lua Telemetry Screen Setup instructions. If you're still having memory issues, you can free up memory by deleting unused models, turning off OpenTX firmware build options, and removing other Lua Scripts from screens. Keep in mind that a not enough memory error doesn't indicate a problem with Lua Telemetry. It only indicates that your transmitter is out of memory and therefore can't run Lua Telemetry.

If trying to run Betaflight TX lua script for VTx control, try using my Taranis VTx port that uses less memory and allows for both Lua Telemetry and VTx scripts to run on the same model.

• Between flights (before armed), long-press Enter/dial and select Reset telemetry to reset telemetry values
• If current sensor isn't present or battery isn't fully charged when plugged in, fuel gauge will be based on battery voltage
• If fuel gauge isn't shown or accurate, be sure you've set CLI values smartport_fuel_unit = percent and battery_capacity correctly. Also, current sensor settings in the configurator need to be calibrated for proper amperage and fuel % data
• Uses transmitter settings for RSSI warning/critical levels for bar gauge range and audio/haptic warnings
• Uses transmitter settings for transmitter voltage min/max for battery bar gauge in screen title
• If you change a telemetry sensor's unit (for example m to ft), power cycle the transmitter to see changes
• If config option Battery View is set to Total but average cell voltage is displayed, send INAV CLI command: set report_cell_voltage = OFF
• When GPS accuracy (HDOP) is displayed as a decimal, the range is 0.8 - 5.3 and it's rounded to the nearest 0.5 HDOP. This is due to HDOP being sent as a single integer from 0 to 9, not as the actual HDOP decimal value.