> For the complete documentation index, see [llms.txt](https://docs.twtg.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.twtg.io/docs/configuration/online-configurator.md).

# Online Configurator

All NEON devices are configurable via LoRa downlinks which can be generated using the [NEON Online Configurator](https://neon-configurator.twtg.io/). Select the product type and the protocol version and click **Open**, prompting a new tab to display the available settings for the selected device.

{% hint style="info" %}
If you are uncertain of the protocol version please refer to [Communication Protocol](/docs/data-and-communication/communication-protocol.md)
{% endhint %}

Depending on the device type and the protocol the configurator can consist of several tabs. The configurator is tabs-sensitive, therefore the user must click the **Encode** button and send a downlink for every set of options they want to set up. 

After clicking **Encode** a pop-up will appear with the following information:

* **JSON**: JSON structure of the downlink message with the configured settings. 
* **Hex array**: Encoded hex array of the downlink message.
* **Hex string**: Encoded hex string of the downlink message.
* **Base64**: Encoded base64 string of the downlink message. 
* **CRC/tag**: A number to confirm the device's configuration. For devices with CRC, it is the cyclic redundancy check calculated over the configuration. For devices with a tag, it is a 32-bit value that the user can label the configuration with, e.g. a version number or the time (seconds since Unix epoch).
* **fPort**: Number of the fPort to send the downlink in the LNS. 

An example of the pop-up is displayed below.

<figure><img src="/files/vcCOzSY99rcLdb5mJVcZ" alt=""><figcaption><p>Example of the pop-up after clicking encode</p></figcaption></figure>


---

# 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://docs.twtg.io/docs/configuration/online-configurator.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.