> 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/cue_viewer.md). # CUE viewer `Windows` `macOS` `Linux` `RasPi` Interpret messages from [TWELITE CUE](https://mono-wireless.com/cue). {% hint style="info" %} During this commentary, the cupcake image of the previous version is shown. {% endhint %} ## TWELITE CUE ![Screen example: Detecting upward-facing surfaces](/files/UXuSsb2OfxT0L82GL1Iz) The default setting (CUE mode) of TWELITE CUE 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. {% hint style="info" %} In CUE mode, all on-board sensors and LEDs are in operation in order to test the operation of TWELITE CUE. {% endhint %} #### wakeup factors * Timer wake-up (periodic wake-up by set value) * Wake-up by acceleration detection * Wake-up by magnetic sensor (when a magnet is detected approaching) #### Transmission data * Detection event (see below) * Module power supply voltage * Magnetic sensor detection value * Acceleration data ### Packet Displays basic packet information. | Item | Explanation | | ----- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | #???? | The number of packets received so far. | | 種別 | 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. | ### Events The default output of TWELITE CUE is always as an acceleration event. Regardless of the wake-up factor, a fixed number of samples of acceleration is measured after wake-up. The event corresponding to the result of this acceleration is sent. | Detection Event | Number | Description | | --------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Dice | 1(0x00) .. 6(0x06) | The judgment is made based on the regular wake-up and the wake-up detected by the magnetic sensor. If a large acceleration is detected after waking up, an event (0xFF) may be detected that is not allowed to be judged. | | Move | 16(0x10) | A move or shake event occurs when the accelerometer wakes up when it detects an acceleration above a certain level. A move event occurs when the change in measured acceleration is not very large. (When a change in acceleration is detected, but there is no continuous change in acceleration) | | Shake | 8(0x08) | A move or shake event occurs when the accelerometer wakes up when it detects an acceleration above a certain level. A shake occurs when the change in measured acceleration is relatively large. (When changes in acceleration are detected and continuous changes in acceleration can be detected. (As the name Shake implies, it occurs when the CUE is continuously shaken.) | {% hint style="info" %} We do not provide a quantitative definition of the detection threshold and event detection conditions for wake-up due to acceleration. {% endhint %} ### Voltage Supply voltage of the module\[mV]. ### Magnet Displays detected or undetected magnet poles. {% hint style="info" %} No indication of whether the magnetic sensor is waking up due to detection. {% endhint %} ### Acceleration Displays acceleration measured after waking up. | | | | ------- | --------------------------------------------------------------------------------------------------------- | | sample | The number of samples of acceleration is shown. 10 fixed samples. | | Rate ID | The sample rate of acceleration. 04 fixed at 100 Hz. | | X,Y,Z | Acceleration of three axes, obtained as an average of 8 samples. The unit is milli-G (1000mG=1G=9.8m/s2). | ## Screen examples ![Screen example: Move (acceleration detection)](/files/UnakyNrfBzsFud7K9ITk) ![Screen example: Shake (continued shaking)](/files/KbTAHCJN3QWMcQ9aSAv0) --- # 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/cue_viewer.md?ask=&goal= ``` `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.