> 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/lua-api-reference/model/setcurve.md).

# model.setCurve(curve, params)

Set Curve parameters

The first and last x value must -100 and 100 and x values must be monotonically increasing

@status current Introduced in 2.2.0

Example setting a 4-point custom curve:

```lua
  params = {}
  params["x"] =  {-100, -34, 77, 100}
  params["y"] = {-70, 20, -89, -100}
  params["smooth"] = true
  params["type"] = 1
  val =  model.setCurve(2, params)
```

setting a 6-point standard smoothed curve

```lua
 val = model.setCurve(3, {smooth=true, y={-100, -50, 0, 50, 100, 80}})
```

## Parameters

* `curve` (unsigned number) curve number (use 0 for Curve1)
* `params` see [model.getCurve](/lua-api-reference/model/getcurve.md) return format for table format. setCurve uses standard lua array indexing and arrays start at index 1

## Return value

* \`\` 0 - Everything okay

  ```
     1 - Wrong number of points
     2 - Invalid Curve number
     3 - Cuve does not fit anymore
     4 - point of out of index
     5 - x value not monotonically increasing
     6 - y value not in range [-100;100]
     7 - extra values for y are set
     8 - extra values for x are set
  ```


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://luadoc.edgetx.org/lua-api-reference/model/setcurve.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.