# Telemetry Scripts

## Overview

Telemetry scripts are used for building customized screens. Each model can have up to three active scripts as configured on the model's telemetry configuration page. The same script can be assigned to multiple models.

**Please note:** Telemetry scripts are only available on radios with telemetry screens, such as e.g. FrSky Taranis models (including Xlite), Radiomaster TX12 and and Jumper T12.

## Lifetime

* Telemetry scripts are loaded when the model is selected.
* `init` function is called one time when the script is loaded
* `background` function is periodically; both when the telemetry screen is visible and when it is not.
* `run` function is called periodically only when the telemetry screen is visible
* script is stopped and disabled if it misbehaves (e.g. run-time error or low memory)
* all telemetry scripts are stopped if a one-time script is running (see One-time scripts)

## File Location

Scripts are located on the SD card in the folder /SCRIPTS/TELEMETRY/<*name*>.lua. File name length (without extension) **must be 6 characters or less** (this limit was 8 characters in OpenTX 2.1).

## Interface

Every script must include a `return` statement at the end, defining its interface to EdgeTX. This statement returns a table with the following fields:

* `init` function (optional)
* `background` function (optional)
* `run` function

### Example

```lua
local function init()
  -- init is called once when model is loaded
end

local function background()
  -- background is called periodically
end

local function run(event)
  -- run is called periodically only when screen is visible
end

return { run = run, background = background, init = init }
```

### Notes:

* The `event` parameter indicates which transmitter key has been pressed (see [Key Events](/2.10/part_iii_-_opentx_lua_api_reference/constants/key_events.md)).


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://luadoc.edgetx.org/2.10/part_i_-_script_type_overview/telemetry.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.