Hardware Independence Eliminates Reprogramming

Most major PLC and DCS manufacturers provide good programming tools for their hardware. But if you need to replace their hardware with a different brand, you will likely need to reprogram the logic using a different editor.

Not with UCOS.

In UCOS, you create one set of logic for a particular type of device and tie that logic to tags that are associated with I/O. Then UCOS drivers transparently translate that logic into the particular commands required by a specific brand and model of hardware and use the tags to communicate with the device via the I/O.

Your logic does not need to reflect the differences among models. The UCOS drivers take care of that for you.

Here's a real-life example.

The fragment of logic shown above was originally written to handle the fault logic for a Rotork valve actuator connected to a UCOS system.

This same logic - unchanged - was later used to handle faulting for valve actuators made by Limitork, EIM, BIFI, and Keystone. Only the device names changed, and even that was handled automatically by UCOS.

With UCOS, you can upgrade to the hardware that suits your budget and technology needs. You're never held hostage by a particular line of hardware simply because you don't have the resources to re-engineer your system.

< Previous 1 2 3 4 5 Next >