
1. Stable real-time implementation
- Maintain to regularity by storing the control commands of windows in each memory channel and buffer and transmitting the commands according to the cycle
- Possible to fast and accurate control calculation through the same control signal and language regardless of network
- Possible to stable control by processing at precise intervals on the real-time OS
- Freedom to configure the sequence by setting the cycle you want
2. Multi-network
- Possible to various network matching only by changing the interface since the control module and the communication module are separated
- Utilize hybrid network by defining two or more communication protocols within the interface
3. Device reliability and scalability
- Possible to create and add a separate control device besides general motion
- Maintain optimal system resources by automatically creating a status monitoring management unit for each device
- Minimize conflicts between devices by using individual memory and buffers in each device
*Device: an element or handler that can perform a control operation; Utility
4. Program extensibility
- Possible to optimal linkage with 3rd party programs other than motion control programs
- Possible to develop and customize your own sequence by providing API library
5. High compatibility with hardware
- Compatible with various slave H/W considering only communication protocol
- Maximize hardware scalability when using multi-network