Manual ArmorStart
Manual ArmorStart
Activities including installation, adjustments, putting into service, use, assembly, disassembly, and maintenance are required
to be carried out by suitably trained personnel in accordance with applicable code of practice.
If this equipment is used in a manner not specified by the manufacturer, the protection provided by the equipment may be
impaired.
In no event will Rockwell Automation, Inc. be responsible or liable for indirect or consequential damages resulting from the
use or application of this equipment.
The examples and diagrams in this manual are included solely for illustrative purposes. Because of the many variables and
requirements associated with any particular installation, Rockwell Automation, Inc. cannot assume responsibility or
liability for actual use based on the examples and diagrams.
No patent liability is assumed by Rockwell Automation, Inc. with respect to use of information, circuits, equipment, or
software described in this manual.
Reproduction of the contents of this manual, in whole or in part, without written permission of Rockwell Automation,
Inc., is prohibited.
Throughout this manual, when necessary, we use notes to make you aware of safety considerations.
WARNING: Identifies information about practices or circumstances that can cause an explosion in a
hazardous environment, which may lead to personal injury or death, property damage, or economic loss.
ATTENTION: Identifies information about practices or circumstances that can lead to personal injury or
death, property damage, or economic loss. Attentions help you identify a hazard, avoid a hazard, and
recognize the consequence.
IMPORTANT Identifies information that is critical for successful application and understanding of the product.
SHOCK HAZARD: Labels may be on or inside the equipment, for example, a drive or motor, to alert
people that dangerous voltage may be present.
BURN HAZARD: Labels may be on or inside the equipment, for example, a drive or motor, to alert
people that surfaces may reach dangerous temperatures.
ARC FLASH HAZARD: Labels may be on or inside the equipment, for example, a motor control center, to alert people to
potential Arc Flash. Arc Flash will cause severe injury or death. Wear proper Personal Protective Equipment (PPE). Follow ALL
Regulatory requirements for safe work practices and for Personal Protective Equipment (PPE).
Allen-Bradley, ArmorConnect, ArmorStart, ControlLogix, DeviceLogix, On-Machine, PowerFlex, RSLinx, RSLogix 5000, RSNetWorx, and StepLogic are trademarks of Rockwell Automation, Inc.
Trademarks not belonging to Rockwell Automation are property of their respective companies.
Trademarks not belonging to Rockwell Automation are property of their respective companies.
European Communities (EC) Directive Compliance
If this product has the CE mark it is approved for installation within the European Union and EEA regions. It has been
designed and tested to meet the following directives.
This product is tested to meet Council Directive 2006/95/EC Low Voltage Directive and Council Directive
2004/108/EC Electromagnetic Compatibility (EMC) by applying the following standard(s):
• Bulletin 280E/281E: EN 60947-4-1 — Low-voltage switchgear and controlgear — Part 4-1: Contactors and motor-
starters — Electromechanical contactors and motor-starters.
• Bulletin 284E: EN 61800-5-1 — Adjustable speed electronic power drive systems — Part 5-1: Safety requirements
— Electrical, thermal and energy.
• Bulletin 284E: EN 61800-3 — Adjustable speed electronic power drive systems — Part 3: EMC product standard
including specific test methods.
Chapter 1
Product Overview Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Catalog Number Explanation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Mode of Operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Bulletin 280E, 281E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Full-Voltage Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Bulletin 284E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Sensorless Vector Control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Description of Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Overload Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Embedded Switch Technology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Switched vs. Unswitched Control Power Input/Output (I/O)
Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
EtherNet/IP Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Embedded Web Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
E-mail Notification Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
EtherNet/IP LED Status Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Control Module LED Status and Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Electronic Data Sheet (EDS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Fault Diagnostics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Protection Faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Standard Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Gland Plate Entrance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Motor Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
DeviceLogix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Factory-Installed Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Optional HOA Keypad Configuration
(Bulletin 280E, 281E only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Optional HOA Selector Keypad with Jog Function
(Bulletin 284E only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Source Brake Contactor and Connector (Bulletin 284E only) . . . . 25
EMI Filter (Bulletin 284E only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Dynamic Brake Connector (Bulletin 284E only) . . . . . . . . . . . . . . . . 26
IP67 Dynamic Brake Resistor (Bulletin 284E only). . . . . . . . . . . . . . 26
Output Contactor (Bulletin 284E only) . . . . . . . . . . . . . . . . . . . . . . . . 26
Shielded Motor Cable (Bulletin 284E only). . . . . . . . . . . . . . . . . . . . . 26
ArmorStart EtherNet/IP Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Chapter 2
Installation, Wiring, and Receiving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Maintenance Unpacking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Inspecting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Storing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
General Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Precautions for Bulletin 284E Applications . . . . . . . . . . . . . . . . . . . . . . . . . 30
Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
280E, 281E Conduit Gland Entrance Bulletin . . . . . . . . . . . . . . . . . . 31
280E, 281E Daisy Chain (DR) Conduit Entrance . . . . . . . . . . . . . . . 32
284E Conduit Gland Entrance Bulletin . . . . . . . . . . . . . . . . . . . . . . . . 33
284E Daisy Chain (DR) Conduit Entrance . . . . . . . . . . . . . . . . . . . . . 34
280E, 281E ArmorConnect Gland Connectivity Bulletin . . . . . . . . 35
284E ArmorConnect Gland Connectivity Bulletin . . . . . . . . . . . . . . 36
Mount Orientation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Power, Control, and Ground Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Standard Conduit/Knockout Size. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Terminal Designations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Control Power Wiring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
24V DC Control Power. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
ArmorStart with EtherNet/IP Internal Wiring . . . . . . . . . . . . . . . . . . . . . 41
Recommended Cord Grips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
AC Supply Considerations for Bulletin 284E Units . . . . . . . . . . . . . . . . . 45
Ungrounded and High Resistive Distribution Systems . . . . . . . . . . . 45
Disconnecting MOVs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Group Motor Installations for USA and Canada Markets. . . . . . . . . . . . 46
Wiring and Workmanship Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Other System Design Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Electromagnetic Compatibility (EMC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
General Notes (Bulletin 284E only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Wiring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Grounding. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Grounding Safety Grounds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Grounding PE or Ground . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Shield and Grounding of Motors and Motor Cables . . . . . . . . . . . . . . . . . 50
Motor Cable Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Unshielded Cable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Shielded Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Shield Terminating Connectors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
ArmorConnect Power Media. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
ArmorConnect Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Control Power Overview Using 6/5 Pin Control . . . . . . . . . . . . . . . . 55
Control Power using 4-Pin Auxiliary Power Tee Adapter . . . . . . . . 57
ArmorConnect Cable Ratings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Chapter 3
Introduction to EtherNet/IP and Terminology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Device Level Ring Technology Introduction to EtherNet/IP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Linear Network Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Device Level Ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Number of Nodes on a DLR Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Ethernet Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Ethernet Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
EtherNet/IP General Wiring Guideline. . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Requested Packet Interval. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Chapter 4
Product Commissioning IP Address. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Gateway Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Subnet Mask . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Configuring EtherNet/IP Address. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Manually Configure the Network Address Switches . . . . . . . . . . . . . 79
Use the Rockwell Automation BootP/DHCP Utility . . . . . . . . . . . . . . . 81
Save the Relation List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
DHCP IP Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Using the Rockwell Automation Embedded Web Server . . . . . . . . . . . . 85
Internal Web Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Network Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Parameter Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
E-mail Notification Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Device Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Ownership . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Ethernet Statistics Web Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Connection Manager Cmd Object Info Web Page . . . . . . . . . . . . . . . . . . 93
Ring Statistics Web Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Chapter 5
Adding an ArmorStart to RSLogix Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
5000 Connect and Configure ArmorStart with Add-On-Profile (AOP) . . . 98
Offline Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
General Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Connection Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Parameters Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Chapter 6
Optional HOA Keypad Operation Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Keypad Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Keypad and HOA Disable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Chapter 7
Bulletin 280E/281E/284E Basic Setup Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Programmable Parameters Parameter Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
ArmorStart EtherNet/IP Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Parameter Programming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Bulletin 280E, 281E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Basic Status Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Produced Assembly Config Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Starter Protection Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
User I/O Configuration Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Miscellaneous Configuration Group . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Starter Display Group (Bulletin 280E, 281E only) . . . . . . . . . . . . . . 146
Starter Setup Group (Bulletin 280E, 281E only). . . . . . . . . . . . . . . . 148
Bulletin 284E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Basic Status Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Produced Assembly Config Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Starter Protection Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
User I/O Configuration Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Miscellaneous Configuration Group . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Drive I/O Configuration Group (Bulletin 284E only) . . . . . . . . . . 168
Drive Display Group (Bulletin 284E only) . . . . . . . . . . . . . . . . . . . . . 170
Drive Setup Group (Bulletin 284E only). . . . . . . . . . . . . . . . . . . . . . . 175
Drive Advanced Setup Group (Bulletin 284E only). . . . . . . . . . . . . 179
Clear a Type 1 Fault and Restart the Drive . . . . . . . . . . . . . . . . . . . . . 189
Clear an Overvoltage, Undervoltage, or Heatsink OvrTmp Fault
without Restarting the Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Linear List of Parameters for Bulletin 280E, 281E and
Bulletin 284E. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Chapter 8
How to Configure an Explicit Message Programming ControlLogix Explicit Message. . . . . . . . . . . . . . . . . . . . . . 207
Explicit Messaging with ControlLogix. . . . . . . . . . . . . . . . . . . . . . . . . 207
Chapter 9
Diagnostics Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
Protection Programming. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
Fault Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
Clear Fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
Fault Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Fault Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Short Circuit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Overload Trip. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Phase Loss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Phase Short . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Ground Fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Stall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Control Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
I/O Fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Over Temperature. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Phase Imbalance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Over Current . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
A3 Power Loss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
Internal Communication Fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
DC Bus Fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
Electrically Erasable Programmable Read-Only Memory
EEPROM Fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
Hardware Fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
Restart Retries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
Miscellaneous Faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
EtherNet/IP LED Status Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
Control Module LED Status and Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
Control Module Fault LED Indications. . . . . . . . . . . . . . . . . . . . . . . . . . . 217
Fault 11 Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
Resetting Device to Factory Defaults. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
Chapter 10
Troubleshooting Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
Bulletin 280E, 281E Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
Bulletin 284E Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
Fault Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
IP67 Dynamic Brake Diagnostic (DB1) . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
DB1 Faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
Operation and Troubleshooting of the DB1 - Dynamic Brake. . . 232
DB1 Resistor Overtemperature Fault . . . . . . . . . . . . . . . . . . . . . . . . . 232
DB1 Overcurrent Fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
Chapter 11
Specifications for EtherNet/IP Bulletin 280E, 281E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
Motor Overload Trip Curves . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
Contactor Life Load Curves . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
Bulletin 284E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
Sensorless Vector Control (SVC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
Motor Overload Trip Curves . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
Altitude Derating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
Altitude Rating for 280/281 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
Altitude Rating for 284 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
Chapter 12
Accessories Industrial Ethernet Media. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
D Code Connectivity (M12) – 1585D . . . . . . . . . . . . . . . . . . . . . . . . 271
Sensor Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
Sensor Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
Motor and Brake Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
Appendix A
Applying More Than One ArmorStart Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
Motor Controller in a Single Branch ArmorStart Product Family . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284
Multiple-Motor Branch Circuits and Motor Controllers Listed for Group
Circuit on Industrial Machinery
Installation – General. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
Maximum Fuse Ampere Rating According to 7.2.10.4(1) and
7.2.10.4(2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
Complete Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
Explanatory Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
Input and Output Conductors of Bulletin 290E and
291E Controllers (a). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295
Input and Output Conductors of Bulletin 294E Controllers (b) . . . . 295
Combined Load Conductors (c) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295
Appendix B
CIP Information High Level Product Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
Product Codes and Name Strings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
CIP Explicit Connection Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
EDS Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
CIP Object Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
Identity Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
CLASS CODE 0x0001 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
Assembly Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
CLASS CODE 0x0004 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
I/O Assemblies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
Connection Manager Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306
CLASS CODE 0x0006 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306
Class 1 Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
Exclusive Owner Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
Listen Only Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308
Class 3 CIP Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308
Discrete Input Point Object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
CLASS CODE 0x0008 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
Discrete Output Point Object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310
CLASS CODE 0x0009 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310
Parameter Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311
Appendix C
Using DeviceLogix DeviceLogix Programming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
DeviceLogix Programming Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333
Import and Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
Appendix D
Renewal Parts Bulletin 280E, 281E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
Control Module Renewal Part Product Selection. . . . . . . . . . . . . . . 341
Base Module Renewal Part Product Selection . . . . . . . . . . . . . . . . . . 342
Bulletin 284E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343
Control Module Renewal Part Product Selection. . . . . . . . . . . . . . . 343
Base Module Renewal Part Product Selection . . . . . . . . . . . . . . . . . . 344
Replacement Fuses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346
Replacement Parts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346
Appendix E
System Design Considerations When General Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347
Using a Line Reactor Reasons to Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347
Design. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348
Appendix F
Application Examples Manual Brake Control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349
284 - VFD Preset Speed Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352
Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357
DeviceLogix Ladder Editor Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358
ArmorStart 280 and 281 Status Bits. . . . . . . . . . . . . . . . . . . . . . . . . . . 358
Bulletin 280 and 281 ArmorStart Fault Bits . . . . . . . . . . . . . . . . . . . 359
Bulletin 280 and 281 ArmorStart Outputs . . . . . . . . . . . . . . . . . . . . 360
Bulletin 280 and 281 ArmorStart Produced Network Bits . . . . . . 360
Bulletin 284 ArmorStart Status Bits. . . . . . . . . . . . . . . . . . . . . . . . . . . 361
Bulletin 284 ArmorStart Fault Bits . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
Bulletin 284 ArmorStart Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362
Bulletin 284 ArmorStart Produced Network Bits . . . . . . . . . . . . . . 363
Reporting Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364
How to Report the RPM of the 284 Internal Fan . . . . . . . . . . . . . . 364
How to report the Heat Sink Temperature of the 284 . . . . . . . . . . 364
How to Report the Last Four Faults. . . . . . . . . . . . . . . . . . . . . . . . . . . 365
How to Report an IP Address Conflict Detection . . . . . . . . . . . . . . 365
Demand Torque Off Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366
Keypad Disable with DeviceLogix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366
Motion Disable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366
Notes:
Product Overview
Introduction This chapter provides a brief overview of the features and functionality of the
ArmorStart® EtherNet/Industrial Protocol (IP) Distributed Motor Controllers,
Bulletin 280E, 281E, and 284E.
Description The ArmorStart EtherNet/IP Distributed Motor Controllers are integrated, pre-
engineered, motor starting solutions. Bulletins 280E and 281E are used for full-
voltage and reversing applications, respectively. Bulletin 284E is used in variable
frequency applications where more precise motor control is needed. The
ArmorStart EtherNet/IP controller offers a robust IP67/UL Type 4/12
enclosure design, that is suitable for water wash down environments.
The controller’s embedded web server allows the user to check status, diagnostics,
and perform simple device configuration using a standard web browser. It also
supports SMTP protocol that allows the user to configure the device to send an
alert e-mail of potential issues.
The copy and paste function allows easy configuration of multiple ArmorStart
controllers. RSLogix 5000 revision 17.01 or later is required to implement AOP
support.
The ArmorStart controller and associated motor cable have been evaluated as a
system by UL and is suitable for group installation. ArmorStart controllers
contain a UL Listed disconnect that in many applications, eliminates the need for
additional components.
Catalog Number Explanation Examples that are given in this section are for reference purposes. This basic
explanation should not be used for product selection because not all
combinations produce a valid catalog number.
a e h
Bulletin Number Short Circuit Protection Option 1
Code Description (Motor Circuit Protection) Code Description
Full Voltage Starter Code Description Hand/Off/Auto Selector Keypad
280 3
281 Reversing Starter 10 10 A Rated Device Hand/Off/Auto Selector Keypad with
3FR
25 25 A Rated Device Forward/Reverse
b
f
Code Description Overload Selection Current Range
E EtherNet/IP Code Description
A 0.24…1.2 A
c B 0.5…2.5 A
C 1.1…5.5 A
Enclosure Type
D 3.2…16 A
Code Description
F IP67/ UL Type 4/12
g
d Control and 3-Phase Power Connections/Motor Cable Connection
(CR: Conduit/Round Media) or (RR: Round/Round Media) or (DR: D/Round Media)
Contactor Size/Control Voltage
Description
24V DC Code Control Power 3-Phase Power Motor Cable
12Z
3 m, unshielded cordset
23Z CR blank Conduit Entrance Conduit Entrance male 90°
CR W Conduit Entrance Conduit Entrance No cable
3 m, unshielded cordset
DR blank Conduit Daisy Chain Conduit Daisy Chain
male 90°
a d f i
Bulletin Number Torque Performance Mode Control Voltage Option 1
Code Description Code Description Code Description Code Description
284 VFD Starter Sensorless Vector Control Z 24V DC Hand/Off/Auto Selector
V 3
and Volts per Hertz Keypad with Jog Function
b
g j
Communications e
Short Circuit Protection (Motor
Code Description Output Current Circuit Protector) Option 2
E EtherNet/IP 380…480V Code Description Code Description
Code Description 10 10 A Rated Device DB blank DB Brake Connector
D1P4 1.4 A, 0.4 kW, 0.5 Hp 25 25 A Rated Device Connectivity to IP67
c DB1 blank
DB Resistor
D2P3 2.3 A, 0.75 kW, 1.0 Hp
Enclosure Type Source Brake
D4P0 4.0 A, 1.5 kW, 2.0 Hp SB blank
Code Description Contactor
D6P0 6.0 A, 2.2 kW, 3.0 Hp
F Type 4 (IP67) SB W No cable
D7P6 7.6 A, 3.3 kW, 5.0 Hp
k
h
Option 3
Control and 3-Phase Power Connections / Motor Cable Connection
Code Description
(CR: Conduit/Round Media) or (RR: Round/Round Media)
EMI EMI Filter
Description
Code OC Output Contactor
Control Power 3-Phase Power Motor Cable
3 m, unshielded
CR blank Conduit Entrance Conduit Entrance
cordset male 90°
3 m, shielded
CR N Conduit Entrance Conduit Entrance
cordset male 90°
CR W Conduit Entrance Conduit Entrance No cable
3 m, unshielded
DR blank Conduit Daisy Chain Conduit Daisy Chain
cordset male 90°
3 m, shielded
DR N Conduit Daisy Chain Conduit Daisy Chain
cordset male 90°
DR W Conduit Daisy Chain Conduit Daisy Chain No cable
Round Media Round Media 3 m, unshielded
RR blank
(Male Receptacle) (Male Receptacle) cordset male 90°
Round Media Round Media 3 m, shielded
RR N
(Male Receptacle) (Male Receptacle) cordset male 90°
Round Media Round Media
RR W No cable
(Male Receptacle) (Male Receptacle)
Operation The ArmorStart Distributed Motor Controllers can operate three-phase squirrel-
cage induction motors as follows:
Full-Voltage Start
This method is used in applications requiring across-the-line starting, where full
inrush current and locked-rotor torque are realized. The ArmorStart Bulletin
280E offers full-voltage starting and the Bulletin 281E offers full-voltage starting
for reversing applications.
100%
Percent
Voltage
Time (seconds)
Bulletin 284E
• Able to develop high torque over a wide speed range and adapts to
individual motor characteristics.
The Bulletin 280E, 281E overload trip class can be selected for class 10, 15, 20
protection. The Bulletin 284E overload trip class is Class 10 only. Ambient
insensitivity is inherent in the electronic design of the overload (see Chapter 11
for the specification for overload trip curves).
In general, for a Device Level Ring (DLR) or linear network keep individual
segments to 50 nodes or less. In addition, it is important to reserve a minimum of
10% of available bandwidth to allow for processing of explicit messages.
• Supports IEEE 1588 transparent clock for CIP Motion and CIP Sync
applications
Note: DLR ports cannot be used as two Network Interface Cards (NICs)
connected to two different subnets.
Switched vs. Unswitched The voltage at terminals A1/A2 supplies power to the ArmorStart outputs.
Removing this power or placing the ArmorStart disconnect in the “OFF”
Control Power Input/Output position disables the outputs.
(I/O) Connections
The unswitched power A3/A2 supplies power to the input and communication
module. This power is not affected by the state of the disconnect switch. This
ensures that anytime the controller can communicate, the state of the inputs is
correct.
EtherNet/IP Ports ArmorStart EtherNet/IP controller includes a dual port Ethernet switch that
supports 10/100 Mbps It utilizes a sealed D-coded micro (M12) style ethernet
connector. Dynamic Host Configuration Protocol (DHCP) is enabled as the
factory default. Before using your adapter in an EtherNet/IP network, you may
need to configure an IP address or set the address statically.
Embedded Web Server The embedded web server allows the user to view information and configure the
ArmorStart controller via a web browser. The default login is “Administrator”.
There is no password set by default.
IMPORTANT The user should set the password to a unique value for authorized personnel. If the
Login and password are lost, you will need to reset the device to factory defaults
via the Programmable Logic Controller (PLC). Note: The configuration will be lost.
The embedded web server supports configuration of the Simple Mail Transfer
Protocol (SMTP). Once properly configured, the motor controller e-mails the
user with specific fault/trip messages.
• RUN LED
This LED is illuminated solid green when a start command and control
power are present.
• NETWORK LED
This bicolor (red/green) LED indicates the status of the internal
communication link.
• FAULT LED
This indicates a Controller Fault (trip) condition.
Electronic Data Sheet (EDS) EtherNet/IP devices have Electronic Data Sheets (EDS). These are specially
formatted text files, as defined by the CIP specifications, that represent the object
model of the device. EDS files contain details about the readable and
configurable parameters of the EtherNet/IP device. They also provide
information about the I/O connections the device supports and the content of
the associated data structures. EDS files are used by EtherNet/IP device
configuration tools, such as RSNetWorx™ for EtherNet/IP, and data servers such
as RSLinx® Classic.
EDS files for all ArmorStart EtherNet/IP devices can also be uploaded directly
from the device via the web server interface. Rockwell Automation product EDS
files are also available on the internet at: http://www.ab.com/networks/eds.
Fault Diagnostics Fault diagnostics capabilities that are built in the ArmorStart Distributed Motor
Controller are designed to help you pinpoint a problem for easy troubleshooting
and quick restarting.
Protection Faults
Protection Faults are generated when potentially dangerous or damaging
conditions are detected. Protection Faults are also known as “Trips.”
The EtherNet/IP version includes four 24V DC inputs that are single keyed (two
inputs per connector) and sourced from A3/A2 control power. The inputs use
two M12 connectors. Each input has an LED status indication. They are
configurable as sinking or sourcing.
Outputs
The EtherNet/IP version includes two self-protected solid state outputs that are
single keyed (one per connector), sourced from A1/A2 control power. Outputs
are sourcing type with a maximum current per output point of 0.5 A DC. The
outputs use one M12 connector per output, each having LED status indication.
For high duty cycle applications, consider using an interposing relay to reduce the
wear on the internal output.
Motor Cable
DeviceLogix
Factory-Installed Options Optional HOA Keypad Configuration (Bulletin 280E, 281E only)
Optional HOA Selector Keypad with Jog Function (Bulletin 284E only)
The HOA Selector Keypad with Jog Function allows for local start/stop control
with capabilities to jog in forward/reverse motor directions.
The user selectable DB Option includes a 3-meter, 3-pin cordset for connection
to an IP20 Dynamic Brake Module. See Chapter 11 for available dynamic brake
modules.
Note: The IP67 Dynamic Brake Resistor cannot be used with the -DB
factory-installed option.
The IP67 Dynamic Brake Resistor design offers simplicity in wiring and
installation. The user-selectable DB1 option provides the quick connector and an
internal resistor monitoring circuit board. The cable lengths available are 0.5 m
and 1.0 m. The IP67 Dynamic Brake is separately ordered. See Chapter 11 for
available IP67 Dynamic Brake Resistors.
Note: The IP67 Dynamic Brake Resistor is used only with the -DB1
factory-installed option. Only the specified IP67 Dynamic Brake Resistor can be
used based on the VFD horsepower. Connecting resistors other than those
specified, result in a DB1 fault.
2 Outputs (Micro/M12)
Hand-Off-Auto Keypad
4 Inputs (Micro/M12)
IP Address Switches
Local Disconnect
LED Status
Indication and Reset
IP Address Notation Area
Control Module
2 Outputs (Micro/M12)
Hand-Off-Auto Keypad
4 Inputs (Micro/M12)
Source Brake Connection
IP Address Switches
Motor Connection
Ethernet Ports (DLR)
Notes:
Receiving It is the responsibility of the user to thoroughly inspect the equipment before
accepting the shipment from the freight company. Check the item(s) received
against the purchase order. If any items are damaged, it is the responsibility of the
user not to accept delivery until the freight agent has noted the damage on the
freight bill. If any concealed damage is found during unpacking, it is again the
responsibility of the user to notify the freight agent. The shipping container must
be left intact and the freight agent should be requested to make a visual
inspection of the equipment.
Unpacking Remove all packing material, wedges, or braces from within and around the
Armorstart distributed motor controller. Remove all packing material from the
device(s). Check the contents of the package. Contact your local Allen-Bradley®
representative if any items are missing.
IMPORTANT Before the installation and start-up of the drive, a general inspection of mechanical
integrity (i.e. loose parts, wires, connections, packing materials, etc.) must be made.
Inspecting After unpacking, check the item(s) nameplate catalog number(s) against the
purchase order. See Chapter 1 for an explanation of the catalog numbering system
that aids in nameplate interpretation.
Storing The controller should remain in its shipping container before installation. If the
equipment is not to be used for a period of time, it must be stored according to
the following instructions to maintain warranty coverage.
General Precautions In addition to the precautions listed throughout this manual, the following
statements, that are general to the system, must be read and understood.
ATTENTION: Total circuit impedance must be low enough to ensure any short
circuit or ground fault current is large enough to operate the fuse or circuit
breaker. Failure to comply can result in death, personal injury, and/or
equipment damage.
Precautions for Bulletin 284E WARNING: The drive contains high voltage capacitors that take time to
Applications discharge after removal of mains supply. Before working on a drive, verify
isolation of mains supply from line inputs (R, S, T [L1, L2, L3]). Wait three
minutes for capacitors to discharge to safe voltage levels. Failure to do so may
result in personal injury or death.
Darkened display LEDs are not an indication that capacitors have discharged
to safe voltage levels. Risk of shock – environment rating may not be
maintained with open receptacles.
Dimensions Dimensions are shown in millimeters (inches). Dimensions are not intended to
be used for manufacturing purposes. All dimensions are subject to change.
268
[10.55]
287,5
[11.32 ]
3,02
6,8 [ .12 ]
150
[.27 ] [6 ]
MOTOR CONNECTION 185 [7.3] M22 CORDSET
MOTOR CONN ECTION 243 [9.57] M35 CORDSET
373
[14.69 ] 11
[ .43 ]
195
[7.68 ]
67,9
[3]
290 30,5
189
[11.42] [1.20]
[7]
268
[10.55]
287,5
[11.32]
3,02
[.12]
6,8
[.27] 150
[6]
195
[7.68]
80,32
[3.2] 67,95
[2.7]
268
[10.55]
287,5
[11.32 ]
3,02
6,8 [.12 ]
[.27 ]
MOTO R CONNECTION 266.9 [10.51]
373
[14.69] 11
[.43 ]
195
[7.68 ]
67,9
[3 ]
290 30,5
[11.42] [1.20] 236
[9]
268
[10.55]
287,5
[11.32]
6,8
[.27]
3,02
[.12]
373
[14.69]
15,48
[.6]
195
[7.68
80,32
[3.2]
67,95
[2.7]
268 287,5
268 287,5 [10.55 ]
[10.55] [11.32 ] [11.32]
77,6 77,6
[3] [3 ]
60,6 60,6
[2 ] [2 ]
25,5 68 25,5 68
[1 ] [2.68 ] [1 ] [2.68 ]
6,8 6,8
[.27 ] [.27 ]
10 A Short Circuit 25 A Short Circuit
Protection (M22) Protection (M35)
77,6
[3 ]
77,6
[3]
60,6
[2 ]
60,6
[2] 25,5 68
25,5 68 [1 ] [2.68 ]
[1] [2.68 ]
IMPORTANT For proper heat dissipation and product operation, mount in the vertical orientation
as shown.
Bulletin 280E, 281E: 0.24…16 A; 200V AC, 230V AC, 460V AC; 50/60 Hz.
Bulletin 284E: up to 5 Hp (3.0 kW) @ 480V AC
Table 2 provides the power, control, and ground wire capacity and the tightening
torque requirements. The power, control, ground, and terminals accepts a
maximum of two wires per terminal.
Terminal Designations As shown in Figure 18, the ArmorStart Distributed Motor Controller contains
terminals for power, control, and ground wiring. Access can be gained by
removing the terminal access cover plate.
Control Power Wiring ArmorStart EtherNet/IP controller uses 24V DC control power for
communications and I/O. The control power terminal connections are labeled
A1, A2, and A3. Switched power supplies the outputs. Unswitched power
supplies logic power and sensor inputs.
• A1 = Switched +V
• A3 = Unswitched +V
• Sensor Power is sourced from +24V supplied from A3(+) and A2(–).
• Output power is sourced from +24V supplied from A1(+) and A2(–).
• Max. current per output point is 0.5 A and is not to exceed 1.0 A total
IMPORTANT Instantaneous capacitive inrush exists for less than 10 ms, that can exceed 20 A. The
power supply must be capable of supporting this amount of instant power demand
when multiple ArmorStart controllers are turned ON simultaneously. For supplies
without this capacity, it is recommended to apply unswitched power (A3-A2) first and
after a 2…4 second delay, apply switched power. If control power falls below 19V DC,
there is a higher risk of communications issues or device faults.
AS Logic F
Control
Power
Sense AS Logic
Control
140M
Off/Tripped On 7A
Class CC 24V Note: This power supply is not
A1 present in the Status Only versions.
A2 26V
Current supplied by
control power due to the
2A SC Protected 2.5A power supply voltage
Class CC being greater than A3
Port 2 Port 1
Output A voltage 140M Trip
Input 10mA @ 24V DC
140M Status
1 Ampere Input 10mA @ 24V DC
FA
Total Input 10mA @ 24V DC
2A SC Protected Reversed bias 11 -
+24V DC Status Not Used
Input 10mA @ 24V DC
Output B Ethernet under normal 25V DC
Logic operation
24V DC
A3 11 -
+5V DC
25V DC
Input 1
Input 2
Input 3
4 Inputs
50mA Max/input depends
on sensor attached to input
140M
L1
L2 Motor
L3
AS Logic F R
Control RB
FB
Power
Sense AS Logic
Control AS Logic
Control
140M
Off/Tripped 7A
On
Class CC 24V Note: This power supply is not
A1 present in the Status Only versions.
A2 26V
Current supplied by
control power due to the
2A SC Protected 2.5A power supply voltage
Class CC being greater than A3
Output A Port 1 Port 2 voltage 140M Trip
Input 10mA @ 24V DC
140M Status
1 Ampere Input 10mA @ 24V DC
FA
Total Input 10mA @ 24V DC
2A SC Protected Reversed bias 11 -
+24V DC Status Not Used
Input 10mA @ 24V DC
Output B Ethernet under normal 25V DC
Logic operation
24V DC
A3 11 -
+5V DC
25Vdc
Input 3
Input 2
4 Inputs
50mA Max/input depends
on sensor attached to input
Output Contactor
Option
Option
Filter
L2 L2 T2 Motor
L3 L3 T3
01 02 03 04 05 06 07 08 09
3A RJ-45
AS Logic Class CC
BR+ BR-
Control 11 12 13 14 15 16 17 18 19
11 - +5V DC
A3 25V DC
PTC Port 1 Port 2
300mA Max
AS Logic
Current supplied by 5V DC
Circuits
A3 when A1 control
power is lost
Input 0
Input 1
Input 2
Input 3
Ethernet
Logic
Short
4 Inputs Detect
50mA Max/input depends
on sensor attached to input
Thomas & Betts Cord Grip Thomas & Betts Cord Grip
Cat. No. 2931NM Cat. No. 2940NM
0.75 in. Stain Relief Cord Connector 1 in. Stain Relief Cord Connector
Cable Range: 0.31…0.56 in. Cable Range: 0.31…0.56 in.
Used with Control Power Media Used with Three-Phase Power
Cordset - Example: Media Cordset - Example:
Cat. No. 889N-M65GF-M2 Cat. No. 280-PWR22G-M1
Figure 23 - Cord Grips for ArmorStart Devices with 25 A Short Circuit Protection Rating
Thomas & Betts Cord Grip Thomas & Betts Cord Grip
Cat. No. 2931NM Cat. No. 2942NM
0.75 in. Stain Relief Cord Connector 1 in. Stain Relief Cord Connector
Cable Range: 0.31…0.56 in. Cable Range: 0.70…0.95 in.
Used with Control Power Media Used with Three-Phase Power
Cordset - Example: Media Cordset - Example:
Cat. No. 889N-M65GF-M2 Cat. No. 280-PWR35G-M1
ATTENTION: Do not remove this jumper, that is shown in Figure 25, if the unit
is equipped with an EMI filter installed.
Disconnecting MOVs
IMPORTANT Do not apply the EMI filter option to grounded or ungrounded Delta power source.
The EMI option requires a solidly grounded Wye (Y) power source (i.e. 480/277 or
400/230V AC 3-Phase). If applied to a grounded or ungrounded 480V AC Delta
power source, the EMI filter will not function properly and will be damaged.
1. Before installing the Bulletin 284E, loosen the four mounting screws.
2. Unplug the control module from the base unit by pulling it forward.
Remove Jumper
Group Motor Installations for The ArmorStart Distributed Motor controllers are listed for use with each other
in group installations per National Fire Protection Association (NFPA) 79,
USA and Canada Markets Electrical Standard for Industrial Machinery. When applied according to the
group motor installation requirements, two or more motors, of any rating or
controller type, are permitted on a single branch circuit. Group motor
installation has been successfully used for many years in the USA and Canada.
Note: For additional information regarding group motor installations with the
ArmorStart Distributed Motor Controller, see Appendix A.
Wiring and Workmanship In addition to conduit and seal-tite raceway, it is acceptable to use cable that is
dual rated Tray Cable Exposed Runs (TC-ER) and Cord, STOOW, for power
Guidelines and control wiring on ArmorStart installations. In the USA and Canada
installations, the following guidance is outlined by the National Electrical Code
(NEC) and NFPA 79.
The working space around the ArmorStart controller may be minimized as the
ArmorStart does not require examination, adjustment, servicing, or maintenance
while energized. In lieu of this service, the ArmorStart controller is meant to be
unplugged and replaced after proper lockout/tag-out procedures have been
employed.
The Hand-Off-Auto (HOA) is a factory-installed option that the user may select.
The HOA keypad may require the ArmorStart controller to be selected and
installed as follows if the application requires frequent use of the hand operated
interface by the equipment operator:
1. They are not less than 0.6 m (2 ft) above the servicing level and are within
easy reach of the normal working position of the operator.
2. The operator is not placed in a hazardous situation when operating them.
3. The possibility of inadvertent operation is minimized.
The user should keep 3-phase power cabling at least 150 mm (6 in.) away from
the EtherNet/IP network to avoid noise issues. EtherNet/IP is an unpowered
network therefore, if device status is important when the power distribution
disconnect is in the OFF position, the A3 terminal must have an unswitched
power source.
Electromagnetic The following guidelines are provided for EMC installation compliance.
Compatibility (EMC)
General Notes (Bulletin 284E only)
• The motor Cable should be kept as short as possible to avoid
electromagnetic emission and also capacitive currents.
• Using an EMI filter, with any drive rating, may result in relatively high
ground leakage currents. Therefore, the filter must only be used in
installations that are solidly grounded (bonded) to the building power
distribution ground. Grounding must not rely on flexible cables and
should exclude any form of plug or socket that would permit inadvertent
disconnection. Some local codes may require redundant ground
connections. The integrity of all connections should be periodically
checked.
• When using a shielded motor cable the drain wire should be bonded to
chassis ground at the motor. The recommended motor connection should
use a shielded concentric connector. This provides 360° shielding. A single
point connection can be used but is less effective.
Wiring
Wire in an industrial control application can be divided into three groups: power,
control, and signal. The following recommendations for physical separation
between these groups, are provided to reduce the coupling effect:
• Minimum spacing between different wire groups in the same tray should
be 16 cm (6 in.).
General safety dictates that all metal parts are connected to earth with separate
copper wire or wires of the appropriate gauge. Most equipment has specific
provisions to connect a safety ground or PE (protective earth) directly to it.
Grounding PE or Ground
The safety ground - PE, must be connected to earth ground. This point must be
connected to adjacent building steel (girder, joist), a floor ground rod, bus bar, or
building ground grid. Grounding points must comply with national and local
industrial safety regulations or electrical codes. Some codes may require
redundant ground paths and periodic examination of connection integrity.
IMPORTANT To avoid electrolytic corrosion on the external earth terminal, avoid spraying
moisture directly on the terminal. When used in washdown environments
apply a sealant or other corrosion inhibitor on the external ground terminal to
minimize any negative effects of galvanic or electro-chemical corrosion.
Ground connections should be inspected regularly.
Shield and Grounding of The motor frame or stator core must be connected directly to the PE connection
with a separate ground conductor. It is recommended that each motor frame be
Motors and Motor Cables grounded to building steel at the motor.
Most recommendations regarding motor cable address issues are caused by the
nature of the drive output. A PWM drive creates AC motor current by sending
DC voltage pulses to the motor in a specific pattern. These pulses affect the wire
insulation and can be a source of electrical noise. The rise time, amplitude, and
frequency of these pulses must be considered when choosing a wire/cable type.
The choice of cable must consider:
Keep the motor cable lengths less than 13.7 m (45 ft) unless otherwise noted in
the device specifications.
Unshielded Cable
The use of cables without shielding is generally acceptable for installations where
electrical noise created by the drive does not interfere with the operation of other
devices such as: communications cards, photoelectric switches, weigh scales, and
others. Be certain the installation does not require shielded cable to meet specific
EMC standards for CE, C-Tick, or FCC. Cable specifications depend on the
installation type.
Shielded Cable
Shielded cable contains all general benefits of multi-conductor cable with the
added benefit of a copper braided shield that can contain much of the noise that
is generated by a typical AC Drive. Strong consideration for shielded cable should
be given for installations with sensitive equipment such as weigh scales, capacitive
proximity switches, and other devices that may be affected by electrical noise in
the distribution system. Applications with large numbers of drives in a similar
location, imposed EMC regulations, or a high degree of communications/
networking are also good candidates for shielded cable.
An acceptable shielded cable has four XLPE insulated conductors with a 100%
coverage foil and an 85% coverage copper braided shield (with drain wire)
surrounded by a PVC jacket.
The cable connector that is selected must provide good, 360° contact and low
transfer impedance from the shield or armor of the cable to the conduit entry
plate at both the motor and the ArmorStart controller for electrical bonding.
SKINTOP® MS-SC/MS-SCL cable grounding connectors and NPT/PG
adapters from LAPPUSA are good examples of this type of shield terminating
gland.
The ArmorConnect power media offers both three-phase and control power
cable cord set systems including patchcords, receptacles, tees, reducers and
accessories to be used with the ArmorStart Distributed Motor Controller. These
cable system components allow quick connection of ArmorStart Distributed
Motor Controllers, reducing installation time. They provide for repeatable,
consistent connection of the three-phase and control power to the ArmorStart
Distributed Motor Controller and motor by providing a plug-and-play
environment that also avoids system mis-wiring.
IMPORTANT ArmorConnect connections should be made hand tight. See the ArmorConnnect
instructions for recommended tightening torque. The use of a tool to help in the
tightening of the connector is not recommended.
When specifying power media for use with the ArmorStart Distributed Motor
Controllers (Bulletins 280E, 281E, and 284E), use only motor and power cables
that are listed for use with ArmorStart.
IMPORTANT The ArmorStart UL listing does not permit using a third party or un-listed motor and
power cable assembly. Using a cable assembly that is not permitted results in a loss of
Listing and does not comply with NFPA 79 or the NFPA 70 (NEC) (see 110.3(B) of the
NEC).
For reference, the UL White Book states the following for power media cable
assemblies meeting UL 2237 standard:
“These devices are intended for use only with the Listee’s same line of products that are
covered under this category....”
Illumination Contact
Enclosure Type Quick Connect Knockout Type Operator Voltage Configuration Cat. No.
Plastic 24V AC/DC 800F-1YMQ4
Mini Receptacle Metric Twist to Release 1 N.C./1 N.O.
Metal 24V AC/DC 800F-1MYMQ4
As an alternative to the unique 6/5 pin control cable the auxiliary power cabling
can be used. Auxiliary Power is based on a 4–pin connector system and is used to
provide 24V DC power to I/O modules and other devices separately from
network power. Running separate power to these devices is typically used for I/O
devices with output connections to prevent power supply interruption due to
switching of outputs.
Figure 34 - Control Power Overview using 4-Pin Auxiliary Power Tee Adapter
➒ Bulkhead pass-thru connectors are passive male to female 4-pin mini connectors within a
threaded metal housing that is used for Auxiliary Power - Cat. No. 889A-CXN4-M4
➓Auxiliary power trunk cables are four-pin mini-style patchcords. - Cat. No. 889N-F4HKNM-*
(Straight Female to Straight Male)
ArmorStart auxiliary adapter power tees allow connecting devices to the power trunk line using
an associated power drop cordset - Cat. No. 898N-543ES-NKF
12 Auxiliary power drop cable - Cat. No. 889D-R4HJDM-* (18AWG wire Right Female to
Straight Male)
ArmorConnect Cable Ratings The ArmorConnect power media cables are rated per UL Type TC 600V 90°C
Dry 75°C Wet, Exposed Run (ER) or MTW 600V 90°C or STOOW 105°C
600V - Canadian Standards Association (CSA) STOOW 600V FT2. For
additional information regarding ArmorConnect power media see publication
280PWR-SG001.
Circuit Breaker: Suitable for use on a circuit capable of delivering not more than
65 000 RMS symmetrical amperes at 480V AC maximum when protected by a
Bulletin 140U-H or Bulletin 140G-H circuit breaker, not rated more than 480V,
100 A and a maximum interrupting of 65 000 RMS symmetrical amperes Short
Circuit Current Rating (SCCR). Examples include 140G-H6F3-D10 or 140U-
H6C3-D10.
Fusing: Suitable for use on a circuit capable of delivering not more than 65 000
RMS symmetrical amperes (SCCR) at 600V AC maximum when protected by
CC, J, and T class fuses.
Circuit Breaker: Suitable for use on a circuit capable of delivering not more than
45 000 RMS symmetrical amperes at 480Y/277V AC maximum when protected
by Cat. No. 140U-D6D3-C30 circuit breaker, not rated more than 480V, 30 A,
having an interrupting rating not more than 45 000 RMS symmetrical amperes.
WARNING: The total circuit impedance including each cable assembly's own
impedance, must be low enough to ensure any short-circuit or ground fault current that
can flow through any assembly, is large enough to operate the magnetic trip of the Cat.
No. 140U-D63-C* circuit breaker. See your local electrical code for acceptable practices
for this evaluation.
Fusing: Suitable for use on a circuit capable of delivering not more than 65 000
RMS symmetrical amperes (SCCR) at 600V AC maximum when protected by
CC, J, and T class fuses, rated 40 A non-time delay or 20 A time delay.
Ethernet and I/O Connections ArmorStart EtherNet/IP controller uses a sealed D-coded M12 (micro) style
ethernet connector.
Power Connections
Figure 39 - External Connections for Motor Connector – Bulletin 284E - 5 Hp and
Bulletin 280E, 281E - 3 Hp or less (M22) at 480V AC
Pin 1 - T1 (black)
Pin 2 - T2 (white)
Pin 3 - T3 (red)
Pin 4 - Ground (green/yellow)
Figure 40 - External Connections for Motor Connector – Bulletin 280E, 281E - 10 Hp (M35)
at 480V AC
Pin 1 - T1 (black)
Pin 2 - Ground (green/yellow)
Pin 3 - T3 (red)
Pin 4 - T2 (white)
Pin 1 - L1 (black)
Pin 2 - Ground (green/yellow)
Pin 3 - L2 (white)
Pin 1 - L1 (black)
Pin 2 - L2 (white)
Pin 3 - L3 (red)
Pin 4 - Ground (green/yellow)
Pin 1 - L1 (black)
Pin 2 - Ground (green/yellow)
Pin 3 - L3 (red)
Pin 4 - L2 (white)
Optional Locking Clip The clam shell design clips over the ArmorStart motor connector and motor
cable to limit customer access from disconnecting the motor cable on the
ArmorStart Distributed Motor Controller. The locking clip is an optional device
that can be used, if desired. A locking clip is not available for the M25 Source
Brake connection.
Maintenance The ArmorStart controller does not require much regular maintenance. There
are a few checks that are needed to verify continued proper operation. When
using ArmorConnect media or conductors, verify that the connections remain
tight where exposed to shock and vibration. Check that the heatsink allows good
air flow. Bulletin 284 includes an internal circulating fan to support heat
conduction in high ambient applications. This fan operates when control power
is applied and cannot be controlled by any other means. Monitor the fan speed to
receive early warning of fan failure. If the fan rpm falls below 1740, a Hardware
Fault F14 is generated. Also in parameter 61, Last Pr Fault indicates a FAN RPM
fault has occurred.
IMPORTANT The FAN RPM fault can be reset with firmware 66.022 or later. The fault reset
function is modified to allow normal operation for 24 hours before the fault
reoccurs. The replacement fan is PN 284-FAN. Refer to Hardware Fault -
Fan RPM Warning on page 235 for information regarding the monitoring of the
Fan RPM
The host name can also see the fully qualified domain name (FQDN), or in this
example, www.trading.com. Both naming methods seem to be used
interchangeably in various documents. For the purposes of this document, the
host name sees the FQDN, or as in this example, www.trading.com.
Hub A central connecting device that joins devices together in a star configuration.
Hubs are generally not suitable for use in I/O control systems, since they are
time-critical applications that cannot tolerate lost packets.
Implicit messaging Real-time messaging of I/O data.
IP Internet protocol that provides the routing mechanism for messages. All
messages contain not only the address of the destination station, but the
address of a destination network, that allows messages to be sent to multiple
networks within an organization or around the world.
IP address A 32-bit identification number for each node on an Internet Protocol network.
These addresses are represented as four sets of 8-bit numbers (numbers from 0
to 255), with decimals between them. Each node on the network must have a
unique IP address.
Latency The time between initiating a request for data and the beginning of the actual
data transfer.
Multicast In the CIP producer/consumer model, one producer multicasts (broadcasts) the
data once to all consumers.
Producer The source of information in the CIP networking model. See CIP.
Introduction to EtherNet/IP Automation architectures must provide users with three primary services:
EtherNet/IP is a CIP adaptation of TCP/IP that fully uses the IEEE standard.
The relationship between the TCP/IP and CIP to form EtherNet/IP is shown in
the ISO/OSI 7-layer model is shown in Figure 49. The OSI model is an ISO
standard for network communications that define all functions from a physical
layer to the protocol.
Distributed I/O
1769-L23Ex
1768-L4x
1768-ENBT 1756-EN2T
1756 I/O Modules
1769-L3xE
1794-AENT
1794 I/O Modules
1734-AENT
PowerFlex 1734 I/O Modules
Drive
Workstation
1783-ETAP 1783-ETAP
ArmorStart Workstation
Ethernet/IP 1783-ETAP
PanelView Terminal
1734-AENTR 1738-AENTR
1756-EN2TR 1734 I/O Modules 1738 I/O Modules
1756 I/O Modules
This approach provides real time technology into the Ethernet domain. With the
network extensions of CIP Safety, CIP Sync, and CIP Motion, CIP networks
allow for safety communication, time synchronization, and simple to high
performance motion all over the same EtherNet/IP network.
Linear Network Introduction A linear network is a collection of devices that are daisy-chained together.
The primary disadvantage of a linear network is that any break of the cable
disconnects all devices downstream from the break from the rest of the network.
IMPORTANT Products with EtherNet/IP embedded switch technology have two ports to connect to
a linear or DLR network in a single subnet.
You cannot use these ports as two Network Interface Cards (NICs) connected to two
different subnets.
A Device Level Ring (DLR) protocol defines a set of behaviors, see Figure 52. A
ring supervisor keeps packets of information from circulating infinitely around
the ring by blocking one of the ports. A beacon frame constantly is detected on
both ring supervisor ports. If a beacon frame is not detected the supervisor
detects the physical layer issue and reconfigures the network to a linear topology
without the loss of any node communication or data. Once repaired the ring
supervisor reconfigures back to ring mode.
When the physical layer fault is corrected the supervisor will “hear” the beacon
frame again on both ports. Once this is detected the ring supervisor re-establishes
and configures the ring topology. All neighboring nodes detect this and
reconfigure themselves back to ring. A DLR network is a single-fault tolerant
network that is intended for the interconnection of automation devices.
IMPORTANT Any nodes that do not support DLR should not be directly connected to the ring.
The node should be connected to the ring through a switch that supports DLR.
The primary disadvantage of the DLR topology is the additional effort that is
required to set up and use the network as compared to a linear or star network.
IMPORTANT Products with EtherNet/IP embedded switch technology have two ports to connect to
a linear or DLR network in a single subnet.
You cannot use these ports as two Network Interface Cards (NICs) connected to two
different subnets.
Number of Nodes on a Rockwell Automation recommends that you use no more than 50 nodes on a
single DLR or linear network. If your application requires more than 50 nodes, it
DLR Network is recommended that the DLR networks are segmented.
Ethernet Switches Ethernet managed switches are key components that provide determinism and
the required throughput to achieve automation needs. Switches are able to
manage network traffic that reduces unnecessary delays or band width needs. A
properly designed EtherNet/IP infrastructure that implement segregation via
managed switch technology achieves a more reliable and secure network.
Ethernet Media Today, unshield twisted pair (UTP) wiring is the standard in most applications
and allows for greatest flexibility and ease of installation and maintenance.
Category 5e (e-enhanced) cable is specifically designed to meet today’s
automation needs.
Standard RJ-45 connectors are not designed for industrial environments. For
outside the panel, IP67 connectors are required for EtherNet/IP.
EtherNet/IP General Ethernet is found in automation equipment, panels, and components. There are a
few guidelines, that if followed, will reduce the number of issues an EtherNet/IP
Wiring Guideline application may experience.
• Where possible, route the Ethernet/IP media five feet or more from high
voltage sources (for example, lights, ballasts, motors, …) or sources of radio
frequency, such as variable frequency drives.
• Maintain media lengths between nodes to less than 100 m (328 ft). In
today’s environment, it may be challenging to maintain these guidelines,
however these reduce potential application issues.
Requested Packet Interval The Requested Packet Interval (RPI) is the update rate that is specified for a
particular piece of data on the network. This value specifies how often to produce
the data for that device. For example, if you specify an RPI of 50 ms, it means that
every 50 ms the device should send data to the controller or the controller should
send data to the device.
IMPORTANT The RPI determines the number of packets per second that the module produces on a
connection. Each module can produce only a limited number of packets per second.
Exceeding this limit prevents the module from opening more connections.
5. Click OK.
Notes:
Product Commissioning
IP Address The IP address identifies each node on the IP network (or system of connected
networks). Each TCP/IP node on a network must have a unique IP address.
The IP address is 32 bits long and has a net ID part and Host ID part. Networks
are classified A, B, C, (or other). The class of the network determines how an IP
address is formatted.
0 23 24 31
Class C 110 Net ID Host ID
You can distinguish the class of the IP address from the first integer in its
dotted-decimal IP address as follows:
There are reserved values that you cannot use as the first octet in the address.
These numbers are examples of values you cannot use:
• 001.xxx.xxx.xxx
• 127.xxx.xxx.xxx
• 223 to 255.xxx.xxx.xxx
The specific reserved values that cannot be used vary according to the conditions
of each application. The previous values are only examples of reserved values.
Each node on the same physical network must have an IP address of the same
class and must have the same net ID. Each node on the same network must have a
different Host ID thus giving it a unique IP address.
Gateway Address
Subnet Mask
Subnet addressing is an extension of the IP address scheme that allows a site to use
a single network ID for multiple physical networks. Routing outside of the site
continues by dividing the IP address into a net ID and a host ID via the class.
Inside a site, the subnet mask is used to redivide the IP address into a custom
network ID portion and host ID portion. This field is set to 0.0.0.0 by default.
If you change the subnet mask of an already-configured module, you must cycle
power to the module for the change to take effect.
Configuring EtherNet/ Before using the ArmorStart, you may need to configure an IP address, subnet
mask, and optional Gateway address. The rotary network address switches found
IP Address on the I/O section of the ArmorStart are set to 999 and DHCP is enabled as the
factory default. The ArmorStart reads these switches first to determine if the
switches are set to a valid IP address between 1…254. When switches are set to a
valid number the IP address will be 192.168.1._ _ _ [switch setting].
This document assumes that the user has set the IP address to 192.168.1.1. The
user can change this IP address to any address either statically or dynamically.
Remove the protective caps from the rotary switches. Set the network address by
adjusting the three switches on the front of the I/O module.
X100 X10 X1
This example shows the 0 0 0
Valid IP address switch settings range from 001 to 254. When the switches are set
to a valid number, the adapter’s IP address will be 192.168.1.xxx (where xxx
represents the number set on the switches; see Figure 57). The adapter’s subnet
mask is 255.255.255.0 and the gateway address is set to 0.0.0.0. A power cycle is
required for any new IP address to take effect.
Note: The upper three octets are fixed. DHCP or the embedded webserver must
be used to configure the IP address to a value other than 192.168.1.xxx.
If the switches are set to an invalid number (such as 000 or a value greater than
254), the adapter will check to see if DHCP is enabled. If DHCP is enabled, the
adapter requests an address from a DHCP server. If DHCP is not enabled, the
adapter will use the IP address (along with other TCP configurable parameters)
stored in non-volatile memory.
IMPORTANT See Figure 58. The ArmorStart is shipped with the control module rotary switches
set to a value of 99. DO NOT modify this setting. If these are changed and the
unit stops responding, the switches will need to be manually set to node address
63 and power cycled.
Factory Setting 99
DO NOT CHANGE!
Use the Rockwell Automation The Rockwell Automation BootP/DHCP utility is a stand alone program that
incorporates the functionality of standard BootP/DHCP software with a user-
BootP/DHCP Utility friendly graphical interface. It is located in the Utils directory on the
RSLogix 5000 installation CD. The ArmorStart EtherNet/IP adapter must have
DHCP enabled (factory default) to use the utility.
To configure your adapter using the BootP/DHCP utility, perform the following
steps:
3. Enter the IP Address that you want to assign to the device, and click OK.
The device is added to the Relation List, displaying the Ethernet Address
(MAC) and corresponding IP Address, Hostname, and Description (if
applicable).
When power is cycled to the device, it uses the configuration you assigned
and does not issue a DHCP request.
5. To enable DHCP for a device with DHCP disabled, highlight the device
in the Relation List, and click the Enable DHCP button.
You must have an entry for the device in the Relation List panel to
re-enable DHCP.
You can save the Relation List to use later. To save the Relation List perform the
following steps:
3. Enter a File name for the Relation List (for example, Control System
Configuration), and click Save.
You can leave the Save as type at the default setting: Bootp
You can then open the file containing the Relation List at a later session.
DHCP IP Support DHCP (Dynamic Host Configuration Protocol) software automatically assigns
IP addresses to client stations logging onto a TCP/IP network.
When DHCP is enabled (factory default Enabled), the unit will request its
network configuration from a DHCP/BOOTP server. Any configuration
received from a DHCP server is stored in non-volatile memory.
IMPORTANT The user should set the password to a unique value for authorized personnel.
If the login and password are lost you will need to reset the device to the factory
defaults, that results in losing its configuration.
To access the internal web browser, open your computers internet browser and
enter the IP address of the desired ArmorStart (for example, 192.168.1.1).
From here you are able to view parameter settings, device status, and diagnostics
from multiple tab views.
Network Configuration
From this screen you can change the Ethernet Configuration. For example, in the
above image the default IP address was changed from 192.168.1.1 to
10.10.10.101. To access the webpage after a power cycle, the new address must be
used.
It is also important to leave the Ethernet link configuration P1/P2 set to auto
negotiate to minimize network issues. But if this is not acceptable you must verify
that all devices on the network are set to the same setting or network issues may
result.
Parameter Configuration
ArmorStart Ethernet/IP embedded web server provides the user the ability to
view and modify the device configuration without having to access
RSLogix 5000. To view the device configuration from the web server, select the
Parameters folder. For the parameter configuration, the user logs in through the
Administrative Settings, or when prompted.
In the figure above the Starter Setup parameters are viewed. The user can view
all parameters from this screen. To modify a parameter, the user clicks the “Edit”
button.
The user is prompted to enter the default user name (Administrator). There is no
password set by default. The user is expected to change the user name (login) and
password to avoid unauthorized access to the device configuration.
The above screen shows an example of changing the Overload Class setting to 15.
Once all changes are made select Apply.
Note: “Cleared Event” e-mails are only sent when all events have been cleared and
if a trip event e-mail has previously been sent. For example, if the device is
configured to send e-mails when a phase loss trip and an overload trip is detected,
no e-mail is sent when both the overload and the phase loss is cleared.
Body:
Trip Info: Load has drawn excessive current that is based on the trip
class selected.
Device Connections The device supports both scheduled (Class 1) and unscheduled (Class 3 &
UCMM) CIP connections. A maximum of two Class 1 CIP connections (one
exclusive owner and one listen only) are supported, one per PLC. Six Class 3 CIP
connections are supported.
Ownership In a Studio 5000® system, modules multicast data. Therefore, multiple modules
can receive the same data simultaneously from a single module. When choosing a
communication format, decide whether to establish an owner-controller or
listen-only relationship with the module.
Listen-only connection An I/O connection where another controller owns/provides the configuration data for the I/O module. A controller using a listen-only
connection monitors only the module. It does not write configuration data and can only maintain a connection to the I/O module when the
owner controller is actively controlling the I/O module.
Ethernet Statistics Web Page The Ethernet Statistics web page of a scanner provides a summary of the status of
communication activity on the Ethernet network.
The most commonly monitored fields are circled in the graphic and described in
the table that follows.
This table describes the field that is most commonly used on the Ethernet
Statistics web page.
Field Specifies
Ethernet Port 1 (These definitions apply to the same fields in the Ethernet Port 2 section.)
Interface State Whether the port is turned off or on. Active or inactive indicates whether there is a cable that is connected.
Link Status Whether the port is blocked for DLR protocol frames.
Speed Whether the Ethernet port is operating at 10 or 100 MBps.
Duplex Whether the Ethernet port is operating at half duplex or full duplex.
Autonegotiate Status Whether the port speed and Duplex mode were determined via autonegotiation or whether they were manually configured.
Media Counters Port 1
Alignment Errors A frame containing bits that do not total an integral multiple of eight.
FCS Errors A frame containing eight bits, at least one of which has been corrupted.
Single Collisions The number of outgoing packets that encountered only one collision during transmission.
Field Specifies
Multiple Collisions The number of outgoing packets that encountered 2...15 collisions during transmission.
SQE Test Errors A test to detect the collision-present circuit between a transceiver and a network interface card (NIC).
IMPORTANT: Because most NICs now have an integrated transceiver, the SQE test is unnecessary. Ignore this media counter.
Deferred Transmissions The number of outgoing packets whose transmission is deferred because the network is busy when the first attempt is made to send them.
Late Collisions The number of times two devices transmit data simultaneously.
Excessive Collisions The number of frames that experience 16 consecutive collisions.
MAC Transmit Errors Frames for which transmission fails due to an internal MAC sublayer transmit error.
Carrier Sense Errors Times that the carrier sense condition was lost or never asserted when attempting to transmit a frame.
Frame Too Long The number of incoming packets that exceed the maximum Ethernet packet size.
MAC Receive Errors Frames for which reception on the Ethernet interface failed due to an internal MAC sublayer receive error.
Connection Manager Cmd The Connection Manager Cmd Object Info web page of a scanner provides a
summary of connection request activity on the Ethernet network.
Object Info Web Page
The most commonly used field on this page is Connections Closed due to a
Timeout. This field shows the number of CIP connection timeouts that have
occurred on the module.
The Ring Statistics web page of a scanner provides a summary of the module’s
operating state in a DLR application.
The most commonly monitored fields are circled in the graphic and described in
the table that follows.
This table describes the field that is most commonly used on the Ring Statistics
web page.
Field Specifies
Ring Supervisor
Ring Supervisor Mode Whether a module is configured to function as supervisor node or a ring node.
Ring Supervisor Status Whether a module that is configured to function as a supervisor node is functioning as the active ring supervisor or a
backup supervisor node.
Ring Fault Location
Last Active Node on Port 1 The IP or MAC ID address of the last active node between port 1 on the module and the faulted part of the network.
Last Active Node on Port 2 The IP or MAC ID address of the last active node between port 2 on the module and the faulted part of the network.
Active Ring Supervisor
Address The IP or MAC ID address of the active ring supervisor.
Precedence The precedence value of the module. If the active supervisor node’s operation is interrupted the backup supervisor with
the next highest precedence value becomes the active supervisor node.
Setup This section shows you how to add an ArmorStart AOP to RSLogix™ 5000
software. It is assumed that you have downloaded and installed the AOP so that
the RSLogix 5000 software can fully support the ArmorStart EtherNet/IP. The
AOP can be downloaded from: http://support.rockwellautomation.com/
controlflash/LogixProfiler.asp.
3. Enter the name of the project and select your controller from the Type
pull-down menu. (For this example, a Cat. No. 1769-L35E and software
version 19 is used.) Click OK.
4. To add a new module to the tree, right-click Ethernet and select New
Module. This allows you to add a new ArmorStart selection to the Logix
Project.
6. The AOP is shown below. Enter a Name for this ArmorStart selection and
an Ethernet address. For this example, the Private Network setting is used.
This should be set to match the IP address switch setting on the
ArmorStart selection. Click OK.
Connect and Configure This section shows the AOP tabs and how they can be used to connect, obtain
status, and configure the ArmorStart selection. Before the walkthrough is started,
ArmorStart with Add-On- the RSLogix 5000 software should be open and an AOP displayed as shown
Profile (AOP) below.
The screenshot above displays that the AOP has seven tabs that can be used to
configure and/or monitor your ArmorStart selection. The following lists the tabs
and whether they are editable or not, with the controller when OFFLINE,
ONLINE, or both:
• General – OFFLINE
• Connection – OFFLINE
• Module Info – ONLINE
• Parameters – OFFLINE/ONLINE
The last five tabs in the list do not display information until the ONLINE
connection has been established with the ArmorStart device. The General,
Connection, and Parameters tabs are discussed first, because they are used to
define OFFLINE settings so that connection with the ArmorStart device can be
established.
This tab allows you to name your module, which should be descriptive and
representative of the module. The IP Address of the module must also be input so
that communication can be established. The IP Address should be the one
defined using the BootP/DHCP Server, the Rotary Network Address Switches
or the ArmorStart internal web server.
For most cases, the Host Name and Module Definition section of this tab do not
require any adjustment. Changes to either of these should only be made if you are
familiar with the functionality of each of these sections.
Connection Tab
The Request Packet Interval (RPI) indicates the maximum frequency at which
data is received. It is possible that data could come more quickly than the time
interval assigned in the RPI. In most cases, the default 20 ms should be the
optimal setting. If you check the Inhibit Module option, connection to controller
tags will be broken. The Major Fault on Controller if Connection Fails While in
Run Mode option should be checked to ensure that the controller processes the
connection fault with the ArmorStart. The Use Unicast Connection over
EtherNet/IP is checked to use the Unicast mode instead of the EtherNet/IP
mode. This appears only for modules using RSLogix 5000 software version 18 or
later that supports Unicast.
Parameters Tab
The parameters are divided into groups that are based on the type of ArmorStart
device. By clicking in the Group pull-down menu, you can choose which
parameter group is displayed. When the Parameters tab is selected, the tab
defaults to the Drive Setup (Bulletin 284E) or Starter Setup (Bulletin 280E)
groups depending on the ArmorStart selection. These Setup groups are the
minimum required parameters to get the ArmorStart device running.
After this parameter group has been set, the next time that the Parameters tab is
opened, all parameters are shown and the tab is no longer default to the setup
groups.
Online Connection Now that the offline connection settings have been set, connect to the
ArmorStart device to review the last five AOP tabs.
Note: If you are using a Cat. No. 1756-ENBT Ethernet module to communicate with
the PLC, verify that you have updated the module’s firmware to Revision 6.001 or
later. The latest firmware can be found at http://support.rockwellautomation.com/
controlflash/.
1. If a controller path is not set in the field that is shown below, you must first
set a path before going online with the controller. Click the RSwho
button shown below.
4. The following appears and for this example, click Download to connect to
the controller.
7. The controller should now be online. If at any point you go offline and a
path is selected, you can also go online by clicking the Offline drop down
in the upper left corner of the screen. Click Go Online to connect to the
ArmorStart device, as shown below.
Parameters Tab
Return to the Parameters tab again once the AOP is opened by selecting the
ArmorStart in the project tree. Notice that when clicking in the Parameters tab,
an ArmorStart Correlation pop-up window is displayed, as shown below.
This indicates that the AOP is comparing the parameter data entered offline vs.
the parameter data that is stored in the ArmorStart device. If any discrepancies are
found between the parameters in the AOP and the parameters in the ArmorStart
device, a window will pop-up, as shown below, asking you to decide which
parameters you want to keep.
If you want to keep the parameters in the AOP, select Download. If you want to
keep the parameters in the ArmorStart device, select Upload. Otherwise, select
Cancel. Clicking Cancel locks the user out of viewing the values. If you are
connected to a new ArmorStart device and you just created the ArmorStart
object and have not made any changes in the parameters, the ArmorStart
correlation should not find any discrepancy.
Note: If you make any changes to the parameters offline, they will not be
downloaded to the ArmorStart device when the connection is made (going
Online). For the Offline changes to take effect you must go to the Parameters tab.
Once you click the Parameters tab, ArmorStart correlation takes place and then
the changes can be downloaded to the ArmorStart device.
If the IP address was set up using the Rotary Network Address Switches, default
settings for the IP would already be established and you will not be able to make
any changes in this tab. In most cases, you would not need to make any changes in
this tab and it only displays the current IP Settings Configuration.
This tab is used to enable or disable a physical port in the module. The ports are
normally in Auto Negotiate mode, which in general, is the recommended setting.
Otherwise, you have to physically set the Speed or Duplex selection in this tab. It
is important to note that although there are two physical ports, they act as one.
Therefore, when you press either of the Port Diagnostic buttons, information
coming from both of the physical ports is displayed.
Network Tab
This tab displays information about the network configuration, such as the type
of topology (linear or device level ring).
Auto-Generated Tags
After you install and configure the AOP, the controller tags are generated. The
tags names are descriptive and automatically generated. This greatly simplifies
programming. The figure below shows an example of the auto-generated tags for
an ArmorStart selection.
The following tables provide more clarification regarding the Produce and
Consume assemblies and how they correlate with the auto-generated names.
Using an AOP the data in the Consumed and Produced Assemblies are
automatically created as descriptive tag names. To drive this point home we've
highlighted a few of the commands to demonstrate the AOP tag alignment to the
Consumed and Produced Assemblies in the following tables.
0 Reserved - {name}:I.Fault ➊
1 Reserved - {name}:I.Fault ➊
2 Reserved - {name}:I.Fault ➊
3 Reserved - {name}:I.Fault ➊
Network
4 AtReference NetControlStatus Ready RunningReverse RunningForward WarningPresent TripPresent
ReferenceStatus
Output Brake
5 DisconnectClosed Hand In3 In2 In1 In0
ContactorStatus ContactorStatus
6 OutputFrequency (Low) (xxx.x Hz)
7 OutputFrequency (High) (xxx.x Hz)
8 Pt07DeviceOut Pt06DeviceOut Pt05DeviceOut Pt04DeviceOut Pt03DeviceOut Pt02DeviceOut Pt01DeviceOut Pt00DeviceOut
9 LogicEnable Pt14DeviceOut Pt13DeviceOut Pt12DeviceOut Pt11DeviceOut P10DeviceOut Pt09DeviceOut Pt08DeviceOut
10 Value of the parameter pointed to by "Parameter 13 Prod Assy Word 0" (low byte)" - Int00DeviceOut
11 Value of the parameter pointed to by "Parameter 13 Prod Assy Word 0" (high byte)" - Int00DeviceOut
12 Value of the parameter pointed to by "Parameter 14 Prod Assy Word 1" (low byte)" - Int01DeviceOut
13 Value of the parameter pointed to by "Parameter 14 Prod Assy Word 1" (high byte)" - Int01DeviceOut
14 Value of the parameter pointed to by "Parameter 15 Prod Assy Word 2" (low byte)" - Int02DeviceOut
15 Value of the parameter pointed to by "Parameter 15 Prod Assy Word 2" (high byte)" - Int02DeviceOut
16 Value of the parameter pointed to by "Parameter 16 Prod Assy Word 3" (low byte)" - Int03DeviceOut
17 Value of the parameter pointed to by "Parameter 16 Prod Assy Word 3" (high byte)" - Int03DeviceOut
➊ Identifies if a Communication Fault exists. If a communication loss is present the PLC writes four bytes of 1's to this tag. The user
should monitor this tag to ensure the data is valid.
IMPORTANT The user PLC control program should monitor the I.Fault tag to ensure the data is
accurate. When a communications fault occurs, the data in the consume and produce
tags may not accurately reflect the status.
Table 17 -
Instance 150 "Starter Stat" - Default Status Assembly for Bulletin 280E, 281E Starters
Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
0 Reserved - {name}:I.Fault ➊
1 Reserved - {name}:I.Fault ➊
2 Reserved - {name}:I.Fault ➊
3 Reserved - {name}:I.Fault ➊
Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
➊ Identifies if a Communication Fault exists. If a communication loss is present the PLC writes four bytes of 1's to this tag. The user
should monitor this tag to ensure the data is valid.
IMPORTANT The user PLC control program should monitor the I.Fault tag to ensure the data is
accurate. When a communications fault occurs, the data in the consume and produce
tags may not accurately reflect the status.
Introduction This chapter provides a basic understanding of the programming of the factory-
installed optional built-in Hand/Off/Auto (HOA) keypad. The HOA keypad
can be programmed for maintained or momentary operation.
Keypad Description The keys that are found on the optional HOA keypads are described below:
The Auto key allows for Start/Stop control via the communications
AUTO network
OFF If the starter is running, pressing the OFF key causes the starter to stop.
DIR Arrow The Dir arrow selects the direction of the motor, either forward or reverse.
When pressed, JOG will be initiated if no other control devices are sending
JOG a stop command. Releasing the key causes the drive to stop, using selected
stop mode.
The following state transition matrix summarizes the HOA Keypad when
Parameter 45 “Keypad Mode” is set to 1=momentary.
.
The following state transition matrix summarizes the HOA Keypad when
Parameter 45 “Keypad Mode” is set to 0=maintained.
.
The following state transition matrix summarizes the HOA behavior when
Parameter 45 “Keypad Mode” is set to 1=momentary.
Command motor OFF and transition to Command motor OFF and transition to Command motor OFF and transition to
Ignore “HAND STOP” “HAND STOP” “HAND STOP”
The following state transition matrix summarizes the HOA behavior when
Parameter 45 “Keypad Mode” is set to 0=maintained.
Command motor OFF and transition to Command motor OFF and transition to Command motor OFF and transition to
Ignore “HAND STOP” “HAND STOP” “HAND STOP”
The following state transition matrix summarizes the Jog/HOA behavior when
Parameter 45 “Keypad Mode” is set to 1 = momentary.
HAND STOP HAND FWD HAND REV JOG FWD JOG REV AUTO
If (FWD LED) If (FWD LED)
If (FWD LED) Set REV LED Set REV LED Set REV LED
Ignore Ignore Ignore
Else If (REV LED) Set FWD LED Else If (REV LED) Else If (REV LED)
Set FWD LED Set FWD LED
Command motor OFF and transition to AUTO Ignore Ignore Ignore Ignore Ignore
The following state transition matrix summarizes the Jog/HOA behavior when
Parameter 45 “Keypad Mode” is set to 0 = maintained.
HAND STOP HAND FWD HAND REV JOG FWD JOG REV AUTO
Command motor Command motor Command motor Command motor
No Key Pressed Ignore OFF and transition OFF and transition OFF and transition OFF and transition Ignore
to HAND STOP to HAND STOP to HAND STOP to HAND STOP
Command motor OFF and Transition to AUTO Ignore Ignore Ignore Ignore Ignore
Command motor Command motor Command motor Command motor Command motor
Ignore OFF and transition OFF and transition OFF and transition OFF and transition OFF and transition
to HAND STOP to HAND STOP to HAND STOP to HAND STOP to HAND STOP
Note: In nearly all instances, if the processor detects multiple buttons are pressed
simultaneously, the software interprets this as a “no button pressed” condition.
The only exception to this rule is if multiple buttons are pressed and one of them
is the “OFF” button. If the “OFF” button is pressed in combination with any
combination of other buttons, the processor will interpret this the same as if the
“OFF” button were pressed by itself.
Keypad and HOA Disable Parameter 46 “Keypad Disable”, disables the “HAND”, “FWD”, “REV” and “Jog”
buttons on the HOA keypad. The “OFF” and “AUTO” buttons are always
enabled, even if Parameter 46 is set to “1=Disable”. In addition for Bulletin 284
the user can disable the HAND-Reverse and Jog-Reverse operation by setting
parameter 195, Reverse Disable.
Notes:
Bulletin 280E/281E/284E
Programmable Parameters
Basic Setup Parameters To configure the basic ArmorStart functionality see Table 22 below. These are the
minimum setup configurations that are required for Bulletin 280E, 281E, or
Bulletin 284E. There are additional capabilities and motor protection that are
not enabled or left at their default values.
Table 22 - Quick Parameter Setup
Parameter Groups
Bulletin 284E
Common to Bulletin 280E, 281E, and Bulletin 284E Units Units Only
Produced Assembly
Basic Status Config Group Starter Protection User I/O Config Miscellaneous Config Drive I/O Config
1 Hdw Inputs 13 Int00DeviceOut Cfg 23 Pr FltResetMode 30 Anti-bounce On Delay 8 Network Override 48 Drive Control
2 DeviceIn Data 14 Int01DeviceOut Cfg 24 Pr Fault Enable 31 Anti-bounce OFF Delay 9 Comm Override 49 DrvIn Pr FltState
3 DeviceOut Data 15 Int02DeviceOut Cfg 25 Pr Fault Reset 32 In Sink/Source 45 Keypad Mode 50 DrvIn Pr FltValue
4 Trip Status 16 Int03DeviceOut Cfg 26 Str Net FltState 33 OutA Pr FltState 46 Keypad Disable 51 DrvIn Net FltState
5 Starter Status 27 Str Net FltValue 34 OutA Pr FltValue 47 Set To Defaults 52 DrvIn Net FltValue
6 InternalLinkStat 28 Str Net IdlState 35 OutA Net FltState 53 DrvIn Net IdlState
7 Starter Command 29 Str Net IdlValue 36 OutA Net FltValue 54 DrvIn Net IdlValue
22 Breaker Type 37 OutA Net IdlState
56 Base Enclosure 38 OutA Net IdlValue
57 Base Options 39 OutB Pr FltState
58 Wiring Options 40 OutB Pr FltValue
59 Starter Enclosure 41 OutB Net FltState
60 Starter Options 42 OutB Net FltValue
61 Last Pr Fault 43 OutB Net IdlState
62 Warning Status 44 OutB Net IdlValue
63 Base Trip
Bulletin280E, 281E
Units Only Bulletin 284E Units Only
Starter Display Drive Display Drive Setup Drive Advanced Setup
101 Phase A Current 101 Output Freq 131 Motor NP Volts 151 Digital In 1 Sel 181 DC Brake Level 201 Program Lock
102 Phase B Current 102 Commanded Freq 132 Motor NP Hertz 152 Digital In 2 Sel 182 DB Resistor Sel 205 Comm Loss Action
103 Phase C Current 103 Output Current 133 Motor OL Current 153 Digital In 3 Sel 183 S Curve % 206 Comm Loss Time
104 Average Current 104 Output Voltage 134 Minimum Freq 154 Digital In 4 Sel 184 Boost Select 214 Slip Hertz @ FLA
105 Therm Utilized 105 DC Bus Voltage 135 Maximum Freq 155 Relay Out Sel 185 Start Boost 217 Bus Reg Mode
106 Drive Status 136 Start Source 156 Relay Out Level 186 Brake Voltage 218 Current Limit 2
Starter Setup 107 Fault 1 Code 137 Stop Mode 167 Accel Time 2 187 Brake Frequency 219 Skip Frequency
108 Fault 2 Code 138 Speed Reference 168 Decel Time 2 188 Maximum Voltage 220 Skip Freq Band
106 FLA Setting 109 Fault 3 Code 139 Accel Time 1 169 Internal Freq 189 Current Limit 1 221 Stall Fault Time
107 Overload Class 110 Process Display 140 Decel Time 1 170 Preset Freq 0 190 Motor OL Select 224 Var PWM Disable
108 OL Reset Level 112 Control Source 141 Reset To Defaults 171 Preset Freq 1 191 PWM Frequency 225 Torque Perf Mode
113 Contrl In Status 143 Motor OL Ret 172 Preset Freq 2 192 Auto Rstrt Tries 226 Motor NP FLA
114 Dig In Status 173 Preset Freq 3 193 Auto Rstrt Delay 227 Autotune
115 Comm Status 174 Preset Freq 4 194 Start At PowerUp 228 IR Voltage Drop
116 Control SW Ver 175 Preset Freq 5 195 Reverse Disable 229 Flux Current Ref
117 Drive Type 176 Preset Freq 6 196 Flying Start En 260 EM Brk OFF Delay
118 Elapsed Run Time 177 Preset Freq 7 197 Compensation 261 EM Brk On Delay
122 Output Power 178 Jog Frequency 198 SW Current Trip 262 MOP Reset Sel
123 Output Power Fctr 179 Jog Accel/Decel 199 Process Factor 263 DB Threshold
124 Drive Temp 180 DC Brake Time 200 Fault Clear 264 Comm Write Mode
125 Counter Status
126 Timer Status
129 Torque Current
Parameter Programming
Each Distributed Motor Controller type has a common set of parameters
followed by a set of parameters that pertain to the individual starter type.
Parameters 1…100 are common to all ArmorStart devices.
IMPORTANT Parameter setting changes take effect immediately unless otherwise noted in the
parameter listing. These changes maybe immediate even during the "running" status.
Bit
Function
3 2 1 0
— — — X In0
— — X — In1
— X — — In2
X — — — In3
Bit
Function
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
— — — — — — — — — — — — — — — X Pt00DeviceIn
— — — — — — — — — — — — — — X — Pt01DeviceIn
— — — — — — — — — — — — — X — — Pt02DeviceIn
— — — — — — — — — — — — X — — — Pt03DeviceIn
— — — — — — — — — — — X — — — — Pt04DeviceIn
— — — — — — — — — — X — — — — — Pt05DeviceIn
— — — — — — — — — X — — — — — — Pt06DeviceIn
— — — — — — — — X — — — — — — — Pt07DeviceIn
— — — — — — — X — — — — — — — — Pt08DeviceIn
— — — — — — X — — — — — — — — — Pt09DeviceIn
— — — — — X — — — — — — — — — — Pt10DeviceIn
— — — — X — — — — — — — — — — — Pt11DeviceIn
— — — X — — — — — — — — — — — — Pt12DeviceIn
— — X — — — — — — — — — — — — — Pt13DeviceIn
— X — — — — — — — — — — — — — — Pt14DeviceIn
X — — — — — — — — — — — — — — — Pt15DeviceIn
Bit
Function
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
— — — — — — — — — — — — — — — X Pt00DeviceOut
— — — — — — — — — — — — — — X — Pt01DeviceOut
— — — — — — — — — — — — — X — — Pt02DeviceOut
— — — — — — — — — — — — X — — — Pt03DeviceOut
— — — — — — — — — — — X — — — — Pt04DeviceOut
— — — — — — — — — — X — — — — — Pt05DeviceOut
— — — — — — — — — X — — — — — — Pt06DeviceOut
— — — — — — — — X — — — — — — — Pt07DeviceOut
— — — — — — — X — — — — — — — — Pt08DeviceOut
— — — — — — X — — — — — — — — — Pt09DeviceOut
— — — — — X — — — — — — — — — — Pt10DeviceOut
— — — — X — — — — — — — — — — — Pt11DeviceOut
— — — X — — — — — — — — — — — — Pt12DeviceOut
— — X — — — — — — — — — — — — — Pt13DeviceOut
— X — — — — — — — — — — — — — — Pt14DeviceOut
X — — — — — — — — — — — — — — — Reserved
Bit
Function
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
— — — — — — — — — — — — — — — X Short Circuit
— — — — — — — — — — — — — — X — Overload
— — — — — — — — — — — — — X — — Phase Loss
— — — — — — — — — — — — X — — — Reserved
— — — — — — — — — — — X — — — — Reserved
— — — — — — — — — — X — — — — — Control Power
— — — — — — — — — X — — — — — — I/O Fault
— — — — — — — — X — — — — — — — Over Temperature
— — — — — — — X — — — — — — — — Phase Imbalance
— — — — — — X — — — — — — — — — A3 Power Loss
— — — — — X — — — — — — — — — — Reserved
— — — — X — — — — — — — — — — — Reserved
— — — X — — — — — — — — — — — — EEprom
— — X — — — — — — — — — — — — — HW Fault
X X — — — — — — — — — — — — — — Reserved
Bit
Function
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
— — — — — — — — — — — — — — — X TripPresent
— — — — — — — — — — — — — — X — WarningPresent
— — — — — — — — — — — — — X — — RunningForward
— — — — — — — — — — — — X — — — RunningReverse
— — — — — — — — — — — X — — — — Ready
— — — — — — — — — — X — — — — — Net Ctl Status
— — — — — — — — — X — — — — — — Reserved
— — — — — — — — X — — — — — — — At Reference
— — — — — — — X — — — — — — — — Reserved
— — — — — — X — — — — — — — — — Reserved
— — — — — X — — — — — — — — — — Reserved
— — — — X — — — — — — — — — — — Keypad Hand Mode
— — — X — — — — — — — — — — — — HOA Status
— — X — — — — — — — — — — — — — DisconnectClosed
X X — — — — — — — — — — — — — — Reserved
Bit
Function:
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
— — — — — — — — — — — — — — — X Explicit Connection
— — — — — — — — — — — — — — X — I/O Connection
— — — — — — — — — — — — — X — — Explicit Fault
— — — — — — — — — — — — X — — — I/O Fault
— — — — — — — — — — — X — — — — I/O Idle
X X X X X X X X X X X — — — — — Reserved
Bit
Function:
7 6 5 4 3 2 1 0
— — — — — — — X Run Fwd
— — — — — — X — Run Rev
— — — — — X — — Fault Reset
— — — — X — — — Reserved
— — — X — — — — Reserved
— — X — — — — — Reserved
— X — — — — — — OutA
X — — — — — — — OutB
Last PR Fault
Parameter Number 61
0 = None
1 = Hardware Short Circuit
2 = Software Short Circuit
3 = Motor Overload Access Rule GET
4 = Reserved
5 = Phase Loss
6…12 = Reserved
13 = Control Power Loss Data Type UINT
14 = Control Power Fuse
15 = I/O Short
16 = Output Fuse
17 = Overtemp Group Basic Status
18 = Reserved
19 = Phase Imbalance
20 = Reserved
21 = A3 Power Loss Units —
22 = Internal Comm
23…26 = Reserved
27 = MCB EEPROM
28 = Base EEPROM Minimum Value 0
29 = Reserved
30 = Wrong Base
31 = Wrong CTs
32…100 = Reserved Maximum Value 100
Default Value 0
Warnings are always enabled. The warning conditions are reported even if the
corresponding fault conditions are disabled.
Warning bits in the Warning Status parameter are cleared automatically when the
warning condition is no longer present.
Bit
Warning
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
— — — — — — — — — — — — — — — X Reserved
— — — — — — — — — — — — — — X — Reserved
— — — — — — — — — — — — — X — — Phase Loss
— — — — — — — — — — — — X — — — Reserved
— — — — — — — — — — — X — — — — Reserved
— — — — — — — — — — X — — — — — Control Power
— — — — — — — — — X — — — — — — I/O Warning
— — — — — — — — X — — — — — — — Reserved
— — — — — — — X — — — — — — — — Phase Imbalance
— — — — — — X — — — — — — — — — A3 Power Loss
— — — — — X — — — — — — — — — — Reserved
— — — — X — — — — — — — — — — — Reserved
— — — X — — — — — — — — — — — — Reserved
— — X — — — — — — — — — — — — — Hardware
X X — — — — — — — — — — — — — — Reserved
Bit
Warning
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
— — — — — — — — — — — — — — — X EEPROM Fault
— — — — — — — — — — — — — — X — Internal Comm
— — — — — — — — — — — — — X — — Hardware Fault
— — — — — — — — — — — — X — — — Control Module
X X X X X X X X X X X X — — — — Reserved
Bit
Function
13 12 11 10 9 8 7 6 5 4 3 2 1 0
— — — — — — — — — — — — — X Short Circuit ➊
— — — — — — — — — — — — X — Overload ➊
— — — — — — — — — — — X — — Phase Loss
— — — — — — — — — — X — — — Reserved
— — — — — — — — — X — — — — Reserved
— — — — — — — — X — — — — — Control Power
— — — — — — — X — — — — — — I/O Fault
— — — — — — X — — — — — — — Over Temperature ➊
— — — — — X — — — — — — — — Phase Imbalance
— — — — X — — — — — — — — — A3 Power Loss
— — — X — — — — — — — — — — Reserved
— — X — — — — — — — — — — — Reserved
— X — — — — — — — — — — — — EEprom ➊
X — — — — — — — — — — — — — HW Fault ➊
➊ Cannot be disabled
This parameter allows for the local logic to Access Rule GET/SET
override a Network fault. Data Type BOOL
0 = Disable
1 = Enable Group Misc. Config.
Units —
Minimum Value 0
Maximum Value 1
Default Value 0
This parameter if set to “1” will set the Access Rule GET/SET
device to the factory defaults (but will not Data Type BOOL
cause the ArmorStart to reboot).
0 = No Operation Group Misc. Config.
1 = Set to Defaults
Units —
Minimum Value 0
Maximum Value 1
Default Value 0
Table 23 - FLA Setting Ranges and Default Values (with indicated setting precision)
FLA Current Range (A)
Default Value
Minimum Value Maximum Value
0.24 1.2 0.24
0.5 2.5 0.5
1.1 5.5 1.1
3.2 16.0 3.2
Bit
Function
3 2 1 0
— — — X In0
— — X — In1
— X — — In2
X — — — In3
Bit
Function
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
— — — — — — — — — — — — — — — X Pt00DeviceIn
— — — — — — — — — — — — — — X — Pt01DeviceIn
— — — — — — — — — — — — — X — — Pt02DeviceIn
— — — — — — — — — — — — X — — — Pt03DeviceIn
— — — — — — — — — — — X — — — — Pt04DeviceIn
— — — — — — — — — — X — — — — — Pt05DeviceIn
— — — — — — — — — X — — — — — — Pt06DeviceIn
— — — — — — — — X — — — — — — — Pt07DeviceIn
— — — — — — — X — — — — — — — — Pt08DeviceIn
— — — — — — X — — — — — — — — — Pt09DeviceIn
— — — — — X — — — — — — — — — — Pt10DeviceIn
— — — — X — — — — — — — — — — — Pt11DeviceIn
— — — X — — — — — — — — — — — — Pt12DeviceIn
— — X — — — — — — — — — — — — — Pt13DeviceIn
— X — — — — — — — — — — — — — — Pt14DeviceIn
X — — — — — — — — — — — — — — — Pt15DeviceIn
Bit
Function
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
— — — — — — — — — — — — — — — X Pt00DeviceOut
— — — — — — — — — — — — — — X — Pt01DeviceOut
— — — — — — — — — — — — — X — — Pt02DeviceOut
— — — — — — — — — — — — X — — — Pt03DeviceOut
— — — — — — — — — — — X — — — — Pt04DeviceOut
— — — — — — — — — — X — — — — — Pt05DeviceOut
— — — — — — — — — X — — — — — — Pt06DeviceOut
— — — — — — — — X — — — — — — — Pt07DeviceOut
— — — — — — — X — — — — — — — — Pt08DeviceOut
— — — — — — X — — — — — — — — — Pt09DeviceOut
— — — — — X — — — — — — — — — — Pt10DeviceOut
— — — — X — — — — — — — — — — — Pt11DeviceOut
— — — X — — — — — — — — — — — — Pt12DeviceOut
— — X — — — — — — — — — — — — — Pt13DeviceOut
— X — — — — — — — — — — — — — — Pt14DeviceOut
X — — — — — — — — — — — — — — — Reserved
Bit
Function
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
— — — — — — — — — — — — — — — X Short Circuit
— — — — — — — — — — — — — — X — Overload
— — — — — — — — — — — — — X — — Phase Short
— — — — — — — — — — — — X — — — Ground Fault
— — — — — — — — — — — X — — — — Stall
— — — — — — — — — — X — — — — — Control Power
— — — — — — — — — X — — — — — — I/O Fault
— — — — — — — — X — — — — — — — Over Temperature
— — — — — — — X — — — — — — — — Over Current
— — — — — — X — — — — — — — — — A3 Power Loss
— — — — — X — — — — — — — — — — Internal Comm ➊
— — — — X — — — — — — — — — — — DC Bus Fault
— — — X — — — — — — — — — — — — EEprom
— — X — — — — — — — — — — — — — HW Fault ➊
— X — — — — — — — — — — — — — — Restart Retries
X — — — — — — — — — — — — — — — Misc. Fault ➊
Bit
Function
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
— — — — — — — — — — — — — — — X TripPresent
— — — — — — — — — — — — — — X — WarningPresent
— — — — — — — — — — — — — X — — RunningForward
— — — — — — — — — — — — X — — — RunningReverse
— — — — — — — — — — — X — — — — Ready
— — — — — — — — — — X — — — — — Net Ctl Status
— — — — — — — — — X — — — — — — Net Ref Status
— — — — — — — — X — — — — — — — At Reference
— — — — — — — X — — — — — — — — DrvOpto1
— — — — — — X — — — — — — — — — DrvOpto2
— — — — — X — — — — — — — — — — Keypad Jog
— — — — X — — — — — — — — — — — Keypad Hand
— — — X — — — — — — — — — — — — HOA Status
— — X — — — — — — — — — — — — — Disconnect Closed
— X — — — — — — — — — — — — — — Contactor 1 ➊
X — — — — — — — — — — — — — — — Contactor 2 ➋
Bit
Function:
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
— — — — — — — — — — — — — — — X Explicit Connection
— — — — — — — — — — — — — — X — I/O Connection
— — — — — — — — — — — — — X — — Explicit Fault
— — — — — — — — — — — — X — — — I/O Fault
— — — — — — — — — — — X — — — — I/O Idle
X X X X X X X X X X X — — — — — Reserved
Bit
Function:
7 6 5 4 3 2 1 0
— — — — — — — X Run Fwd
— — — — — — X — Run Rev
— — — — — X — — Fault Reset
— — — — X — — — Jog Fwd
— — — X — — — — Jog Rev
— — X — — — — — Reserved
— X — — — — — — OutA
X — — — — — — — OutB
Last PR Fault
Default Value 0
Bit
Warning ➊
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
— — — — — — — — — — — — — — — X Reserved
— — — — — — — — — — — — — — X — Reserved
— — — — — — — — — — — — — X — — Phase Loss
— — — — — — — — — — — — X — — — Reserved
— — — — — — — — — — — X — — — — Reserved
— — — — — — — — — — X — — — — — Control Power
— — — — — — — — — X — — — — — — I/O Warning
— — — — — — — — X — — — — — — — Reserved
— — — — — — — X — — — — — — — — Phase Imbalance
— — — — — — X — — — — — — — — — A3 Power Loss
— — — — — X — — — — — — — — — — Reserved
— — — — X — — — — — — — — — — — Reserved
— — — X — — — — — — — — — — — — Reserved
— — X — — — — — — — — — — — — — Hardware
— X — — — — — — — — — — — — — — Reserved
X — — — — — — — — — — — — — — — Miscellaneous ➋
➊ The warning is triggered simultaneously, the fault is generated. If the fault is disabled a warning will still occur.
➋ Includes DB1 Thermal Warning
Bit
Warning
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
— — — — — — — — — — — — — — — X EEPROM Fault
— — — — — — — — — — — — — — X — Internal Comm
— — — — — — — — — — — — — X — — Hardware Fault
— — — — — — — — — — — — X — — — Control Module
X X X X X X X X X X X X — — — — Reserved
➊ When “Pr FltReset Mode” is set to 0=manual mode, and Parameter 192 (Auto Rstrt Tries) is set to allow the drive faults to auto-
reset, the “Pr FltReset Mode” takes precedence. In this case, the ArmorStart will remain faulted until the fault is manually cleared.
Bit
Function
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
— — — — — — — — — — — — — — — X Short Circuit ➊
— — — — — — — — — — — — — — X — Overload ➊
— — — — — — — — — — — — — X — — Phase Loss ➊
— — — — — — — — — — — — X — — — Ground Fault ➊
— — — — — — — — — — — X — — — — Stall ➊
— — — — — — — — — — X — — — — — Control Power
— — — — — — — — — X — — — — — — I/O Fault
— — — — — — — — X — — — — — — — Over Temperature ➊
— — — — — — — X — — — — — — — — Over Current ➊
— — — — — — X — — — — — — — — — A3 Power Loss
— — — — — X — — — — — — — — — — Internal Comm ➊
— — — — X — — — — — — — — — — — DC Bus Fault ➊
— — — X — — — — — — — — — — — — EEprom ➊
— — X — — — — — — — — — — — — — HW Fault ➊
— X — — — — — — — — — — — — — — Restart Retries ➊
X — — — — — — — — — — — — — — — Misc. Fault ➊
➊ Cannot be disabled
This parameter allows for the local logic to Access Rule GET/SET
override a Network fault. Data Type BOOL
0 = Disable
1 = Enable Group Misc. Config.
Units —
Minimum Value 0
Maximum Value 1
Default Value 0
This parameter if set to “1” will set the Access Rule GET/SET
device to the factory defaults (but will not Data Type BOOL
cause the ArmorStart to reboot).
0 = No Operation Group Misc. Config.
1 = Set to Defaults
Units —
Minimum Value 0
Maximum Value 1
Default Value 0
Bit
Function
11 10 9 8 7 6 5 4 3 2 1 0
— — — — — — — — — — — X Accel 1 En
— — — — — — — — — — X — Accel 2 En
— — — — — — — — — X — — Decel 1 En
— — — — — — — — X — — — Decel 2 En
— — — — — — — X — — — — Freq Sel 0
— — — — — — X — — — — — Freq Sel 1
— — — — — X — — — — — — Freq Sel 2
— — — — X — — — — — — — Reserved
— — — X — — — — — — — — Drv In 1
— — X — — — — — — — — — Drv In 2
— X — — — — — — — — — — Drv In 3
X — — — — — — — — — — — Drv In 4
Default Value 0
Output frequency present at T1, T2, T3. Related Parameters 102, 110, 134, 135, 138
Access Rule GET
Data Type UINT
Group Drive Display
Units 0.1 Hz
Minimum Value 0.0
Maximum Value 400.0 Hz
Default Value Read Only
Value of the active frequency command. Related Parameters 101, 113, 134, 135, 138
Displays the commanded frequency even Access Rule GET
if the drive is not running.
Data Type UINT
Group Drive Display
Units 0.1 Hz
Minimum Value 0.0
Maximum Value 400.0 Hz
Default Value Read Only
Output Voltage present at T1, T2, T3. Related Parameters 131, 184, 188
Access Rule GET
Data Type UINT
Group Drive Display
Units 1V AC
Minimum Value 0
Maximum Value 480V
Default Value Read Only
A code that represents the drive fault. The Access Rule GET
code appears in this parameter as the Data Type UINT
most recent fault that has occurred. (See
Internal Drive Faults in Chapter 10 for Group Drive Display
more information).
Units —
Minimum Value F2
Maximum Value F122
Default Value Read Only
The output frequency that is scaled by the Related Parameter 101. 199
process factor (Parameter 199). Access Rule GET
Data Type UINT
Group Drive Display
Units —
Minimum Value 0.00
Maximum Value 9999
Default Value Read Only
Displays the source of the Start Command 136, 138, 151…154 (Digital In x
and Speed Reference. Sel) must be set to Option 4, 169,
Related Parameters
1 = Internal Frequency 170…177 (Preset Freq x),
4 = Preset Freq x 240…247 (StpLogic x)
5 = Network Control Access Rule GET
9 = Jog Freq
Data Type UINT
Group Drive Display
Units 1
Minimum Value 0
Maximum Value 9
Default Value Read Only
Status of control inputs. These can be used Related Parameter 102, 134, 135
in DeviceLogix. Access Rule GET
Bit 0 = Start/Run FWD Input
Bit 1 = Direction/Run REV Input Data Type UINT
Bit 2 = Stop Input
Bit 3 = Dynamic Brake Transistor On Group Drive Display
Units 1
Minimum Value 0
Maximum Value 1
Default Value Read Only
The output power present at T1, T2, and Access Rule GET
T3. Data Type UINT
Group
Drive Display
Units
Minimum Value 0.00
Maximum Value Drive rated power X 2
Default Value Read Only
The current value of the timer when timer Access Rule GET
is enabled. Data Type UINT
Group Drive Display
Units 0.1 sec
Minimum Value 0
Maximum Value 9999
Default Value Read Only
Set to the maximum allowable current. 155, 189, 190, 198, 214, 218,
Related Parameter
The drive fault on an F7 260…261
Motor Over load if the value of this Access Rule GET/SET
parameter is exceeded by 150%
for 60 s. Data Type UINT
Group Drive Setup
Units 0.1 A
Minimum Value 0.0
Maximum Value Drive rated amps x 2
Default Value Based on Drive Rating
Sets the lowest frequency that the drive 101, 102, 113, 135, 185…187,
Related Parameter
will output continuously. 260, 261
Access Rule GET/SET
Data Type UINT
Group Drive Setup
Units 0.1 Hz
Minimum Value 0.0
Maximum Value 400
Default Value 0.0
Stop Mode
Parameter Number 137
Valid Stop Mode for the Bulletin 284E ArmorStart are the following:
0 = Ramp, CF Ramp to Stop. Stop command clears active fault. Related Parameters 136, 180…182, 205, 260, 261 ➊
1 = Coast, CF Coast to Stop. Stop command clears active fault.
2 = DC Brake,CF DC Injection Braking Stop. Stop command clears active fault.
3 = DCBrkAuto, CF DC injection Braking with Auto Shutoff. Access Rule GET/SET
Standard DC Injection Braking for value set in Parameter 180 (DC Brake Time) or
Drive shuts off if the drive detects that the motor is stopped. Stop command clears
active fault. Data Type UINT
4 = Ramp, Ramp to Stop
5 = Coast, Coast to Stop Group Drive Setup
6 = DC Brake, DC Injection Braking Stop
7 = DC BrakeAuto, DC Injection Stop with Auto Shutoff
Standard DC Injection Braking for value set in Parameter 180 (DC Brake Time) Units —
or
Drive shuts off if current limit is exceeded.
8 = Ramp + EM B, CF Ramp to Stop with EM Brake Control. Stop command clears Minimum Value 0
active fault. ➊
9 = Ramp + EM Brk Ramp to Stop with EM Brake Control. ➊
Maximum Value 9
Default Value 9
Valid Speed References for the Bulletin 101, 102, 112, 139, 140,
284E ArmorStart are the following: Related Parameters 151…154, 169, 170…177, 232,
1 = Internal Freq 240…247, and 250…257
4 = Preset Freq Access Rule GET/SET
5 = Comm Port
9 = Jog Freq Data Type UINT
Group Drive Setup
Units —
Minimum Value 0
Maximum Value 7
Default Value 5
Sets the rate of acceleration for all speed 138, 140, 151…154, 167,
Related Parameters
increases. 170…177, and 240…247
Maximum Freq- = Accel Rate
-------------------------------------
Access Rule GET/SET
Accel Time Data Type UINT
Group Drive Setup
Units 0.1 sec
Minimum Value 0.0 sec
Maximum Value 600.0 sec
Default Value 10.0 sec
Sets the rate of deceleration for all speed 138, 139, 151…154, 168,
Related Parameters
decreases. 170…177, and 240…247
Maximum Freq- = Decel Rate
-------------------------------------
Access Rule GET/SET
Decel Time Data Type UINT
Group Drive Setup
Units 0.1 sec
Minimum Value 0.1 sec
Maximum Value 600.0 sec
Default Value 10.0 sec
Sets the condition that changes the state Related Parameters 133, 156, 192, 240…247,
of the output relay contacts. 250…257, 260, 261
Access Rule GET/SET
Data Type UINT
Group Drive Advanced Setup
Units —
Minimum Value 0
Maximum Value 22
Default Value 22
➊ The customer is responsible to make sure the brake release function operates properly and safely.
18 1/180°
Maximum Value 9999
20 0/1
Default Value 0.0
When active, sets the rate of acceleration for all speed increases except for jog. 139, 151…154, 170…177,
Related Parameters 240…247
Maximum Freq- = Accel Rate
-------------------------------------
Accel Time Access Rule GET/SET
Parameter 135
Data Type UINT
(Maximum Freq) Group Drive Advanced Setup
Dec
n
atio
eler
Units 0.1 sec
eler
atio
Speed
Acc
n
Minimum Value 0.0
0
Param. Time Param. Maximum Value 600.0
0 139 or 140 or
167 168
(Accel (Decel Default Value 20.0
Time x) Time x)
When active, sets the rate of deceleration for all speed decreases except for jog. 140, 151…154, 170…177,
Related Parameters 240…247
Maximum Freq- = Decel Rate
-------------------------------------
Decel Time Access Rule GET/SET
eler
atio
Speed
Acc
Input State of Digital In 1 (I/ Input State of Digital In 2 (I/ Input State of Digital In 3 (I/ Accel/Decel
O Terminal 05 when O Terminal 06 when O Terminal 07 when Frequency Parameter
Parameter 151 = 4) Parameter 152 = 4) Parameter 153 = 4) Source Used ➊
0 0 0 170 (Preset Freq 0) (Accel Time 1)/(Decel Time 1)
1 0 0 171 (Preset Freq 1) (Accel Time 1)/(Decel Time 1)
0 1 0 172 (Preset Freq 2) (Accel Time 2)/(Decel Time 2)
1 1 0 173 (Preset Freq 3) (Accel Time 2)/(Decel Time 2)
0 0 1 174 (Preset Freq 4) (Accel Time 3)/(Decel Time 3)
Input State of Digital In 1 (I/ Input State of Digital In 2 (I/ Input State of Digital In 3 (I/ Accel/Decel
O Terminal 05 when O Terminal 06 when O Terminal 07 when Frequency Parameter
Parameter 151 = 4) Parameter 152 = 4) Parameter 153 = 4) Source Used ➋
1 0 1 175 (Preset Freq 5) (Accel Time 3)/(Decel Time 3)
0 1 1 176 (Preset Freq 6) (Accel Time 4)/(Decel Time 4)
1 1 1 177 (Preset Freq 7) (Accel Time 4)/(Decel Time 4)
➊ When a Digital Input is set to "Accel 2 & Decel 2", and the input is active, that input overrides the settings in this table.
Sets the output frequency when the jog Related Parameters 135, 151…154, 179
command is issued. Access Rule GET/SET
Data Type UINT
Group Drive Advanced Setup
Units 0.1 Hz
Minimum Value 0.0
Maximum Value 400.0
Default Value 10.0
Sets the length of time that DC brake Related Parameters 137, 181
current is injected into the motor. See Access Rule GET/SET
Parameter 181 (DC Brake Level).
Data Type UINT
Group Drive Advanced Setup
Units 0.1 sec
Minimum Value 0.0
99.9
Maximum Value (Setting of 99.9 = Continuous)
Default Value 0.0
ATTENTION:
Ramp-to-Stop Mode DC Injection Braking Mode
Voltage
Volts Speed
Volts Speed
Vo [DC Brake Time]
lta Speed
}
ge [DC Brake Time]
Spe
}
ed
Time Time
Stop Command Stop Command
Figure 76 - S Curve
Sets the boost voltage (% of Parameter Related Parameters 104, 131, 132, 185…187, 225
131 (Motor NP Volts)) and redefines the Access Rule GET/SET
Volts per Hz curve. Active when Parameter
225 (Torque Perf Mode) = 0 (V/Hz). Drive Data Type UINT
may add additional voltage unless Option
5 is selected. Group Drive Advanced Setup
➊To activate 170 (Preset Freq 0) set 138 (Speed Reference) to "4" (Preset Freq).
➋When a Digital Input is set to "Accel 2 & Decel 2", and the input is active, that input overrides the settings in this table.
[Motor NP Hertz]
1/2
Settings
5-14
0 50 100
% P132 [Motor NP Hertz]
Sets the boost voltage (% of Parameter 131, 132, 134, 135, 184,
Related Parameters
131 (Motor NP Volts)) and redefines the 186…188, 225
Volts per Hz curve when Parameter 184 Access Rule GET/SET
(Boost Select) = 0 (Custom V/Hz) and
Parameter 225 (Torque Perf Mode) = 0 (V/ Data Type UINT
Hz)
Group Drive Advanced Setup
Units 1.1%
Minimum Value 0.0%
Maximum Value 25.0%
Default Value 2.5%
Voltage
Parameter 186 (Break Voltage)
Parameter 186
(Start Boost)
Parameter 187 (Break Frequency) Parameter 132 (Motor NP Hertz)
Parameter 134 (Minimum Freq) Frequency Parameter 135 (Maximum Freq)
Sets the frequency where brake voltage is 131, 132, 134, 135, 184, 185, 187,
Related Parameters
applied when Parameter 184 (Boost 188, 225
Select) = 0 (Custom V/Hz) and Parameter Access Rule GET/SET
225 (Torque Perf Mode) = 0 (V/Hz).
Data Type UINT
Group Drive Advanced Setup
Units 1.1%
Minimum Value 0.0%
Maximum Value 100.0%
Default Value 25.0%
Sets the frequency where brake frequency 131, 132, 134, 135, 184, 185, 186,
Related Parameters
is applied when Parameter 184 (Boost 188, 225
Select) = 0 (Custom V/Hz) and Parameter Access Rule GET/SET
225 (Torque Perf Mode) = 0 (V/Hz).
Data Type UINT
Group Drive Advanced Setup
Units 0.1 Hz
Minimum Value 0.0 Hz
Maximum Value 400.0 Hz
Default Value 15.0 Hz
Sets the highest voltage that the drive will Related Parameters 104, 185, 186, 187
output. Access Rule GET/SET
Data Type UINT
Group Drive Advanced Setup
Units 1V AC
Minimum Value 20V AC
Maximum Value Drive Rated Volts
Default Value Drive Rated Volts
80 80 80
60 60 60
40 40 40
20 20 20
0 0 0
0 25 50 75 100 125 150 175 200 0 25 50 75 100 125 150 175 200 0 25 50 75 100 125 150 175 200
% of P132 [Motor NP Hertz] % of P132 [Motor NP Hertz] % of P132 [Motor NP Hertz]
Sets the carrier frequency for the PWM Related Parameters 224
output waveform. The Figure 80 provides Access Rule GET/SET
derating guidelines that are based on the
PWM frequency setting. Data Type UINT
Group Drive Advanced Setup
Units 0.l Hz
Minimum Value 2.0 Hz
Maximum Value 16.0 Hz
Default Value 4.0 Hz
Figure 80 - Derating Guidelines that are Based on the PWM Frequency Setting
100
96
92
88
% Output Current (A)
84
80
76
72
68
64
60
56
52
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
Carrier Frequency (kHz)
Set the maximum number of times the Related Parameter 155, 193
drive attempts to reset a fault and restart. Access Rule GET/SET
Data Type UINT
Group Drive Advanced Setup
Units 1
Minimum Value 0
Maximum Value 9
Default Value 0
ATTENTION: Equipment damage and/or personal injury may result if this parameter is
used in an inappropriate application. Do not use this function without considering
applicable local, national, and international codes, standards, regulations, or industry
guidelines.
ATTENTION: Equipment damage and/or personal injury may result Group Drive Advanced Setup
if this parameter is used in an inappropriate application. Do not use
this function without considering applicable local, national, and Units —
international codes, standards, regulations, or industry guidelines.
Minimum Value 0
Maximum Value 1
Default Value 0
Sets the condition that allows the drive to Access Rule GET/SET
reconnect to a spinning motor at actual Data Type UINT
RPM.
0 = Disabled Group Drive Advanced Setup
1 = Enabled
Units —
Minimum Value 0
Maximum Value 1
Default Value 0
Compensation
Parameter Number 197
Enables/disables correction options that
may improve problems with motor Access Rule GET/SET
instability,
0 = Disabled
1 = Electrical (Default) Data Type UINT
Some drive/motor combinations have
inherent instabilities that are exhibited as
non-sinusoidal motor currents. This Group Drive Advanced Setup
setting attempts to correct this condition
2 = Mechanical Units —
Some motor/load combinations have
mechanical resonances that can be excited
by the drive current regulator. This setting Minimum Value 0
slows down the current regulator response
and attempts to correct this condition.
3 = Both Maximum Value 3
Default Value 1
Default Value 0
Sets the time that the drive remains in Related Parameters 115, 205
communication loss before implanting the Access Rule GET/SET
option selected in Parameter 205 (Comm
Loss Action). Data Type UINT
Group Advanced Program Group
Units 0.1 sec
Minimum Value 0.1 sec
Maximum Value 60.0 sec
Default Value 15.0 sec
Scales the time value when the drive is Related Parameters 110, 134
running at Parameter 134 (Minimum Access Rule GET/SET
Freq). When set to a value other than zero,
Parameter 110 (Process Display) indicates Data Type UINT
the duration of the process.
Group Drive Advanced Setup
Units Hz
Minimum Value 0.00
Maximum Value 99.99
Default Value 0.00
Scales the time value when the drive is Related Parameters 110, 135
running at Parameter 135 (Maximum Access Rule GET/SET
Freq). When set to a value other than zero,
Parameter 110 (Process Display) indicates Data Type UINT
the duration of the process.
Group Drive Advanced Setup
Units Hz
Minimum Value 0.0
Maximum Value 99.99
Default Value 0.00
Maximum output current that is allowed Related Parameters 133, 151…154, 189
before current limiting occurs. This Access Rule GET/SET
parameter is only active if Parameters
151…154 (Digital In x Sel) is set to Option Data Type UINT
25 (Current Lmt2) and is active.
Group Drive Advanced Setup
Units 0.1 A
Minimum Value 0.0 A
Maximum Value Drive rated amps x 1.8
Default Value Drive rated amps x 1.5
Sets the frequency at which the drive will Related Parameters 220
not operate. Access Rule GET/SET
Data Type UINT
Group Drive Advanced Setup
Units 0.1 Hz
Minimum Value 0.0
Maximum Value 400.0 Hz
Default Value 0.0 Hz
Frequency Command
Frequency
Drive Output
Frequency
2x Skip
Skip Frequency Frequency Band
Time
Sets for the fault time that the drive will Access Rule GET/SET
remain in stall mode before a fault is Data Type UINT
issued.
0 = 60 sec (Default) Group Drive Advanced Setup
1 = 120 sec
2 = 240 sec Units —
3 = 360 sec
4 = 480 sec Minimum Value 0
5 = Flt Disabled Maximum Value 5
Default Value 0
Autotune
Parameter Number 227
Stop drive before changing this parameter.
Provides an automatic method for setting Parameter 228 (IR Voltage Drop) and Parameter 229 (Flux Related Parameters 225, 226, 228, 229
Current Ref), that affect sensorless vector performance. Parameter 226 (Motor NP FLA) must be set to
the motor nameplate full load amps before running the Autotune procedure.
0 = Ready/Idle (Default)
1 = Static Tune Access Rule GET/SET
2 = Rotate Tune
Ready (0) – Parameter returns to this setting following a Static Tune or Rotate Tune.
Static Tune (1) – A temporary command that initiates a non-rotational motor stator resistance test Data Type UINT
for the best possible automatic setting of Parameter 228 (IR Voltage Drop). A start command is
required within 30 seconds of setting this parameter following initiation of this setting. The
parameter returns to Ready (0) following the test, at which time another start transition is required to Group Drive Advanced Setup
operate the drive in normal mode. Used when motor cannot be uncoupled from the load.
Rotate Tune (2) – A temporary command that initiates a Static Tune followed by a rotational test for
the best possible automatic setting of Parameter 229 (Flux Current Ref). A start command is required Units —
following initiation of this setting. The parameter returns to Ready (0) following the test, at which
time another start transition is required to operate the drive in normal mode.
Minimum Value 0
Maximum Value 3
Default Value 0
IMPORTANT Used when motor is uncoupled from the load. Results may not be valid if a load is
coupled to the motor during this procedure. Applies to rotate tune only.
ATTENTION: Rotation of the motor in an undesired direction can occur during this
procedure. To guard against possible injury and/or equipment damage, it is
recommended that the motor be disconnected from the load before proceeding.
Sets the time that the drive will remain at Related Parameters 134, 137
minimum frequency before ramping to Access Rule GET/SET
the commanded frequency and energizing
the brake coil relay when Parameter 137 Data Type UNIT
(Stop Mode) is set to Option 8 or 9.
Group Drive Advanced Setup
Units 0.01 sec
Minimum Value 0.01 sec
Maximum Value 10 sec
Default Value 0.0 sec
Frequency
260 [EM Brk Off Delay] Ram 261 [EM Brk On Delay]
l
cce
pD
pA
ece
l
Ram
Minimum Freq
Time
Start EM Brk Stop EM Brk Drive Stops
Commanded Energized (Off) Commanded De-Energized (On)
Sets the time that the drive will remain at Related Parameters 134, 137
minimum frequency before stopping and Access Rule GET/SET
de-energizing the brake coil relay when
Parameter 137 (Stop Mode) is set to Data Type UNIT
Option 8 or 9.
Group Drive Advanced Setup
Units 0.01 sec
Minimum Value 0.01 sec
Maximum Value 10.00 sec
Default Value 0.0 sec
Sets the drive to save the current MOP Related Parameters 169
Reference command. Access Rule Get/Set
0 = Zero MOP Ref
This option clamps Parameter 169 Data Type UINT
(Internal Freq) at 0.0 Hz when drive is not
running. Group Drive Advanced Setup
1 = Save MOP Ref (Default)
Reference is saved in Parameter 169 Units —
(Internal Freq). Minimum Value 0
Maximum Value 1
Default Value 1
ATTENTION: Equipment damage may result if this parameter is set to a value that
causes the dynamic braking resistor to dissipate excessive power. Parameter settings
less than 100% should be carefully evaluated to ensure that the dynamic brake
resistor’s wattage rating is not exceeded. In general, values less than 90% are not
needed. This parameter’s setting is especially important if Parameter 182 (DB Resistor
Sel) is set to “2” (No Protection).
110 Process Display The output frequency that is scaled by Parameter 199 Read Only Drive Display 284E
(Process Factor).
Displays the source of the Start Command and Speed 5=
112 Control Source Drive Display 284E
Reference. RS485 (DSI) Port
113 Control In Status of control inputs. These can be used in DeviceLogix Read Only Drive Display 284E
114 Dig In Status Status of the control terminal block digital inputs. 0 Drive Display 284E
115 Comm Status Status of the communications ports 0 Drive Display 284E
116 Control SW Ver Main Control Board software version for AC Drive. Read Only Drive Display 284E
118 Elapsed Run Time Accumulated time drive is outputting power. Read Only Drive Display 284E
122 Output Power Output power present at T1, T2 & T3 (U, V & W). Read Only Drive Display 284E
The angle in electrical degrees between motor voltage and
123 Output Power Fctr Read Only Drive Display 284E
motor current.
A tag name must be given to the MSG function before the rest of the information
can be defined. In this example, a tag was created with the name explicit_mess.
After the instruction has been named, click the gray box to define the rest of
the instruction.
Formatting an Explicit ControlLogix scanners and bridges accommodate both downloading Explicit
Message Requests and uploading Explicit Message Responses. The message
Message format is shown in Figure 84.
Box Description
➊ Message Type
The message type is usually CIP Generic.
➋ Service Type
The service type indicates the service (for example, Get Attribute Single or Set Attribute Single) that you
want to perform.
➌ Service Code
The service code is the code for the requested EtherNet/IP service. This value changes based on the Service
Type that has been selected. In most cases, this is a read-only box.
If you select “Custom” in the Service Type box, then you need to specify a service code in this box (for
example, 4B for a Get Attributes Scattered service or 4C for a Set Attributes Scattered service).
➍ Class
The class is an EtherNet/IP class.
➎ Instance
The instance is an instance (or object) of an EtherNet/IP class.
➏ Attribute
The attribute is a class or instance attribute.
➐ Source Element
This box contains the name of the tag for any service data to be sent from the scanner or bridge to the
module and drive.
Box Description
➑ Source Length
This box contains the number of bytes of service data to be sent in the message.
➒ Destination
This box contains the name of the tag that receives service response data from the module and drive.
➓ Path
The path is the route that the message follow.s
Note: Click Browse to find the path or type in the name of a module that you previously mapped.
Name
The name for the message.
Performing Explicit
Messages IMPORTANT There are five basic events in the Explicit Messaging process that is defined below. The
details of each step vary depending on the controller. See the documentation for your
controller.
Box Description
➊ Format the required data and set up the ladder logic program to send an Explicit Message Request to the
scanner or bridge module (download).
➋ The scanner or bridge module transmits the Explicit Message Request to the slave device over the
EtherNet/IP network.
➌ The slave device transmits the Explicit Message Response back to the scanner. The data is stored in the
scanner buffer.
➍ The controller retrieves the Explicit Message Response from the scanner’s buffer (upload).
The MSG (message) instruction handles all explicit messaging that is initiated by
a Logix Controller program.
The Class, Instance, and Attribute define the actual information being requested.
Additional configurations of these parameters can be found in Chapter B.
Diagnostics
Overview This chapter describes the fault diagnostics of the ArmorStart Distributed Motor
Controller and the conditions that cause various faults to occur.
Protection Programming
Many of the protective features available with the ArmorStart Distributed Motor
Controller can be enabled and adjusted through the programming parameters
provided. For further details on programming, see Chapter 7, Bulletin 280E/
281E/284E Programmable Parameters.
Fault Display The ArmorStart Distributed Motor Controller comes equipped with a built-in
LED status indication that provides four status LEDs and a Reset button.
Clear Fault You may clear a fault using the following methods:
• Locally via the “Reset” button on the LED Status indication keypad.
Fault Codes Table 30 provides a reference of the Fault LED indications for Bulletin 280E,
281E, and Bulletin 284E Distributed Motor Controllers.
Fault Types
Blink Pattern
Bulletin 280E/281E Bulletin 284E
1 Short Circuit Short Circuit
2 Overload Trip Overload Trip
3 Phase Loss Phase Short
4 Reserved Ground Fault
5 Reserved Stall
6 Control Power Control Power
7 I/O Fault I/O Fault
8 Over Temperature Over Temperature
9 Phase Imbalance Over Current
10 A3 Power Loss A3 Power Loss
11 Reserved Internal Communications
12 Reserved DC Bus Fault
13 EEPROM Fault EEPROM Fault
14 Hardware Fault Hardware Fault
15 Reserved Restart Retries
16 Reserved Misc. Fault
Short Circuit indicates that the Bulletin 140M motor protector has tripped, or
that the internal wiring protection algorithm has detected an unsafe current
surge. This fault cannot be disabled.
Overload Trip
The load has drawn excessive current and based on the overload trip class that is
selected, the device has tripped. This fault cannot be disabled.
When using Bulletin 280, 281 with a mechanical motor brake actuator
connected to motor out leads, care must be taken with 1 Hp (0.73 kW) or smaller
loads as the current is elevated in those legs that influence the electronic overload
and may cause nuisance phase imbalance or overload faults. An adjustment to the
full load amps (FLA) setting to offset this additional current may be necessary.
Phase Loss
Indicates a missing supply phase. This fault can be disabled and is disabled by
default.
Phase Short
Indicates the drive has detected a phase short. This fault cannot be disabled.
Ground Fault
Indicates the drive has detected a ground fault. This fault cannot be disabled.
Stall
Indicates the drive has detected a stall condition, indicating the motor has not
reached full speed. This fault cannot be disabled.
Control Power
Indicates a loss of control power voltage or a blown control power circuit. This
fault can be disabled and is disabled by default.
I/O Fault
This error can indicate a shorted sensor, shorted input device, or input wiring
mistakes. It can also indicate a blown output fuse. This fault can be disabled and is
disabled by default.
Over Temperature
Indicates that the operating temperature has been exceeded. This fault cannot be
disabled.
Phase Imbalance
Indicates an imbalance supply voltage. This fault can be disabled and is disabled
by default.
Over Current
Indicates the drive has detected an over current fault. This fault cannot be
disabled.
A3 Power Loss
Power has been lost or has dropped below the 12V threshold. This fault can be
disabled and is disabled by default.
DC Bus Fault
Indicates the drive has detected a DC Bus Fault. This fault cannot be disabled.
This is a major fault, that renders the ArmorStart inoperable. This fault cannot be
disabled.
Hardware Fault
Restart Retries
This fault is generated when the drive detects that the auto retries count has been
exceeded. This fault cannot be disabled.
Miscellaneous Faults
For Bulletin 284E units, this fault is actually the logical of several drive faults not
specifically enumerated. This includes DB1 Brake fault, Heatsink Over
Temperature (fault code F8), Params Defaulted fault (fault code F48), and SVC
Autotune fault (fault code F80).
EtherNet/IP LED Status EtherNet/IP LED status and diagnostics consists of four LEDs.
Indication • Link Activity/Status LEDS
Figure 88 - EtherNet/IP LED
– Link1 Activity/Status (Port 1) – LED Color: Bicolor (Green/Yellow).
see Table 31
See Parameter 63 “Base Trip” for the Base Module Trip Status.
Control Module LED The Control Module LED status and diagnostics consists of four status LEDs
and a Reset button. The following is a brief explanation of the operation of each
Status and Reset LED found on the Control Module.
Figure 89 - LED Status
Indication and Reset Table 35 - Control Module LED Status Indication
LED Definition Recommended Action
Power This LED is illuminated solid green when switched Verify 24V DC is present on A1 and A2. Check if the
control power is present and with the proper local disconnect is in the OFF position.
polarity.
Run This LED is illuminated solid green when a start Verify 24V DC is present on A1 and A3. Check if the
command and control power is present. user is properly commanding to RUN via Instance
162 or 166.
Network This bicolor LED is used to indicate the status of the See Table 34, Network Status Indicator table above
internal network connection. for additional information.
Fault This LED is used to indicate the fault status of the See Table 36 and Table 37 below for additional
ArmorStart. When the unit is faulted, the unit information.
responds with a specific blink pattern to identify
the fault.
Control Module Fault The PrFlt Reset Mode (Parameter 23) determines how a fault is reset. When this
parameter is set to the value 0 = manual mode, a local or remote fault reset is
LED Indications needed to reset the fault. When this parameter is set to the value 1 = auto reset,
faults are cleared automatically when the fault condition goes away. Referring to
Table 37 for the 284, in addition to the “Pr FltReset Mode” the Auto Rstrt Tries
(Parameter 192) must be set greater than 0.
NOTE: The “Pr FltReset Mode” parameter takes precedence. Therefore if P23 is
set to manual, changing P192 to a value greater than 0 has no effect.
➊ When "Drive Controlled", see Internal Drive Faults see Table 39 for details regarding which drive faults can be auto reset.
Fault 11 Detail Parameter 61 provides a more granular description of the faults that occur.
• An F11 protection fault indicates that the internal communication has
stopped
• There is a 10 second delay before an F11 Internal Comm. fault is present
Resetting Device to To factory reset the base and control module see parameter 47 “Set to Defaults”.
To reset only the VFD in the control module for Bulletin 284 see Parameter 141
Factory Defaults “Reset To Defaults”. Both these resets are limited and do not put the product
completely in the “out of box” configuration. The Type 1 Reset performs a full
product reset to the “out of box” status.
SERVICE CODE 0X05
Class Code 0x0001
INSTANCE 1
Data (USINT) 1
You need to perform a Type 1 Reset if the login and password for the product is
lost and forgotten.
WARNING: A Type 1 Reset causes all parameters and web page login to revert to their
factory defaults. No user date is saved.
WARNING: A Type 1 Reset should only be executed when necessary or when the login
and password must be cleared and set to the factory default setting.
1. Within RSLogix 5000, from the File menu, choose New to create a new
project. Make sure that the project is offline.
2. If an Add-On-Profile (AOP) window is open, click Cancel to close it at the
bottom of the AOP screen.
3. Close any internet browser windows, including Internet Explorer, that are
being used to view the ArmorStart web browser.
IMPORTANT For those using an Internet Browser with multiple tabs open, you need to close the
entire browser window, not just the tab within the ArmorStart browser.
4. Unplug any inputs and outputs that are connected to the ArmorStart unit.
WARNING: A Type 1 Reset cannot be done if there is an I/O device plugged into the
product port. This may cause an unsafe state to occur in the ArmorStart or the
environment around the ArmorStart.
5. Create a new Controller Tag of data type DINT and enter a value of 1.
a. Double click Controller Tags in the Controller Organizer.
c. Create another new tag, the example that is used below is named
Data1.
d. To assign Data1 a value of 1, click Monitor Tags tab and enter a 1 in the
Value field.
2. Select Edit Tags at the bottom of the screen and create a tag
named Reset of the type BOOL (Boolean).
b. Add a Message (MSG) instruction that will be used to execute the reset.
The message instruction can be found in the Input/Output instruction
set tab.
c. Check the tag data type and options with the figure below and click
OK.
g. From the Source Element pull-down menu, choose Data1 tag that was
created earlier and press Enter.
h. Type 5 for the Service Code, 1 for the Class, and 1 for the Instance.
Leave the Attribute value at 0. Once you have added these values, the
Service Type should automatically change to Device Reset.
j. You do not need to configure anything in Tag. Click Apply and then
OK.
8. Save your project. Download the project to the PLC and go Online.
9. Inhibit the ArmorStart using the AOP:
a. Once online, open the ArmorStart's AOP and click Connection. Select
Inhibit Module from the options.
b. Click Apply. The following screen should pop-up. Click Yes. Click OK
to close out the AOP.
c. You should see the yellow inhibit symbol next to the ArmorStart in the
I/O Configuration tree showing that the module is inhibited.
10. Execute the instruction by toggling the Reset input that was created earlier.
a. To energize the bit, left mouse click the input and press CTRL+T. To
de-energize the bit, press CTRL+T again.
b. You should see the status LEDs on the ArmorStart display the Reset
and Power Cycle sequence. You should also see the Done (DN) bit of
the message turn green indicating that the reset was successful.
11. Check if the reset works by bringing the ArmorStart's web browser back up
and checking that the User Name is Administrator and that there is no set
password.
12. Uninhibit the ArmorStart module through the AOP and plug any I/O
connections back into the ArmorStart.
Notes:
Troubleshooting
Introduction The purpose of this chapter is to help with troubleshooting the ArmorStart
Distributed Motor Controller by using the LED status display and diagnostic
parameters.
ATTENTION: Do not attempt to defeat or override fault circuits. The cause of the fault
indication must be determined and corrected before attempting operation. Failure to
correct a control system of mechanical malfunction may result in personal injury and /
or equipment damage due to uncontrolled machine system operation.
ATTENTION: The drive contains high voltage capacitors that take time to discharge
after removal of mains supply. Before working on the drive, verify the isolation of mains
supply from line inputs (R, S, T, [L1, L2, L3]). Wait three minutes for capacitors to
discharge to safe voltage levels. Failure to do so may result in personal injury or death.
Darkened display LEDs is not an indication that capacitors have discharged to safe
voltage levels.
ATTENTION: Only qualified personnel familiar with adjustable frequency AC drives and
associated machinery should plan or implement the installation, startup, and
subsequent maintenance of the system. Failure to comply may result in personal injury
and/or equipment damage.
ATTENTION: This drive contains electrostatic discharge (ESD) – sensitive parts and
assemblies. Static control precautions are required when installing, testing, servicing, or
repairing this assembly. Component damage may result if ESD control procedures are
not followed. If you are not familiar with static control procedures, see Allen-Bradley
Publication 8000-4.5.2, Guarding against Electrostatic Damage, or any other applicable
ESD protection handbook.
Bulletin 280E/281E The following flowchart for Bulletin 280E, 281E units is provided to aid in quick
troubleshooting.
Troubleshooting
Figure 90 - Bulletin 280E, 281E Control Module LED Status
Faulted Display
Yes
No
Faulted Display
Yes
No
Define Nature of
the Problem
Fault Network
LED LED
Motor does
not start
See See
Table 37 Table 34
See
Table 40
Actions
IP67 Dynamic The IP67 operation is different from most other DB resistors. The ArmorStart
controller includes specialized function that protects the DB from current faults.
Brake Diagnostic (DB1) This capability is found on an optional monitoring board that is located in the
control module of the 284 that is included when the DB1 option is selection.
A DB1 fault is not annunciated until the DB switch in the drive is activated and
conducting current.
If the ArmorStart Fault LED blinks 11x's check parameter 61. If value is 41,
check the following:
• DB1 Comm Fault - Communication loss exists between the Dynamic
Brake board and the main control board.
This is also enunciated in the Trip Status parameter 4 bit 10 called Internal
Comm fault.
If the ArmorStart Fault LED blinks 16x's check parameter 61. If value is 42 (DB1
Fault), check the following:
• DB1 Resistor Overtemperature Fault
• DB1 Overcurrent Fault
• DB1 Undercurrent Fault
• DB1 Open Fault
• DB1 VBus Link Fault
This is also enunciated in the Trip Status parameter 4-bit 15 called Miscellaneous
Fault.
If the ArmorStart Fault LED blinks 16x's check parameter 61. If value is 43,
check the following:
• DB1 Switch Fault
Troubleshooting – DB1 Resistor body temperature is too hot. Allow the resistor
to cool.
The DB1 compares each current measurement against the Max Current Level. If
5 consecutive samples are above the Max Current Level, then a fault is recorded.
This fault is intended to notify the user if the DB1 resistance is lower than
expected. This fault is disabled when Parameter 182 (DB1 Resistor Sel) is
“Disabled”.
The DB1 compares each current measurement against the Min Current Level.
The Min Current Level = Min DB1 Voltage Level/Max DB1 Resistance. If 5
consecutive samples are below the Min Current Level and the DB1 is ON, then a
fault is recorded. This fault is intended to notify the user if the DB1 resistance is
higher than expected. This fault is disabled when Parameter 182 (DB1 Resistor
Sel) is “Disabled”.
A DB1 Switch fault is issued when continuous DB1 resistor current is detected
when the Drive Bus Voltage level is less than the DB1 Voltage Level. If 5
consecutive samples of Drive Bus Voltage less than DB1 Level is detected along
with continuous DB1 resistor current flow, then a shorted DB1 IGBT fault
(DB1 Switch) is recorded.
Troubleshooting – Attempt to reset the fault by removing all power to the unit
and restarting. If the fault persists, replace control module.
A DB1 Open fault is issued when Bus Voltage is greater than the DB1 Voltage
Level, and no DB1 resistor current has been detected. If 5 consecutive samples of
Drive Bus Voltage greater than the DB1 Level is detected along with no DB1
resistor current flow, then an open DB1 fault is recorded. This fault is intended to
notify the customer of an open DB1 resistor, or open wire. The fault is disabled
when the DB1 Resistor Sel, Parameter (182) is “Disabled”.
Troubleshooting – Verify that 3-phase line power and control power is applied
to unit. Attempt to reset fault. If fault persists, replace control module.
Troubleshooting – None. DB1 resistor thermal value has exceeded the preset
threshold of 90% of thermal value.
Operation
If the RPM of the internal fan drops below the minimum threshold a Warning bit
in Stater Status, Parameter 5 will be set and the Warning Status, Parameter 62 Bit
13 hardware warning will be set. A 24 hour count down timer begins. If the
warning flag is set continuously for the 24 hr period and time expires a F14 (LED
Flashes 14 times) Hardware fault occurs. Also Last Pr Fault, Parameter 61 shows
Fan RPM fault. If within the 24 hr period the fan rpm climbs above the minimum
threshold the warning flags will be removed and timer reset and turned off.
When set to "1" indicates a Warning if a Fan RPM issue occurs. The warning bit
can also be triggered by other warning type faults that are found in parameter 62.
When Alarm Code UINT = 31 (decimal) this is a FAN RPM warning. For a full
list of fault code references see parameter 61.
When the fault occurs the following Trip bits are activated:
• Parameter 4, Trip Status, bit 13 turns to a "1" indicating a hardware trip has
occurred
• Parameter 5, Starter Status, bit 0 turns to a "1" indicating a TripPresent
• Parameter 61 displays "Fan RPM" Fault 31 as the last protection fault.
The Auto Restart feature provides the ability for the drive to automatically
perform a fault reset followed by a start attempt without user or application
intervention. This allows remote or unattended operation. Only certain faults are
allowed to be reset. Certain faults (Type 2) that indicate possible drive
component malfunction cannot be reset. Caution should be used when enabling
this feature, since the drive will attempt to issue its own start command that is
based on user selected programming.
The following table describes Bulletin 284E Faults as seen in Parameters 107,
108, and 109 (Fault 1, 2, or 3).
Table 39 - Bulletin 284E Faults – Parameters 107, 108, and 109 (Fault 1, 2 or 3)
No. Fault Type ➊ Description Action
F2 Auxiliary Input 1 Auxiliary input interlock is open. 1. Check remote wiring.
2. Check communications.
F3 Power Loss 2 DC bus voltage remained below 85% of 1. Monitor the incoming AC line for low voltage or line power interruption.
nominal. 2. Check input fuses.
F4 UnderVoltage 1 DC bus voltage fell below the minimum 1. Monitor the incoming AC line for low voltage or line power interruption.
value.
F5 OverVoltage 1 DC bus voltage exceeded maximum 1. Monitor the AC line for high line voltage or transient conditions. Bus overvoltage can
value. also be caused by motor regeneration. Extend the decel time or install dynamic brake
option.
F6 Motor Stalled 1 Drive is unable to accelerate motor. 1. Increase Parameters 139 or 167 (Accel Time x) or reduce load so drive output current
does not exceed the current set by Parameter 189 (Current Limit 1).
F7 Motor Overload 1 Internal electronic overload trip 1. An excessive motor load exists. Reduce load so drive output current does not exceed the
current set by Parameter 133 (Motor OL Current).
2. Verify Parameter 184 (Boost Select) setting
F8 Heatsink OvrTmp 1 Heatsink temperature exceeds a 1. Check for blocked or dirty heat sink fins. Verify that ambient temperature has not
predefined value. exceeded 40°C.
2. Replace internal fan.
F12 HW OverCurrent 2 The drive output current has exceeded 1. Check programming. Check for excess load, improper programming of Parameter 184
the hardware current limit. (Boost Select), DC brake volts set too high, or other causes of excess current.
F13 Ground Fault 2 A current path to earth ground has been 1. Check the motor and external wiring to the drive output terminals for a grounded
detected at one or more of the drive condition.
output terminals.
F33 Auto Rstrt Tries Drive unsuccessfully attempted to reset a 1. Correct the cause of the fault and manually clear.
fault and resume running for the
programmed number of Parameter 192
(Auto Rstrt Tries).
F38 Phase U to Gnd 2 A phase to ground fault has been 1. Check the wiring between the drive and motor.
F39 Phase V to Gnd detected between the drive and motor in 2. Check motor for grounded phase.
F40 Phase W to Gnd this phase. 3. Replace starter module if fault cannot be cleared.
F41 Phase UV Short 2 Excessive current has been detected 1. Check the motor and drive output terminal wiring for a shorted condition.
F42 Phase UW Short between these two output terminals. 2. Replace starter module if fault cannot be cleared.
F43 Phase VW Short
F48 Params Defaulted 2 The drive was commanded to write 1. Clear the fault or cycle power to the drive.
default values to EEPROM. 2. Program the drive parameters as needed.
F63 SW OverCurrent 2 Programmed Parameter 198 (SW Current 1. Check load requirements and Parameter 198 (SW Current Trip) setting.
Trip) has been exceeded.
Table 39 - Bulletin 284E Faults – Parameters 107, 108, and 109 (Fault 1, 2 or 3)
No. Fault Type ➊ Description Action
F64 Drive Overload 2 Drive rating of 150% for 1 min or 200% 1. Reduce load or extend Accel Time.
for 3 s has been exceeded.
F70 Power Unit 2 Failure has been detected in the drive 1. Cycle power.
power section. 2. Replace starter module if fault cannot be cleared.
F80 SVC Autotune The autotune function was either 1. Restart procedure.
cancelled by the user or failed.
F81 Comm Loss 2 RS485 (DSI) port stopped 1. Turn off using Parameter 205 (Comm Loss Action).
communicating. 2. Replace starter module if fault cannot be cleared.
F100 Parameter 2 The checksum read from the board does 1. Set Parameter 141 (Reset To Defaults) to Option 1 (Reset Defaults).
Checksum not match the checksum calculated.
F122 I/O Board Fail 2 Failure has been detected in the drive 1. Cycle power.
control and I/O section. 2. Replace starter module if fault cannot be cleared.
➊ See Table 38 for Type description.
Ethernet Statistics The EtherNet/IP communication module may experience intermittent network
connectivity due to these conditions:
• Duplex mismatch
• Electrical noise that is induced into a cable or resulting from a Logix/
switch ground potential difference
• Bad hardware, such as a cable or switch part
Troubleshoot and General Before attempting to correct specific faults on the linear or DLR network, it is
recommended to first take the following actions when a fault appears.
Solutions for Linear or DLR
• For a DLR network check that:
Networks – At least one node is configured as a supervisor on the network and that
Network Topology = Ring.
– All cables on the network are securely connected to each device.
– All devices that require an IP address have one assigned correctly.
– The Network Status field on the active supervisor node’s status page to
determine the fault type.
• For a linear network check that:
– None of the nodes are configured as a supervisor on the network and
that Network Topology = Linear.
If any nodes on a linear network are configured as a supervisor, it may
impact communication to other devices connected to the network.
If the fault is not cleared after completing the actions listed above, use the tables
in the rest of this chapter to troubleshoot issues specific to a DLR network or a
linear network.
Use the following table to troubleshoot possible specific issues on your DLR or
linear network that are not solved by the actions that are described above.
Supervisor Reports Once the fault is corrected, the ring is automatically restored, and the Network Status field returns to
a Ring Fault Normal.
On a DLR network, it is not uncommon to see low levels of media counter errors. For example, if the
network breaks, a low level of media counter errors appear. With a low level of media counter errors, the
value typically does not continuously increase and often clears.
A high level of media counter errors typically continues to increase and does not clear. For example,
there is a mismatch of speed between two linked nodes, a high level of media counter errors appears,
steadily increasing and not clearing.
Media Counter To access the RSLinx screen above, browse the network, right-click the device, select Module Properties
Errors or Collisions and click Port Diagnostics.
If Then
Any media counters are greater than zero You need to investigate further.
These errors are counted: A duplex mismatch exists between your EtherNet/IP communication module and the switch port.
• Alignment To clear the duplex mismatch:
• FCS 1. Configure the EtherNet/IP communication module and the corresponding Ethernet switch port for a forced operation, not auto-
• Carrier Sense negotiation.
2. Verify that the firmware revision of your Logix controller and switch, or converter are identical.
3. If the revisions are not identical, replace the controller, switch, or converter so that they match.
Single Collisions or Multiple Collisions are No action is required.
greater than zero Important: If two stations attempt to transmit data simultaneously, the packets collide with each other. However, collisions are not
errors and do not indicate a network problem. The number of network collisions can vary greatly due to traffic patterns or CPU
utilization. Consequently, there is no set range of acceptable collisions for each outgoing packet. Collisions are a normal aspect of
Ethernet networking.
Late Collisions are greater than zero 1. Check to see if a network segment is too long.
2. Remove repeaters from between devices.
Excessive Collisions are greater than zero Calculate your network’s typical rate of excessive collisions and decide whether the rate of packet loss will affect your network’s
performance.
Important: Excessive collisions indicate that your network has become congested. For each collision after the sixteenth, your
network drops a packet.
MAC Transit Errors are greater than zero No action is required.
Frame Too Long is greater than zero Limit the size of your tags to ≤ 500 bytes.
Ethernet Statistics
➊ When you use an EtherNet/IP communication module with multiple ports, make sure that you use the same Autonegotiate Status
configuration for both ports.
If Then
Any media counters are greater than zero You need to investigate further.
These errors are counted: A duplex mismatch exists between your EtherNet/IP communication module and the switch port.
• Alignment To clear the duplex mismatch:
• FCS 1. Configure the EtherNet/IP communication module and the corresponding Ethernet switch port for a forced operation, not
• Carrier Sense autonegotiation.
2. Verify that the firmware revision of your Logix controller and switch, or converter are identical.
3. If the revisions are not identical, replace the controller, switch, or converter so that they match.
Single Collisions or Multiple Collisions are greater No action is required.
than zero Important: If two stations attempt to transmit data simultaneously, the packets collide with each other. However, collisions are
not errors and do not indicate a network problem. The number of network collisions can vary greatly due to traffic patterns or
CPU utilization. Consequently, there is no set range of acceptable collisions for each outgoing packet. Collisions are a normal
aspect of Ethernet networking.
Late Collisions are greater than zero 1. Check to see if a network segment is too long.
2. Remove repeaters from between devices.
Excessive Collisions are greater than zero Calculate your network’s typical rate of excessive collisions and decide whether the rate of packet loss will affect your network’s
performance.
Important: Excessive collisions indicate that your network has become congested. For each collision after the sixteenth, your
network drops a packet.
MAC Transit Errors are greater than zero No action is required.
Frame Too Long is greater than zero Limit the size of your tags to ≤ 500 bytes.
Ethernet Managed Switch To help troubleshoot the EtherNet/IP network, a managed switch must be used.
Considerations These are important features in a managed switch:
• Internet Group Multicast Protocol (IGMP) snooping
• Support for Virtual Local Area Networks (VLAN)
• Port mirroring
IMPORTANT Use a switch equipped with wire-speed switching fabric. The switch fabric is a measure
of the maximum traffic that a switch can handle without dropping a packet and
without storing a packet in memory. Wire-speed switching fabric refers to a switch
that can handle the maximum data rate of the network on each of its ports.
Switches are typically rated in Gbps. For a 10-port switch connected to EtherNet/IP
products, the maximum data rate that is needed, is typically 100...200 MB/s. Therefore,
a 10-port-switch rated at least 1 GB/s should be adequate for an EtherNet/IP
application.
Switches that support IGMP snooping learn which ports have devices that are
part of a particular multicast group and only forward the multicast packets to the
ports that are part of the multicast group.
IMPORTANT Not all switches support the IGMP snooping querier function, that is, snooping. Those
that do not support IGMP snooping querier require a router. For switches that do
support IGMP snooping, you can configure them to conduct the polling.
This example assumes that the switch does not support IGMP snooping querier
function, so a router is required.
With a managed switch, virtual local area networks (VLAN) can be established
to segregate various kinds of network traffic and also increase security between
the networks. Multiple isolated networks could be created so that the traffic from
one network does not burden the other network.
As with IGMP snooping, VLAN can control multicast traffic. However, unlike
IGMP snooping, VLAN can also control and block this traffic:
• Unicast traffic
• Broadcast traffic
Port Mirroring
Select a managed switch that supports port mirroring. With port mirroring,
frames being transmitted on one port to another port, can be directed for analysis
by a traffic analyzer. Besides monitoring the ethernet media counters, port
mirroring allows anomalies in traffic flow to be spotted immediately. A traffic
analyzer can monitor the traffic on a given port and troubleshoot a problem.
Without port mirroring, frames on other ports cannot be seen. The effective
support and maintenance of ethernet networks often depends on reliable traffic
analysis.
1. Disconnect power by going to the control module and turning OFF the
At-Motor disconnect and performing lockout-tagout per your company
policy.
2. Remove motor cable.
3. Loosen the four mounting screws.
4. Unplug the Control module from the base by pulling forward.
Motor Cable 2
7
3.39 N•m (30 lb•in.)
Fuse Replacement .
Replace the fuse and cycled unswitched power to reset the fault.
UL/NEMA IEC
Operating Temperature Range –20…40 °C (–4…104 °F)
Storage and Transportation –25….85 °C (–13…185 °F)
Temperature Range
Altitude ➊ 2000 m
Environmental
Humidity 5…95% (on-condensing)
Pollution Degree 3
Enclosure Ratings NEMA 4/12 IP67
Approximate Shipping Weight 10.4 kg (23 lbs)
Resistance to Shock
Operational 15 G
Non-Operational 30 G
Resistance to Vibration
Operational 1 G, 0.15 mm (0.006 in.) Displacement
Non-Operational 2.5 G, 0.38 mm (0.015 in.) Displacement
Power and Ground Terminals
Wire Size Primary/Secondary Terminal: #16…#10 AWG Primary/Secondary Terminal: 1.0…4.0 mm2
Mechanical Primary Terminal: 10.8 lb·in. Primary Terminal: 1.2 N·m
Tightening Torque Secondary Terminal: 4.5 lb·in. Secondary Terminal: 0.5 N·m
Wire Strip Length 0.35 in. (9 mm)
Control Terminals
Wire Size #18…#10 AWG 1.0…4.0 mm2
Tightening Torque 6.2 lb·in. 0.7 N·m
Wire Strip Length 0.35 in. (9 mm)
Recommend 8 mm (5/16 in.) lock shackle or hasp.
Disconnect Lock Out The hasp should not exceed 8 mm (5/16 in.) when closed.
CatNo 100- Ops C12 (AC3) C23 (AC3)
Contactor Mechanical Life 280/1_-_12* Mil 13 —
280/1_-_23* Mil — 13
EMC Emission Levels
10V rms Communications Cables
Conducted Radio Frequency Emissions 10V rms (PE)
150 kHz…80 MHz
Radiated Emissions Class A, Group 1, Equivalent to C2 emissions
EMC Immunity Levels
Electrostatic Discharge 4 kV contact and 8 kV Air
10V/m, 80 MHz…1 GHz
Radio Frequency Electromagnetic Field 3V/m, 1.4 GHz…2 GHz
1V/m, 2.0 GHz …2.7 GHz
Other Rating 2 kV (Power)
Fast Transient 2 kV (PE)
1 kV (Communications and Control)
Surge Transient 1 kV (12) L-L, 2 kV (2) L-N (Earth)
280_-____-10A-* 0.24…1.2 A
280_-____-10B-* 0.5…2.5 A
Overload Current Range
280_-____-10C-* 1.1…5.5 A
280_-____-25D-* 3.2…16 A
Trip Classes ➋ 10, 15, 20
Trip Rating 120% of Full Load current (FLC) Setting
Number of poles 3
➊ Refer to Altitude Derating on page 269 for derating guide
➋ Refer to Motor Overload Trip Curves on page 259
UL/NEMA IEC
UL 508
CSA C22.2, No. 14
EN/IEC 60947-4
EN/IEC 60947-4-1
Standards Compliance
CE Marked per Low Voltage 2006/95/EC
EMC Directive 2004/108/EC
CCC
ODVA for EtherNet/IP
Certifications cULus (File No. E3125, Guides NLDX, NLDX7)
UL/NEMA IEC
Rated Operation Voltage 24V DC
Input On-State Voltage Range 10…26V DC
3.0 mA @ 10V DC
Input On-State Current
7.2 mA @ 24V DC
Input Off-State Voltage Range 0…5V DC
Input Off-State Current <1.5 mA
200 Hz
Input Ratings – Sourced from Maximum Input Frequency Response (DeviceLogix response is greater than 200 Hz. Network response depends on
Control Circuit control system network performance.)
(A3/A2) Input Filter – Software Selectable
Off to On Settable from 0…64 ms in 1 ms increments
On to Off Settable from 0…64 ms in 1 ms increments
Input Compatibility N/A IEC 1133 Type 1+
Number of Inputs 4
Sensor Source
Voltage Status Only 11…26.4V DC from unswitched power (A3-A2)
Current Available 50 mA max. per input, 200 mA for any single point
UL/NEMA IEC
Rated Operation Voltage 26.4V DC
Rate Insulation Voltage 250V
Dielectric Withstand 1500V AC (UL) 2000V AC (IEC)
Operating Frequency Solid state sourcing output
Type of Current 24V DC
Conventional Thermal Current Ith 0.5 A each, 1 A max. combined
Peak Output Current Current limited 2-8 amps (5 amps nominal) @ 24V DC
Output Ratings – Sourced
from Control Circuit (A1/A2) Type of Contacts Normally open (N.O.)
(Do not use as a power supply Number of Contacts 2
source to other devices)
Load Types Resistive or light inductive
Surge Suppression Integrated diode, clamps @ 35V DC
Thermo-Protection Integrated short circuit and over current protection
Maximum Cycle Rate 30 operations/minute capacitive and inductive loads
Maximum Blocking Voltage 35V DC
Maximum On-State Voltage @ Maximum Output 1.5V DC
Maximum Off-State Leakage Current 10 μA
Beacon-based performance including IEEE 1588 end to end transparent clock
Device Level Ring (DLR)
Fault Recovery Ring recovery time is less than 3 ms for a 50 node network
Ethernet Receptacles 2 D-coded, 4-pin female M12 connectors
Ports Embedded switch with 2 ports
IP Address DHCP enabled by default
Ethernet Port DHCP Timeout 30 s
Communication Rate 10/100 Mbs with auto negotiate half duplex and full duplex
• Transported over both TCP and UDP
Data • Min. of 500 I/O packets/second (pps)
• Supports up to 150 concurrent TCP sockets
Embedded web server
Security Login and password configurable
Web Server
E-mail Support Simple Mail Transfer Protocol (SMTP)
Configuration Status, diagnostics, and configuration tabs
Supports scheduled (Class 1) and unscheduled (Class 3 & UCMM) connections
6 - Class 3 connections are supported simultaneously
Supports up to 2 Class 1 CIP connections [Exclusive owner (data) or listen-only]. One connection per PLC.
Listen-only connection requires a data connection to be established.
Device Connections
Class 1 Connection API: 2…3200 ms, Class 3 Connection API: 100…10 000 ms
20 ms Request Packet Interval (RPI) default
3 concurrent Encapsulation sessions
TCP port supports 5 concurrent incoming connections
ClassClass
10 Overload
10 Curves Class 15 Overload
Class 15 Curves
10000 10000
Approximate Trip Time (sec)
Cold Cold
100 100
Hot Hot
10
1 1
0 100 200 300 400 500 600 700 0 100 200 300 400 500 600 700
% of Full Load Current
Multiples Multiples%for
of Full Load Current
Note: For 280 and 281, if an overload fault occurs it may require 60 s or more before a fault
Class 20 Overload Curves
Class 20 reset is allowed. Refer to Overload Class Parameter 107, Thermo-Utilization parameter
105, and OL Reset Level parameter 108 to adjust the reset time.
10000
Note: For 280 and 281, when the mechanical motor brake voltage is applied using power from
Approximate Trip Time (sec)
the load side of the ArmorStart controller, this current adds to the load and may result in a
phase imbalance or overload if the FLA of the motor and the brake current are similar in
scale.
Cold
100
Hot
1
0 100 200 300 400 500 600 700
% of
Multiples of Full Load Current
Bulletin 284E
UL/NEMA IEC
Operating Temperature Range –20…40 °C (–4…104 °F)
Storage and Transportation –25….85 °C (–13…185 °F)
Temperature Range
Altitude ➊ 1000 m
Environmental
Humidity 5…95% (on-condensing)
Pollution Degree 3
Enclosure Ratings NEMA 4/12 IP67
Approximate Shipping Weight 13.6 kg (30 lb)
Resistance to Shock
Operational 15 G
Non-Operational 30 G
Resistance to Vibration
Operational 1 G, 0.15 mm (0.006 in.) Displacement
Non-Operational 2.5 G, 0.38 mm (0.015 in.) Displacement
Power and Ground Terminals
Primary/Secondary Terminal: Primary/Secondary Terminal:
Wire Size
Mechanical #16…#10 AWG 1.0…4.0 mm2
Primary Terminal: 10.8 lb·in. Primary Terminal: 1.2 N·m
Tightening Torque Secondary Terminal: 4.5 lb·in. Secondary Terminal: 0.5 N·m
Wire Strip Length 9 mm (0.35 in.)
Control
Terminal Wire Size #18…#10 AWG 1.0…4.0 mm2
Tightening Torque 6.2 lb·in. 0.7 N·m
Wire Strip Length 9 mm (0.35 in.)
Recommend 8 mm (5/16 in.) lock shackle or hasp.
Disconnect Lock Out The hasp should not exceed 8 mm (5/16 in.) when closed.
➊ Refer to Altitude Derating on page 269 for derating guide
UL/NEMA IEC
UL 508C
CSA C22.2, No. 14
EN50178
EN61800-3
Standards Compliance
EN/IEC 60947-4-2
CE Marked per Low Voltage 2006/95/EC
EMC Directive 2004/108/EC
ODVA for EtherNet/IP
cULus (File No. E207834,
Certifications
Guide NMMS, NMMS7)
Drive Characteristics
Output Frequency 0…400 Hz (Programmable)
Efficiency 97.5% (Typical)
Sensorless Vector Control
Maximum (kW) Hp Rating/Input Voltage 5 Hp (3.3 kW)/480V AC
Preset Speeds 8
Skip Frequency ✓
StepLogic® Functionality ✓
Timer/Counter Functions ✓
Minimum DB Resistance
Drive Rating Minimum DB Resistance
Input Voltage [kW] [Hp] [Ω]
0.4 0.5 97
0.75 1 97
480V, 50/60 Hz,
1.5 2 97
Three-Phase
2.2 3 97
4.0 5 77
UL/NEMA IEC
Rated Operation Voltage 24V DC
Input On-State Voltage Range 10…26V DC
3.0 mA @ 10V DC
Input On-State Current
7.2 mA @ 24V DC
Input Off-State Voltage Range 0…5V DC
Input Off-State Current <1.5 mA
200 Hz
Input Ratings – Sourced Maximum Input Frequency Response (DeviceLogix response is greater than 200 Hz. Network response depends on control system
from Control network performance.)
Circuit (A3/A2) Input Filter – Software Selectable
Off to On Settable from 0…64 ms in 1 ms increments
On to Off Settable from 0…64 ms in 1 ms increments
Input Compatibility N/A IEC 1+
Number of Inputs 4
Sensor Source
Voltage Status Only 11…26.4V DC from unswitched power
Current Available 50 mA max. per input, 200 mA, any single point
Rated Operation Voltage 26.4V DC
Rate Insulation Voltage 250V
Dielectric Withstand 1500V AC (UL) 2000V AC (IEC)
Type of Control Circuit Solid state sourcing output
Type of Current 24V DC
Conventional Thermal Current Ith 0.5 A each, 1 A max. combined
Peak Output Current Current limited 2-8 amps (5 amps nominal) @ 24V DC
Output Ratings – Sourced Type of Contacts Normally open (N.O.)
from Control Circuit (A1/ Number of Contacts 2
A2)
Load Types Resistive or light inductive
Surge Suppression Integrated diode, clamps @ 35V DC
Thermo-Protection Integrated short circuit and over current protection
Maximum Cycle Rate 30 operations/minute capacitive and inductive loads
Maximum Blocking Voltage 35V DC
Maximum On-State Voltage @
1.5V DC
Maximum Output
Maximum Off-State Leakage Current 10 μA
— Beacon-based performance including IEEE 1588 end to end transparent clock
Device Level Ring (DLR)
Fault Recovery Ring recovery time is less than 3 ms for a 50 node network
— 2 D-coded, 4-pin female M12 connectors
Ports Embedded switch with 2 ports
IP Address DHCP enabled by default
Ethernet Port DHCP Timeout 30 s
Communication Rate 10/100 Mbs with auto negotiate half duplex and full duplex
•Transported over both TCP and UDP
Data • Min. of 500 I/O packets/second (pps)
• Supports up to 150 concurrent TCP sockets
— Embedded web server
Security Login and password configurable
Web Server
E-mail Support Simple Mail Transfer Protocol (SMTP)
Configuration Status, diagnostics, and configuration tabs
UL/NEMA IEC
Supports scheduled (Class 1) and unscheduled (Class 3 & UCMM) connections
6 - Class 3 connections are supported simultaneously
Supports up to 2 Class 1 CIP connections [Exclusive owner (data) or listen-only]. One connection per PLC.
Listen only connection requires a data connection to be established.
Device Connections Class 1 Connection API: 2…3200 ms
Class 3 Connection API: 100…10 000 ms
20 ms Request Packet Interval (RPI) default
3 concurrent Encapsulation sessions
TCP port supports 5 concurrent incoming connections
Accessories
Male Straight
to 1585D-M4TBDM- ➊
Male Straight
Male Straight
to 1585D-M4TBDE- ➊
Male Right Angle
Male Straight
to 1585D-M4TBDF- ➊
Female Straight
Male Straight
to 1585D-M4TBJM- ➊
RJ45
Sensor Media
Description Description I/O Connection Pin Count Connector Cat. No.
Straight Female
889D-F4ACDM- ➊
DC Micro Straight Male
Input/Output
Patchcord Straight Female
889D-F4ACDE- ➊
EtherNet/IP Right Angle Male
4-Pin
Communications Straight Female 879D-F4ACDM- ➊
DC Micro V- Input
Cable Right Angle Female 879D-R4ACM- ➊
➊ Replace symbol with desired length in meters (for example, Cat. No. 889D-F4ACDM-1 for a 1 m cable). Standard cable lengths: 1
m, 2 m, 5 m, and 10 m.
Sensor Wiring
Three-Phase Power
Field-Installed Receptacles
Female Male
Pin Count Assembly Rating Certifications Cable Diameter Cat. No. Cat. No.
16 AWG, 600V, 10 A 0.28…0.47 in. 280-FAM22F 280-FAM22M
14 AWG, 600V, 15 A UL Listed UL 2237
4-Pin (File No. E318496, Guide PVVA)
10 AWG, 600V, 25 A ➊ 0.48…0.81 in. 280-FAM35F 280-FAM35M
➊ When used with Cat. No. 280-PWRM24_-M* [E,F,G,or H], use Cat. No. 280-FAM35* and the corresponding mating receptacle 280-
M35F-M* .
Sealing Caps
EtherNet/IP
Description
Input Output
Plastic Sealing Cap (M12) ➊ 1485A-M12 1485A-M12
Motor Connector Aluminum Sealing Cap
— 1485A-C1
(M22) for 10A protection*
Motor Connector Aluminum Sealing Cap
— 889A-QMCAP
(M35) for 25A protection
Dynamic Brake Connector (M22) — 1485A-C1
Source/Control Brake Cap (M25) — 280-BRCAP-M25
➊ To achieve IP67 rating, sealing caps must be installed on all unused I/O connections.
Locking Tag
Padlock attachment to the lockable handles 140M-C-M3
Up to three padlocks 4…8 mm (5/16 in. diameter) shackle
Dynamic Braking Resistors Sensorless Vector Control (SVC) Minimum Resistance and
Recommended Modules for Option DB
➊ The resistors that are listed in this table are rated for 5% duty cycle.
Note 1: Always check resistor ohmic value against minimum resistance for drive
being used.
Note 2: Duty cycle that is listed, is based on full speed to zero speed deceleration.
For constant regen. at full speed, duty cycle capability is half of what is listed.
Application Type 1 represents maximum capability up to 100% braking torque
where possible.
Application Type 2 represents more than 100% braking torque where possible, up
to a maximum of 150%.
ATTENTION: AC drives do not offer protection for externally mounted brake resistors,
especially in the case of brake IGBT failure. A risk of fire exists if external braking
resistors are not protected. External resistor packages must be protected from over
temperature or the protective circuit shown, or equivalent, must be supplied.
Frame A Frame B
30.0 61.0
17.0 (1.18) 60.0 31.0 (2.40) 59.0
(0.67) (2.36) (1.22) (2.32)
US
C
US
C
SURFACES MAY BE
AUTOMATION
Thermostat
ROCKWELL
13.0
(0.51)
AK-R2-091P500 AK-R2-030P1K2
AK-R2-047P500 AK-R2-120P1K2
AK-R2-360P500
R (L1)
3-Phase
Power S (L2)
T (L3)
(M)
Contactor
➊ Drive rating and DB part numbers are not interchangeable. Only use specified resistor. Customer is responsible to evaluate if
performance meets application requirement.
➋ Length is user-selectable based on a suffix added to the catalog number. For a length of 500±10 mm, add -M05 to the end of the
catalog number. For a length of 1000±10 mm, add -M1 to the end of the catalog number.
Note: Duty Cycle that is listed, is based on full speed to zero speed deceleration.
For constant regen at full speed, duty cycle capability is half of what is listed.
Application Type 1 represents maximum capability up to 100% braking torque
where possible.
Application Type 2 represents more than 100% braking torque where possible, up
to a maximum of 150%.
B
C D
F
G
A B C D E F G H J
Cat. No. mm (in.) mm (in.) mm (in.) mm (in.) mm (in.) mm (in.) mm (in.) mm (in.) mm (in.)
284R-091P500 215 ± 5 235 ± 5
284R-120P1K2 89 ± 3 (8.46 ± 0.2) M05 = 0.5 m (9.25 ± 0.2) 60 ± 2 127 12.54 60 ± 2 50 ± 1.5
(3.5 ± 0.12) M1 = 1 m ➊ (2.36 ± 0.08) (5) (0.49) (2.36 ± 0.08) (1.97 ± 0.06)
420 ± 5 440 ± 5
284R-120P1K2
(16.54 ± 0.2) (17.32 ± 0.2)
➊ Length is user-selectable based on the suffix added to the catalog number. For a length of 500 ±10 mm, add
-M05 to the end of the catalog number. For a length of 1000 ±10 mm, add -M1 to the end of the catalog number.
Note: The customer must protect the resistor in the event of a shorted switch in
the VFD. This is done via PLC control. An example ControlLogix program can
be downloaded from http://samplecode.rockwellautomation.com
Introduction In the general multiple-motor branch circuit case, installing a motor controller
that is not listed for group installation, violates the NEC and NFPA 79.
Each ArmorStart motor controller is listed for group installation. This appendix
explains how to use this listing to apply ArmorStart motor controllers in
multiple-motor branch circuits.
Background The NEC®is NFPA 70, National Electrical Code. NFPA 79 is the Electrical
Standard for Industrial Machinery. The 2012 NEC refers to NFPA 79 in Article
670's first informational note.
Group installation means that a single set of fuses or a single circuit breaker
protects a branch circuit that supplies two or more motors and their controllers.
Both the NEC and NFPA 79 have rules for installing controllers in these
multiple-motor branch circuits. Both also have special rules for controllers that
are not listed for group installation and general rules for those that are.
The special rules for controllers that are not listed for group installation restrict
some variables. These restricting rules are found in the NEC's 430.53(A),
430.53(B), and 430.53(C)(2)(b) and NFPA 79's 7.2.10.2, 7.2.10.3, and the
7.2.10.4(1) condition “…does not exceed that permitted by 7.2.10.1…”. . For
example, for 480V motors, the NEC's 430.53(A) limits each motor's rating to
1 Hp or less and the protective device rating to 15 amperes or less. The following
will not address these special cases.
The following addresses this general case: if a motor controller is listed for group
installation, the NEC and NFPA 79 permit (1) installing it in a branch circuit
with other motors having any mix of horsepower ratings and (2) protecting all
wiring and controllers with a single set of fuses or a single circuit breaker large
enough to operate this mix of motors. The rules for this general case are found in
the NEC's 430.53(C) and 430.53(D) and NFPA 79's 7.2.10.4 and 7.2.10.5.
From the perspective of the ArmorStart product family, being listed for group
installation means one set of fuses or one circuit breaker may protect a branch
circuit that has two or more of these motor controllers that are connected to it.
This appendix refers to this type of branch circuit as a multiple-motor branch
circuit. The circuit topology that is shown in Figure 106, is one configuration,
but not the only possible configuration, of a multiple-motor branch circuit. In
these circuits, a single set of fuses (or a single circuit breaker) protects multiple
motors, their controllers, and the circuit conductors. The motors may be any
mixture of power ratings and the controllers may be any mixture of motor
controller technologies (magnetic motor controllers and variable-frequency AC
drive controllers).
This appendix addresses only NFPA 79 applications. This is not because these
products are only suitable for industrial machinery, but because industrial
machinery is their primary market. In fact, while all versions of the ArmorStart
products may be applied on industrial machinery, the versions that have the
Conduit Entrance Gland Plate Option may also be used in applications governed
by NFPA 70, National Electrical Code (NEC), (see “ArmorStart Product
Family”).
In the 2012 Edition of NFPA 79, motor controllers that are listed for group
installation may be installed in multiple-motor branch circuits according to
either of two alternative sets of requirements. The first is found in 7.2.10.4(2),
the second in 7.2.10.4(3). The requirements of 7.2.10.4(3) are similar to those in
430.53(C) of NFPA 70, while the requirements of 7.2.10.4(2) are found only in
NFPA 79. This appendix explains the requirements of 7.2.10.4(2), rather than
those of 7.2.10.4(3), because this is the simpler method to use when applying the
ArmorStart family of motor controllers.
The user must determine the requirements – NFPA 79 or NFPA 70 – to use for
the application. When making this determination, it is necessary to understand
the ArmorStart product characteristics and useful to understand the definition of
industrial machinery. The section of this appendix, “ArmorStart Product Family”,
specifies whether a motor controller is suitable for installation according to
NFPA 79 or NFPA 70 (or both). The definition of industrial machinery is found
in 3.3.56 of NFPA 79 and 670.2 of Article 670, Industrial Machinery, in NFPA
70.
These conventions are used throughout this appendix. First, although all
equipment is connected to a three-phase electrical supply, all figures are shown as
one-line diagrams. Second, although all ArmorStart motor controllers are listed
for group installation with both fuses and a specific family of inverse time circuit
breakers, this appendix considers only fuses. This is done to avoid repetitive
explanations with minor, but necessary qualifications, for circuit breakers.
Generally, the principles for selecting the fuses also apply to selecting inverse time
circuit breakers. Third, all references, unless indicated otherwise, are to NFPA 79
– 2012.
Electrical Supply
Disconnecting
Means
Final
Overcurrent Single Set of Fuses
Device
NFPA 79, 3.3.10 Branch Circuit. The Circuit
Conductors Between the Final Overcurrent Device
Protecting the Circuit and the Outlet(s). [70:100]
1/2 Hp 2 Hp 5 Hp 5 Hp 1 Hp
ArmorStart Product Family This section contains a brief description of the attributes of the ArmorStart LT
motor controllers that are relevant to applying them in multiple-motor branch
circuits. These same relative attributes are can be assumed for ArmorStart.
controllers
The term motor controller refers to the device that stops and starts the motor.
The ArmorStart product family consists of two types of motor controllers. The
Bulletin 290 and 291 controllers are magnetic motor controllers that use an
electromechanical contactor to stop and start the motor. The Bulletin 294 motor
controllers use a variable-frequency AC drive to stop, start and vary the speed of
the motor. This appendix refers to the Bulletin 290, 291 and 294 products as
either motor controllers or just controllers.
Multiple-Motor Branch Multiple-motor branch circuits, like that shown in Figure 106, have this
fundamental tradeoff: protecting more than one controller with a single set
Circuits and Motor of fuses requires more electrical and mechanical robustness in each controller.
Controllers Listed for Group
Installation – General In exchange for eliminating the cost and space necessary for a dedicated set of
fuses in front of each controller, the construction of each controller itself must be
more robust. For the circuit configuration shown in Figure 106 to be practical,
the ampere rating of the fuse must be large enough to operate all motors, without
opening, under normal starting and running conditions. This rating of fuse must
be larger than the rating permitted to protect a circuit that supplies only a single
motor and its controller. In general, as the rating of the fuse increases, so does the
magnitude of fault currents that flow until the fuse opens. This higher magnitude
of fault current results in more damage to the controller. Therefore, the
additional controller robustness is necessary to withstand these higher fault
currents, without controller damage, that could result in a shock
or fire hazard.
Consequently, to the controller, being listed for group installation mostly means
the UL testing is performed with fuses that have this practical, and higher,
ampere rating. This testing verifies that it is safe to apply this controller in a
multiple-motor branch circuit, provided the fuse is of the same class and does
not have a rating exceeding that marked on the controller.
The example in Figure 107, illustrates this increase in the maximum ampere
rating of fuse that is permitted to protect a controller. This example compares the
rating of the fuse used in the UL testing of two variable-frequency AC drive-
based motor controllers. Both controllers have a rated power of 0.5 Hp and a
rated output current of 1.5 A. The controller that is shown on the left is intended
for installation in individual-motor branch circuits. The controller that is shown
on the right is the ArmorStart LT Bulletin 294 controller that must be listed for
group installation to be installed, as intended, in multiple-motor branch circuits.
For this example, assume that all testing is done with fuses of the same class.
Referring to the controller on the right, UL 508C permits the group installation
testing to be performed with the maximum rating of fuse that can be used to
protect a multiple-motor branch circuit. According to both NFPA 70
(430.53(C)) and NFPA 79 (7.2.10.4(3)), this is 250 amperes. This value, derived
from the installation requirements of 430.53(C) and 430.53(D) of NFPA 70, is
determined by the largest size of power conductor that the ArmorStart LT
controller can accept, 10 AWG. Because the UL 508C test covers all possibilities
in NFPA 70 and NFPA 79, it permits the maximum value of 250 amperes. This
covers 7.2.10.4(2), which permits only 100 amperes. However, in this case, the
manufacturer, Rockwell Automation, chose to test and mark with the lower value
of 45 A. This value was chosen as the tradeoff between the maximum number
and type of controllers in the branch circuit – limited by the maximum fuse
rating - and the electrical and mechanical robustness engineered into each
controller.
Therefore, to make its use in the multiple-motor branch circuit of Figure 106
practical, the 0.5 Hp, Bulletin 294 controller was engineered to be robust enough
to safely contain the damage when protected by a fuse having a rating
of 45 A, rather than just 6 A.
6A fuse max
Current 45 A fuse max
Maximum
conductor size
= 10 AWG
Motor Motor
Maximum Fuse Ampere This section uses Figure 108 to explain the requirements from 7.2.10.4(1) and
7.2.10.4(2) that are relevant to, and permit, the multiple-motor branch circuit of
Rating According to Figure 106.
7.2.10.4(1) and 7.2.10.4(2)
The following is the complete text of 7.2.10.4(1) and 7.2.10.4(2) and an
abbreviated version of Table 51 from the 2012 Edition of NFPA 79. The table is
abbreviated to cover the size of conductors that are generally relevant to the
ArmorStart LT motor controllers.
Complete Text
“7.2.10.4 Two or more motors or one or more motor(s) and other load(s), and
their control equipment shall be permitted to be connected to a single branch
circuit where short-circuit and ground-fault protection is provided by a single
inverse time circuit breaker or a single set of fuses, provided the following
conditions under (1) and either (2) or (3) are met:
(1) Each motor controller and overload device is either listed for group
installation with specified maximum branch-circuit protection or selected such
that the ampere rating of the motor branch short-circuit and ground-fault
protective device does not exceed that permitted by 7.2.10.1 for that individual
motor controller or overload device and corresponding motor load.
(2) The rating or setting of the branch short-circuit and ground-fault protection
device does not exceed the values in Table 51 for the smallest conductor in the
circuit.”
The following text and Figure 108 provide an explanation of 7.2.10.4(1) and (2).
In the following, the text not relevant to Figure 106 is replaced by ellipsis points
(…). Then each individual requirement is underlined and followed by an
underlined letter in parentheses. This underlined letter in the following text
corresponds to the letter in Figure 108.
“7.2.10.4 Two or more motors (a)…and their control equipment (b) shall be
permitted to be connected to a single branch circuit (c) where short-circuit and
ground-fault protection is provided by a single inverse time circuit breaker or a
single set of fuses (d), provided the following conditions under (1) and…(2)…are
met:
(1) Each motor controller and overload device is… listed for group installation
with specified maximum branch-circuit protection (e) …
(2) The rating or setting of the branch short-circuit and ground-fault protection
device does not exceed the values in Table 7.2.10.4 for the smallest conductor in
the circuit.” (f )
1/2 HP 2 HP 5 HP 5 HP 1 HP
FLC = FLC = FLC = FLC = FLC =
1.1 A** 3.4 A** 7.6 A** 7.6 A** 2.1 A**
Explanatory Example The example addresses the overcurrent protection of the conductors, controllers
and motors. Protection for three overcurrent conditions is considered: motor
running overloads, short-circuit (line-to-line) faults, and ground-faults (line-to-
ground). The short-circuit fault and ground-fault protection is governed by
7.2.10.4(1) and 7.2.10.4(2) and explained in Requirements 1,2 and 3 and
Figure 109. The overload protection, explained in Requirement 4, is governed by
7.3.1 and 7.3.1.1. Overload coordination depends on each conductor having the
minimum ampacity given by 12.5.3 and 12.5.4. The method for determining this
minimum ampacity is explained in Requirement 5 and Figure 110.
The example branch circuit is shown in Figure 109 and Figure 110. The circuit
topology consists of a set of 10 AWG conductors that supply multiple sets of
14 AWG conductors. Each set of 14 AWG conductors supply a controller and
motor. These conductor sizes are chosen to be the smallest conductors that have
sufficient ampacity, without derating, for the loads each must carry. All wiring is
customer-supplied, rather than the ArmorConnect Power Media, because all
controllers have the Conduit Entrance Gland Plate Option. Fuses protect the
branch circuit.
The example addresses five basic requirements that the motor controllers, fuses,
and conductors must satisfy. The letters in the circles on Figure 109 and
Figure 110 are referenced in the explanations as letters in parentheses. Ellipses
points (…)
are used to replace NFPA 79 text that is not applicable to the multiple-motor
branch circuit that is shown in Figure 109 and Figure 110. Unless indicated, all
text is from NFPA 79.
Electrical Supply -
480Y/277V
Available Fault Current
Sym. Amps RMS 9 KA
Disconnecting
Means
Fuses
a
45 A Max,
Branch short-circuit
CC, J or T
and ground-fault
d protection device
Combined Load Conductors 10 AWG
Controller
ratings
further
restrict the
fuse
“Suitable for Motor Group Installation”
14 AWG
14 AWG
14 AWG
14 AWG
14 AWG
Max. Ratings
Sym. Amps RMS 5 KA 10 KA
Fuse 45A 45A*
14 AWG
14 AWG
14 AWG
14 AWG
14 AWG
Conductor
Table 7.2.10.4
Conductor c protection
Max protection -
Fuse 60 A max, “Smallest
AWG (A) any class Determine conductor”
- - fuse class
14 60 and max
12 80 rating for
10 100 1/2 HP 2 HP 5 HP 5 HP 1 HP
conductor FLC = FLC = FLC = FLC = FLC =
8 150
- - protection 1.1 A** 3.4 A** 7.6 A** 7.6 A** 2.1 A**
7.2.10.4(2) -
“smallest
conductor in
the circuit” * Each controller is suitable for group installation with the same maximum ratings of fuse.
= 14 AWG
** Table 430.250 of NFPA 70-2011
14 AWG
14 AWG
14 AWG
14 AWG
1.8 A 5.5 A 7.6 A 7.6 A 3.0 A
½ HP 2 HP 5 HP 5 HP 1 HP
Bulletin Bulletin Bulletin Bulletin Bulletin
294 294 291 290 294
14 AWG
14 AWG
14 AWG
14 AWG
Min Amp. = Min Amp. = Min Amp. = Min Amp. = Min Amp. =
125% * 1.1A 125% * 3.4 A 125% * 7.6 A a 125% * 7.6 A b 125% * 2.1 A
1/2 HP 2 HP 5 HP 5 HP 1 HP
FLC = FLC = FLC = FLC = FLC =
1.1 A** 3.4 A** 7.6 A** 7.6 A** 2.1 A**
Text: “7.2.10.4(1) Each motor controller and overload device is… listed for group
installation with specified maximum branch-circuit protection…”
Referring to Figure 110 (a) indicates the markings on the nameplate that satisfy
7.2.10.4(1). The marking “Suitable for Motor Group Installation” satisfies the
requirement to be listed for group installation. The ratings that are located
beneath the description “Max. Ratings” are the specified maximum branch
circuit protection. The (a) beside the fuse(s) indicates that the maximum
protection specified on the nameplate applies to these fuse(s).
Text: “7.2.10.4(2) The rating or setting of the branch short-circuit and ground-
fault protection device does not exceed the values in Table 51 for the smallest
conductor in the circuit.”
Supplementary Note 2: The note at (b) points to the conductor on the output
of the 0.5 Hp Bulletin 294E controller to emphasize that the smallest conductor
in the circuit includes the conductors between each controller and motor. This
includes the output of the variable-frequency AC drive-based Bulletin 294E
controllers; even though these drives have electronic short-circuit protection.
According to NFPA 79, the fuse, and not the drive’s electronic short-circuit
protection, provides the short-circuit fault and ground-fault protection for these
output conductors.
Text: “(1) Each motor controller and overload device is… listed for group
installation with specified maximum branch-circuit protection…”
Analysis: See (d) in Figure 109. The characteristics of the fuse(s) permitted to
protect the conductors (see Requirement 2) must now be compared to those in
the controller’s ratings. To comply with the listing of each motor controller and
overload relay, the fuse(s) must comply with the maximum branch-circuit
protection specified in the controller markings. Therefore, the fuse(s) must be
of a class marked on all controllers and the rating of the fuse(s) must not exceed
the rating that is marked on any of the controllers. The markings of each
controller specify that a fuse having a maximum rating of 45 A may protect the
motor controller. When connecting to an electrical supply having an available
fault current of 5000 A or less, the class of the fuse is not specified and may be any
class. When connecting to an electrical supply having an available fault current
from 5000 to 10000 A, the class of the fuse must be CC, J
or T. Since the electrical supply has an available fault current of 9000 A, selecting
a Class CC, J or T fuse with a rating of 45 A or less ensures each motor controller
is applied within its own ratings.
Supplementary Note 1: The rating of the fuse must not exceed the rating that is
permitted by 7.2.10.4(2) to protect the smallest conductor in the circuit.
Selecting a Class CC, J or T fuse with a rating of 45 A, being less than 60 A, also
protects the conductors (see Requirement 2). Although the ArmorStart LT
products presently have a maximum fuse rating of 45 A, future controllers may
have maximum fuse ratings that exceed 60 A. In this case, the maximum rating of
fuse is limited by the rating to protect the 14 AWG conductors, 60 A. The
maximum rating that is permitted for the controller, 45 A, is a maximum rating
and can be reduced, for more conservative protection, provided nuisance opening
of the fuses do not occur.
Text:
“7.3.1 General. Overload devices shall be provided to protect each motor, motor
controller, and branch-circuit conductor against excessive heating due to motor
overloads or failure to start.”
Text:
“12.5.3 Motor circuit conductors supplying a single motor shall have an ampacity
not less than 125 percent of the motor full-load current rating.”
“12.5.4 Combined load conductors shall have an ampacity not less than … 125
percent of the full-load current rating of the highest rated motor plus the sum of
the full-load current ratings of all other connected motors…”
Analysis: Referring to Figure 110, (a), (b) and (c) explain the method for
calculating the minimum required conductor ampacity for each of these
conductors: input and output conductors of Bulletin 290E and 291E controllers
(a), input and output conductors of Bulletin 294E controllers (b) and combined
load conductors that supply Bulletin 290E, 291E, and 294E controllers (c). The
currents I1 through I5 are the input currents to the controllers. For the Bulletin
290E and 291E controllers, these are the same as the output motor currents. For
the Bulletin 294E controllers, these currents are the rated input currents.
The example does not address conditions of use such as an ambient temperature
exceeding 30 °C or more than three current-carrying conductors in a cable or
raceway. In a particular application, these conditions of use may require derating
of the ampacity that is given in Table 12.5.1. This example assumes that, under
the conditions of use, both conductors have sufficient ampacity for the
application. This means the 14 AWG conductors have an ampacity of no less
than 9.5 A and the 10 AWG conductors have an ampacity of no less than 27.4 A.
Input and Output Conductors AmorStart models that use an electromechanical contactor to control the motor,
the input current like the output current, is just the current to the motor.
for Mechanical Controllers (a) Therefore, the minimum conductor ampacity for both input and output
conductors is 125 percent of the motor full-load current rating, as specified in the
text of 12.5.3 (a).
Input and Output Conductors ArmorStart models that are a variable-frequency AC drive, are used to control
the motor. These drives use a power conversion method that generates input
for Variable Frequency Drives currents that are larger than the output currents. The input currents are larger
(b) because, unlike the output currents to the motor, they are not sinusoidal.
Consequently, when determining the minimum ampacity of the input
conductors, the requirement of 12.5.3 must be based on the rated input current
of the controller, rather than the full-load current rating of the motor. Therefore,
the minimum ampacity of the input conductors must be 125% of the controller
rated input current, while that of the output conductors must be 125% of the
motor full-load current rating.
Referring to Figure 110, the 1 Hp Bulletin 294E controller has a rated input
current of 3.0 A. Using the rated input current, the conductors from the
combined load conductors to the controllers must have an ampacity of 125%
of 3.0 A or 3.75 A. The output conductors must have an ampacity of 125% of
2.1 A or 2.6 A.
Combined Load Conductors The requirement for the minimum ampacity of the combined load conductors
is given by 12.5.4. When the combined load conductors supply one or more
(c) Bulletin 294E controllers, the minimum ampacity calculation of 12.5.4 must
be made by substituting the rated input current of the Bulletin 294E controllers
for the full-load current rating of the motors that these controllers supply.
In Figure 110, the currents I1, I2, I3, I4, and I5 are the input currents to each
controller. I3 and I4 are the full-load current ratings of the 5 Hp motors. I1, I2
and I5 are the rated input currents of the Bulletin 294E controllers. Referring to
the explanatory text (c) in Figure 110, the method for calculating the minimum
ampacity of the combined load conductors follows: first, multiply the largest
input current to any controller – Bulletin 290E, 291E or 294E - by 125%. In this
case, the input currents to the Bulletin 290E and 291E controllers, I3 and I4, are
the largest, 7.6 A. Because they are the same, either can be used. Choose I3 to
calculate 125% of the maximum. 125% of 7.6 A is 9.5 A. Second, sum the
remaining input currents (I1, I2, I4, I5) for a total of 17.9 A. Third, add the result
from the first step to the result from the second for a total of 27.4 A. Finally, the
minimum ampacity of the combined load conductors is 27.4 A.
CIP Information
High Level Product The ArmorStart EtherNet/IP controller is an extension of the ArmorStart
DeviceNet controller. Three product types are offered:
Description
Bulletin Number Distributed Starter Type
280E DOL
281E Reversing
284E Inverter
The following table lists the product codes and name strings that will be added
to the ArmorStart product family for EtherNet/IP.
CIP Explicit Connection The ArmorStart controller allows run, jog and user outputs to be driven by
connected explicit messages when no I/O connection exists, or when an I/O
Behavior connection exists in the idle state, a single EtherNet/IP Class 3 explicit
connection is allowed to send “explicit control” messages via an “Active Explicit”
connection.
EDS Files
Most of the information that is contained in the EDS (Electronic Data Sheet)
files for the ArmorStart EtherNet/IP product line is able to be extracted via the
network.
CIP Object Requirements The following CIP objects are covered in the following subsections.
Class Object
0x0001 Identity Object
0x0004 Assembly Object
0x0006 Connection Manager Object
0x0008 Discrete Input Point Object
0x0009 Discrete Output Point Object
0x000F Parameter Object
0x0010 Parameter Group Object
0x001D Discrete Input Group Object
0x001E Discrete Output Group Object
0x0029 Control Supervisor Object
0x002C Overload Object
0x0047 Device Level Ring Object
0x0048 QoS Object
0x0097 DPI Fault Object
0x0098 DPI Alarm Object
0x00B4 Interface Object
0x00F5 TCP/IP Interface Object
0x00F6 Ethernet Link Object
For convenience, all objects that are accessible via the EtherNet/IP port
are included.
The following class attributes are supported for the Identity Object:
Up to nine instances (Instance 1…9) of the Identity Object are supported. The
following table shows what each instance represents, and what the revision
attribute reports:
➊ These instance numbers assume the next available instance base on the unit configuration. (If the unit is a DOL (No Drive) and there
is an MCB Daughter board present its instance number will be 7.)
IMPORTANT Attempts to access Attribute 10 of all DeviceNet Main Control Board instances are
blocked. If Attribute 10 (Heartbeat Interval) is accessed, an “Attribute Not Supported”
error will be generated.
➊ Instance 1 only.
The following common services are implemented for Instance 1. Service requests
to other instances are serviced through the bridge.
Implemented for:
Service Code Class Instance Service Name
0x01 Yes Yes Get_Attributes_All
0x05 No Yes Reset
0x0E Yes Yes Get_Attributes_Single
The Type 0 and 1 reset service types, reset the Control Module. The EtherNet/IP
module performs the Type 0 or 1 reset on itself.
The following class attributes are supported for the Assembly Object:
The following static Assembly instance attributes are supported for each
Assembly instance.
Implemented for:
Service Code Class Instance Service Name
0x0E Yes Yes Get_Attribute_Single
0x10 No Yes Set_Attribute_Single
0x18 No Yes Get_Member
I/O Assemblies
The following table summarizes the Assembly instances that are supported in the
ArmrorStart EtherNet/IP product:
Instances 3 and 52 are required by the ODVA Motor Starter Profile. When used
as an EtherNet/IP Class 1 connection point, the I/O data attribute is simply
passed through the bridge.
Instance 3
Instance 52
Instance 150
This is the default input (produced) assembly for Bulletin 280E, 281E starters.
Instance 150 "Starter Stat" - Default Status Assembly for Bulletin 280E, 281E Starters
Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
0 Reserved (AOP Tag name: {name}:I.Fault)
1 Reserved (AOP Tag name: {name}:I.Fault)
2 Reserved (AOP Tag name: {name}:I.Fault)
3 Reserved (AOP Tag name: {name}:I.Fault)
4 — — — Ready RunningReverse RunningForward WarningPresent TripPresent
5 — — DisconnectClosed Hand In3 In2 In1 In0
6 Pt07DeviceOut Pt06DeviceOut Pt05DeviceOut Pt04DeviceOut Pt03DeviceOut Pt02DeviceOut Pt01DeviceOut Pt00DeviceOut
7 Logic Enable Pt14DeviceOut Pt13DeviceOut Pt12DeviceOut Pt11DeviceOut Pt10DeviceOut Pt09DeviceOut Pt08DeviceOut
8 Value of the parameter pointed to by “Parameter Int00DeviceOut Cfg” (low byte) - ProducedWord0Param
9 Value of the parameter pointed to by “Parameter Int00DeviceOut Cfg” (high byte) - ProducedWord0Param
10 Value of the parameter pointed to by “Parameter Int01DeviceOut Cfg” (low byte) - ProducedWord1Param
11 Value of the parameter pointed to by “Parameter Int01DeviceOut Cfg” (high byte) - ProducedWord1Param
12 Value of the parameter pointed to by “Parameter Int02DeviceOut Cfg” (low byte) - ProducedWord2Param
13 Value of the parameter pointed to by “Parameter Int02DeviceOut Cfg” (high byte) - ProducedWord2Param
14 Value of the parameter pointed to by “Parameter Int03DeviceOut Cfg” (low byte) - ProducedWord3Param
15 Value of the parameter pointed to by “Parameter Int03DeviceOut Cfg” (high byte) - ProducedWord3Param
Note: Byte 0 - 3 refers to PLC communication status. All 1s (bit high) indicates a
connection fault (communication fault) exists or all 0s (bit low) connection
is normal.
Instance 151
This is the default input (produced) assembly for Inverter Type Distributed
Starters.
Note: Byte 0 - 3 refers to PLC communication status. All 1s (bit high) indicates a
connection fault (communication fault) exists or all 0s (bit low) connection
is normal.
** Contactor Reference
Contactor 1 Source Brake Contactor status
Contactor 2 Output Contactor status
Instance 162
Instance 166
This is the standard output (consumed) assembly for Inverter Type Distributed
Starters with network inputs.
The following class attributes are supported for the Connection Manager Object.
2 Get/Set Open Format Rejects UINT Number of Forward Open service requests that were rejected
due to bad format.
Number of Forward Open service requests that were rejected
3 Get/Set Open Resource Rejects UINT due to lack of resources.
Number of Forward Open service requests that were rejected
4 Get/Set Open Other Rejects UINT for reasons other than bad format or lack of resources.
5 Get/Set Close Requests UINT Number of Forward Close service requests received.
Number of Forward Close service requests that were rejected
6 Get/Set Close Format Requests UINT due to bad format.
Number of Forward Close service requests that were rejected
7 Get/Set Close Other Requests UINT for reasons other than bad format.
Total number of connection timeouts that have occurred in
8 Get/Set Connection Timeouts UINT connections that are controlled by this Connection Manager
The following services are implemented for the Connection Manager Object.
Implemented for:
Service Code Class Instance Service Name
0E hex Yes Yes Get_Attribute_Single
4E hex No Yes Forward_Close
54 hex No Yes Forward_Open
Class 1 Connections
Class 1 connections are used to transfer I/O data, and can be established to the
assembly object instances. Each Class 1 connection establishes two data
transports, one consuming and one producing. The heartbeat instances are used
for connections that shall access only inputs. Class 1 uses UDP transport.
• Total numbers of supported Class 1 connections equals 2 (total for:
exclusive owner + input only + listen only)
• Supported Actual Packet Interval (API): 2…3200 ms (Note that the
minimum API can be higher if processor resources become a problem)
• T->O (Target to Originator) Connection type: point-to-point, multicast
• O->T (Originator to Target) Connection type: point-to-point
• Supported trigger type: cyclic, change-of-state
This connection type is used for controlling the outputs of the module and shall
not be dependent on any other condition. Only one exclusive owner connection
can be opened against the module.
It is recommended that the originator sets the data size in the Forward_Open
be zero.
Class 3 CIP connections are used to establish connections to the message router.
The connection is used for explicit messaging. Class 3 CIP connections use TCP
connections.
• Three concurrent encapsulation sessions are supported
• Six concurrent Class 3 CIP connections are supported
• More than one Class 3 CIP connection per encapsulation session are
supported
• Supported Actual Packet Interval (API): 100…10000 ms
• T->O Connection type: point-to-point
• O->T Connection type: point-to-point
• Supported trigger type: application
The following class attributes are currently supported for the Discrete Input
Point Object:
Four instances of the Discrete Input Point Object are supported. All instances
contain the following attributes.
The following common services are implemented for the Discrete Input Point
Object.
Implemented for:
Service Code Class Instance Service Name
0x0E Yes Yes Get_Attribute_Single
0x10 No Yes Set_Attribute_Single
Four instances of the Discrete Output Point Object are supported for DOL/
Reverser units. Ten instances are supported for Drive units. The following table
summarizes the DOP instances.
➊ For DOP Instances 1, 2, 9 and 10, Attributes 113 and 114 have “Get” only access, and their values are always 0.
The following common services are implemented for the Discrete Output Point
Object.
Implemented for:
Service Code Class Instance Service Name
0x0E Yes Yes Get_Attribute_Single
0x10 No Yes Set_Attribute_Single
The following class attributes are supported for the Parameter Object.
The number of instances of the parameter object depend upon the type of
Control Module that the EtherNet/IP board is connected to.
The following instance attributes are implemented for all parameter attributes.
Implemented for:
Service Code Class Instance Service Name
0x01 No Yes Get_Attribute_All
0x0E Yes Yes Get_Attribute_Single
0x10 No Yes Set_Attribute_Single
0x4b No Yes Get_Enum_String
The following class attributes are supported for the Parameter Object.
The following instance attributes are supported for all parameter group instances.
The following common services are implemented for the Parameter Group
Object.
Implemented for:
Service Code Class Instance Service Name
0x01 Yes Yes Get_Attribute_All
0x0E Yes Yes Get_Attribute_Single
No class attributes are supported for the Discrete Input Group Object.
A single instance of the Discrete Input Group Object is supported and contains
the following instance attributes.
The following common services are implemented for the Discrete Input Group
Object.
Implemented for:
Service Code Class Instance Service Name
0x0E No Yes Get_Attribute_Single
0x10 No Yes Set_Attribute_Single
Instance 1 exists for all ArmorStart units. Instance 2 exists for drive units only.
The following common services are implemented for the Discrete Output Group
Object.
Implemented for:
Service Code Class Instance Service Name
0x0E No Yes Get_Attribute_Single
0x10 No Yes Set_Attribute_Single
The following common services are implemented for the Control Supervisor
Object.
Implemented for:
Service Code Class Instance Service Name
0x0E No Yes Get_Attribute_Single
0x10 No Yes Set_Attribute_Single
A single instance (Instance 1) of the Overload Object is supported for DOL and
Reversing Starters. Instance 1 contains the following instance attributes.
The following common services are implemented for the Overload Object.
Implemented for:
Service Code Class Instance Service Name
0x0E No Yes Get_Attribute_Single
0x10 No Yes Set_Attribute_Single
A single instance (Instance 1) are supported with the following instance attributes.
The following common services are implemented for the DLR Object.
Implemented for:
Service Code Class Instance Service Name
0x01 Yes Yes Get_Attribute_All
0x0E Yes Yes Set_Attribute_Single
The following class attributes are supported for the QoS Object.
The following common services are implemented for the QoS Object.
Implemented for:
Service Code Class Instance Service Name
0x0E Yes Yes Get_Attribute_Single
0x10 No Yes Set_Attribute_Single
The DPI Fault Object is implemented in the DeviceNet Main Control Board.
Four instances of the DPI Fault Object are supported. Instance 1 is the most
recent fault while 4 is the oldest. The have the following instance attributes:
Implemented for:
Service Code Class Instance Service Name
0x0E Yes Yes Get_Attribute_Single
0x10 Yes No Set_Attribute_Single
The table below lists Fault Codes, Fault Text, and Fault Help Strings for DOL
and Reversers.
The table below lists Fault Codes, Fault Text, and Fault Help Strings for VFD
units.
45 ➊ Incompatible COMM The Software version of the Drive is not compatible with the ArmorStart.
Device
➊ The Fault text for this error is not return by the device, and is only reported as “Fault 45”.
Four instances of the DPI Alarm Object are supported with the following
instance attributes. Instance 1 is the most recent fault while 4 is the oldest. See
Table 52 on page 322 and Table 53 on page 323 above for fault codes.
Implemented for:
Service Code Class Instance Service Name
0x0E Yes Yes Get_Attribute_Single
0x10 Yes No Set_Attribute_Single
The table below lists Warning Codes, Warning Text, and Warning Help Strings
that do not match the fault text.
The following common services are implemented for the Interface Object.
Implemented for:
Service Code Class Instance Service Name
0x0E No Yes Get_Attribute_Single
0x10 No Yes Set_Attribute_Single
One instance of the TCP/IP Interface Object are supported with the following
instance attributes.
The following common services are implemented for the TCP/IP Interface
Object.
Implemented for:
Service Code Class Instance Service Name
No Yes Get_Attribute_All
0x0E Yes Yes Get_Attribute_Single
0x10 No Yes Set_Attribute_Single
One instance of the Ethernet Link Object are supported with the following
instance attributes.
The following common services are implemented for the Ethernet Link Object.
Implemented for:
Service Code Class Instance Service Name
0x01 No Yes Get_Attribute_All
0x0E Yes Yes Get_Attribute_Single
0x10 No Yes Set_Attribute_Single
Using DeviceLogix
• If both overrides are disabled and the logic is enabled, the ONLY time
DeviceLogix runs is if there is an active I/O connection with a master, i.e.
the master is in Run mode. At all other times, DeviceLogix is running the
logic, but does NOT 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.
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 shut down through local logic
DeviceLogix Programming The following example shows how to program a simple logic routine to interface
the ArmorStart EtherNet I/P controller with a remote hard-wired startstop
Example station. In this case, the I/O is wired as shown in Table 54.
IMPORTANT Before programming logic, it is important to decide on the conditions under which the
logic will run. As defined earlier, the conditions can be defined by setting parameter 8
(Network Override) and parameter 9 (Comm. Override) to the desired value.
1. While in the AOP, click the DeviceLogix tab. Click the Launch Editor
button.
2. Select Function Block or Ladder editor. Note that once selected, you are
not able to switch back without recreating the logic.
3. Refer to the tool bar at the top of the DeviceLogix editor window, click the
Move/Logical group and select the RSTD (Latch Reset). Move it to the
work space and click to drop it.
4. From the toolbar, Click the “Bit Input” button and select In 0 from the
Hardware Boolean tree. This is the remote start button based on the
example I/O table.
5. Place the input to the left of the reset function. To drop the input on the
page, left click the desired position.
6. Place the mouse cursor over the tip of In 0. The tip turns green. Click the
tip when it turns green.
7. Move the mouse cursor toward the Set input of the reset function. A line
follows the cursor. When a connection can be made, the tip of the RSL
function also turns green. Click the on Input and the line is drawn from In
0 to the Set Input of the reset function.
Note: If this was not a valid connection, one of the pin tips would have turned
red rather than green. Left double-clicking the unused portion of the grid or
pressing the “Esc” key at any time cancels the connection process.
8. From the toolbar, Click the “Bit Input” button and select In 1 from the
pull-down menu. This is the remote stop button based on the example I/O
table.
9. Place the input to the left of the reset function.
10. Connect the input to the reset input of the reset function.
11. From the toolbar, Click the “Bit Output” button and select “Run
Forward” from the hardware boolean tree. Run Forward is the relay
controlling the coil of the contactor.
12. Move the cursor into the grid and place the Output to the right of the reset
function block.
13. Connect the output of the reset function block to Run Forward.
14. Click the “Verify” button that is located in the toolbar or select “Logic
Verify” from the “Tools” pull-down menu.
15. Click file close. The program is not saved automatically. Fill in the
information on following window and accept changes. This saves the
program but has not been downloaded in the product.
16. The last step is to enable the logic via the pull-down menu.
17. Click OK. To download the DeviceLogix program, you must go on-line
with the PLC and allow the download. Ensure that the PLC is in the
Program position. If in any other position, the download will not occur
and an error will be generated.
18. The ArmorStart is now programmed and the logic is Active.
Import and Export The ArmorStart EtherNet/IP AOP provides users an import or export function.
The export function allows the DeviceLogix program to be saved to a file. This
file can then be imported into a similar product of same function regardless of
horsepower. Importing of DeviceLogix between unlike products is not allowed,
for example Bulletin 284E and Bulletin 280E.
Notes:
Renewal Parts
Overload Selection
Contactor Size/Control Voltage Current Range
A 0.24…1.2
24V DC
B 0.5…2.5 A
12Z Control Module C 1.1…5.5 A
N Control Module Only D 3.2…16 A
23Z
kW Hp Cat. No.
Current Rating 230V AC 400V AC 200V AC 230V AC 460V AC
[A] 50 Hz 50 Hz 60 Hz 60 Hz 60 Hz 24V DC
0.24…1.2 0.18 0.37 — — 0.5 280E-F12Z-NA-R
0.5…2.5 0.37 0.75 0.5 0.5 1 280E-F12Z-NB-R
1.1…5.5 1.1 2.2 1 1 3 280E-F12Z-NC-R
3.2…16 4 7.5 3 5 10 280E-F23Z-ND-R
kW Hp Cat. No.
Current Rating 230V AC 400V AC 200V AC 230V AC 460V AC
[A] 50 Hz 50 Hz 60 Hz 60 Hz 60 Hz 24V DC
0.24…1.2 0.18 0.37 — — 0.5 281E-F12Z-NA-R
0.5…2.5 0.37 0.75 0.5 0.5 1 281E-F12Z-NB-R
1.1…5.5 1.1 2.2 1 1 3 281E-F12Z-NC-R
3.2…16 4 7.5 3 5 10 281E-F23Z-ND-R
280 E – F N – 10 – C
Bulletin Number
280 Base Module
Communications
E EtherNet/IP
Motor Connection
C Conduit Entrance
R ArmorConnect Power Media
Enclosure Type
F Type 4/12 (IP67)
Short Circuit Protection (Bulletin 140M)
10 10 A Rated Device
Control Module
25 25 A Rated Device
N Control Module Only
Table 57 - Bulletin 280E Full Voltage Starters and Bulletin 281E Reversing Starters –
IP67/NEMA Type 4, with Conduit Entrance
kW Hp
Current Rating 230V AC 400V AC 200V AC 230V AC 460V AC
[A] 50 Hz 50 Hz 60 Hz 60 Hz 60 Hz Cat. No.
0.24…1.2 0.18 0.37 — — 0.5 280E-FN-10-C
0.5…2.5 0.37 0.75 0.5 0.5 1 280E-FN-10-C
1.1…5.5 1.1 2.2 1 1 3 280E-FN-10-C
3.2…16 4 7.5 3 5 10 280E-FN-25-C
Table 58 - Bulletin 280E Full Voltage Starters and Bulletin 281E Reversing Starters –
IP67/NEMA Type 4, with ArmorConnect Connectivity
kW Hp
Current Rating 230V AC 400V AC 200V AC 230V AC 460V AC
[A] 50 Hz 50 Hz 60 Hz 60 Hz 60 Hz Cat. No.
0.24…1.2 0.18 0.37 — — 0.5 280E-FN-10-R
0.5…2.5 0.37 0.75 0.5 0.5 1 280E-FN-10-R
1.1…5.5 1.1 2.2 1 1 3 280E-FN-10-R
3.2…16 4 7.5 3 5 10 280E-FN-25-R
Table 59 - Motor and Brake Cables - See Motor and Brake Cables
Bulletin Number
284 VFD Starter Option 3
EMI EMI Filter
Communications OC Output Contactor
E EtherNet/IP
Option 2
DB DB Brake Connector
Enclosure Type DB1 DB Brake Connector for IP67 Dynamic
F Type 4 (IP67) Brake Resistor
Control Module
SB Source Brake Connector
N Control Module Only
Output Current
284 D – F N – 10 – C – Options
Bulletin
Number
Option 2 & 3 — Brake Cable Options
Communications SM Safety monitor
D DeviceNet
Line Media
Enclosure Type C Conduit
F Type 4/12 (IP67) R ArmorConnect™ Power Media
Short-Circuit Protection
Bulletin 140 Current Rating (A)
Base
10 10 A Rated Device
N Base Only — no starter
25 25 A Rated Device
Table 61 - Bulletin 284E Base Module Renewal Part, IP67/Type 4/12, Up to 600V AC With Conduit
Entrance
Input Voltage kW Hp Output Current Cat. No.
200..240V 0.4…0.75 0.5…1.0 2.3 A 280D-FN-10-C
50/60 Hz
1.5 2.0 7.6 A 280D-FN-25-C
3-Phase
380…480V 0.4…2.2 0.5…3.0 1.4…4.0 A 280D-FN-10-C
50/60 Hz
3.0 5.0 6.0…7.6 A 280D-FN-25-C
3-Phase
460…600V 50/60Hz 0.75…1.5 1.0…2.0 1.7....3.0 A 280D-FN-10-C
3-Phase
2.2...4.0 3.0...5.0 4.2...6.6 A 280D-FN-25-C
Table 62 - Bulletin 284E Base Module Renewal Part, IP67/Type 4/12, Up to 600V AC with
ArmorConnect Connectivity
Input Voltage kW Hp Output Current Cat. No.
200..240V 0.4…0.75 0.5…1.0 2.3 A 280D-FN-10-R
50/60 Hz
1.5 2.0 7.6 A 280D-FN-25-R
3-Phase
380…480V 0.4…2.2 0.5…3.0 1.4…4.0 A 280D-FN-10-R
50/60 Hz
3.0 5.0 6.0…7.6 A 280D-FN-25-R
3-Phase
460…600V 50/60Hz 0.75…1.5 1.0…2.0 1.7....3.0 A 280D-FN-10-R
3-Phase
2.2...4.0 3.0...5.0 4.2...6.6 A 280D-FN-25-R
Table 66 - Miscellaneous
Replacement Fuses
Description
Output Fuse
Fast acting, high-interupting capacity, tubular fuse
Rating: 2.5 A, 250V Littlefuse PN 021602.5
Dimension [mm (in.)]: 20 (0.787) x 5 (0.197)
Control Fuse
UL Listed Class CC, CSA HRC-1 Cooper Bussman PN KTK-R-7
Rating: 7 A, 600V or
Dimensions [in.]: 1.5 x 0.405 Littlefuse PN KLKR007.T
Source Brake Fuse (For use with Bulletins 284 and 283 with Brake option CB/SB)
UL Listed Class CC, CSA HRC-1 Cooper Bussman PN KTK-R-3
Rating: 3 A, 600V or
Dimensions [in.]: 1.5 x 0.405 Littlefuse PN KLKR003.T
Replacement Parts
Description Cat. No.
➊ These pins are replacement parts for factory-installed alignment pins. They cannot be retrofitted in the field. The base module and
control module require mating features as indicated in the following diagrams.
General Rule Generally a line reactor for an ArmorStart controller is not required. Customers
familiar with Rockwell Automation PowerFlex drives may ask this when
installing an ArmorStart controller.
Reasons to Use The most common reason's to use a line reactor are to:
• Extend the working life of the DC- bus capacitors by reducing the
associated heating impact that is caused by ripple noise currents in these
capacitors.
• Reduce the impact of line disturbances on other equipment that result
VFD input switching.
• Reduce the RMS input current that is associated with peak changes in
current that results from VFD input switching, allowing the use of smaller
input conductors and transformers.
• Mitigate the impact of power system transients on the drive.
Repeated line disturbances in current and voltage can lead to premature input
power structure failure for AC drives. One way to mitigate these types of issues is
to add impedance to the incoming power line to the drive. Impedance comes in
the form of transformers, line reactors, and conductors. When a large power
distribution system (>100 kVA) is feeding many small VFDs, the associated input
impedance can be lower than 1%. This low impedance can result in voltage and
current disturbances that negatively impact performance and the overall life of an
AC drive. A line reactor is one possible solution to absorb these power line
disturbances. This does not mean that a reactor must be used in every situation.
Conductors add impedance. On Machine solutions are generally further away
from the power distribution panel therefore the length of cable adds impedance.
ArmorStart Design The ArmorStart design incorporates features and additional components that
allow for better heat transfer keeping the internal components cooler. This cooler
design assures longer life of the DC bus capacitors that extend the life of the
VFD. In addition, if line disturbance mitigation is necessary, the ArmorStart can
be equipped with an EMI filter and shielded motor cable reducing the impact of
the power switching components. However, if users specify input line reactors or
transformers the recommendation is to group the ArmorStarts at the distribution
panel under one line reactor (not individual reactors or transformers).
Lastly, when full voltage ArmorStarts controllers are included with VFD
ArmorStart controllers, and line reactors are used, the starting currents of the full
voltage ArmorStart controllers can be significant. The current must be accounted
for in the selection of the line reactor or there is a risk of nuisance faults.
Application Examples
Manual Brake Control If the user wants to activate the mechanical brake (source brake option) of the
ArmorStart Bulletin 284E there are several parameters that need attention. The
following configuration allows the brake to operate normally during running and
when the Bulletin 284 is not running, allows the release of the brake for
maintenance.
See the consume assembly (164 for DeviceNet or 166 for EtherNet/IP).
1. Select which Drive Input (1, 2, 3, 4) you will use to trigger the release of the
brake. Configure the corresponding parameter that references the Drive
Input P151, P152, P153, or P154.
27 ➊ Em Brk Rls If EM Brake function enabled, this input releases the brake. See parameter 155 and set to EM Brk Cntrol (22).
➊ Provides programmable control of Em Brk via digital input (1...4)
3. Set P155, Relay Out Sel, to "22" EM Brk Cntrl EM Brake is energized.
• Program Parameter 260 (EM Brk OFF Delay) for desired action.
– Sets the time that the drive remains at minimum frequency (P134)
before ramping to the commanded frequency.
Frequency
260 [EM Brk Off Delay] Ram 261 [EM Brk On Delay]
l
cce
pD
pA
ece
l
R am
Minimum Freq
Time
Start EM Brk Stop EM Brk Drive Stops
Commanded Energized (Off) Commanded De-Energized (On)
4. See the consume assembly below. The Drive Input that was configured in
step #1, is used to control the mechanical brake.
Default Instance 166 Consumed Inverter Type Starter with Network Inputs ArmorStart EtherNet/IP
Bulletin 284 - VFD Preset DeviceLogix can be used to select one of multiple preset frequencies
cooperatively with the PLC or independently based on user input. This can be
Speed Example done using the four digit inputs or the frequency control bits in DeviceLogix.
The digital inputs provide the user the most flexibility, but can be more complex
to configure. If a preset speed is needed, the simpler approach is to use frequency
control that is found in the produced network bits of DeviceLogix. If you prefer
not to apply DeviceLogix for preset speeds, then implement the digit inputs to
select preset speed via Instance 166 found in Chapter 5. The following example
demonstrates the use of frequency control bits in DeviceLogix
Frequency control (Freq Cntl) bits allow a maximum of 4 Preset Speeds, each
preset has a predefined accel or decel reference. If more are required, then digital
inputs must be configured and properly used. The example focuses on Frequency
Control 2,1,0 in the Produced Network Bit Table 68. Note that there are other
capabilities that are shown in the table that are not reviewed in this example.
Figure 115 below shows all available network outputs supported by Bulletin
284.Referring to Table 68 the preset frequencies are defined in parameter
170,171,172 and 173 of Bulletin 284. Also note the truth table that selects each
of those frequencies. For example if Freq Cntl bit 2=1, 1=1, and 0=0 then the
controller frequency is based on Parameter 172 (Preset Freq 2).
Table 68 -
See table 22 - Parameters 170…177 Preset Freq Options for predefined accel
and decel
Using parameters 170-173, set them to 0,10,30, and 60 respectively. Figure 116
shows the preset frequencies 0-3.
In this example, DeviceLogix receives data from the PLC program. The
communication and network overrides are disabled as shown below.
Figure 117 shows the DeviceLogix program. This allows the user to select one
of three predefined frequencies that are based on two network bits.
Once you exit the DeviceLogix editor, verify that the logic is “Enabled” otherwise
the preset frequency control does not operate. See Figure 118.
Figure 118 -
This simple PLC program is used to select one of three preset speeds, speed 1, 2,
or 3. For the purpose of this example speed 1, 2, & 3 are BOOL bits but they can
be any valid input. Notice that there is an interlock for speed 1 and speed 2 to
ensure that they do not trigger simultaneously. This would accidentally cause
speed 3 to run.
Download the finished program file to the PLC. In order for the parameters and
DeviceLogix program to update in the device, verify the PLC is in program
mode, and open the AOP for the Bulletin 284E.
Select the Parameters and DeviceLogic tab. This forces a correlation between the
program file and the device. If a difference exists either upload from the device or
download from the project to the device. In this example, choose to download.
Figure 119 -
After both correlations are complete place the PLC in run mode and test the
program by exercising speed 1, 2, and 3 bits.
IMPORTANT To download a new DeviceLogix program, connect to the PLC and stay in program
mode. There can be no active I/O connections to the device or the download fails. Open
the AOP and select the DeviceLogix tab to start the correlation process. If a difference
exists, then an upload or download is necessary.
Operation
When bit Speed_1 is ON then the Bulletin 284E accelerates to 10 Hz or
decelerate using accel/decel Time 2
The following table contains the status bit definitions for ArmorStart 280D and
281D units:
The screen capture below shows how to choose fault bits in the ladder editor.
The following table contains the fault bit definitions for Bulletin 280D and
281D ArmorStart units:
The screen capture below shows how to choose outputs in the ladder editor.
The Bulletin 280 and 281 have the following bit definitions:
0 = Run Forward
1 = Run Reverse
2 = User Output A
3 = User Output B
The following table contains the produced network bit definitions for Bulletin
280 and 281 ArmorStart units
The following table contains the status bit definitions for ArmorStart 284
The screen capture below shows how to choose Fault Bits in the ladder editor.
The following table contains the fault bit definitions for ArmorStart 284
0 = Run Forward
1 = Run Reverse (Reserved)
2 = User Output A
3 = User Output B
4 = Drive Digital In 1
5 = Drive Digital In 2
6 = Drive Digital In 3
7 = Drive Digital In 4
8 = Jog Forward
9 = Jog Reverse
The screen capture below shows how to choose Produced Network Bits in the
ladder editor.
The following table contains the produced network bit definitions for Bulletin
284 ArmorStart units
0
Reporting Examples How to Report the RPM of the 284 Internal Fan
To get the fan RPM of the fan, an explicit "get single" message instruction is
needed using a service of 0x000E.
The fan RPM can be read using the following CIA Class 0x00B4, Instance 1, and
Attribute 103. The nominal fan rpm value is 2800-3000 RPM. The ArmorStart
trips once the fan speed falls below 62% (1736)
There is no FAN FAULT warning. The user needs to develop their own warning
PLC code using the CIA message referred above for critical applications.
To get the heat sink temperature of the 284, an explicit "get single" message
instruction is needed.
The heat sink temperature can be read using the following CIA Class 0x000F,
Instance 124, and Attribute 1.
By default, the ArmorStart controller provides only the last fault as a parameter.
To retrieve the last four faults, a PLC message instruction is required. Class
0x0097 DPI Fault Object is used to extract a structure of information that is
related to the last four faults. The following example shows how to configure an
explicit message to get all four fault logs. To retrieve information on all four
faults, the instance value must be indexed from 1, 2, 3, and 4, where 1 is the most
recent fault information. If more detailed information is needed, change the
attribute to 0.
Refer CIP Class 0x00F5 address conflict detection. This is stored in non-volatile
memory and can be accessed through the TCP/IP Interface Object, instance 1,
attribute 11 (“LastConflictDetected”) via Message instruction.
Demand Torque Off ArmorStart EtherNet/IP does not support safety torque off internally, therefore
this capability must be implemented external to the ArmorStart controller within
Considerations the safety circuit. To achieve a required safety performance without damage to
the ArmorStart 284 its required to have some coordination between the safety
safety circuit and the VFD enable. When there is a demand of the safety system it
is important that the ArmorStart VFD is disabled before any line side contactor
opening. One way to accomplish this digitally is to configure one of digital inputs
via parameter 151- 154 to option 9. Then using the consumed instance 166 and
the previously defined digit input to disable the VFD before the safety contactors
opening. This disables the ArmorStart allowing the contactors to open without
damaging the VFD. Alternatively, if the safety circuit removes A1-A2 (switched
control power) power before the safety contactors open this results in the same
behavior and prevents damage to the VFD.
Keypad Disable with HOA operation can be prevented dynamically without parameter modification,
as follows:
DeviceLogix
The DeviceLogix program that is shown below turns off the keypad if both
inputs are true and the keypad is in either “OFF” or “AUTO” mode.
Note: If the user is already pressing the “HAND” button, the program does not
disable the keypad; if the inputs are on after the “HAND” mode is actuated.
Motion Disable The motion disable program disables motion regardless of the HOA status, PLC
control, or DeviceLogix. Once motion disable is turned off, the ArmorStart or
PLC resumes control of the motor again. The motion disable does not disable the
HOA keypad. The keypad operation appears normal but it does not control the
run command until the motion disable is off.
In addition, we offer multiple support programs for installation, configuration, and troubleshooting. For more
information, contact your local distributor or Rockwell Automation representative, or visit
http://www.rockwellautomation.com/services/online-phone.
Installation Assistance
If you experience a problem within the first 24 hours of installation, review the information that is contained in this
manual. You can contact Customer Support for initial help in getting your product up and running.
United States or Canada 1.440.646.3434
Outside United States or Canada Use the Worldwide Locator at http://www.rockwellautomation.com/rockwellautomation/support/overview.page, or contact your local
Rockwell Automation representative.
Rockwell Automation tests all of its products to help ensure that they are fully operational when shipped from the
manufacturing facility. However, if your product is not functioning and needs to be returned, follow these procedures.
United States Contact your distributor. You must provide a Customer Support case number (call the phone number above to obtain one) to your
distributor to complete the return process.
Outside United States Please contact your local Rockwell Automation representative for the return procedure.
Documentation Feedback
Your comments will help us serve your documentation needs better. If you have any suggestions on how to improve this
document, complete this form, publication RA-DU002, available at http://www.rockwellautomation.com/literature/.
Rockwell Otomasyon Ticaret A.Ş., Kar Plaza İş Merkezi E Blok Kat:6 34752 İçerenköy, İstanbul, Tel: +90 (216) 5698400