> For the complete documentation index, see [llms.txt](https://luadoc.edgetx.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://luadoc.edgetx.org/opentx_2.3/part_iv_-_converting_opentx_20_scripts/known_issues.md).

# General Issues

## Deprecated Functions

**lcd.Lock()** is deprecated, will be obsolete in 2.2. Lua scripts must now explicitly call lcd.Clear() and re-draw the whole display if necessary.

TODO: research killEvents() and use of keys in telemetry scripts

## Obsolete Telemetry Field Names

OpenTX since version 2.1 provides more flexibility in the number and type of supported remote sensors. As a result, several field name constants are obsolete and need to be modified in scripts originally written for OpenTX 2.0.

**GPS field names** are covered in [Handling GPS Sensor Data](/opentx_2.3/part_iv_-_converting_opentx_20_scripts/handling_gps_sensor_data.md)

**Lipo voltage field names (LVSS)** are covered in [Handling Lipo Sensor Data](/opentx_2.3/part_iv_-_converting_opentx_20_scripts/handling_lipo_sensor_data.md)

## Maintaining compatibility with OpenTX 2.0

**Automatic invocation of the background function** - Beginning in OpenTX 2.1 the background() function is called automatically prior to each invocation of the run() function. Under 2.0 you must explicitly call your background function within your run function.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://luadoc.edgetx.org/opentx_2.3/part_iv_-_converting_opentx_20_scripts/known_issues.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.