TWELITE STAGE APP is a tool to build/program TWELITE wireless microcontroller series apps and view the execution results.

Designed to work on a variety of platforms.

• Windows 10

• macOS (High Sierra and later)》(High Sierra and later)

• Linux (Ubuntu18.04)

• 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)

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

  • macOS -- Mac OS X, macOS

  • Linux -- Linux (Ubuntu etc.})

  • RasPi -- RaspberryPi

Windows

Environment

The following environment is used for development.

• Windows 10 version 1903

• VisualStudio 2019 (32bit build )

Requirements for operation

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.

• 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.

0.9.8a.

M5Stack version with MW-SLA-1J,E / MW-OSSLA-1J,E dual license and updated readme-j.txt.

0.9.8

Added `[Web]' button to viewer list view, added ability to open related sites, etc.

Revisions.

• Added Viewer > Commander.

  • Standard App 0x80 command

  • NOTICE PAL LED control (send commands to App_Wings)

• NOTICE PAL support in Viewer > PAL Viewer.

• Add Act extras menu.

  • More advanced than Act ⌘_samples

  • External open source libraries (e.g. sensor procedures)

• Expanded mouse actions (lists, buttons, tabs)

  • Mouse move to focus, left click to confirm, right click to input [ESC] key

• Reduced screen display load

  • Disabled screen saver when application is in background

  • Reduced CPU load by reducing the number of drawings when the application is in the background.

• Enhanced the list of build projects (Act, TWE_Apps, Act Extra)

  • Displaying a summary at the bottom when an item is selected (load 000desc.txt file, processed by TWE_Desc class)

  • Open project folder (or open with VSCode)

  • 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.

• Added logging (serial port input/output) function.

  • (Alt/Cmd+L) to start/end logging

  • Log files are stored in {folder with {TWELITE_Stage executable}/log

  • File name is twestage_{date-time}.log

  • Shift+Alt/Cmd+L to open log file folder

• Other changes/modifications, etc.

  • Changed the display method of serial (FTDI) device names and IDs

  • Fixed the problem that App_UART did not transition to Interactive settings mode

  • 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].

Known issues

• M5Stack may hang and initialize settings when saving settings.

0.8.9

2020_05 Release Version.

• Added window icons.

• Relaxed the restriction on the maximum number of listings in the BIN file list screen (win/linux/mac)

• Added Glancer viewer

• Adjusted explanation text, etc.

• Adjusted drawing of console screen.

• The settings for the destination screen (Interactive settings mode or Terminal) after writing the firmware were not working.

• Changed the assignment of Alt(or Cmd)+W

• Fixed other bugs

0.8.6

First Linux release

0.8.5

First release

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.

extract TWELITE STAGE SDK

2. 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

3. 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}.

Settings unique to each system, etc.

See below.

Folder structure of TWELITE STAGE SDK

The folder {MWSTAGE installation} where the TWELTIE STAGE SDK is installed contains the following

• TWELITE STAGE application executable

• MWSDK folder - libraries, source code, etc.

• Tools - toolchain for building, etc.

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}.

The execution method differs for each system (Windows, macOS, Linux).

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

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.

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.

• Four executable versions are available: framebuffer version, X11 version, framebuffer lightweight version, and X11 lightweight version. The lightweight version omits semi-transparency effects, etc.

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.

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

The following settings are required: OpenGL related drivers must be enabled.

• Select Advanced Settings → A2 GL Driver → G2 GL (Fake KMS\ in raspi-config)

• Install the libgles-dev package.

• Touch screen operation has not been tested

The executable of TWELITE™ Stage distributed by Monowireless, Inc. is subject to MW-SLA-1J,1E.

Open source deliverables used

We would like to thank the open source projects that provided us with high quality source code.

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.

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 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 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.

$ xcode-select --install

After installation is complete, type "make" and the following message should appear.

$ make
make: *** No targets specified and no makefile found.  Stop.

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.

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.

$ sudo kextunload -b com.apple.driver.AppleUSBFTDI

TWELITE STAGE applications are distributed in the following ways

TWELITE STAGE SDK

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.

Windows

Mac (macOS)

Linux

Raspberty Pi

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.

Windows macOS Linux RasPi

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.

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).

Windows macOS Linux RasPi

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.

• Interactive settings mode (interactive.md): to set the connected TWELITE radio module to interactive settings mode.

• Description : Menu to display the description. Open the following instructions in your browser.

  • TWELITE STAGE application (this document)

  • MWX library

  • TWENET_C library

Linux

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.

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

$ cd ./MWSTAGE/TWELITE_Stage/INSTALL/ubuntu/
$ sudo ./set_udev_sudo.sh

Definition file (line breaks for easier reading)

ACTION=="add",
   ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6001",
   MODE="0666",
   RUN+="/bin/sh -c 'rmmod ftdi_sio && rmmod usbserial'"
ACTION=="add",
   ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6015",
   MODE="0666",
   RUN+="/bin/sh -c 'rmmod ftdi_sio && rmmod usbserial'"

Centos 7

$ cd ./MWSTAGE/TWELITE_Stage/INSTALL/centos/
$ sudo ./set_udev_sudo.sh

Definition file (line breaks for easier reading)

ACTION=="add",
   ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6001",
   MODE="0666", 
   RUN+="/bin/sh -c '/usr/sbin/rmmod ftdi_sio'"
ACTION=="add",
   ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6015",
   MODE="0666", 
   RUN+="/bin/sh -c '/usr/sbin/rmmod ftdi_sio'"

Application Registration

Register your program according to your desktop environment if necessary.

Ubuntu 16.04, 18.04, 20.04

Definition file generation scripts for Ubuntu are available.

$ cd ./MWSTAGE/TWELITE_Stage/INSTALL/ubuntu/
$ ./make_launch_icon.sh

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.

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.

Windows macOS Linux RasPi

TWELITE CUE

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.

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.

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.

Voltage

Supply voltage of the module[mV].

Magnet

Displays detected or undetected magnet poles.

Acceleration

Displays acceleration measured after waking up.

Screen examples

Windows macOS Linux RasPi

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.

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)

• 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)

Operation

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.

• 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).

Additional Information

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.

Additional Information

Windows macOS Linux RasPi

Write the application (firmware) for the TWELITE wireless microcontroller.

• Write a pre-built .BIN file (Windows/Mac/Linux/RasPi)

• 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)

Windows macOS Linux RasPi

Re-selects the item that was specified and re-programmed immediately before.

Windows macOS Linux

Folders or .BIN files can be dragged and dropped throughout the TWELITE STAGE APP screen. Select to perform an operation on the dropped object.

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.

• 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.

Operation

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.

• 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.

[List] <--> [24 hours] <--> [Live]
              ↓↑
          [Select Year, Month, Date]

Open at startup of sensor graph mode.

Specify 32 in [STAGE Common Settings -> Startup Application Designation].

About DB table

sensor_data

sensor_node

Used to store additional information (text) in sensor nodes.

sensor_last

Used for the purpose of maintaining the last received timestamp.

Windows macOS Linux RasPi

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.

Windows macOS Linux RasPi

This section describes the operation through the TWELITE STAGE application.

Key Operations.

Windows macOS Linux RasPi

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

Windows macOS Linux RasPi

help screen

Windows macOS Linux RasPi.

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.

! [help screen](... /.gitbook/assets/img_help_ovrly.png)

Alt(Cmd)+Operation.

Windows macOS Linux RasPi.

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

Mouse Operation

Windows macOS Linux RasPi.

Mouse is mostly left click, but right click, right double click, and wheel may be used.

A,B,C buttons with mouse

Windows macOS Linux RasPi.

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,d to select)

In-screen operations with the mouse

Windows macOS Linux RasPi

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.

Windows macOS Linux RasPi

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.

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.

Windows macOS Linux RasPi

Build and rewrite TWELITE APPS. (Windows/Mac/Linux)

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).

Folder

The projects to be built are as follows

{MWSTAGE installation folder}/MWSTAGE/Wks_TweApps

Operation

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.

Tab: TWELITE

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

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.

Windows macOS Linux RasPi

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.

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.

Windows macOS Linux RasPi

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.

Build 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.

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.

Failure while programming

If the programming is in error, the screen will look like the above

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.

Windows macOS Linux RasPi

Build and rewrite Act.

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).

Folder

The projects to be built are located as follows

Operation

Windows macOS Linux RasPi

Writes a pre-built application (.BIN file).

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.

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.

Windows macOS Linux RasPi

The screen consists of two types of screens.

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).

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.

Windows macOS Linux RasPi

Reselect the serial port.

Windows macOS Linux RasPi

Build and rewrite Act. (Windows/Mac/Linux)

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).

Folder

The projects to be built are as follows

{MWSTAGE installation folder}/MWSTAGE/Act_samples

Operation

If 000desc.txt is created in the project folder, TWELITE STAGE APP will display its contents in the list of project folders.

The file is written in UTF-8. There are two types of formats.

Format 1

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

• 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

[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

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.

About URL specification

Windows macOS Linux RasPi

Configure various settings.

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 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

common setting

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

Wrt Firmware

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

Saved Data Utility

r: Read sector.
R: Read ALL sectors.
e: Erase sector.
E: Erase ALL sectors.

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).

Windows macOS Linux RasPi

TWELITE Allows logging of serial communications with a wireless microcontroller.

Start Logging

Windows macOS Linux RasPi

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

Windows macOS Linux RasPi

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.

The TWELITE STAGE APP runs as a front-end application in the TWELITE STAGE SDK package. Here is its folder structure.

... /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 folder

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

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

• 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

log folder

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

Search order of folders

Search for build project folders (e.g., Act_samples) in the following order

1. the folder where the TWELITE STAGE app was launched

2. the folder where the TWELITE STAGE app executable is located

3. {MWSDK folder}/...

4. {MWSDK folder}/..

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.

Windows macOS Linux RasPi

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.

• 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.

Operation flow of Interactive settings mode screen

The following is a rough process flow.

[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.  

command line arguments

Command line arguments provides some minor settings of TWELITE Stage.

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

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.