 Overview...
The
Motion Coordinator supports two open standards to allow connection
to a broad range of third party operator interfaces. (HMIs)
The
Modbus RTU protocol provides single point to point communication
between the Motion Coordinator and a programmable keypad/display or
touch-screen HMI. Implementation of the Modbus slave protocol is
provided on serial port 1 for RS232 and port 2 for RS485. Baud rate
and slave address can be set in the Trio BASIC program during serial
port initialisation.
On controllers with built-in Ethernet or when the Ethernet daughter board P296 is fitted, then Modbus TCP can be
selected to communicate with a suitable Ethernet equipped HMI.
Operator
interfaces based on the Windows operating system can use the TrioPC
Windows ActiveX component to allow either synchronous or
asynchronous connection to the Motion Coordinator over USB or an
Ethernet TCP link. One HMI can control multiple Motion
coordinators over a local Ethernet network.
In
addition to the functionality provided, it is possible for a user to
implement many other serial protocols using the simple but powerful
input functions in Trio BASIC. Serial bytes can be handled
either as ASCII characters or as binary data and protocols written
include Siemens S39/64 and ANSI.
Third
party operator interfaces that have been interfaced to a Motion
Coordinator using the Modbus protocol include: Automation
Direct, Eason
Technology, ESA, Exor
R&D, Horner, Maple
Systems, Pro-face and Total
Control.
Features....
- Open Standard - Modbus RTU / Modbus TCP
- Supported by most quality HMIs
- 16/32 bit Integer transfers
- 32bit IEEE Floating Point transfers
- Access to VR() or TABLE memory
- Motion Coordinator is Modbus slave
- Reliable established communications technology
|
printer friendly