Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
TWELITE Standard App Viewer
Windows macOS Linux RasPi
Interprets 0x81 command of App_Twelite (standard app).
The TWELITE wireless microcontroller is written with App_Twelite (standard app) or App_Wings, and the serial message from the communication partner is displayed before it is used.
The communication partner is App_Twelite (standard app), and when it receives a standard app button or analog input status message (0x81 message), its contents are interpreted and displayed by mwm5's parser library.
| Operation | Desc. |
|---|---|
[ A ]
No assignment.
[ A ] long press
Exit this screen and return to the previous menu.
[ B ]
Change the font.
[ B ] long press
Screen display with dummy data for testing.
[ C ]
No assignment.
[ C ] long press
Controls and resets the reset pin of the TWELITE wireless module.
ESC ESC
Exit this screen by entering double ESC keys.
Acceleration real-time graph
Windows macOS Linux RasPi
Used for the purpose of referencing sample data from TWELITE CUE and TWELITE MOTION SENSE PAL.
Note: The Sensor Graph Function records one packet as one sample, even when continuous measurement is performed such that multiple samples are included in one packet.
CUE mode, MOT mode, and 2525 FIFO mode.
When the number of consecutive samples exceeds a certain number (analysis window), the XYZ axis is displayed with frequency analysis. However, in 2525 FIFO mode, it is always assumed to be continuous.
When a packet is explicitly delimited (when more than 3 seconds have elapsed since the previous packet, every packet in CUE mode, or when the sequence number of packets becomes discontinuous in MOT mode), a dummy of 4 samples is (When more than 3 seconds have elapsed since the last packet.
Data is stored for up to 4 nodes in order of arrival first.
During multi-node operation, communication failures often occur due to mutual packet collisions. In particular, in FIFO mode, the transmission cycle is almost constant, and packets are attempted to be sent at almost the same time to each other, resulting in transmission failures due to interference, which may continue for a long time. In principle, one node per CHANNEL should be used.
measure continuously at about 25 Hz. (Transmit Interval: 0, Sensor Parameter: 03000000)
measure continuously at about 50 Hz. (Transmit Interval: 0, Sensor Parameter: 03000100)
measure continuously at about 100 Hz. (Transmit Interval: 0, Sensor Parameter: 03000200)
measure 128 samples at about 100Hz about every 10 seconds. (Transmit Interval: 10, Sensor Parameter: 03000208)
measure 256 samples at about 100Hz about every 10 seconds. (Transmit Interval: 10, Sensor Parameter: 03000210)
measure 64 samples at about 50Hz every 10 seconds. (Transmit Interval: 10, Sensor Parameter: 03000104)
measure 128 samples at about 200Hz about every 10 seconds. (Transmit Interval: 10, Sensor Parameter: 03000308)
The sampling rate is calculated from the packet reception time. Since the reception time of multiple past samples is averaged to obtain one sample, the error will be larger if there are packet skips, etc.
After the sample rate is estimated, the graph display scrolls smoothly.
The timestamp of the related log record (T_SMPL) is also estimated in the same way, and the timestamp is after the time of packet acquisition.
Specify 31 in [STAGE Common Settings→Designate Startup Application].
By clicking the [Data Save] button, data for up to 512 samples will be output starting from the display position on the screen (rightmost sample). Note that the most recent sample comes last, so there may be no data at the beginning.
The log file name is log folder/accel_{serial number}_{time stamp}.csv.
The most recent sample on the right end is the 512th data (at the end of the file).
When frequency analysis is performed, the number of frequency analysis samples is the number of frequency analysis samples from the last sample.
The frequency analysis results are added to the line where the sample subject to frequency analysis is recorded (in the case of 64 samples, the 32nd line from the 449th sample is the result, from DC component to high frequency component).
When this screen is opened and data is entered, a log file is automatically output.
The log file name is log folder/accel_{serial number}_{time stamp}.csv.
While the screen is open, the file is being written out. It may not be opened for reading, or even if it is opened, all data may not be read.
CUE Viewer
Windows macOS Linux RasPi
Interpret messages from TWELITE CUE.
During this commentary, the cupcake image of the previous version is shown.
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.
In CUE mode, all on-board sensors and LEDs are in operation in order to test the operation of TWELITE CUE.
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)
Detection event (see below)
Module power supply voltage
Magnetic sensor detection value
Acceleration data
Displays basic packet information.
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.
We do not provide a quantitative definition of the detection threshold and event detection conditions for wake-up due to acceleration.
Supply voltage of the module[mV].
Displays detected or undetected magnet poles.
No indication of whether the magnetic sensor is waking up due to detection.
Displays acceleration measured after waking up.
ARIA Viewer
Windows macOS Linux RasPi
Interpret messages from .
During this commentary, the cupcake image of the previous version is shown.
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 by timer (periodic wake-up by set value)
Wake-up by magnetic sensor (when a magnet is detected approaching)
Module power supply voltage
Magnetic sensor detection value
Temperature and humidity data
Displays basic packet information.
Displays the history of the last 9 data received from TWELITE ARIA. The higher the number, the more recent the data.
The time in seconds from the start of the TWELITE STAGE APP until the data is received.
Logical device ID of the module.
Supply voltage of the module[mV].
The temperature measured by the module (°C).
The humidity (%) measured by the module.
Displays detected or undetected magnet poles.
No indication of whether the magnetic sensor is awake or not due to detection.
Simple monitor
: Interpret packets from TWELITE CUE and display them in a simplified manner
: Interpret packets from TWELITE ARIA and display them in a simplified manner
: Simple monitor compatible with many kinds of TWELITE wireless packets
Graph
: Displays accelerometer packets in real time. Frequency domain display and CVS save function are available.
: TWELITE Stores data from various sensors in a sqlite3 database and displays graphs.
Sensor Graph
Windows macOS Linux RasPi
Various sensor data are recorded in a database file. There is also a function to simply refer to the measured values on the TWELITE Stage screen.
It is not possible to start multiple TWELITE STAGE with the same executable name and use the sensor graph at the same time.
The database file is stored in the {MWSTAGE installation}/log folder and the file name is determined by the TWELITE_Stage executable name.This is because the same executable file name refers to the same database file. The TWELITE STAGE app implementation does not expect multiple application instances to be adding data to the database at the same time. In some situations, this may result in a database file access error, which may cause the TWELITE STAGE app to crash.
For example, if you want to connect two MONOSTICKs and run multiple "sensor graphs" at the same time, run the TWELITE STAGE application with different executable names (stage_a.exe, stage_b.exe) for each. The database file names are log/stage_a_WSns.sqlite and log/stage_b_WSns.sqlite.
Data is stored in a file named {MW_STAGE Install}/log/{MW_STAGE file name}_WSns.sqlite using sqlite3.
The screen transition is [List (with graph preview)]>[24-hour data]>[Live View].
From [24-hour data], you can move to [Year], [Month], [Day (with graph preview)] selection screen.
About the [Live] display screen
Select a specific node from the list.
Display real-time data every second, up to 450 seconds in the past.
About [24-hour data] display screen
Display data for a specific day.
Data is acquired every second, and if there are multiple data, they will be thinned out.
Except for the maximum magnification (1 second per pixel), the data is displayed by averaging the acquired values in each pixel range.
If the value extends beyond the screen, the measurement points are displayed at the top and bottom edges.
If the current time is included, the display is updated when new data arrives.
Wheel, cursor up/down: zoom in/out of time axis
Mouse move: Simplified display of the acquired data in the time axis corresponding to the mouse pointer.
Cursor→, ←: Move to the next acquisition data.
Click and drag: Scroll (only when zoomed in)
When zoomed in, operation by scroll bar is also available.
The [CSV Output] function displays all acquired values contained in the database.
Use the tools at https://sqlitebrowser.org/ to extract data.
v1.3.9or later
On the "24-hour data screen," left-clicking on the memo portion of the sensor node in the upper right corner of the screen will prompt you to edit the memo.
IME input operations (e.g. Japanese) may depend on the system you are using.
Unexpected character strings may be input depending on the operation at the time of IME input. When an unnecessary string is displayed in the input area, delete the unnecessary part by pressing the BS key.
There are three basic types of screens: list, 24-hour, and live.
Specify 32 in [STAGE Common Settings -> Startup Application Designation].
Used to store additional information (text) in sensor nodes.
Used for the purpose of maintaining the last received timestamp.
| Operation | Desc. |
|---|---|
| Label | Item | Desc. |
|---|---|---|
| Label | Item | Desc. |
|---|---|---|
| Label | Item | Desc. |
|---|---|---|
| Label | Item | Desc. |
|---|---|---|
| Item | Explanation |
|---|---|
| Detection Event | Number | Description |
|---|---|---|
| Item | Desc. |
|---|
| Operation | Desc |
|---|
| Key | Description |
|---|
| Column Name | Type | Description |
|---|
| Column Name | Type | Description |
|---|
| Column Name | Type | Description |
|---|
Right part of the [(I)ID#] button
Switch IDs with each click. (Note: For continuous sample data in FIFO mode, operation with multiple IDs is not practical.
Right part [(f)SMP#] button
Change the frequency analysis size to 64, 128, or 256 with each click.
right part [[>PAUSE( )] button
aborts display update (sample acquisition is performed until the internal temporary sample buffer is full)
right part [(c)SAVE DISPLAYED DATA] button
output data in CSV format (log folder). Outputs data from the sample displayed on the rightmost side of the screen to the oldest sample in the buffer. The number of output is always 5120, and the sample displayed on the rightmost side of the screen is the last data.
Mouse drag (graph section)
Move the position of the displayed sample
Mouse drag (bottom scroll bar)
Move the position of the displayed sample (in larger steps)
Cursor→, ←
Move sample display
Cursor↑, ↓
Zoom in/out on the sample horizontal axis (Equal, 2x, 3x, 4x; for 256 analysis samples, 2x). (Equal, 2x, 3x, 4x, up to 2x if the number of samples is 256)
#
Sample number
T_PKT[ms]
Packet reception time
Since one packet contains multiple samples, samples with the same timestamp are lined up.
SEQ
Packet Sequence Number
Packets are assigned and if they are consecutive, there is no missing packet.
T_SMPL[ms]
Sample time (virtual or estimated)
Timestamp of each sample generated from the packet reception time. It does not match the actual time the sample was taken. (The error is large because the sample rate is estimated from the received packet interval, and the timestamp is one packet period later than the actual sample time because the sample period is calculated by adding the sample period to the received sample.
X[G]
Sample value on the X-axis
Based on the value from the sensor, the unit is [G].
Y[G]
sample value of Y axis
based on the value from the sensor, unit is [G].
Z[G]
sample value of Z-axis
based on the value from the sensor, unit is [G].
FD#
Number of the frequency analysis calculated value
If the number of frequency analysis samples is 64, they are ordered in the order of DC,1,2,...,31. ,31` if the number of frequency analysis samples is 64.
Hz
Frequency axis value of the frequency analysis calculation result
Approximate frequency. The frequency is calculated by (FD# / FD_Len) * FD_Freq.
X
Frequency analysis calculated value of X-axis
Y
Frequency analysis calculated value of Y-axis
X
X-axis frequency analysis calculated value
Label
additional information name
see table below
Info
additional information
see table below
Label
Additional Information
Refer to the table below
ModuleSID
Serial number of the sending side
Tick[ms]
System on TWELITE STAGE app side at log file open [ms]
Date
Date when log file was opened
Time
Time
Time_Msec_part
Time when log file was opened
Time_Msec_part
Less-than-seconds portion of log file open [ms]
Samples
Valid sample data
FD_Len
Number of frequency analysis samples
FD_Start#
Frequency analysis start sample number
FD_Freq
Frequency estimate of frequency analysis range [Hz]
Estimated value from sample reception interval
FD_Freq
#
Sample number
T_PKT[ms]
Packet reception time
Since one packet contains multiple samples, samples with the same timestamp are lined up.
SEQ
Packet Sequence Number
Packets are assigned and if they are consecutive, there is no missing packet.
T_SMPL[ms]
Sample time (virtual or estimated)
Timestamp of each sample generated from the packet reception time. It does not match the actual time the sample was taken. (The error is large because the sample rate is estimated from the received packet interval, and the timestamp is one packet period later than the actual sample time because the sample period is calculated by adding the sample period to the received sample.
X[G]
Sample value on the X-axis
Based on the value from the sensor, the unit is [G].
Y[G]
sample value of Y axis
based on the value from the sensor, unit is [G].
Z[G]
sample value of Z-axis
based on the value from the sensor, unit is [G].
Label
Additional information name
Refer to the following table
Info
Additional Information
Refer to the table below
ModuleSID
Serial number of the sending side
Tick[ms]
System on TWELITE STAGE app side at log file open [ms]
Date
Date when log file was opened
Time
Time_Msec_part
Time when log file was opened
Time_Msec_part
Less-than-second part of log file open [ms]
#????
The number of packets received so far.
種別
The value of 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.
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.)
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).
Mouse drag (graph area) | Move the display position when zooming in |
Mouse drag (bottom scroll bar) | Move the display position when zooming in |
Cursor →, ← | Move the sample display |
Cursor up, down, wheel | Zoom in/out on sample horizontal axis |
| Go to the one-second increment view that displays the latest arrival data |
| Go to daily graph |
| Go to the nodes selection screen |
| Select a specific date by year, month, and day. |
| Go to today's data |
| Output one day's data to CSV file |
| Change the display method of the list |
| Change the order of the list |
| Reverses the order of the listings |
ASCII charavcters | If you enter a normal alphanumeric string directly, it will be switched accordingly on the screen. |
| Delete the trailing characters displayed. |
| The entered string is reflected in the database. |
| INTEGER | continuation number used in the database |
| INTEGER
| serial number stored in |
| INTEGER | The time the system received the packet, a timestamp value stored of type |
| INTEGER | The milliseconds portion of the timestamp. |
| INTEGER | The year portion of the local time from the timestamp. |
| INTEGER | The month portion of the local time from the timestamp. |
| INTEGER | The day portion of the local time relative to the timestamp. |
| INTEGER | The hour portion of local time from the time stamp. |
| INTEGER | The identification value, e.g., LID, assigned by the user. |
| INTEGER | Approximate value of the reception strength (Link Quality Indicator). |
| INTEGER | The sequential number of the packet. The possible values depend on the firmware. |
| INTEGER | The type of wireless packet.
|
| REAL | measured value (definition depends on packet type)
|
| REAL | measured value (definition depends on packet type)
|
| REAL | measured value (definition depends on packet type)
|
| REAL | measurement value (definition depends on packet type)
|
| INTEGER | voltage[mV] |
| INTEGER
| b0..b7: DI1..DI8 values (1 is LO, 0 is HIGH level) b24..b25: magnet value (if b28 is 1), 00->no magnet, 01->N pole, 10->S pole b28: if 1 Magnet data is stored in b24..b25 b31: Regular transmission bit (magnet only) |
| INTEGER |
|
| INTEGER |
|
| INTEGER | Other data storage purpose |
| INTEGER | Source of the event |
| INTEGER | Event ID
|
| INTEGER | Event Parameter |
| INTEGER | SID above |
| TEXT | SID converted to hexadecimal string (for readability) |
| TEXT | Auxiliary information corresponding to the SID, to be displayed together in a list, etc. |
| INTEGER | SID above. |
| INTEGER | Timestamp of last receipt |
| Here are some excerpts from the last data received |
|
|
|
|
|
|
|
|
|
Viewer
Windows macOS Linux RasPi
The viewers display information from the TWELITE wireless microcontroller connected via the serial port and send commands (commands) to the contrary.
Each viewer is a relatively small program that also serves as an example of how to use the mwm5 library.
#???? | The number of packets received so far. |
Type |
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. |
Glancer
Windows macOS Linux RasPi
Glancer is an English word for a person who glances, and it is a simple display of information in incoming messages. TWELITE Radio App_Wings is written in the microcontroller, and the communication partner (App_Twelite, TWELITE PAL, ...) is set to the same channel as the application ID. Application ID and CHANNEL can be mixed as long as they match).
The screen consists of two types of screens.
Enumerates information from the communication partner. The contents displayed are (message type, logical ID, serial ID, LQI(Lq), supply voltage (if included in the information), and reception time).
This screen is accessed by moving an item in the list view and making a selection when the item is highlighted. Displays information on specific communication partners in order of arrival.
The number of packets received and the average LQI value since the selection is made are displayed.
Commander
Windows macOS Linux RasPi
The Commander sends serial messages to the TWELITE radio microcontroller. The first screen of the Commander describes the notes.
At the top of the screen are tabs represented by text, which can be clicked on with the mouse to move to the screen in the tab.
| Operation | Desc. |
|---|---|
This screen generates and sends the 0x80 command for App_Twelite (standard application), writes App_Twelite or App_Wings to the TWELITE radio microcontroller, sets the Application ID CHANNEL, and confirms that the message is received from the communication partner Confirm that the message has been received from the communicating party.
A command is generated each time each item is changed. Pressing the Send button will re-send the command for the current setting.
This screen generates NOTICE PAL's Commands for LED control, which writes App_Wings to the TWELITE radio microcontroller, sets the Application ID CHANNEL, and verifies that the message is received from the communication partner.
A command is generated each time each item is changed. Pressing the lit button will re-send the command for the current setting.
The bottom of the screen displays the timestamp at which the command was generated and the command beginning with :. The clipboard will copy the contents of this screen.
Terminal
Windows macOS Linux RasPi
This is a simple terminal that supports ANSI escape sequences (partial) and performs I/O directly with the TWELITE radio microcontroller.
| Operation | |
|---|---|
The value of , which is the packet type; packets from CUE usually have PKT_PAL=02.
| Operation | Desc. |
|---|---|
| Operation | Desc. |
|---|---|
| Item | Content |
|---|---|
| Item | Content |
|---|---|
[ A ]
Move to the previous item on the list.
[ A ] long press
Exit this screen and return to the previous menu.
[ B ]
Shifts to selection view.
[ B ] long press
Sorts items. Each time the sort is performed, the sort key changes sequentially.
[ C ]
Move to the next item on the list.
[ C ] long press
Controls and resets the reset pin of the TWELITE wireless module.
ESC ESC
Exit this screen by entering the ESC key.
[ A ]
No assignment
[ A ] long press
Exit this screen and return to the list view.
[ B ]
No assignment
[ B ] long press
No assignment
[ C ]
No assignment
[ C ] long press
Controls and resets the reset pin of the TWELITE wireless module.
ESC
Exit this screen and return to the list view.
Destination
The Destination. If you are a Child Node, specify "Parent Node:0". If you are the Parent Node, specify "All Child Nodes = 0x78" or a specific Child Node ID (up to 1..8 can be specified).
DI1..DI4
This is the setting status from DI1 to DI4. ■ means selection (LOW=GND level) and □ means (HIGH=VCC level). Specify SEL for the item below.
SEL
Selection bits for each DI (0 to ignore the DI designation, 1 to enable the designation)
PWM1..4
Set the duty ratio of PWM. 0 is equivalent to GND level, 1024 (100%) is equivalent to VCC level, and the PWM port set to N.A. is not changed. The LED of PWM1 on the TWESTAGE board is sucked in from VCC, so it lights up brightest at 0 and turns off at 100%.
Child Node ID
Destination. 1..8. Assign the same ID to the Child Node.
Color
Specify the lighting color from 7 colors. There are two types of white, one is a mixture of RGB colors and one is white LED lighting alone.
brightness
0..15 where 0 is off.
Light blinking
Select light-on or blinking pattern.
Lighting time
This function automatically turns off the light after a certain period of time after issuing a command.
Off button
Generates a lights-off message.
On button
Transmits the current settings.
[ A ]
Move tab (left)
[ A ] long press
Exit this screen and return to the selection screen.
[ B ]
No assignment
[ B ] long press
No assignment
[ C ]
Move tabs (right)
[ C ] long press
TWELITE Controls the wireless module's reset pin and resets it.
ESC
Exit this screen and return to the selection screen.
[ A ]
input + + + sequence (Interactive settings mode)
[ A ] long press
Exit this screen and return to the previous menu.
[ B ]
Display in large font. Display a partial area of the first screen. Select the area so that the cursor is displayed in the screen, but`, depending on the screen output, the part you want to see may not be visible.
[ B ] long press
Turn-on/off of the wrapping control, which by default is turned on, but can also be turned off. Text after the right edge of the screen is not displayed.
[ C ]
Go to the firmware programming screen. Shortcuts are provided for frequent source code modifications, operation checks, and build & write operations during firmware development.
[ C ] long press
Controls and resets the reset pin of the TWELITE wireless module.
ESC ESC
Exit this screen by quickly entering the ESC key twice. In most screens, pressing the ESC key once is the operation for exiting the screen, but since the terminal may use the ESC key alone, it is assigned to two consecutive entries.
