At a Glance
The
PLC Engine allows data processing in production lines.
It connects controllers, devices, SCADA systems and databases from various
manufacturers. It processes the data and dispatches them between the
connected devices and other systems. It collects data, manages them and
creates overviews for OEE applications.
Additional all the data can be handled over OPC. This are processed data and
all data from the connected controllers, devices, OPC systems and databases.
PLC Engine is the perfect component for using it for communications in
Industrie 4.0.
You will implement important use cases with
PLC Engine
|
Boosts the PLC communication with logical
optimizing of the requests. Often this will happen to error texts
from the controllers. The messages need to be fetched normally if
the corresponding error number is changing and a new error condition
becomes true. Without any change to Your SCADA system the
communication speeds up. The main reason is less load on the
communication line. |
|
Exchanges data between controllers and devices without PLC
programming or SCADA functionality. That's how it's done:
PLC Engine is reading the data from a controller or device and writes
them into another controller or device. The writing normally takes
place if the data are changing. With configurable triggers data
which are depending on other data conditions for the writing can be
defined. The data will converted if necessary. This is important if both controllers are different: One Siemens S7, the other a Rockwell Control Logix.
More complex handling is possible, too: Collecting of data from one
or multiple controllers, do some calculation with the data, and
write the result to a controller or device. Of course, any OPC
compatible system can use the same data also. |
|
Collects and processes data
PLC Engine is reading data from one
or more controllers.
The data are collected and possibly calculated
or normalized.
If all data are in place they are ready to process
for other systems or OPC access.
During the logical processing the
data are blocked for access.
Syncronous data access are waiting
until the collection is finished.
Configurable error conditions are
configurable: If one of the controllers is not available constant data are
used, or an error number is processed. |
|
Exchanges
data with common databases. You can read data from
controllers and write them directly into common databases - with
optional calculations. Data readed from databases can be written
into controllers, too. All the data are available for OPC systems
also. |
|
Collects data over long time
for OEE into a local or external database. So easily OEE
applications can be build. The integrated websites are offering the
collected and calculated data directly as curves or other.
Additionally the data can be handled over OPC. |
Configuration
The configuration mostly works in graphical style. Lot of wizards simplify
tis. Diagnostics boost the startup in plants. Use Your smartphone or tablet
and all of the status displays. You can define break points. The execution
will stop at the defined condition. The diagnostics logger handles longer
running information collecting.
