Devicelogix programming example, Devicelogix programming, Example – Rockwell Automation 284D On-Machine ArmorStart Accelerator Toolkit User Manual
Page 84
![background image](/manuals/581661/84/background.png)
84
Publication IASIMP-QS015C-EN-P - August 2011
Chapter 4
ArmorStart Local Control Configuration
DeviceLogix Programming Example
This example is a combination of different modes that can be used together in an application for the 284D
ArmorStart device. A logic controller ladder logic program is controlling the ArmorStart device (auto
control). In the event of an I/O connection fault, the external push buttons (manual control) will be allowed
to control the ArmorStart and local I/O. A tripped condition, whether in manual or auto control, will
provide a status indication of a trip using a stack light (controlled by output A). An IO Connection fault is
also indicated on the same stack light. In an IO Connection fault, the stack light will be steady state. If both
happen, the stack light will remain solid. In addition to the fault or tripped indication on the stack light, a
second stack light is used to indicate the ArmorStart device is given a run command either from the PLC
processor or the push buttons. Drive input 1 is used to command the preset speed of the drive in manual
control.
DeviceLogix Example
The automatic (PLC processor) controlled portion of the DeviceLogix example shows the network input 0
and IO Connection fault negated to provide an output. The Boolean OR gate is in place for a second input
that is used later in the example. If there is an IO Connection fault, the PLC processor will not be able to
control the DeviceNetLogix device.