User Manual Owner's manual
Table Of Contents
- ArmorStart Distributed Motor Controller with EtherNet/IP User Manual
- European Communities (EC) Directive Compliance
- Table of Contents
- Chapter 1
- Product Overview
- Introduction
- Description
- Catalog Number Explanation
- Operation
- Mode of Operation
- Description of Features
- Embedded Switch Technology
- Switched vs. Unswitched Control Power Input/Output (I/O) Connections
- EtherNet/IP™ Ports
- Embedded Web Server
- EtherNet/IP LED Status Indication
- Control Module LED Status and Reset
- Electronic Data Sheet (EDS)
- Fault Diagnostics
- Standard Features
- Factory-Installed Options
- Optional HOA Keypad Configuration (Bulletin 280E/281E only)
- Optional HOA Selector Keypad with Jog Function (Bulletin 284E only)
- Source Brake Contactor and Connector (Bulletin 284E only)
- EMI Filter (Bulletin 284E only)
- Dynamic Brake Connector (Bulletin 284E only)
- IP67 Dynamic Brake Resistor (Bulletin 284E only)
- Output Contactor (Bulletin 284E only)
- Shielded Motor Cable (Bulletin 284E only)
- ArmorStart® EtherNet/ IP Features
- Notes:
- Product Overview
- Chapter 2
- Installation and Wiring
- Receiving
- Unpacking
- Inspecting
- Storing
- General Precautions
- Precautions for Bulletin 280E/281E Applications
- Precautions for Bulletin 284E Applications
- Dimensions
- Mount Orientation
- Operation
- Wiring
- Terminal Designations
- Control Power Wiring
- ArmorStart with EtherNet/IP Internal Wiring
- AC Supply Considerations for Bulletin 284E Units
- Electromagnetic Compatibility (EMC)
- Grounding
- ArmorConnect Power Media
- ArmorConnect Connections
- ArmorConnect Cable Ratings
- Ethernet and I/O Connections
- Power Connections
- Optional Locking Clip
- Installation and Wiring
- Chapter 3
- Chapter 4
- Chapter 5
- Chapter 6
- Chapter 7
- Bulletin 280E/281E/284E Programmable Parameters
- Basic Setup Parameters
- Parameter Groups
- ArmorStart EtherNet/IP Parameters
- Bulletin 280E/281E
- Bulletin 284E
- Basic Status Group
- Produced Assembly Config Group
- Starter Protection Group
- User I/O Configuration Group
- Miscellaneous Configuration Group
- Drive I/O Configuration Group (Bulletin 284E only)
- Drive Display Group (Bulletin 284E only)
- Drive Setup Group (Bulletin 284E only)
- Drive Advanced Setup Group (Bulletin 284E only)
- Clear a Type 1 Fault and Restart the Drive
- Clear an Overvoltage, Undervoltage, or Heatsink OvrTmp Fault without Restarting the Drive
- How StepLogic Works
- StepLogic Settings
- Linear List of Parameters for Bulletin 280E/281E and Bulletin 284E
- Bulletin 280E/281E/284E Programmable Parameters
- Chapter 8
- Chapter 9
- Chapter 10
- Chapter 11
- Chapter 12
- Appendix A
- Applying More Than One ArmorStart Motor Controller in a Single Branch Circuit on Industrial Machinery
- Introduction
- ArmorStart LT Product Family
- Multiple-Motor Branch Circuits and Motor Controllers Listed for Group Installation – General
- Maximum Fuse Ampere Rating According to 7.2.10.4(1) and 7.2.10.4(2)
- Explanatory Example
- Input and Output Conductors of Bulletin 290E and 291E Controllers (a)
- Input and Output Conductors of Bulletin 294E Controllers (b)
- Combined Load Conductors (c)
- Applying More Than One ArmorStart Motor Controller in a Single Branch Circuit on Industrial Machinery
- Appendix B
- CIP Information
- High Level Product Description
- CIP Explicit Connection Behavior
- CIP Object Requirements
- Identity Object
- Assembly Object
- Connection Manager Object
- Discrete Input Point Object
- Discrete Output Point Object
- Parameter Object
- Parameter Group Object
- Discrete Input Group Object
- Discrete Output Group Object
- Control Supervisor Object
- Overload Object
- Device Level Ring (DLR) Object
- Qos Object
- DPI Fault Object
- DPI Alarm Object
- Interface Object
- TCP/IP Interface Object
- Ethernet Link Object
- CIP Information
- Appendix C
- Using DeviceLogix
- DeviceLogix Programming
- DeviceLogix Programming Example
- Import and Export
- Bulletin 284 - VFD Preset Speed Example
- DeviceLogix Ladder Editor Example
- ArmorStart 280 and 281 Status Bits
- Bulletin 280 and 281 ArmorStart Fault Bits
- Bulletin 280 and 281 ArmorStart Outputs
- Bulletin 280 and 281 ArmorStart Produced Network Bits
- Bulletin 284 ArmorStart Status Bits
- Bulletin 284 ArmorStart Fault Bits
- Bulletin 284 ArmorStart Outputs
- Bulletin 284 ArmorStart Produced Network Bits
- Using DeviceLogix
- Appendix D
- Appendix E
- Appendix F
- Back Cover

308 Rockwell Automation Publication 280E-UM001B-EN-P – July 2012
Appendix C Using DeviceLogix
• If the Network Override is enabled and the logic is enabled then
DeviceLogix controls the state of the outputs when the PLC is in Run
mode and if a network fault such as Duplicate MAC ID or module Bus off
condition occurs.
• If the Communications Override is enabled and the logic is enabled, the
device does not need any I/O connection to run the logic. As long as there
is control power and a DeviceNet power source connected to the device,
the logic will control the state of the outputs.
DeviceLogix Programming
DeviceLogix has many applications and the implementation is typically only
limited to the imagination of the programmer. Keep in mind that the application
of DeviceLogix is only designed to handle simple logic routines.
DeviceLogix is programmed using simple Boolean math operators such as AND,
OR, NOT, timers, counters, and latches. Decision making is done by combining
these Boolean operations with any of the available I/O. The inputs and outputs
used to interface with the logic can come from the network or from the device
hardware. Hardware I/O is the physical Inputs and Outputs located on the device
such as push buttons and pilot lights that are connected to the ArmorStart.
There are many reasons to use the DeviceLogix functionality, but some of the
most common are listed below:
• Increased system reliability
• Fast update times (1 - 2 ms possible)
• Improved diagnostics and reduced troubleshooting
• Operation independent of PLC or network status
• Continue to run process in the event of network interruptions
• Critical operations can be safely shutdown through local logic
DeviceLogix Programming
Example
The following example will show how to program a simple logic routine to
interface the ArmorStart EtherNet I/P with a remote hard-wired startstop
station. In this case the I/O is wired as shown in Tab l e 51
.
Table 51 - Hardware Bit Assignments and Description for the ArmorStart
Input Table Output Table
Bit Description Bit Description
In 0 Start Button Run Forward Contactor Coil
In 1 Stop Button N/A N/A
In 2 N/A — —
In 3 N/A — —