Support for user application development running only on a non real-time OS

WMX3 also supports building applications that operate only in non-real-time space.

Overview

The base WMX3 library is used to write applications that run on Windows, and the library communicates with the real-time process with IMDll.dll.

If the WMX3 body process run on a non-real-time OS, all process related WMX3 will run entirely on Winodws.

WMX3 Windows Version supports the above solutions and is a independent product separete from WMX3 RTX Version.

So, for user application development running only on a non real-time OS, WMX3 Windows Version must be installed.

The following two diagrams show the overall flow of data in the WMX3 architecture.

The case in which WMX3 is operated from a user application on the non real-time os and WMX3 engine runs on real-time os:

../_images/WMXDOC_FUNC_ARCHITECTURE_2_image0.png

The case in which WMX3 is operated from a user application on the non real-time os and WMX3 engine does not run in real-time space:

../_images/WMXDOC_FUNC_ARCHITECTURE_2_image2.png

Individual Precautions and Support Specifications

  • WMX3 Windows Version is not real-time. So it may not be possible to communicate with the actual slaves if synchronous communication is enabled in the platform module. It is recommended to enable asynchronous communication mode in the platform module or use a simulator platform for the debug of the application. Please refer to the platform module sections of this document for more information.

  • Some optional components are not supported by the WMX3 Windows Version. Please contact us for more information.

  • Supported CPU, OS, and NIC are not RTX bound, so the WMX3 engine and APIs shoulld work in most environments that is notreccomended for RTX Version, although the Windows Version has not been verified in all cases. And disabling Windows Updates is unnecessary for Windows Version.