Active Opc Server Lite-From Pull To Push - Moxa Technologies ioLogik E1210 User Manual

ioLogik E1200 User's Manual
Active OPC Server Lite—From Pull to Push
When first looking up the I/O devices' Modbus table, creating one tag requires 19 or more steps,
including specifying the IP address, selection of the protocols, and definition of the data type. The
procedure is repeated over and over until all the devices and tags have been created. A technician
can expect to take 1 minute to create just one tag. But what if there are 400 tags in the OPC system?
Using more tags will result in a higher CPU loading.
A general OPC requires connected I/O devices to use fixed IP addresses, if applications are
running on a public network, which usually involves dynamic IPs, or portable measurements are
being taken, there is no way to connect to an I/O device using OPC. This architecture is also called
"pull" technology because the OPC server always polls the I/O devices from tag creation, IP
connection and tag status update.
Moxa's ioLogik series products provide I/O status reports by TCP/UDP messages, e-mail, or
SNMP traps. These benefits have now expanded to OPC technology. Without needing additional
information (even the IP address is not needed), tag settings are automatically created by the
ioLogik itself to determine which tag should be created. Users only need to launch the Active OPC
Server program, and those I/O channels selected by a user will be "pushed" from an ioLogik to the
Active OPC Server.
5-3
Active OPC Server Lite