> For the complete documentation index, see [llms.txt](https://stage.twelite.info/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://stage.twelite.info/eng/usage/screens/main_menu/viewer/smpl_mon/aria_viewer.md).

# ARIA viewer

`Windows` `macOS` `Linux` `RasPi`

Interpret messages from [TWELITE ARIA](https://mono-wireless.com/jp/products/twelite-aria/index.html).

{% hint style="info" %}
During this commentary, the cupcake image of the previous version is shown.
{% endhint %}

## TWELITE ARIA

![Screen example](/files/v6S3aRDyl7PBz1BsxgM3)

The default setting (ARIA mode) of TWELITE ARIA wakes up due to several factors and transmits various information after waking up while driving intermittently using sleep, which can be operated even with coin cell batteries.

#### Wake-up factors

* Wake-up by timer (periodic wake-up by set value)
* Wake-up by magnetic sensor (when a magnet is detected approaching)

#### Transmitted data

* Module power supply voltage
* Magnetic sensor detection value
* Temperature and humidity data

### Packet

Displays basic packet information.

| Item  | Desc.                                                                                                                                                            |
| ----- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| #???? | The number of packets received so far.                                                                                                                           |
| Type  | The value of [`E_PKT`](https://mwm5.twelite.info/references/parser/twefmt/twepacket/e_pkt), which is the packet type; packets from CUE usually have PKT\_PAL=02. |
| ID    | Logical ID of the sender. Normally the value is 0..100.                                                                                                          |
| AD    | The serial number of the sender.                                                                                                                                 |
| LQ    | LQI, the value corresponding to the radio wave strength.                                                                                                         |
| SQ    | Packet sequence number.                                                                                                                                          |

### Data Table

Displays the history of the last 9 data received from TWELITE ARIA. The higher the number, the more recent the data.

#### Time(s)

The time in seconds from the start of the TWELITE STAGE APP until the data is received.

#### ID

Logical device ID of the module.

#### VCC(mV)

Supply voltage of the module\[mV].

#### Temperature(C)

The temperature measured by the module (°C).

#### Humidity(%)

The humidity (%) measured by the module.

#### Magnet

Displays detected or undetected magnet poles.

{% hint style="info" %}
No indication of whether the magnetic sensor is awake or not due to detection.
{% endhint %}


---

# 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://stage.twelite.info/eng/usage/screens/main_menu/viewer/smpl_mon/aria_viewer.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.