Please refer to handling of materials. If you have any questions or concerns, we would appreciate it if you would contact our support office.
The image files (screen captures), may differ from the version used, and there may be differences in the strings displayed in the images, menu order, etc.
TWELITE STAGE APP is a tool to build/program TWELITE wireless microcontroller series apps and view the execution results.
On Windows/macOS/Linux, the MWSDK, which contains compiler sample code, etc., is included. For more details, please refer to the following.
MWSDK in general -
MWX Library -
Designed to work on a variety of platforms.
Windows 10
macOS (High Sierra and later)》(High Sierra and later)
Linux (Ubuntu18.04)
Operating conditions, distribution format, and implemented functions differ depending on the platform.
About this document.
.
The following pages are listed to indicate supported platforms.
Windows -- Windows 10
LICENSE
LICENSE
The executable of TWELITE™ Stage distributed by Monowireless, Inc. is subject to MW-SLA-1J,1E.
For source code, applies. Please refer to the link for an overview.
If you build from source code, you can operate with MW-OSSLA-1J,1E
Raspberry Pi (Raspberry Pi 3 Model B, Lcd Touch Screen, Raspberry Pi OS August-2020)
(M5stack : supported up to version 1.0, v1.3 and later are not supported at source level)
which has more relaxed restrictions for non-commercial purposes.
Some distribution packages (as of 2020/10/9, only the 0.8.9a package for M5Stack is available) apply a dual license with MW-SLA-1J,1E and MW-OSSLA-1J,1E. Please check the license description in the package.
Please note that you must select MW-SLA-1J,1E for commercial use.
Open source deliverables used
We would like to thank the open source projects that provided us with high quality source code.
Name
Description
SDL2
Simple DirectMedia Layer Copyright (C) 1997-2020 Sam Lantinga
getopt
Copyright (c) 1987, 1993, 1994The Regents of the University of California. All rights reserved.
regex
regex - Regular expression pattern matching and replacementBy: Ozan S. Yigit (oz) Dept. of Computer Science York University
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.
Select from BIN
Select from BIN
WindowsmacOSLinuxRasPi
Writes a pre-built application (.BIN file).
selection screen
Selecting the menu will display a list of files. Select the firmware you wish to write.
Before selecting the menu, store the BIN file you want to write in the following.
Platform
Location
In the BIN folder, store the .BIN file (stored under the build folder of each project) built with TWELITE STAGE, without changing the file name.
The file name is used to identify BLUE/RED.
Other specifications etc.
Others
About environment variables
Graph
Graph
Accel real-time graph : Displays accelerometer packets in real time. Frequency domain display and CVS save function are available.
Sensor Graph : TWELITE Stores data from various sensors in a sqlite3 database and displays graphs.
specified
Specified Folder
WindowsmacOSLinux
Folders or .BIN files can be dragged and dropped throughout the TWELITE STAGE APP screen. Select to perform an operation on the dropped object.
When a .BIN file is dropped, the list of firmware in that folder will be displayed with the same behavior as if the folder in which the file is stored had been dropped.
This is an explanation of the TWELITE STAGE screen and operation methods.
About Execution
To start the TWELITE STAGE application, execute the executable found in {MWSTAGE Installation}.
When replacing the TWELITE STAGE application executable due to updates, etc., be sure to copy it to the designated folder {MWSTAGE Installation}. If you place the executable in any other folder, the behavior is undefined.
The execution method differs for each system (Windows, macOS, Linux).
system
file extension
notes
About Executable
Two executables are available.
TWELITE_Stage.{extension} - starts with default settings
TWELITE_Stage_VSCode.{extension} - "Use VSCode" is already set (settings are stored in TWELITE_Stage_VSCode.ini). Enabling the Use VSCode setting will make the behavior suitable for development work using VSCode It will become
Although it is not an error to launch multiple TWELITE STAGE applications, there are some functions (such as the sensor graph function) that are infeasible when multiple applications are launched.
In this case, make a copy of the executable and launch it as a separate file name. The file names of the various settings and input/output files will be different and will not interfere with each other.
About the Execution Screen
There are two types of running screens: one is the command screen (if started from the command screen, the same screen is used) and one is the main screen of TWELITE STAGE. The command screen is not normally used, although it is possible to check the operation and other auxiliary information.
Exit
Please use one of the following methods to exit.
Move the mouse pointer to the upper right on the execution screen, and the Exit button will appear. Press this button.
Close the window of the execution screen.
In rare cases, the run screen may remain after the exit operation. In this case, please try the following.
Close the command line window of the TWELTIE STAGE application.
Get the latest version
Get the latest version
TWELITE STAGE applications are distributed in the following ways
For Windows/Mac/Linux platforms, a complete set is distributed including development tools, etc.
TWELITE STAGE Binary Distribution
If you have the latest TWELITE STAGE app update from TWELITE STAGE SDK in your update history, or if you want to distribute the M5Stack version, please see below. Please check the tag on GitHub for the distribution version.
The TWELITE STAGE app is intended to work with the latest version of the TWELITE STAGE SDK, which is distributed as a stable plate. Newer TWELITE STAGE apps may not work properly with older SDKs.
Windows
Mac (macOS)
Linux
The Linux version is included in the package. Individual versions are not distributed. Please build from source code.
Raspberty Pi
Raspberry Pi version is included in the package. Individual versions are not distributed. Please build from the source code.
M5Stack
Versions up to 1.0.3a are stored below.
Source code (MWM5 library)
The MWM5 library containing the source code for TWELITE STAGE is available at.
serial port selection
Serial Port Selection
WindowsmacOSLinuxRasPi
Serial Port Selection
On Windows/macOS/Linux, a screen will appear at startup to select the serial port to which the TWELITE wireless microcontroller is connected. The serial port can be connected later without selecting it on this screen.
In the TWELITE STAGE application, the serial port selection is not linked to the processing of each screen. For example, if you start the viewer without selecting a serial port, the display will not be updated. If the serial port is selected in this state, the display will be updated. The serial port can be selected by `Alt(Cmdr)'.
The serial port can be switched at any time by pressing Alt(Cmd)+0,1,2,.... key operation.
Windows
Pressing the c key displays the COM port name of the serial port currently inverted in the list.
RasPi
On the Raspberry Pi, serial0 and serial1 will be displayed if there is a /dev/serial0/dev/serial1 in addition to the USB device. Usually serial0 is used.
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.
Screens
Screen
WindowsmacOSLinuxRasPi
example screen, menu
Windows/Mac/Linux/RaspberryPi(X11)
TWELITE STAGE is an application that is launched from the console screen (command line). Information is output to both the console screen and the window screen.
The console screen outputs the same information as the terminal.
The console screen is accepted in some environments, but it is not a confirmed official feature.
RaspberryPi(FB)
The screen is displayed on a framebuffer without X11. The console screen is not normally displayed (when started from a shell screen on the framebuffer).
SERIAL PORT SELECTION
Serial port selection
WindowsmacOSLinuxRasPi
Reselect the serial port.
Serial port selection
You can use Alt(Cmd)+0, Alt(Cmd)+1,2,... are also allowed.
Installation
Installation
Depending on the environment, this application may not work or may require various settings. If you encounter any problems, please refer to the description in this document to improve your environment.
In order to build a development environment, you must install the software suite and agree to the license agreement. In addition, you may need to configure security settings on your PC or workstation.
terminal
Terminal
WindowsmacOSLinuxRasPi
This is a simple terminal that supports ANSI escape sequences (partial) and performs I/O directly with the TWELITE radio microcontroller.
Operation
Logging function
Logging Function
WindowsmacOSLinuxRasPi
TWELITE Allows logging of serial communications with a wireless microcontroller.
Simple monitor
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
main menu
Main Menu
WindowsmacOSLinuxRasPi
This is the top level of the hierarchical menu.
On this screen, you can make various menu selections. When the menu is inverted, a simple explanation is displayed in the green text area at the bottom.
app rewrite
Write(program) Application Firmware
WindowsmacOSLinuxRasPi
Write the application (firmware) for the TWELITE wireless microcontroller.
Write a pre-built .BIN file (Windows/Mac/Linux/RasPi)
re-write
Re-programming
WindowsmacOSLinuxRasPi
Re-selects the item that was specified and re-programmed immediately before.
Depending on the selection, the behavior will be one of the following
Windows
TWELITE_Stage installation (Windows)
Windows
Environment
The following environment is used for development.
Build and write from a source file such as Act (Windows/Mac/Linux/RasPi⌘)
TWELITE STAGE eliminates the complexity of building source files, disconnecting from the terminal, starting the write utility, and connecting to the terminal during development.
Automatic recognition of TWELITE BLUE/RED (Windows/Mac/Linux/RasPi)
Reset and go to Interactive settings mode or Terminal after writing is finished (Windows/Mac/Linux/RasPi)
Start the project folder or VSCode on the list of each project (Windows/Mac/Linux/RasPi)
Open the related website on the list of each project (Windows/Mac)
Re-programming of the selected project
last selected
Windows 10 version 1903
VisualStudio 2019 (32bit build )
Requirements for operation
FTDI's FT232 series may require device driver installation to work; if MONOSTICK or TWELITE-R is not recognized, please install the D2XX driver from ftdichip.com. Visual C++ Distributable Code for Visual Studio 2019 (runtime library) may be required. If you get an error when starting the application and it does not start, please redistribute it in this package TWELITE_Stage³_INSTALL³VC_redist.x86.exe or get it from Microsoft's website and install it. Distribution binaries are 32-bit.
Description : Menu to display the description. Open the following instructions in your browser.
TWELITE STAGE application (this document)
MWX library
TWENET_C library
Screen Example
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.
[ A ]
No assignment.
[ A ] long press
Exit this screen and return to the previous menu.
[ B ]
Change the font.
[ B ] long press
Although we take all due precautions when distributing the software, we ask that you take care to check for viruses, etc.
Please check with the administrator of your environment regarding your security policy and operations (e.g., whether or not to install external applications).
Download the TWELITE STAGE SDK for your system (Windows, macOS, Linux, etc.).
Extract the downloaded archive file (e.g. ZIP). The folder name of each level of the destination folder should not contain any characters other than one-byte numbers 0..9, one-byte alphabets a..zA..Z, and some symbols -_. . It must not contain spaces, Kanji characters, Hiragana characters, etc. Example(Windows): × C:\work\作業\ × C:\Users\user1\work dir\ 〇 C:\Work\Work1
Check the folder after expansion. If you extract on C:\Work, the folder name will be something like C:\Work\MWSTAGE, but your extractor may create a folder with the archive file name. Rename or move the folder as needed.
In the text, the expanded folder (e.g. C:\WorkMWSTAGE )} may be written as {MWSTAGE installation}.
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 ]
Start Logging
WindowsmacOSLinuxRasPi
Allows logging of serial communications with the TWELITE radio microcontroller.
Press Alt(Cmd)+L key.
Ending logging
Press Alt(Cmd) + L again during logging.
Logging will finish and the log file will be opened in the OS standard way (Notepad for Windows, Console for macOS).
RaspberryPi only saves the log file and does not have the ability to open it.
Logging
String received from the TWELITE radio microcontroller → Logged as is
TWELITE Character string sent to the wireless microcontroller → Each character is enclosed by " " for Windows, " " for macOS/Linux/RaspBerryPi. "" to record the characters.
For example, "t" means you entered t from the keyboard.
Logging folder and file name
WindowsmacOSLinuxRasPi
The file will be saved in {Folder with TWELITE STAGE APP executable}/log with a file name based on the date and time when the logging started.
Press Alt(Cmd)+Shift+L to open that folder.
Linux
TWELITE_Stage installation (Linux)
Linux
USB device ID for TWELITE R2 has changed from 0403:6001 to 0403:6015. udev setting needs to be added.
32bit version is not available.
The Linux environment has different types of packages available depending on the distribution and version. You may need to install and configure packages individually.
Please refer to general information by referring to the error messages.
Environment
TWELITE STAGE is developed and tested in the following environment.
Ubuntu 16.04, 18.04, 20.04
NNLinux Beta8 64bit
Centos7
device driver
In order to recognize MONOSTICK or TWELITE-R from TWELITE STAGE, you must unload the ftdi_sio module and also have read/write permission to the USB device.
The ID of the USB device will be as follows.
Vendor ID 0x0403
Product ID 0x6001(MONOSTICK,TWELITE R) or 0x6015 (TWELITE R2)
We have a udev configuration script Ј(Ubuntu, CentOS Ј) to automate this configuration. It copies the definition to /etc/udev/rules.d and reloads the configuration. After configuration, unplug and plug the USB device before running TWELITE_Stage.run. If the USB device appears on the screen right after startup, the configuration is reflected.
Ubuntu 16.04, 18.04. 20.04
Definition file (line breaks for easier reading)
Centos 7
Definition file (line breaks for easier reading)
Application Registration
Register your program according to your desktop environment if necessary.
You may not be able to run TWELITE_Stage.run from the file icon on your desktop. This is because the system may not recognize TWELITE_Stage.run as an executable.
Ubuntu 16.04, 18.04, 20.04
Definition file generation scripts for Ubuntu are available.
This script creates a .desktop file (app definition) in $HOME/.local/share/applications.
After the script is executed, the TWELITE STAGE icon will be added to the application list.
Act extras
Ac extras
WindowsmacOSLinuxRasPi
Build and rewrite Act.
Act Extras include those that use external open source libraries and other resources, and those that perform relatively complex processing.
When this screen is opened, a list of projects is displayed. Select the project you wish to write, and the build - write will be performed. After the writing is finished, press Enter or [ B ] button to reset the TWELITE radio module and go to the Interactive settings mode screen (or Terminal screen, configuration required).
If you have set up to use VSCode at the TWELITE STAGE settings, do not build, but open under build/.
Folder
The projects to be built are located as follows
Operation
Operation
Desc.
macOS
TWELITE_Stage installation (macOS)
macOS
環境
We develop in the following environment
macOS 10.14 (Mojave, Intel)
macOS 12.4 (Monterey, Apple Silicon)
Additional installation and warning dialogs.
The download archive is not signed. At runtime, you may receive a security warning as an application downloaded from the Internet.
You may be asked for permission to run from the path where you installed TWELITE_Stage.
You may get an installation dialog for the make utility when executing a build.
The above is required to give permission or installation work for the TWELITE_Stage to work.
Reference: Manual installation of the make utility
※ Different OS versions and other factors may require a different procedure.
If an error occurs when executing make on the command line (bash), install XCode.
After installation is complete, type "make" and the following message should appear.
Handling of Serial Port
MONOSTICK and TWELITE-R use FT232 series semiconductors from FTDI (https://www.ftdichip.com). In order to use them, you may need to deal with device drivers.
If the serial port does not appear when you start TWELITE-R, you need to unload (disable) FTDI's driver. See "Reference" below.
Reference: utilities from FTDI, Inc.
This utility suppresses the loading of the OS standard device driver when our MONOSTICK or TWELITE-R is inserted, but it also suppresses it for non-MONOSTICK devices (those with the same USB ID).
Download and use D2xxHelper from https://www.ftdichip.com/Drivers/D2XX.htm. You can find the same in our archive in the TWELITE_Stage/INSTALL folder.
Reference: Manual unloading of FTDI device drivers
Unload FTDI-related drivers.
REVISION HISTORY
revision history
For the revision history of the source code, please refer to and .
The latest version of the revision history may not match the distributed version for each platform.
1.3 MWSTAGE2022_07 recorded version
Major version upgrade.
Act build & rewrite
Act build&Wrt
WindowsmacOSLinuxRasPi
Build and rewrite Act. (Windows/Mac/Linux)
Focus on small-scale source code that can be used as a reference for writing Act (Act).
Interactive settings mode
Interactive settings mode
WindowsmacOSLinuxRasPi
Transition to Interactive settings mode and operation.
This screen behaves much the same as the terminal, but has additional features specific to Interactive settings mode, such as operation for Interactive mode transitions and detection of leaving.
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.
The toolchain is code-signed, but if the code signature is not properly authenticated, you may be asked for permission to run each executable in the build toolchain (ba-elf-gcc etc.}).
The TWELITE radio module to be connected must have furware written for Interactive settings mode.
Since the system operates using input/output from the TWELITE radio microcontroller, it may not be possible to transition to or leave Interactive settings mode as expected, for example, if garbled characters or other problems occur in serial communication.
Mouse operation is not supported. Keyboard operation (using the cursor up/down) is supported.
Transition to Interactive settings mode and operation by terminal is also possible.
The terminal does not operate the SET pin, so the SET pin must be manually set to LO.
The operations to input Alt(Cmd)+I and module reset Alt(Cmd)+R are defined.
Operation flow of Interactive settings mode screen
The following is a rough process flow.
$ cd ./MWSTAGE/TWELITE_Stage/INSTALL/ubuntu/
$ sudo ./set_udev_sudo.sh
[Screen black background].
↓↓
[TWELITE wireless microcontroller reset (SET=LO if controllable)]
↓↓
<Detect interactive mode message for intermittent operation application? > --YES--> Go to [operation screen
↓Time out.
['+' three times].
↓↓
<Detect interactive mode message for normal app? > --YES--> Go to [operation screen
↓Time out
Go to [operation screen] * This state is not Interactive settings mode
[operation screen]
↓↓
<Interactive settings mode escape message? > --> [Exit].
↓
<Leaving screen operation [ A ] long press etc. > --> [Exit].
↓
<ESC ? > -> <determination during input> --NO-> [Exit].
↓ ↓
[Send input string to TWELITE radio module]
↓↓
Return to [Operation screen
[Exit]
↓↓
[TWELITE radio microcontroller reset]
↓↓
[Exit screen] Exit Interactive settings mode screen and return to previous screen.
Changed internal drawing resolution from 320x240 to 640x480 pixels
Added real-time graphs for accelerometer
Added sensor graph to save and graph sensor data
Added support for English display
Changed main manual to local html file
1.0.8 MWSTAGE2021_09 recorded version.
[ A ][ B ][ C ] buttons sometimes remained out of pointer
CRLF is now sent to TWELITE on Enter input in STAGE APP.
updated FTDI library on Mac to work on Apple Silicon(M1) without using serial intermediary program.
added setting the PATH of msys tools on Windows to prevent unexpected make from being invoked.
added support for moving to the write screen even when TWELITE is not connected (by entering B,R keys and specifying the target TWELITE model).
When VSCode is used, the screen for writing .bin files under build/ is opened instead of executing build when Act or TweApps is selected. (Build is performed from VSCode)
Set some environment variables internally and made VSCode started from TWELITE STAGE refer to these variables so that VSCode can execute appropriate builds and refer to appropriate library sources for VSCode's code interpretation
Sample code is stored under the MWSDK folder, but by dropping the build target folder, build and write operations can be performed in folders other than the MWSDK folder (folder names must not contain spaces, Japanese characters, etc.)
The internal folder settings and environment variable settings are now displayed on the console screen at startup.
STAGE APP is terminated after waiting 1 second when terminating.
1.0.7pre2
Enhanced support for Raspberry Pi (1.0.7pre2)
Added serial0 support (TWELITE STAGE HAT)
Added build for Zero (disable build & draw fade function in supported libraries)
Added build for X11 desktop
Added support for general FTDI devices (FT232, FT230). Firmware write mode must be done manually
Added the function to display the COM port assigned by Windows by pressing c key on the serial port selection screen on Windows.
added the ability to change the baud rate from 115200bps
Added a command line option (-E 0) to disable the drawing fade function.
1.0.3 MWSTAGE2020_12 recorded version
TWELITE CUE support (parser and CUE viewer)
Verify (compare) when writing in the rewrite menu.
Apple Silicon tentative support (TWELITE_Stage.command is universal app, external command sersrv_ftdi.command for serial processing, Tools rebuilds intel binary that can work with Rosetta2, serial communication is slower because it is via an external command)
Moved MWSTAGE/MWSDK/Tools to MWSTAGE/Tools in the folder structure. (To make MWSDK available as it is in MWSDK_COMMON repository)
TWELITE_Stage.ini (remove extension from startup filename and add .ini) is now loaded at startup and the MWSDK folder can be selected. (It is now possible to easily switch between older versions of the library set.)
Changed SDL2 library for screen rendering to 2.0.12 (Windows, MacOS, RaspberryPi).
The DLL file is no longer necessary for Windows as a static build.
The number of parallel builds by make -j is now (number of physical CPUs - 1).
reopen serial port explicitly in some places of rewrite menu. added support for easy recovery from USB disconnection when a device is unplugged or plugged in.
added support for opening the folder TWENET/usever.mk when opening mwx or twesettings by pressing Alt(Cmd)+Shift+m, t.
The following changes have been made.
[Raspberry Pi] Fixed a problem that write menu transition at /dev/serial0 fails at the first boot.
Known Issues
Help message may not appear when Alt(Cmd) is pressed down at startup; it appears by typing Alt(Cmd)+0.
In the rewrite menu, when the file name is too long, the line may be disrupted.
We have not fully tested the operation on Apple Silicon.
0.9.11 MWSTAGE2020_10, Raspberry Pi version (tentative)
(* This version is not comprehensively verified.)
Operation on Raspberry Pi
Other functional adjustments
0.9.9 - MWSTAGE202020_10 included version
Added [Web] button to the top level menu as well, so that the related links can be opened in the browser.
Implemented the function to open in Folder, Web and VS Code of Linux version.
It was sometimes difficult to transition to the write menu when the TWELITE radio module was frequently outputting UART.
1.0.3 MWSTAGE2020_12 version
TWELITE CUE support (parser and CUE viewer)
Verify (compare) when writing in the rewrite menu.
Apple Silicon tentative support (TWELITE_Stage.command is universal app, external command sersrv_ftdi.command for serial processing, Tools rebuilds intel binary that can work with Rosetta2, serial communication is slower because it is via an external command)
Moved MWSTAGE/MWSDK/Tools to MWSTAGE/Tools in the folder structure. (To make MWSDK available as it is in MWSDK_COMMON repository)
TWELITE_Stage.ini (remove extension from startup filename and add .ini) is now loaded at startup and the MWSDK folder can be selected. (It is now possible to easily switch between older versions of the library set.)
Changed SDL2 library for screen rendering to 2.0.12 (Windows, MacOS, RaspberryPi).
The DLL file is no longer necessary for Windows as a static build.
The number of parallel builds by make -j is now (number of physical CPUs - 1).
reopen serial port explicitly in some places of rewrite menu. added support for easy recovery from USB disconnection when a device is plugged or unplugged.
Known Issues.
Help message may not appear when Alt(Cmd) is pressed down at startup; it appears by typing Alt(Cmd)+0.
In the rewrite menu, when the file name is too long, the line may be disrupted.
We have not fully tested the operation on Apple Silicon.
0.9.11 MWSTAGE2020_10, Raspberry Pi version (tentative)
(* This version is not comprehensively verified.)
Operation on Raspberry Pi
Other functional adjustments
0.9.9 - MWSTAGE202020_10 included version
Added [Web] button to the top level menu as well, so that the related links can be opened in the browser.
Implemented the function to open in Folder, Web and VS Code of Linux version.
It was sometimes difficult to transition to the write menu when the TWELITE radio module was frequently outputting UART.
When this screen is opened, a list of projects is displayed. Select the project you wish to write, and the build - write will be performed. After writing is complete, press Enter or [ B ] button to reset the TWELITE radio module and go to the Interactive settings mode screen (or Terminal screen, configuration required).
If the configuration is set to use VSCode (open a folder with application rewrite>code), do not build, but open the Build to write BIN file screen under build/.
During this commentary, the cupcake image of the previous version is shown.
TWELITE ARIA
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.
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.
No indication of whether the magnetic sensor is awake or not due to detection.
000desc.txt
000desc.txt
If 000desc.txt is created in the project folder, TWELITE STAGE APP will display its contents in the list of project folders.
Example of display with 000desc.txt
The file is written in UTF-8. There are two types of formats.
Format 1
The first line is the title line.
The second and subsequent lines are descriptions of the details.
If the last line starts with http, it is a link to a website.
Format 2
The format is like an ini file. The item name starting at the beginning of the line and up to the = character is the item definition, and the rest is the content of the item.
Item Definition
Details
About URL specification
About folder structure
About Folder Structure
The TWELITE STAGE APP runs as a front-end application in the TWELITE STAGE SDK package. Here is its folder structure.
MWSDK folder
The MWSDK folder contains libraries for building software for the TWELITE wireless microcontroller, samples, and source code for the TWELITE APPS.
TWELITE_Stage.sav
Records configuration information within the TWELITE Stage application.
The file name is the TWELITE_Stage app file name + .sav.
TWELITE_Stage.ini
see for details.
MWSDK= Edit to specify a different folder instead of the MWSDK/ folder. This is useful if you want to mix multiple library versions. The above example uses the MWSDK2020_10 folder.
LANG= Specify LANG=en to set the display language of TWELITE Stage to English.
Run TWELITE Stage with different settings
Copy TWELITE_Stage.exe (on Windows) with a different file name. For example, if you change it to TWS1.exe, it refers to the configuration files TRS1.sav and TRS1.ini.
BIN folder
When you select the TWELITE STAGE APP's menu, the firmware files (.BIN) for the TWELITE radio microcontroller in this folder are enumerated.
log folder
Log files are stored in this folder when the serial port is performed in the TWELITE STAGE APP.
This folder is also used to store databases when using the graphing function and to output csv files.
Tools folder
This folder contains toolchains for gcc, g++, and other cross-compilers.
Platform specific utilities are also stored in this folder. See Tools/reame-j.txt for details.
About the build project folder
This function is introduced as an extra function. It may work differently from what is described.
Search order of folders
Search for build project folders (e.g., Act_samples) in the following order
the folder where the TWELITE STAGE app was launched
the folder where the TWELITE STAGE app executable is located
{MWSDK folder}/...
MWSDK searches starting from the folder where the TWELITE STAGE APP executable is located.
Wks_Acts
If the Wks_Acts folder exists, this folder is referenced from the menu item Act Build & Rewrite instead of the Act_samples folder.
This folder is intended to be used to store build projects that you create yourself in Wks_Acts.
TWELITE APPS build & rewrite
TWELITE APPS build&Wrt
WindowsmacOSLinuxRasPi
Build and rewrite TWELITE APPS. (Windows/Mac/Linux)
The source code is mainly written in C language by TWENET C API and is relatively large in scale to be used as is.
When this screen is opened, a list of projects is displayed. Select the project you wish to write, and the build - write will be performed. After the writing is finished, press Enter or [ B ] button to reset the TWELITE wireless module and go to the Interactive settings mode screen (or Terminal screen, configuration required).
If you are set to use VSCode (perform programming > open a folder with code), do not build, but open the under build/.
Folder
The projects to be built are as follows
Operation
Operation
Desc.
RaspberryPi
TWELITE_Stage installation (Raspberry Pi)
RasPi
The TWELITE Stage app runs on a Raspberry Pi.
Mouse and touch screen support.
The build toolchain is included and can be used to compile the application.
build/rewrite screen
Build and Programming Screen
WindowsmacOSLinuxRasPi
During Build
This is the screen during the build process. The contents of the build commands are output to the console screen. ..." in the screen shows the number of files being built. is the number of files being built, and the darker color at the bottom is the name of the file being built.
glancer
Glancer
WindowsmacOSLinuxRasPi
Glancer is an English word for a person who glances, and it is a simple display of . 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.
Command line args and ini file
Command line arguments and ini file.
command line arguments
Command line arguments provides some minor settings of TWELITE Stage.
Arg
Desc.
{MWSTAGE installation folder}/MWSTAGE/Act_samples
Turn on LED when switch is pressed
act4 runs an act that turns on an LED when a switch connected to the TWELITE DIP is pressed.
https://mono-wireless.com/jp/products/act/index.html
... /MWSTAGE/ TWELITE STAGE SDK Installation.
/TWELITE_Stage.???? Executable (Windows .exe, macOS .command, Linux .run)
/TWELITE_Stage.sav Configuration file
/TWELITE_Stage.ini Other settings
/TWELITE_Stage/ TWELITE STAGE APP related files
/MWSDK/ MWSDK libraries, etc.
/BIN/ Destination for [BIN file selection
/log/ Logs and databases
/Tools/ gcc compiler and other tools
MWSDK/
Act_samples/ : sample code by mwx library
Wks_TweApps/ : source code for TWELITE APPS
Act_extras/ : more specialized samples by mwx library, citing other libraries
TWENET/ : TWENET library (mwx library and others)
ChipLib/ : semiconductor library
MkFiles/ : body processing part of Makefile
docs/ : Library manuals, etc.
000manifest : Version information of MWSDK
Open related websites.
Open ALt+Shift+m mwx library and Alt+Shift+t twesettings library.
Ability to open folders and build error files currently selected in the build menu.
File name is twestage_{date-time}.log
Shift+Alt/Cmd+L to open log file folder
Changed the behavior when dropping a folder (it used to be a binary write, but now it is a menu transition)
When the terminal is pressed and held down for a long time, the screen is cleared in addition to resetting by pressing [C].
Four executable versions are available: framebuffer version, X11 version, framebuffer lightweight version, and X11 lightweight version. The lightweight version omits semi-transparency effects, etc.
Depending on the OS type, version, and installation status of your RaspberryPi, it may not work or you may need to recompile it.
Environment
TWELITE STAGE has been developed and tested in the following environment.
Hardware
Raspberry Pi 3 Model B
LCD Screen: Raspberry Pi Touch Display (7")
OS & distribution
Raspberry PI OS (32bit) Lite (Version:August 2020)
Known Issues/Limitations.
Operation of /dev/serial0 may fail on the first boot.
The operation of /dev/serial0 has not been tested on Raspberry Pi 4B.
Touch screen operation has not been tested on Raspberry Pi 4B.
The input string to TWELITE STAGE is passed as is to the input string to the shell or getty running on /dev/tty1. It is recommended to start from /dev/tty1.
This may be affected by other installations or running programs (such as X11).
Extract archive
The downloaded archive file should be extracted to a folder whose path name does not contain spaces or Japanese characters.
In the following, it is extracted to the home folder of the Raspberry Pi.
folder structure
Device Driver
In order to recognize MONOSTICK or TWELITE-R from TWELITE STAGE, you must unload the ftdi_sio module and also have read/write permission to the USB device.
The ID of the USB device will be as follows.
Vendor ID 0x0403
Product ID 0x6001(MONOSTICK,TWELITE R) or 0x6015 (TWELITE R2)
A udev configuration script is provided to automate this setup. It copies the definition to /etc/udev/rules.d and reloads the configuration. After configuration, unplug and plug the USB device before running TWELITE_Stage.run. If the USB device appears on the screen right after startup, the configuration is reflected.
Definition file (line breaks for easier reading)
UARTについて
In the environment described above, /dev/serial0 is available by configuring the serial port from raspi-config.
Wiring example
Refer to the manufacturer's manual for both TWELITE and RaspberryPi.
DIP# is the pin number of the TWELITE DIP.
The above wiring does not guarantee stable operation of the TWELITE wireless microcontroller module.
Launch TWELITE Stage app.
It will not run on the X11 desktop; close X11.
Run TWELITE_Stage.run. The TWELITE Stage app will appear on the screen screen.
Notes.
Mouse and touch screen are supported.
During the TWELITE Stage app, the characters you enter may also be displayed on the console screen.
Others
/dev/dri
You may get the following error when starting TWELITE_Stage.run.
You may ignore it.
Insufficient memory
At build time, if the number of CPUs is 4 or more, the parallel compilation is executed minus one CPU number (3 parallel compilations for 4 cores). In some cases, insufficient memory may occur. In that case, please change the number of parallels.
RaspberryPi 4
This information has not been fully validated.
The following settings are required: OpenGL related drivers must be enabled.
Set rendering type by {type} value:
0: default
1: OpenGL
2: DirectX(Windows) Metal(macOS)
3: Software.
-J
Enable game controller.
-x {x_pos}, -y {y_pos}
Set position of TWELITE STAGE App graphical winodow at launch. The {x_pos} and {y_pos} is the screen coordinate of window top-left.
an ini file.
The ini file is used to set some fundamental settings of TWELITE STAGE (like reference MWSDK folder).
The ini file name is {basename of TWELITE STAGE app executable} + .ini, which is normally TWELITE_Stage.ini.
Syntax
The ini file is described as a plain text file.
A key and value is stored in a single line separated with = character (e.g. KEY=value).
A key value string shall begin with line head. (No spaces or other character allowed before a key string.)
No space allowed between the = character.
Comment line is started from ; or # characacter.
Settings
Key
Value.
MWSDK
Change MWSDK folder to another one. The default folder is MWSDK at the same folder where TWELITE STAGE App executable is located. If you need to use older or custom MWSDK, you can specify the name of its folder.
LANG
LANG=en will change the user interface language from default(Japanese) to English.
GEOM_X, GEOM_Y
Change the location of TWELITE STAGE App window is shown
different settings of TWELITE STAGE App.
If you need to different setting type of TWELITE STAGE App, just copy an executable at same folder of the original TWELITE_Stage executable.
e.g. if you needs English interface vesion, you just copy TWELITE_Stage.exe(Note: .exe is suffix of Windows executable) to TWELITE_Stage_en.exe and create .ini file with LANG=en setting.
[JAPANESE]
TITLE=Actのテンプレート
DESC=中身が何もない setup(), loop() のみのファイルです。
新しく Act を記述するのに利用してください。
URL=jp/MWX/content/act_samples/README.html
[ENGLISH]
TITLE=Act empty template
DESC=This act file only contains empty setup() and loop(),
which is intended to write a new Act.
URL=en/MWX/content/act_samples/README.html
{MWSTAGE installation folder}/MWSTAGE/Wks_TweApps
$ cd /home/pi
$ unzip MWSTAGE2020_XX_YYYY.zip
../MWSTAGE
TWELITE_Stage.run TWELITE_Stage App.
BIN/ BIN files of App. firmware
MWSDK/ MWSDK library, etc.
TWELITE_Stage/ TWELITE_Stage Application related files
$ cd ./MWSTAGE/TWELITE_Stage/INSTALL/ubuntu/
$ sudo ./set_udev_sudo.sh
$ sudo raspi-config
From the Menu:
"3 Interface Options Configure connections to peripherals"
→"P6 Serial Port Enable/disable shell messages on the serial connection"
Select the following: do not use as a login shell, or enable hardware.
"Would you like a login shell to be accessible over serial?" -> <No>
"Would you like the serial port hardware to be enabled?" → <Yes>
"The path /dev/dri/ cannot be opened or is not available"
;;; change MWSDK reference.
; MWSDK=MWSDK
MWSDK=MWSDK2020_10
;;; Interface language
LANG=en
;;; Window geometry
;GEOM_X=200
;GEOM_Y=100
TWELITE_Stage.exe
TWELITE_Stage.ini | no special settings
TWELITE_Stage_en.exe | copy of TWELITE_Stage.exe
TWELITE_Stage_en.ini | LANG=en is set
compiling...
Build error
compile error
If the build fails, the screen will look like the above. You can execute a rebuild or view the error log. It will also return to the straight line menu as time expires after a certain period of time.
Only typical error messages are displayed on the screen. When a build fails, error messages may not be displayed.
Operation
Desc.
[ A ] long press
Exit this screen and return to the previous menu.
[ B ]
Rebuild on error
[ C ]
Show error log (Windows/Mac)
The error log is {project folder}/build/builderr.log.
Programming (Writing firmware)
If the build is successful, the screen for writing firmware is displayed.
After v1.0.2 or later, after the firmware is rewritten, a verification process is performed to read and check the rewritten contents.
Programming
Failure while programming
Failure while programming
If the programming is in error, the screen will look like the above
Operation
Desc.
[ A ] long press
Exit this screen and return to the previous menu.
[ B ]
Perform programming again (returns to the previous programming menu. Since the menu item for programming is still selected, press [ B ] again to perform the programming again).
ESC
Exit this screen and return to the programming menu.
Completion of programming
Completion of programming
If the programming is successfully completed, the above message is displayed.
From v1.0.2 onward, after the firmware is rewritten, a verification process is performed to read and check the rewritten contents.
Operation
Desc.
[ A ] long press
Exit this screen and return to the previous menu.
[ B ]
Reset the TWELITE radio module and go to the Interactive settings mode screen (or terminal, depending on your settings) screen.
ESC
Exit this screen and return to the programming menu.
操作
[ A ] long press
Exit this screen and return to the previous menu.
[ B ]
Reset the TWELITE wireless module and go to the Interactive settings mode screen (or terminal, depending on your settings) screen.
ESC
Exit this screen and return to the programming menu.
List view
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).
Operation
Desc.
[ 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.
Selection view
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.
This section describes the operation through the TWELITE STAGE application.
Key Operations.
WindowsmacOSLinuxRasPi
Keystrokes while pressing ALt(Cmd) are operations such as changing the settings of the TWELITE STAGE app. Other keystrokes are usually on-screen inputs.
Common keys
WindowsmacOSLinuxRasPi
Key
Meaning
help screen
WindowsmacOSLinuxRasPi.
In Windows/macOS/Linux, you can press and hold Alt(Cmd) to display the help screen. The help screen will display a description of the keys that can be operated together with Alt(Cmd) and some operational status.
The help screen is also displayed by moving the mouse pointer to the upper left part of the screen.
The following table describes the operations while holding down Alt(Cmd) on Windows/macOS/Linux. In the table, Alt(Cmd)+ is omitted; pressing Alt(Cmd) will bring up a help screen to check the available keys, which are supplemented in the table below.
Other operations
key
meaning
Mouse Operation
WindowsmacOSLinuxRasPi.
Mouse is mostly left click, but right click, right double click, and wheel may be used.
Mouse Operation
Meaning
A,B,C buttons with mouse
WindowsmacOSLinuxRasPi.
The TWELITE STAGE application has a menu that resembles a row of three hardware buttons to which functions are assigned for each screen. When you move the mouse pointer over the menu display at the bottom of the screen, buttons labeled [ A ], [ B ], and [ C ] will appear. Left-click or long-press left-click on this button to select a function. (You can also use Alt(Cmd)+a,s,d or Alt(Cmd)+Shift+a,s
In-screen operations with the mouse
WindowsmacOSLinuxRasPi
On Windows/macOS/Linux, the TWELITE STAGE screen structure consists only of text strings in principle, but menus, buttons, and tabs can be operated with the mouse.
Although it consists only of text, tabs at the top of the screen and highlighted text can be selected with a left mouse click.
TWELITE STAGE settings
Setting up a TWELITE STAGE
WindowsmacOSLinuxRasPi
Configure various settings.
Setup screen
Menus on this screen cannot be operated with the mouse.
It may be difficult to see if you change the color of the screen.
In the menus in the following explanations, there are items that do not exist on some platforms, but all are enumerated and explained.
Color settings other than those in the common menu are omitted.
root menu
common setting
Settings
Content
Wrt Firmware
設定
内容
Saved Data Utility
This screen is a utility that performs maintenance of the data save area, emulating an EEPROM(64 bytes as one sector, up to 60 sectors, 3840 bytes).
Settings
Contents
On WindowsmacOSLinux it is stored in the file {executable name}.sav, i.e. TWELITE_Stage.sav.
CUE viewer
CUE Viewer
WindowsmacOSLinuxRasPi
Interpret messages from .
During this commentary, the cupcake image of the previous version is shown.
commander
Commander
WindowsmacOSLinuxRasPi
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
[ C ] long press
Open a folder (project, related folders). You can set it to open in VS Code in the settings menu.
ESC
Exit this screen and return to the rewriting menu.
[ 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.
[ 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.
Press and hold Shift + A, S, D
A, B, C button.
C
Copy the string of the displayed screen to the clipboard. (The range varies depending on the screen.)
V
Paste from the clipboard as keyboard input.
F
Go to full screen; Shift+F will zoom in more if possible.
G
Change the way the screen is drawn. 640x480 LCD screen is emulated, but you can select one of four drawing methods (1. LCD monitor-like drawing / 2. CRT-like drawing / 3. enlarged with prominent dots / 4. enlarged with blurred dots) when zoomed in. The setting can be changed to the startup setting in the setting menu. The setting can be made at startup in the settings menu.
J
Select the screen size. The available screen sizes are {640,480}, {1280, 720}, {1280,960}, {1920,1440}, {2560,1440}, and {320,240}.
* You can set the startup settings in the settings menu.
Q
Exit TWELITE STAGE.
0
Disconnect the serial port and list the serial ports again.
1,2,...
Select a serial port.
L, Shift+L
Start logging serial port input/output. When finished, the log file will be opened in Notepad on Windows or in Log Viewer on macOS. If you want to open the log folder, press Shift+L to open the folder containing the log.
use by screen
right double-click
escape from screen (same as ESCESC)
wheel
use depending on screen (zoom in/out on graph screen)
,
d
to select)
ESCESC
Press ESC twice quickly. Cancel, return to previous screen. Depending on the screen, one ESC will return you to the previous screen.
Enter
Input, select
Cursor↑↓
Select item
Alt(Cmd)+ key
Meaning
I
Enter + + + key sequence to enter Interactive settings mode.
* Interactive settings mode is not entered with + + + for applications that perform intermittent operation due to sleep.
R
Resets the module, using the TWELITE R or MONOSTICK function to control the reset pin.
A, S, D
Press the A, B, or C button.
Alt(Cmd)+Shift+Ctrl+m
Open MWX library code folder
Alt(Cmd)+Shift+Ctrl+m
Open the log folder
Left Click
Select
Drag while left-clicking
Used depending on the screen (dragging on a graph screen)
left double-click
not used
Example of the virtual [ B ] button at the bottom of the screen
v
right-click
Specify the text color and background color. The color setting values of the common settings are inherited by the settings of other screens. If other screens have not yet been set, the color settings in the common settings will be used. Colors are specified as 24-bit RGB hexadecimal numbers, but the values are internally rounded to 16-bit 565 format.
Baud Rate
TWELITE Set the baud rate on the radio module side so that the terminal and other displays will not be corrupted if the baud rate on the radio module side is not 115200.
The Windows Window compiler can generate slightly smaller binaries through the LTO mechanism, but linking takes time. This procedure can be eliminated, allowing for faster linking.
Entering YES erases all sectors.
Startup App.
This is the setting for moving to the viewer application when TWELITE STAGE is started. The value is 1... {numbers listed in the viewer app menu}. If the serial device ID is not set, it will wait for input on the serial device selection screen when starting.
Screen size and drawing method
WindowsmacOSLinuxRasPi Specify by 2-digit XY character (X:Screen size Y:Drawing method)X 0:640x480 1:1280x720 2:1280x960 3:1920x1440 4:2560x1440 5:320x240, Y 0:LCD-like 1:CRT-like 2:Blurred 3:Block
Serial Device ID
The WindowsmacOSLinuxRasPi setting is a serial device name or a numeric value of 1...9. For numerical values, the order of device enumeration is used.
Number of make jobs at build time
WindowsmacOSLinuxRasPi This is the number of parallel jobs for builds. Setting an appropriate number can be expected to reduce build time. The default value of 0 is calculated by (number of physical processors - 1). As a rough guide, the number of logical processors should be used as the upper limit.
Open a folder with VSCode
WindowsmacOSLinux Setting 1 opens the folder with the code command (VS Code) instead of the standard OS folder window.
Screen after rewriting is completed
Set WindowsmacOSLinuxRasPi 1 to open the terminal instead of the Interactive settings mode screen. 2 to return to the rewrite menu.
r
Reads a sector. 0..59 is entered, the contents of the sector with the entered sector number are displayed.
R
(Entering YES reads all sectors, but only the last one is displayed.
e
Erase Sector (0xFFFF) (Entering 0...59 will erase the sector with the entered sector number.
FG, BG color
LNo LTO
E
Common settings
Terminal
Std App Viewer
Graph Viewer(Accl, Sensors)
Simple monitor (CUA/ARIA/Glancer)
Simple monitor (CUA/ARIA/Glancer)
Commander
Wrt Firmware
Interactive settings mode
Save Data Utility ( Dump/Erase)
Information
a: ( 0x00) Startup App.
G: ( 0x00) Screen size and drawing method
F: ( ) Serial Device ID
f: (0x00FFFFFF) FG color
b: (0x005A0032) BG color
B: ( 115200) Baud Rate
f: (0x00FFFFFF) FG color
b: (0x005A0032) BG color
j: ( 0) Number of make jobs at build time
v: ( 0) Open a folder with VSCode
l: ( 0) LNo LTO
n: ( 0) Screen after rewriting is completed
r: Read sector.
R: Read ALL sectors.
e: Erase sector.
E: Erase ALL sectors.
TWELITE CUE
Screen example: Detecting upward-facing surfaces
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.
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 , 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.
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)
We do not provide a quantitative definition of the detection threshold and event detection conditions for wake-up due to acceleration.
Voltage
Supply voltage of the module[mV].
Magnet
Displays detected or undetected magnet poles.
No indication of whether the magnetic sensor is waking up due to detection.
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).
Exit this screen and return to the selection screen.
[ B ]
No assignment
[ B ] long press
No assignment
[ C ]
Tab: TWELITE
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.
Commander screen
Item
Content
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)
A command is generated each time each item is changed. Pressing the Send button will re-send the command for the current setting.
Tab:NOTICE
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.
NOTICE screen
Item
Content
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.
A command is generated each time each item is changed. Pressing the lit button will re-send the command for the current setting.
Display at the bottom of the screen
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.
AD
The serial number of the sender.
LQ
LQI, the value corresponding to the radio wave strength.
SQ
Packet sequence number.
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.)
TWELITE Controls the wireless module's reset pin and resets it.
ESC
Exit this screen and return to the selection screen.
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%.
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.
Note: The 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.
Typical CUE Interactive settings mode settings
measure continuously at about 25 Hz. (Transmit Interval: 0, Sensor Parameter: 03000000)
measure continuously at about 50 Hz. (Transmit Interval: 0, Sensor Parameter: 03000100)
Operation
Operation
Desc.
Sample Rate Estimation
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.
Open at startup of CUE graph mode.
Specify 31 in [STAGE Common Settings→Designate Startup Application].
Log Output (Data Save)
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.
Label
Item
Desc.
Additional Information
Label
Item
Desc.
Log output (auto save)
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.
Label
Item
Desc.
Additional Information
Label
Item
Desc.
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)
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)
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).
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
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
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
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]
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)
#
Sample number
T_PKT[ms]
Packet reception time
Since one packet contains multiple samples, samples with the same timestamp are lined up.
ModuleSID
Serial number of the sending side
Tick[ms]
System on TWELITE STAGE app side at log file open [ms]
#
Sample number
T_PKT[ms]
Packet reception time
Since one packet contains multiple samples, samples with the same timestamp are lined up.
ModuleSID
Serial number of the sending side
Tick[ms]
System on TWELITE STAGE app side at log file open [ms]
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.
Use the tools at https://sqlitebrowser.org/ to extract data.
Operation
Operation
Desc
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
Edit Sensor Node Description
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.
Sensor node memo section intensive
Key
Description
ASCII charavcters
If you enter a normal alphanumeric string directly, it will be switched accordingly on the screen.
BS
Delete the trailing characters displayed.
ENTER
The entered string is reflected in the database.
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.
Screen Transitions
There are three basic types of screens: list, 24-hour, and live.
Open at startup of sensor graph mode.
Specify 32 in [STAGE Common Settings -> Startup Application Designation].
About DB table
sensor_data
Column Name
Type
Description
_uqid
INTEGER
continuation number used in the database
sid
INTEGER
int32_t
serial number stored in int32_t type." In the case of the serial number "8123abcd", the integer value of -2,128,368,691 is stored.
sensor_node
Used to store additional information (text) in sensor nodes.
Column Name
Type
Description
sid
INTEGER
SID above
sid_text
TEXT
SID converted to hexadecimal string (for readability)
sensor_last
Used for the purpose of maintaining the last received timestamp.
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.
Cursor up, down, wheel
Zoom in/out on sample horizontal axis
[LIVE>>]
Go to the one-second increment view that displays the latest arrival data
[24Hr Data]
Go to daily graph
[<Nodes]
Go to the nodes selection screen
[Yr][Mo][Dy]
Select a specific date by year, month, and day.
[ltst]
Go to today's data
[CSV exprot]
Output one day's data to CSV file
[DISP] at Nodes screen
Change the display method of the list
[SORT] at Nodes screen
Change the order of the list
[↑] at Nodes screen
Reverses the order of the listings
ts
INTEGER
The time the system received the packet, a timestamp value stored of type int64_t UNIX epoch (seconds elapsed since 1970).
ts_msec
INTEGER
The milliseconds portion of the timestamp.
year
INTEGER
The year portion of the local time from the timestamp.
month
INTEGER
The month portion of the local time from the timestamp.
day
INTEGER
The day portion of the local time relative to the timestamp.
hour
INTEGER
The hour portion of local time from the time stamp.
lid
INTEGER
The identification value, e.g., LID, assigned by the user.
lqi
INTEGER
Approximate value of the reception strength (Link Quality Indicator).
pkt_seq
INTEGER
The sequential number of the packet. The possible values depend on the firmware.
pkt_type
INTEGER
The type of wireless packet.
2 PAL AMB, 6 ARIA1 PAL MAG*3 PAL MOT,5 CUE0x101 App_Twelite, *0x103 App_IO
*Not supported at this time
value
REAL
measured value (definition depends on packet type)
pkt_type->2,6: temperature1: presence of magnet 00->no magnet, 01->N-pole, 02->S-pole3,5: X axis acceleration (average if packet includes multiple 0x101,103: bitmap of input IO (same value as the last 8 bits of val_dio)
value1
REAL
measured value (definition depends on packet type)
pkt_type->2,6: Humidity[%]1: not used3,5: Y axis acceleration (average value if packet contains multiple samples)[G]0x101: ADC1[V] ,103: Not used
value2
REAL
measured value (definition depends on packet type)
pkt_type->2: illuminance[lx], 6: not used1: not used3,5: Z axis acceleration (average value if packet contains multiple samples)[G ]
0x101: ADC2[V], 103: unused
value3
REAL
measurement value (definition depends on packet type)
pkt_type->2: not used, 6: not used1: not used3,5: not used0x101: ADC3[V], 103: not used
val_vcc_mv
INTEGER
voltage[mV]
val_dio
INTEGER
int32_t
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)
val_adc1_mv
INTEGER
pkt_type->1,2,3,0x101: Measured value of ADC1
val_adc2_mv
INTEGER
pkt_type->0x101: Measured value of ADC4
val_adc2_mv
INTEGER
Other data storage purpose
ev_src
INTEGER
Source of the event
ev_id
INTEGER
Event ID
pal_type->5: 1.... .6 -> dice 16 -> MOVE ... etc. (see documentation for TWELITE CUE)
ev_param
INTEGER
Event Parameter
desc
TEXT
Auxiliary information corresponding to the SID, to be displayed together in a list, etc.
lid
Here are some excerpts from the last data received
