[XMOVE self-designed somatosensory solution] XMove Studio Management System (I)-XFrmWork-based PC framework

Document directory

• 1. Node Manager
• 2. Communication Manager
• 3. Application Manager

1. Introduction to XMove Studio

XMove Studio is a PC Desktop integrated platform of XMove framework and a Management System and Application Center of XMove. It is developed based on the XFrmWork desktop software framework developed by me. It adopts the plug-in structure and shares the base class library. It has the following features:

• Ability to communicate, control, collect, and reproduce data with nodes.
• A Scalable Application Platform has developed Unity3D-based virtual reality systems, air mouse and data analyzer. And open APIs to third parties
• Communication Methods for adding or deleting nodes, including Bluetooth, WIFI, serial port, and USB

As one of the most important changes in XMove 4.0, the introduction of XMove Studio enables the management of all nodes to move to the PC end. Clear structure Division makes the entire XMOVE framework more flexible. For example, to add new features, you only need to add a PC update package. All node programs do not need to be changed. The management software can automatically configure node parameters, implement data flow control to implement new functions.

II. Introduction to functional components

Thanks to XFrmWork, the system adopts the module design method of plug-in structure. In addition to the underlying services provided by XFrmWork, such as debugging and interface display functions, XMove Studio has clear modules. We can divide it into three components. Communication Manager, Node Manager, and application manager. The Communication Manager is responsible for transmitting sensor data (or storage, network, or even analog data) collected by nodes to the Node Manager. After the node group of the node manager obtains data, it notifies the application registered to the relevant node in event mode, and each application can complete related functions. We can regard the three parts as data sources, data pools, and applications that use data respectively.

(From system operation), which shows the data flow direction, and the relationship between different nodes, communication methods, and applications. In this figure, you can see the time and traffic for each communication channel, the data volume and signal strength received by different nodes, and the mounting nodes of each application.

1. Node Manager

The Node Manager is the central link between the Communication Manager and the application manager. To help readers better understand the system, we will first introduce the Node Manager.

XMove node deployment scheme for example, 15 nodes are deployed in various places of the human body, and the mobile phone and receiving nodes are optional nodes. 17 nodes in totalNode group. Each node group corresponds to an actual user. The system supports multiple users, but the nodes here can be dynamically bound to the actual hardware node. You can change the ing relationship at any time, which means that the node data on user 0 can be mapped to the hardware node on user 1. Different Node groups are differentiated by node group numbers. Users can be added or deleted at runtime. Note that at least one node group instance must be retained in any situation.

When you place the mouse over a virtual node chart, the icon is enlarged to show the node type and functions:

You can switch to the list view. The system displays the features of all activated nodes, including battery, signal strength, working mode, group, and node type. In addition, the system prompts the hardware configuration of the node.

　　

2. Communication Manager

The Communication Manager is the data input source. sensor data can be transmitted to the Node Manager in multiple ways at the same time. Currently, XMove supports the following communication methods:

 

Communication name	Maximum Transmission Rate	Supported node types	Function Description
ATL standard serial port	115200bps	All nodes	Main Methods for communicating with nodes
Standard Bluetooth	560 Kbps	Android mobile phone Node	Android mobile phone communication
Virtual Bluetooth serial port	115200bps	Wince, seban Mobile Node	Supports simulating a Bluetooth serial device
Simulate data debugging	--	--	Simulation of virtual data as required by algorithms facilitates debugging
USB high-speed transmission	2 Mbps	4.0 bridge nodes	Communicate with bridge nodes through USB-HID
Virtual Communication	Same as the recording speed	--	You can record the data of a real node and play it back.
Virtual Network Communication	100 Mbps	Another PC terminal	Node data collected by another PC can be sent to this PC through the network
Wi-Fi LAN	--	Mobile phone	WIFI communication method with mobile phones
3G network	Measured at most 600 KBPS	Mobile phone	3G network communication with mobile phones

It is worth noting that XMove fully supports Kinect, and its communication methods and applications are included in the extended application components. There will be a special article about its functions.

During use, you can easily drag different communication methods from the list on the left to the list on the right to automatically configure:

The following describes how to configure analog data communication:

Analog data debugging is a communication method that provides convenience for debugging applications. It is virtual and has a variety of built-in data generation algorithms, for example, the ing node rotates the "virtual data" around the X axis, but this is transparent to the application. You can select different communication ports from the drop-down menu on the left (different data generation logics are applied to analog data communication ).

Below is the node ing relationship configuration. All hardware sensors are differentiated by RawID, but you can map these hardware nodes to the corresponding virtual nodes and configure their "node group ID" and corresponding node location. On the right of each item in the list, the red star indicates that the node is not activated, and the Green indicates that the node works normally. The Node Type of the node is also provided. You can add or delete node ing items by adding or subtracting signs on the right. When these mappings are closed, the system automatically saves them and restores them when they are enabled for the second time.

You can enable or disable this port. The traffic and duration of the current communication method are displayed in the upper-right corner of the configuration page.

If you do not want to use this communication method, drag it to the outside of the Communication Manager, and the system will automatically recycle the resources and close the port.

The system can enable multiple communication channels at the same time. These channels do not interfere with each other. The system allows two channels to transmit data for one node at the same time, but this is not recommended during use.

3. Application Manager

Application Manager is the core value of XMove Studio. The XFrmWork plug-in structure allows you to add new applications at any time. You only need to copy the component package to the corresponding plug-in directory folder of the application, and the system will automatically load it.

All applications require the data provided by the Node Manager. The XMove Node Manager notifies the application through events. Open APIs can provide complete services for the application.

The use of the application manager is very similar to that of the Communication Manager. You can drag an application to the Application List on the right. Different applications can be executed without interference.

The following uses an air mouse as an example to describe how to use it. The aerial mouse mainly uses the gyroscope of the sensor node. When you drag the aerial mouse to the right application bar, the configuration interface shown is displayed. The node ing configurator allows you to easily map nodes. The color of the five-star symbol on the right shows whether the nodes are activated. Considering that different applications have different requirements on node functions, for example, some applications must require the node to have a hid keyboard device or contain a GPS positioning function, in this case, the node ing must meet the basic functional requirements. Otherwise, the ing will not succeed. It is worth noting that the nodes in the drop-down menu that do not meet the node functional requirements have been deleted, and the activated nodes are prioritized.

You can click the start or close button to configure the function. When you click Start, the resource is automatically loaded and node events are automatically registered. When you click Close, the manager proceeds in reverse order.

Iii. Program Structure

XMove extends the basic functions of XFrmWork, including the following basic class libraries:

　　

The Interface library is a public Interface library between all databases. It defines the abstract structure of different databases and the interaction logic between them.

XFrmWork. Application is an Application-independent plug-in container and the final Application startup point.

Iv. Usage and other precautions

1. When using XMove Studio, you must first enable the XMove Studio application. The system automatically loads the required resources and completes initialization.

2. Enable the Communication Manager to connect the receiver to Studio in the desired communication mode.

3. When the subnode is enabled, the receiver should be able to accept all subnodes and display them in the Node Manager in real time. Configure these nodes to map them to the corresponding virtual node group.

4. After confirming that all nodes are working properly, drag the application you want to enable to the Application List, configure the node ing and other configurations, and select enable.

5. After the application is started, close the application and port normally. If you choose to directly close the main framework, Studio automatically recycles resources for you.

V. Summary

This article introduces the basic structure of XMove Studio, the roles and usage of the three main managers: Node Manager, Communication Manager, and application manager. It also introduces the basic usage steps of Studio.

Taking into account that the other part of the collection provides a detailed description of its use, it is not intended to introduce in depth the use of all components here, but only as a summary article.