About 80 days if only periodic transmission every 5 seconds
About 80 days if periodic transmission every 5 seconds plus TWELITE CUE moved once per minute
About 700 days if only periodic transmission every 1 minute
About 565 days if periodic transmission every 1 minute plus TWELITE CUE moved once per minute
Current consumption is calculated based on actual measurements of sample units using CR2032 batteries with a capacity of 220mAh. Battery life is a reference value and not guaranteed. It varies depending on battery performance, usage temperature, and environment.
1.2 - Cue App Motion Sensor Pal Mode
Mode operating as a motion sensor pal
This mode provides equivalent functionality to the motion sensor pal.
Use this mode when measuring acceleration continuously or detecting impacts.
This mode is divided into three sub-modes:
Acceleration measurement mode
Event detection mode
Dice mode
Acceleration Measurement Mode
This mode intermittently or continuously measures acceleration and transmits the data.
Please refer to Settings for configuration instructions.
TWELITE 2525A Mode Flag
Setting the TWELITE 2525A mode flag to 1 (sensor-specific parameter: 13000000) makes it operate as TWELITE 2525A FIFO (normal) mode. Use this mode if you want to substitute TWELITE 2525A.
Accelerometer Properties
You can change the number of samples and sampling frequency during intermittent transmission with accelerometer properties.
These settings can be combined by adding values.
Setting Value (Hex)
Description
0x?3????00–0x?3????FF
Number of samples to send during intermittent transmission, set in 16-sample units. Sample count = 16 + 16 x value. Examples: 0x00000000: 16 samples (default) 0x00000001: 32 samples … 0x00000007: 128 samples … 0x000000FF: 4096 samples
0x?3???0??–0x?3???F??
Sampling frequency of acceleration: 0x00000000: 25Hz (default) 0x00000100: 50Hz 0x00000200: 100Hz 0x00000300: 190Hz 0x00000400–0x00000F00: Undefined
When the sample count is set to 32 or more, data will be split into separate packets every 16 samples.
For example, if set to 32 samples, two packets with 16 samples each will be received, not one packet with 32 samples.
This mode detects movement and sends data accordingly.
Therefore, if moved slowly, it may not detect movement and output may not change.
In that case, move it a little more vigorously.
Also, setting sensor-specific parameter (p) to 01000000 makes motion detection more sensitive.
If transmissions occur at unintended times, set this parameter to 01000000.
Dice Mode
Detects the face of TWELITE CUE facing upward.
Controls the notification pal’s LED similar to event detection mode.
Settings
Setting Command
Setting Item
Setting Value
Remarks
p
Sensor-specific parameter
02100000
Please refer to Settings for configuration instructions.
This mode detects movement and determines the face orientation.
Therefore, if moved slowly, the face may not be detected and output may not change.
In that case, place it on a desk or give it a light tap.
Also, setting sensor-specific parameter (p) to 02000000 makes motion detection more sensitive.
If transmissions occur at unintended times, set this parameter to 02000000.
Typical Battery Life
About 3.5 years if transmitting once every minute in intermittent transmission acceleration measurement mode
About 20 days if transmitting continuously at 25 Hz sampling frequency in acceleration measurement mode
About 3 years if moving once every minute in event detection or dice mode
Current consumption is calculated based on actual measurements of sample units using CR2032 batteries with a capacity of 220mAh. Battery life is a reference value and not guaranteed. It varies depending on battery performance, usage temperature, and environment.
1.3 - Cue App Open/Close Sensor Pal Mode
Mode operating as an open/close sensor pal
This mode attaches to objects and detects open/close by the presence or absence of a magnet.
Use this mode to measure door opening/closing or factory equipment operation status.
Settings
When using this mode, set the following items.
Setting Command
Setting Item
Setting Value
Remarks
p
Sensor-specific parameter setting
04000000
Please refer to Settings for configuration instructions.
Approximately 4 years if 200 open/close operations per day (including 1-minute periodic transmissions).
Approximately 4.5 years if 0 open/close operations per day (including 1-minute periodic transmissions).
Current consumption is calculated based on actual measurements of sample units using CR2032 batteries with a capacity of 220mAh. Battery life is a reference value and not a guaranteed value. It varies depending on battery performance, usage temperature, and environment.
2 - Cue App Settings
How to configure the Cue App
There are two ways to configure the TWELITE CUE: wired and wireless.
2.1 - Cue App Settings via OTA
How to configure via wireless communication
OTA settings allow you to configure the interactive mode settings wirelessly.
A parent device that can connect to a PC, such as MONOSTICK, is required.
Steps for OTA Configuration
Perform OTA configuration using the following steps.
Place the TWELITE CUE within about 20cm of the MONOSTICK. Turn on the main unit’s power or bring a magnet close to the magnetic sensor more than 5 times to confirm that the TWELITE CUE’s LED is blinking.
5. Confirm the output from the MONOSTICK
Check for the following output messages.
If no output is displayed, see here.
The following message indicates that the distance is too far.
OTA FAILURE
OTA request TS=20515[ms]
LQI:63 (RF strength, >= 100)
SID:810BA765
TWELITE CUE:v1.1.1
Protocol Version:0x11
--— LQI is small. Please make TWELITE CUE closer. —--
In this case, bring the MONOSTICK and TWELITE CUE closer together.
Wrong target
The following message indicates that the TWELITE CUE firmware is different or that the wrong TWELITE CUE is being approached.
OTA FAILURE
OTA request TS=20515[ms]
LQI:180 (RF strength, >= 100)
SID:810BA765
TWELITE CUE:v1.1.1
Protocol Version:0x13
--— Different protocol version. Please update TWELITE CUE. —--
In this case, check that you are not approaching the wrong TWELITE CUE.
Also, if you have rewritten the TWELITE CUE firmware, please use TWELITE R2/R3 to rewrite it back to App_CUE.
2.2 - Cue App Settings via TWELITE R2/R3
How to configure using TWELITE R2/R3
Settings can be made by connecting TWELITE R2/R3 to the 7P interface of TWELITE CUE.
Example connection with TWELITE R2
Connecting TWELITE R2/R3 in reverse direction will damage TWELITE CUE.
When using TWELITE R2/R3 for configuration, please follow the steps below.
1. Launch the TWELITE STAGE APP
Install the TWELITE STAGE SDK on your PC and launch TWELITE_Stage in the MWSTAGE folder.
Detailed configuration changes via Interactive Mode
This app allows detailed configuration from Interactive Mode.
This page explains functions specific to the Cue App (App_CUE). For common functions, see the TWELITE APPS Manual top page.
When entering Interactive Mode, the following screen is displayed.
--- CONFIG/App_CUE V1-00-2/SID=0x810ba765/LID=0x01 ---
a: set Application ID (0x67720102)
i: set Device ID (--)
c: set Channels (18)
x: set Tx Power (13)
b: set UART baud (38400)
B: set UART option (8N1)
k: set Enc Key (0xA5A5A5A5)
o: set Option Bits (0x00000001)
t: set Transmission Interval (5)
p: set Senser Parameter (0x00000000)
---
S: save Configuration
R: reset to Defaults
List of Setting Commands
Command
Setting Item
Default
Explanation
a
Application ID
0x67720102
Multiple groups can use the same frequency channel. The value is set as a 32-bit number.
i
Logical Device ID
–
Sets the logical device ID of the child device. Values from 1 to 100 can be set. If the setting is “–”, the logical device ID is internally set to 1.
c
Frequency Channel Setting
18
Selects the channel (11–26). Multiple channel specifications are invalid to prioritize low power operation.
x
Transmission Power Setting
13
Specify a one- or two-digit number. The second digit is optional. The first digit sets the transmission power. 3 is the strongest, and each step down to 2, 1, 0 reduces output by -11.5 dB. Use this to limit output and reduce the effective radio range. However, transmission distance is affected by environment (noise, obstacles, etc.). ※ Theoretically, transmission distance halves for every 6 dB reduction in output, so one step reduction reduces distance to about 1/4. The second digit sets the number of retransmissions. Specify 0–9 for the second digit; 0 means no retransmission (default), 1–9 correspond to the number of retransmissions.
Enter the encryption key. Set a 32-bit hexadecimal number. Use the same value within the communication group.
o
Option Bits Setting
0x00000001
Various detailed settings can be configured.
t
Transmission Interval Setting
5
Sets the interval for periodic transmission packets in seconds. Valid values are 1 to 4095. Behavior outside this range is undefined.
p
Sensor-Specific Parameter Setting
0
Switch modes and set parameters. Specify as a hexadecimal number greater than or equal to 0. See the page Various Modes for details.
S
Save Settings
Saves settings and restarts the module.
R
Reset to Defaults
Resets settings to default. If you save immediately after without other operations using the S key, the save area is cleared.
Option Bits Setting
Explanation of each bit in the option bit setting value.
Bit (Hex)
Explanation
0x00000001
Transmits to each repeater or parent device, and all information received by the repeaters is forwarded to the parent device and output via serial. In this case, analyzing multiple received packets allows identifying the router that received the signal closest.
0x00000040
Disables OTA.
0x00001000
Enables encrypted communication. (Please also set encryption on the counterpart.)
