Armorstart® Distributed Motor Controller: User Manual
Armorstart® Distributed Motor Controller: User Manual
Controller
USER MANUAL
Bulletin 284
2
Important User Information Because of the variety of uses for the products described in this publication,
those responsible for the application and use of this control equipment must
satisfy themselves that all necessary steps have been taken to assure that
each application and use meets all performance and safety requirements,
including any applicable laws, regulations, codes and standards.
!
or economic loss
• identify a hazard
• avoid a hazard
• recognize the consequences
Trademark List
ArmorStart, ArmorPoint, and ControlLogix are registered trademarks of Rockwell Automation, Inc.
ArmorConnect, DeviceLogix, PLC, RSNetWorx, RSLogix 5000, and SLC are trademarks of Rockwell Automation,
Inc. DeviceNet and the DeviceNet logo are trademarks of the Open Device Vendors Association (ODVA). ControlNet
is a trademark of ControlNet International, LTD.
3
European Communities (EC) 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
Directive Compliance the following directives.
EMC Directive
The modular plug and play design offers simplicity in wiring the installation.
The quick disconnects for the I/O, communications, and motor connections
reduce the wiring time and eliminates wiring errors. The ArmorStart offers as
standard four DC inputs and two relay outputs, to be used with sensors and
actuators respectively, for monitoring and controlling the application process.
The ArmorStart’s LED status indication and built-in diagnostics capabilities
allows for ease of maintenance and troubleshooting. The optional HOA
keypad configuration allows for local start/stop control at the ArmorStart
Distributed Motor Controller.
Operation The Bulletin 284 ArmorStart Distributed Motor Controller can operate
three-phase squirrel induction motors up to 2.0 Hp (1.5 kW) @ 240V AC, up
to 5 Hp (3.0 kW) @ 480V AC, and up to 5 Hp (4.0 kW) @ 575V AC; 50/60
Hz. Depending on the cat. no. order, the ArmorStart Distributed Motor
Controller will accept a control power input of 120V AC, 240V AC, or
24V DC.
1-1
1-2
The LED Status Indication provides four status LEDs and a Reset button. The
• Power LED — The LED is illuminated solid green when control power is
present and with the proper polarity
• 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 communication link
• Fault LED — Indicates Controller Fault (Trip) condition
Fault Diagnostics
• Short Circuit
• Overload
• Phase Short
• Ground Fault
• Stall
• Control Power
• Control Power Fuse Detection
• IO Fault➊
• Over Temperature
• Output Power Fuse Detection
• Overcurrent
• Brake Fuse Detection
• DeviceNet™ Power Loss ➊
• Internal Comm Fault
• DC Bus Fault
• EEPROM Fault
• Hardware Fault
• Restart Retries
• Miscellaneous Fault
Inputs ➊
The inputs are single-keyed (two inputs per connector), which are sourced from
DeviceNet Power (24V DC), with LED status indication.
Outputs
Two dual-key relay output connectors are supplied as standard. The outputs are
sourced from control power (A1 and A2). LED status indication is also
provided as standard for each output.
1-5
Power Connections
Motor Cable
With every Bulletin 284 ArmorStart Distributed Motor Controller, a 3 meter
unshielded four-conductor cordset is provided with each unit as standard. If
the optional EMI filter is selected a shielded four-conductor cordset is
provided with each unit as standard.
DeviceLogix™
EMI Filter
The EMI Filter option is required if the Bulletin 284 ArmorStart Distributed
Motor Controller must be CE-compliant. If the EMI Filter is selected, a
3 meter shielded 4-conductor cordset is provided as standard. This option is
only available with sensorless vector control.
Dynamic Brake
A 3 meter 3-pin cable for connection to a dynamic brake module is provided
as standard when this option is selected. See Appendix E, Accessories, for
available dynamic brake modules.
Output Contactor
An internal contactor will be sourced from control voltage to isolate the load
side of the Bulletin 284 ArmorStart Distributed Motor Controller. When
control power is applied, the output contactor is closed, and when control
power is removed, the output contact opens. There is no switching element,
such as a relay, in the system. If control power is lost then the output contactor
will open, since its coil power is lost. A sequenced stop involving the output
contactor cannot be performed.
1-7
Notes
Chapter 2
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. Should any concealed damage be 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
starter. Remove all packing material from device.
Inspecting After unpacking, check the item(s’) nameplate cat. no. against the purchase
order.
Storing The controller should remain in its shipping container prior to installation. If
the equipment is not to be used for a period of time, it must be stored
according to the following instructions in order to maintain warranty coverage.
1
2-2 Installation and Wiring
General Precautions In addition to the precautions listed throughout this manual, the
following statements, which are general to the system, must be read and
understood.
!
on drive, ensure 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.
!
implement the installation, start-up, and subsequent
maintenance of the system. Failure to comply may result in
personal injury and/or equipment damage.
!
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, refer to Publication 8000-4.5.2,
Guarding against Electrostatic Damage, or any other applicable
ESD protection handbook.
!
or application errors, such as undersizing the motor,
incorrect or inadequate AC supply, or excessive ambient
temperatures may result in malfunction of the system.
Installation and Wiring 2-3
Approximate Dimensions Dimensions are shown in millimeters (inches). Dimensions are not
intended to be used for manufacturing purposes. All dimensions are
subject to change.
Figure 2.1 Dimensions for 1 Hp and below @ 230V AC, 2 Hp and below @
460V AC, and 2 Hp and below @ 575V AC, IP67/NEMA Type 4 with
Conduit Entrance
2-4 Installation and Wiring
Figure 2.2 Dimensions for 1 Hp and below @ 230V AC, 2 Hp and below @
460V AC, and 2 Hp and below @ 575V AC, IP67/NEMA Type 4 with
ArmorConnect™ Connectivity
Figure 2.3 Dimensions for 2 Hp @ 230V AC, 3 Hp and above @ 460V AC, and
3 Hp and above @ 575V AC, IP67/NEMA Type 4 with Conduit
Entrance
2-6 Installation and Wiring
Figure 2.4 Dimensions for 2 Hp @ 230V AC, 3 Hp and above @ 460V AC, and 3 Hp
and above @ 575V AC, IP67/NEMA Type 4 with ArmorConnect
Connectivity
Figure 2.5 Dimensions for 1 Hp and below @ 230V AC, 2 Hp and below @
460V AC, and 2 Hp and below @ 575V AC, NEMA Type 4X with
Conduit Entrance
2-8 Installation and Wiring
Figure 2.6 Dimensions for 1 Hp and below @ 230V AC, 2 Hp and below @
460V AC, and 2 Hp and below @ 575V AC, NEMA Type 4X with
ArmorConnect Connectivity
Figure 2.7 Dimensions for 2 Hp @ 230V AC, 3 Hp and above @ 460V AC, and
3 Hp and above @ 575V AC, NEMA Type 4X with Conduit Entrance
2-10 Installation and Wiring
Figure 2.8 Dimensions for 2 Hp @ 230V AC, 3 Hp and above @ 460V AC, and
3 Hp and above @ 575V AC, NEMA Type 4X with ArmorConnect
Connectivity
Local Disconnect
LED Status
Indication
2 Outputs
(Micro/M12)
4 Inputs
(Micro/M12)
Source Brake
Connector
Motor
DeviceNet Connector
Connection 0…10V➋
Ground (Mini/M18) Dynamic
Analog Input
Terminal Brake Connector
➋ Available only with the Bulletin 284 with sensorless vector control.
Figure 2.10 Bulletin 284 ArmorStart with ArmorConnect
Power, Control, Safety Monitor Table 2.A provides the power, control, safety monitor inputs, and
ground wire capacity and the tightening torque requirements. The
Inputs, and Ground Wiring power, control, and safety monitor terminals will accept a maximum of
two wires per terminal and the ground terminal will accept a maximum a
one wire per terminal.
Table 2.A Power, Control, Safety Monitor Inputs, Ground Wire Size, and
Torque Specifications
Table 2.B Power, Control, Safety Monitor, and Ground Terminal Designations
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.
2. To open, push the tab on the left-hand side and lift the access
cover.
Note: The access door can not be closed when 140 (black handle) is
in the OFF position.
RESET
OFF
Bulletin 800F
Emergency Stop
Pushbutton
➊ Three-Phase Power Trunk- PatchCord cable with integral female or male connector on each end
Example Part Number: 280-PWR35A-M*
➋ Three-Phase Drop Cable- PatchCord cable with integral female or male connector on each end
Example Part Number: 280-PWR22A-M*
➌ Three-Phase Power Tees and Reducer -
Tee connects to a single drop line to trunk with quick change connectors – Part Number: 280-T35
Reducing Tee connects to a single drop line (Mini) to trunk (Quick change) connector – Part Number:
280-RT35
Reducer connects from quick change male connector to mini female connector– Part Number:
280-RA35
2-16 Installation and Wiring
RESET
OFF
Bulletin 800F
Emergency Stop
Pushbutton
➏ Control Power Media Patchcords - PatchCord cable with integral female or male connector on each
end
Example Part Number: 889N-F65GFNM-*
➐ Control Power Tees - The E-stop In Tee (Part Number: 898N-653ST-NKF) is used to connect to the
Bulletin 800F On-Machine E-Stop station using a control power media patchcord. The E-stop Out tee
(Part Number: 898N-653ES-NKF) is used with cordset or patchcord to connect to the ArmorStart
Distributed Motor Controller.
Installation and Wiring 2-17
Cord Grips for ArmorStart Devices with 10 A short circuit protection rating
Thomas & Betts Cord Grip Thomas & Betts Cord Grip
Part Number: 2931NM Part Number: 2940NM
3/4 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 Part Number: Media Cordset - Example Part
889N-M65GF-M2 Number: 280-PWR22G-M1
Cord Grips for ArmorStart Devices with 25 A short circuit protection rating
Maximum Ratings
Voltage (V) 480Y/277 480/480 600Y/347 600/600
Sym. Amps RMS 65 kA 65 kA 65 kA 65 kA
Time Delay Fuse 50 A 30 A 30 A 30 A
Non-Delay Fuse 100 A 60 A 60 A 60 A
Installation and Wiring 2-19
AC Supply Considerations
!
disconnected if the Bulletin 284 is installed on an
ungrounded distribution system.
Disconnecting MOVs
Remove Jumper
!
Installation and Wiring 2-21
Group Motor Installations for The ArmorStart Distributed Motor Controllers are listed for use with
each other in group installations per NFPA 79, Electrical Standard for
USA and Canada Markets 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.
Wiring and Workmanship In addition to conduit and seal-tite raceway, it is acceptable to utilize
cable that is dual rated Tray Cable, Type TC-ER and Cord, STOOW, for
Guidelines power and control wiring on ArmorStart installations. In the USA and
Canada installations, the following guidance is outlined by the NEC and
NFPA 79.
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.
DeviceNet™ Network The ArmorStart Distributed Motor Controller contains the equivalent
of 30 in. (0.76m) of Device Net drop cable's electrical characteristics and
Installation therefore 30 in. of drop cable must be included in the DeviceNet drop
cable budget for each ArmorStart in addition to actual drop cable
required for the installation.
Other DeviceNet System The separation of the control power and DeviceNet power is required
as a good design practice to minimize DC power ampacity for both the
Design Considerations DeviceNet power supply and the 24V DC control voltage power supply
for the ArmorStart Distributed Motor Controllers.
Electromagnetic Compatibility The following guidelines are provided for EMC installation compliance.
(EMC)
CE Conformity
General Notes
Grounding
Wiring
This chapter describes each programmable parameter and its function for
Bulletin 284 Volts per Hertz Controllers.
Parameter Programming Each Distributed Motor Controller type will have a common set of parameters
followed by a set of parameters that pertain to the individual starter type.
3-1
3-2 Programmable Parameters for Volts per Hertz Controllers
Parameter Group Listing The Bulletin 284D ArmorStart contains ten parameter groups. The parameters
shown in the DeviceLogix™ Setup, DeviceNet Setup, Starter Protection
Setup, User I/O Setup, Misc. Parameter Setup, ZIP Parameters, Display
Group, Basic Program, and Advanced Program are discussed in this chapter
.
Programmable Parameters for Volts per Hertz Controllers 3-3
DeviceLogix Group
Hdw Inputs Parameter Number 1➊
This parameter provides status of hardware inputs. Access Rule GET
Data Type WORD
Group DeviceLogix
Units —
Minimum Value 0
Maximum Value 15
Default Value 0
Bit Function
3 2 1 0
— — — X Input 0
— — X — Input 1
— X — — Input 2
X — — — Input 3
Bit Function
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
— — — — — — — — — — — — — — — X Net Input 0
— — — — — — — — — — — — — — X — Net Input 1
— — — — — — — — — — — — — X — — Net input 2
— — — — — — — — — — — — X — — — Net Input 3
— — — — — — — — — — — X — — — — Net Input 4
— — — — — — — — — — X — — — — — Net Input 5
— — — — — — — — — X — — — — — — Net Input 6
— — — — — — — — X — — — — — — — Net Input 7
— — — — — — — X — — — — — — — — Net Input 8
— — — — — — X — — — — — — — — — Net Input 9
— — — — — X — — — — — — — — — — Net Input 10
— — — — X — — — — — — — — — — — Net Input 11
— — — X — — — — — — — — — — — — Net Input 12
— — X — — — — — — — — — — — — — Net Input 13
— X — — — — — — — — — — — — — — Net Input 14
X — — — — — — — — — — — — — — — Net Input 15
3-4 Programmable Parameters for Volts per Hertz Controllers
Bit Function
14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
— — — — — — — — — — — — — — X Net Output 0
— — — — — — — — — — — — — X — Net Output 1
— — — — — — — — — — — — X — — Net Output 2
— — — — — — — — — — — X — — — Net Output 3
— — — — — — — — — — X — — — — Net Output 4
— — — — — — — — — X — — — — — Net Output 5
— — — — — — — — X — — — — — — Net Output 6
— — — — — — — X — — — — — — — Net Output 7
— — — — — — X — — — — — — — — Net Output 8
— — — — — X — — — — — — — — — Net Output 9
— — — — X — — — — — — — — — — Net Output 10
— — — X — — — — — — — — — — — Net Output 11
— — X — — — — — — — — — — — — Net Output 12
— X — — — — — — — — — — — — — Net Output 13
X — — — — — — — — — — — — — — Net Output 14
Programmable Parameters for Volts per Hertz Controllers 3-5
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 — — — — — — IO Fault
— — — — — — — — X — — — — — — — Overtemperature
— — — — — — — X — — — — — — — — Over Current
— — — — — — X — — — — — — — — — Dnet 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 Tripped
— — — — — — — — — — — — — — X — Warning
— — — — — — — — — — — — — X — — Running Fwd
— — — — — — — — — — — — X — — — Running Rev
— — — — — — — — — — — 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 — — — — — — — — — — — — — 140M On
— X — — — — — — — — — — — — — — Contactor 1 ➊
X — — — — — — — — — — — — — — — Contactor 2 ➋
➊ Refers to Source Brake contactor status.
➋ Refers to Output contactor status.
Programmable Parameters for Volts per Hertz Controllers 3-7
Bit Function
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
— — — — — — — — — — — — — — — X Exp Cnxn
— — — — — — — — — — — — — — X — IO Cnxn
— — — — — — — — — — — — — X — — Exp Flt
— — — — — — — — — — — — X — — — IO Flt
— — — — — — — — — — — X — — — — IO Idle
— — — — — — — — X X X — — — — — Reserved
— — — — — — — X — — — — — — — — ZIP 1 Cnxn
— — — — — — X — — — — — — — — — ZIP 1 Flt
— — — — — X — — — — — — — — — — ZIP 2 Cnxn
— — — — X — — — — — — — — — — — ZIP 2 Flt
— — — X — — — — — — — — — — — — ZIP 3 Cnxn
— — X — — — — — — — — — — — — — ZIP 3 Flt
— X — — — — — — — — — — — — — — ZIP 4 Cnxn
X — — — — — — — — — — — — — — — ZIP 4 Flt
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 — — — — — — User Out A
X — — — — — — — User Out B
3-8 Programmable Parameters for Volts per Hertz Controllers
DeviceNet Group
Autobaud Enable Parameter Number 10
When this parameter is enabled, the device will attempt to determine the network Access Rule GET/SET
baud rate and set its baud rate to the same, provided network traffic exists. At least
one node with an established baud rate must exist on the network for autobaud to Data Type BOOL
occur. Group DeviceNet
0 = Disable
1 = Enable Units —
Minimum Value 0
Maximum Value 1
Default Value 1
Bit Function
13 12 11 10 9 8 7 6 5 4 3 2 1 0
— — — — — — — — — — — — — X Tripped
— — — — — — — — — — — — X — Warning
— — — — — — — — — — — X — — Running Fwd
— — — — — — — — — — X — — — Running Rev
— — — — — — — — — X — — — — Ready
— — — — — — — — X — — — — — Net Ctl Status
— — — — — — — X — — — — — — Net Ref Status
— — — — — — X — — — — — — — At Reference
— — — — — X — — — — — — — — User Input 1 ➊
— — — — X — — — — — — — — — User Input 2 ➊
— — — X — — — — — — — — — — User Input 3 ➊
— — X — — — — — — — — — — — User Input 4 ➊
— X — — — — — — — — — — — — HOA Status
X — — — — — — — — — — — — — 140M On
Bit Function
14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
— — — — — — — — — — — — — — X Net Output 0
— — — — — — — — — — — — — X — Net Output 1
— — — — — — — — — — — — X — — Net Output 2
— — — — — — — — — — — X — — — Net Output 3
— — — — — — — — — — X — — — — Net Output 4
— — — — — — — — — X — — — — — Net Output 5
— — — — — — — — X — — — — — — Net Output 6
— — — — — — — X — — — — — — — Net Output 7
— — — — — — X — — — — — — — — Net Output 8
— — — — — X — — — — — — — — — Net Output 9
— — — — X — — — — — — — — — — Net Output 10
— — — X — — — — — — — — — — — Net Output 11
— — X — — — — — — — — — — — — Net Output 12
— X — — — — — — — — — — — — — Net Output 13
X — — — — — — — — — — — — — — Net Output 14
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 — — — — — — IO Fault
— — — — — — — — X — — — — — — — Overtemperature
— — — — — — — X — — — — — — — — Over Current
— — — — — — X — — — — — — — — — Dnet Power Loss
— — — — — X — — — — — — — — — — Internal Comm
— — — — X — — — — — — — — — — — DC Bus Fault
— — — X — — — — — — — — — — — — EEprom
— — X — — — — — — — — — — — — — HW Fault
— X — — — — — — — — — — — — — — Restart Retries
X — — — — — — — — — — — — — — — Misc. Fault
3-14 Programmable Parameters for Volts per Hertz Controllers
Bit Warning
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
X Reserved
X Reserved
X Reserved
X Reserved
X Reserved
X Control Power
X IO Warning
X Reserved
X Phase Imbalance
X DeviceNet ➊
X Reserved
X Reserved
X Reserved
X Hardware
X Reserved
X Reserved
Miscellaneous Group
Keypad Mode Parameter Number 45
This parameter selects if the keypad operation is maintained or momentary. Access Rule GET/SET
0 = Maintained
1 = Momentary Data Type BOOL
Group Misc.
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 3 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
ZIP Parameters
AutoRun Zip Parameter Number 67
Access Rule GET/SET
Enables ZIP data production on power up
Data Type BOOL
Group ZIP Parameters
0=Disable
1=Enable Units —
Minimum Value 0
Maximum Value 1
Default Value 0
Display Group
Output Freq Parameter Number 101
Related Parameters 102, 110, 134, 135, 138
Output frequency present at T1, T2, T3.
Access Rule GET
Data Type UINT
Group Display Group
Units 0.1 Hz
Minimum Value 0.0
Maximum Value 240.0 Hz
Default Value Read Only
De
t
era
cel
Speed
r at
Ac
ion
0
Param. Time Param. Minimum Value 0.0
0 139 or 140 or
167 168 Maximum Value 600.0
(Accel (Decel
Time x) Time x)
Default Value 20.0
De
era
cel
era
Speed
Ac
tio
n
➊ To activate 170 (Preset Freq 0) set 138 (Speed Reference) to option 4 Preset Freq 0-3.
Programmable Parameters for Volts per Hertz Controllers 3-41
➊ To activate 170 (Preset Freq 0) set 138 (Speed Reference) to option 4 Preset Freq 0-3.
➋ When a Digital Input is set to Accel 2 & Decel 2, and the input is active, that input overrides the settings in
this table.
ATTENTION
!
• If a hazard of injury due to movement of equipment or
material exists, an auxiliary mechanical braking device
must be used.
Figure 3.1
3-44 Programmable Parameters for Volts per Hertz Controllers
Figure 3.2
100
% Parameter 131 (Motor NP Volts)
4
3
2
1
(Motor NP Hertz)
1/2
Settings
5...14
0 50 100
% Parameter 132 (Motor NP Hertz)
Programmable Parameters for Volts per Hertz Controllers 3-45
Figure 3.4
!
not use this function without considering applicable local,
national, and international codes, standards, regulations, or
industry guidelines.
!
inappropriate application. Do not use this
function without considering applicable local,
national, and international codes, standards,
regulations, or industry guidelines.
3-48 Programmable Parameters for Volts per Hertz Controllers
Notes
Chapter 4
This chapter describes each programmable parameter and its function for
Bulletin 284 Sensorless Vector Controllers.
Parameter Programming Each Distributed Motor Controller type will have a common set of parameters
followed by a set of parameters that pertain to the individual starter type.
4-1
4-2 Programmable Parameters for Sensorless Vector Controllers
Parameter Group Listing The Bulletin 284D ArmorStart contains ten parameter groups. The parameters
shown in the DeviceLogix™, DeviceNet , Starter Protection , User I/O ,
Misc. Parameter , Drive DeviceNet , Display Group, Basic Program, and
Advanced Program will be discussed in this chapter.
.
Programmable Parameters for Sensorless Vector Controllers 4-3
DeviceLogix Group
Hdw Inputs ➊ Parameter Number 1
This parameter provides status of hardware inputs. Access Rule GET
Data Type WORD
Group DeviceLogix
Units —
Minimum Value 0
Maximum Value 15
Default Value 0
Bit Function
3 2 1 0
— — — X Input 0
— — X — Input 1
— X — — Input 2
X — — — Input 3
➊Reserved for Bulletin 284A units.➊This parameter is not available with the Bulletin 284A.
Bit Function
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
— — — — — — — — — — — — — — — X Net Input 0
— — — — — — — — — — — — — — X — Net Input 1
— — — — — — — — — — — — — X — — Net input 2
— — — — — — — — — — — — X — — — Net Input 3
— — — — — — — — — — — X — — — — Net Input 4
— — — — — — — — — — X — — — — — Net Input 5
— — — — — — — — — X — — — — — — Net Input 6
— — — — — — — — X — — — — — — — Net Input 7
— — — — — — — X — — — — — — — — Net Input 8
— — — — — — X — — — — — — — — — Net Input 9
— — — — — X — — — — — — — — — — Net Input 10
— — — — X — — — — — — — — — — — Net Input 11
— — — X — — — — — — — — — — — — Net Input 12
— — X — — — — — — — — — — — — — Net Input 13
— X — — — — — — — — — — — — — — Net Input 14
X — — — — — — — — — — — — — — — Net Input 15
4-4 Programmable Parameters for Sensorless Vector Controllers
Bit Function
14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
— — — — — — — — — — — — — — X Net Output 0
— — — — — — — — — — — — — X — Net Output 1
— — — — — — — — — — — — X — — Net Output 2
— — — — — — — — — — — X — — — Net Output 3
— — — — — — — — — — X — — — — Net Output 4
— — — — — — — — — X — — — — — Net Output 5
— — — — — — — — X — — — — — — Net Output 6
— — — — — — — X — — — — — — — Net Output 7
— — — — — — X — — — — — — — — Net Output 8
— — — — — X — — — — — — — — — Net Output 9
— — — — X — — — — — — — — — — Net Output 10
— — — X — — — — — — — — — — — Net Output 11
— — X — — — — — — — — — — — — Net Output 12
— X — — — — — — — — — — — — — Net Output 13
X — — — — — — — — — — — — — — Net Output 14
Programmable Parameters for Sensorless Vector Controllers 4-5
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 — — — — — — IO Fault
— — — — — — — X — — — — — — — Overtemperature
— — — — — — — X — — — — — — — — Over Current
— — — — — — X — — — — — — — — — Dnet 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 Tripped
— — — — — — — — — — — — — — X — Warning
— — — — — — — — — — — — — X — — Running Fwd
— — — — — — — — — — — — X — — — Running Rev
— — — — — — — — — — — 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 — — — — — — — — — — — — — 140M On
— 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 Exp Cnxn
— — — — — — — — — — — — — — X — IO Cnxn
— — — — — — — — — — — — — X — — Exp Flt
— — — — — — — — — — — — X — — — IO Flt
— — — — — — — — — — — X — — — — IO Idle
— — — — — — — — X X X — — — — — Reserved
— — — — — — — X — — — — — — — — ZIP 1 Cnxn
— — — — — — X — — — — — — — — — ZIP 1 Flt
— — — — — X — — — — — — — — — — ZIP 2 Cnxn
— — — — X — — — — — — — — — — — ZIP 2 Flt
— — — X — — — — — — — — — — — — ZIP 3 Cnxn
— — X — — — — — — — — — — — — — ZIP 3 Flt
— X — — — — — — — — — — — — — — ZIP 4 Cnxn
X — — — — — — — — — — — — — — — ZIP 4 Flt
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 — — — — — — User Out A
X — — — — — — — User Out B
4-8 Programmable Parameters for Sensorless Vector Controllers
DeviceNet Group
Autobaud Enable Parameter Number 10
When this parameter is enabled, the device will attempt to determine the network Access Rule GET/SET
baud rate and set its baud rate to the same, provided network traffic exists. At least
one node with an established baud rate must exist on the network for autobaud to Data Type BOOL
occur. Group DeviceNet
0 = Disable
1 = Enable Units —
Minimum Value 0
Maximum Value 1
Default Value 1
Bit Function
13 12 11 10 9 8 7 6 5 4 3 2 1 0
— — — — — — — — — — — — — X Tripped
— — — — — — — — — — — — X — Warning
— — — — — — — — — — — X — — Running Fwd
— — — — — — — — — — X — — — Running Rev
— — — — — — — — — X — — — — Ready
— — — — — — — — X — — — — — Net Ctl Status
— — — — — — — X — — — — — — Net Ref Status
— — — — — — X — — — — — — — At Reference
— — — — — X — — — — — — — — User Input 1
— — — — X — — — — — — — — — User Input 2
— — — X — — — — — — — — — — User Input 3
— — X — — — — — — — — — — — User Input 4
— X — — — — — — — — — — — — HOA Status
X — — — — — — — — — — — — — 140M On
Programmable Parameters for Sensorless Vector Controllers 4-11
Bit Function
14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
— — — — — — — — — — — — — — X Net Output 0
— — — — — — — — — — — — — X — Net Output 1
— — — — — — — — — — — — X — — Net Output 2
— — — — — — — — — — — X — — — Net Output 3
— — — — — — — — — — X — — — — Net Output 4
— — — — — — — — — X — — — — — Net Output 5
— — — — — — — — X — — — — — — Net Output 6
— — — — — — — X — — — — — — — Net Output 7
— — — — — — X — — — — — — — — Net Output 8
— — — — — X — — — — — — — — — Net Output 9
— — — — X — — — — — — — — — — Net Output 10
— — — X — — — — — — — — — — — Net Output 11
— — X — — — — — — — — — — — — Net Output 12
— X — — — — — — — — — — — — — Net Output 13
X — — — — — — — — — — — — — — Net Output 14
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 — — — — — — IO Fault
— — — — — — — — X — — — — — — — Overtemperature
— — — — — — — X — — — — — — — — Over Current
— — — — — — X — — — — — — — — — Dnet Power Loss ➊
— — — — — X — — — — — — — — — — Internal Comm
— — — — X — — — — — — — — — — — DC Bus Fault
— — — X — — — — — — — — — — — — EEprom
— — X — — — — — — — — — — — — — HW Fault
— X — — — — — — — — — — — — — — Restart Retries
X — — — — — — — — — — — — — — — Misc. Fault
Miscellaneous Group
Keypad Mode Parameter Number 45
This parameter selects if the keypad operation is maintained or momentary. Access Rule GET/SET
0 = Maintained
1 = Momentary Data Type BOOL
Group Misc.
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 3 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
Display Group
Output Freq Parameter Number 101
Output frequency present at T1, T2, T3. Related Parameters 102, 110, 134, 135, 138
Access Rule GET
Data Type UINT
Group Display Group
Units 0.1 Hz
Minimum Value 0.0
Maximum Value 400.0 Hz
Default Value Read Only
!
22 EM Brk Cntrl EM Brake is energized. Program Parameter 260 (EM Brk Off Delay) and Parameter 262 (EM Brk On Delay) for desired
action.
Programmable Parameters for Sensorless Vector Controllers 4-35
Options Output Range Minimum Output Maximum Output Value A066 DIP Switch Position Related
Value (Analog Out High) Parameter
0 OutFreq 0…10 0…10V 0V = 0 Hz P035 (Maximum Freq) 0…10V 101
1 OutCurr 0…10 0…10V 0V = 0 Amps 200% Drive Rated Output Current 0…10V 103
2 OutVolt 0…10 0…10V 0V = 0 Volts 120% Drive Rated Output Volts 0…10V 104
3 OutPowr 0…10 0…10V 0V = 0 kW 200% Drive Rated Power 0…10V 122
4 TstData 0…10 0…10V 0V = 0000 65535 (Hex FFFF) 0…10V 119
5 OutFreq 0…20 0…20 mA 0 mA = 0 Hz P035 (Maximum Freq) 0…20 mA 101
6 OutCurr 0…20 0…20 mA 0 mA = 0 Amps 200% Drive Rated Output Current 0…20 mA 103
7 OutVolt 0…20 0…20 mA 0 mA = 0 Volts 120% Drive Rated Output Volts 0…20 mA 104
8 OutPowr 0…20 0…20 mA 0 mA = 0 kW 200% Drive Rated Power 0…20 mA 122
9 TstData 0…20 0…20 mA 0 mA = 0000 65535 (Hex FFFF) 0…20 mA 119
10 OutFreq 4…20 4…20 mA 4 mA = 0 Hz P035 (Maximum Freq) 0…20 mA 101
11 OutCurr 4…20 4…20 mA 4 mA = 0 Amps 200% Drive Rated Output Current 0…20 mA 103
12 OutVolt 4…20 4…20 mA 4 mA = 0 Volts 120% Drive Rated Output Volts 0…20 mA 104
13 OutPowr 4…20 4…20 mA 4 mA = 0 kW 200% Drive Rated Power 0…20 mA 122
14 TstData 4…20 4…20 mA 4 mA = 0000 65535 (Hex FFFF) 0…20 mA 119
15 OutTorq 0…10 0…10V 0V = 0 Amps 200% Drive Rated FLA 0…10V 129
16 OutTorq 0…20 0…20 mA 0 mA = 0 Amps 200% Drive Rated FLA 0…20 mA 129
17 OutTorq 4…20 4…20 mA 4 mA = 0 Amps 200% Drive Rated FLA 0…20 mA 129
18 Setpnt 0…10 0…10V 0V = 0% 100.0% Setpoint Setting 0…10V 209
19 Setpnt 0…20 0…20 mA 0 mA = 0% 100.0% Setpoint Setting 0…20 mA 209
20 Setpnt 4…20 4…20 mA 4 mA = 0% 100.0% Setpoint Setting 0…20 mA 209
Note: Only output range 0…10V applies with the factory installed A10
option.
Options 5…14, 16, 17, 19, and 20 are not valid options.
De
Group Advanced Program Group
rat
cel
le
era
Speed
ce
Ac
tio
n
0
Param. Time Param. Minimum Value 0.0
0 139 or 140 or
167 168 Maximum Value 600.0
(Accel (Decel
Time x) Time x) Default Value 20.0
De
cel
cel
era
Speed
Ac
tio
0
Param.
0 139 or
Time Param. Minimum Value 0.0
140 or
167 168 Maximum Value 600.0
(Accel (Decel
Time x) Time x) Default Value 20.0
➊ To activate 170 (Preset Freq 0) set 138 (Speed Reference) to option 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.
ATTENTION
!
• If a hazard of injury due to movement of equipment or
material exists, an auxiliary mechanical braking device
must be used.
Figure 4.1
Figure 4.2
100
% Parameter 131 (Motor NP Volts)
4
3
2
1
(Motor NP Hertz)
1/2
Settings
5...14
0 50 100
% Parameter 132 (Motor NP Hertz)
4-42 Programmable Parameters for Sensorless Vector Controllers
Figure 4.3
Parameter 188 (Maximum Voltage)
Parameter 186
(Start Boost)
Figure 4.5
Programmable Parameters for Sensorless Vector Controllers 4-45
!
not use this function without considering applicable local,
national, and international codes, standards, regulations, or
industry guidelines.
!
inappropriate application. Do not use this
function without considering applicable local,
national, and international codes, standards,
regulations, or industry guidelines.
Figure 4.6
Parameter 135
[Maximum Freq]
e
e nc
fer
d Re
ee
Sp
Parameter 134
[Minimum Freq]
0
0
Parameter 210 Parameter 211
[Anlg In 0-10V Lo] [Anlg In 0-10V Hi]
Figure 4.7
Table 4.H
Options Description
0 Disabled (Default)
1 Fault (F29) F29 Analog Input Loss
2 Stop Uses P037 (Stop Mode)
3 Zero Ref Drive runs at zero speed reference
4 Min Freq Ref Drive runs at minimum frequency
5 Max Freq Ref Drive runs at maximum frequency
6 Int Freq Ref Drive runs at internal frequency
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.
!
and/or equipment damage, it is recommended that the
motor be disconnected from the load before proceeding.
Parameters 240…247 are only active if 138 (Speed Reference) is set to 6 Stp
Logic.
Digits 0…3 for each (Stp Logic x) parameter must be programmed according
to the desired profile.
The speed for any step is programmed using Parameters 170…177 (Preset
Freq x).
Table 4.I
Step Logic Parameter Related Preset Frequency Related Step Logic Time
(Active when 138 = 6 Stp Parameter (Can be activated Parameter (Active when
Logic) independent of Step Logic 240…247 Digit 0 or 1 are set to
Parameters) 1, b, C, d, or E)
240 (Stp Logic 0) 170 (Preset Freq 0) 250 (Stp Logic Time 0)
241 (Stp Logic 1) 171 (Preset Freq 1) 251 (Stp Logic Time 1)
242 (Stp Logic 2) 172 (Preset Freq 2) 252 (Stp Logic Time 2)
243 (Stp Logic 3) 173 (Preset Freq 3) 253 (Stp Logic Time 3)
244 (Stp Logic 4) 174 (Preset Freq 4) 254 (Stp Logic Time 4)
245 (Stp Logic 5) 175 (Preset Freq 5) 255 (Stp Logic Time 5)
246 (Stp Logic 6) 176 (Preset Freq 6) 256 (Stp Logic Time 6)
247 (Stp Logic 7) 177 (Preset Freq 7) 257 (Stp Logic Time 7)
The step logic sequence begins with a valid start command. A normal
sequence always begins with 240 (Stp Logic 0).
Digit 0: Logic For Next Step — This digit defines the logic for the next step.
When the condition is met the program advances to the next step. Step 0
follows Step 7. Example: Digit 0 is set 3. When Logic In2 becomes active, the
program advances to the next step.
Digit 1: Logic to Jump to a Different Step — For all settings other than F,
when the condition is met, the program overrides Digit 0 and jumps to the
step defined by Digit 2.
Digit 2: Different Step to Jump — When the condition for Digit 1 is met,
the Digit 2 setting determines the next step or to end the program.
Digit 3: Step Settings — This digit defines what accel/decel profile the speed
command will follow and the direction of the command for the current step.
In addition, if a relay or opto output (Parameters 155, 158, and 161) is set to 15
StpLogic Out, this parameter can control the status of that output.
The logic for each function is determined by the four digits for each step logic
parameter. The following is a listing of the available settings for each digit.
Refer to Appendix H for details.
Frequency
mp
ce
Ac
De
ce
mp
l
Ra
Minimum Freq
Time
Start EM Brk Stop EM Brk Drive Stops
Commanded Energized (Off) Commanded De-Energized (On)
Notes:
Chapter 5
Keypad Description The keys found on the optional HOA keypad are described below.
5-1
5-2 HOA Keypad Operation
Table 5.B
HAND STOP HAND FWD HAND REV JOG FWD JOG REV AUTO
If (FWD LED) If (FWD LED) If (FWD LED) Ignore Ignore Ignore
Set REV LED Set REV LED Set REV LED
Else If (REV LED) Else If (REV LED) Else If (REV LED)
Set FWD LED Set FWD LED Set FWD LED
If (FWD LED) Ignore Ignore Ignore Ignore Ignore
transition to
JOG FWD
If (REV LED)
Transition to
JOG REV
Command motor Ignore Ignore Ignore Ignore Ignore
off and
Transition to
AUTO
If (FWD LED) Ignore Ignore Ignore Ignore Ignore
transition to
HAND FWD
Else If (REV LED)
Transition to
HAND REV
No Key Ignore Ignore Ignore Command motor Command motor Ignore
Pressed off and transition off and transition
to HAND STOP to HAND STOP
Ignore Command motor Command motor Command motor Command motor Command motor
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
HOA Keypad Operation 5-3
Table 5.C
HAND STOP HAND FWD HAND REV JOG FWD JOG REV AUTO
No Key Ignore Command motor Command motor Command motor Command motor Ignore
Pressed off and transition off and transition off and transition off and transition
to HAND STOP to HAND STOP to HAND STOP to HAND STOP
If (FWD LED) Ignore Ignore Ignore Ignore Ignore
Set REV LED
Else If (REV LED)
Set FWD LED
If (FWD LED) Ignore Ignore Ignore Ignore Ignore
transition to
JOG FWD
If (REV LED)
Transition to
JOG REV
Command motor Ignore Ignore Ignore Ignore Ignore
off and
Transition to
AUTO
If (FWD LED) Ignore Ignore Ignore Ignore Ignore
transition to
HAND FWD
If (REV LED)
Transition to
HAND REV
Ignore Command motor Command motor Command motor Command motor Command motor
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
Keypad Disable and HOA Parameter 46, Keypad Disable, disables the HAND, JOG, and Dir Arrow
buttons on the HOA keypad. The OFF and AUTO buttons are always
enabled, even if Parameter 46 is set to 1 = disable.
Note: In nearly all instances, if the processor detects multiple buttons are
pressed at the same time, 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 other buttons, the processor will interpret this as the same as if the
OFF button were pressed by itself.
5-4 HOA Keypad Operation
Notes:
Chapter 6
DeviceNet™ Commissioning
This chapter refers to the Bulletin 284D products. Refer to Chapter 8 for
commissioning the Bulletin 284A products.
Establishing a DeviceNet The ArmorStart® is shipped with a default node address of 63 and Autobaud
enabled. Each device on a DeviceNet network must have a unique node
Node Address address or MAC ID which can be set to a value 0…63. Keep in mind that
most DeviceNet systems use address 0 for the master device (Scanner) and
node address 63 should be left vacant for introduction of new slave devices.
The ArmorStart offers two methods for node commissioning as shown below.
The node address for a device can be changed using software or by setting
hardware switches that reside on the back of the control module.While both
methods yield the same result, it is good practice to choose one method and
deploy it throughout the system.
The ArmorStart is shipped with the rotary dials set to a value of (99). If the
switches are set to a value (64) or above, the device will automatically
configure itself to the software node address. If the switches are set to a value
of (63) or less, the device will be at the node address designated by the switch
configuration.
!
parameters.
6-1
6-2 DeviceNet™ Commissioning
To set an address using the hardware rotary dials, simply set the switches to
the desired node address and cycle power to the unit. The Device will restart at
the new address.
LSD
MSD
Node Commissioning Using Software
To set the node address of the ArmorStart using software or other handheld
tools, leave the hardware switches in their default position (99) or insure that
they are set to something greater then (63). With the hardware switches set, use
the software or handheld tool to change the address.
DeviceNet™ Commissioning 6-3
3. Click OK.
5. RSNetWorx will now browse the network and display all of the nodes it
has detected on the network. For some versions of RSNetWorx
software the ArmorStart EDS files and icon may not be included and
will show up as an Unregistered Device. If the screen appears like the
example below, continue with Building and Registering an EDS File on
page 6-4.
Figure 6.2
Building and Registering an The EDS file defines how RSNetWorx for DeviceNet will communicate to the
ArmorStart. Follow the steps below to register an EDS file. To register a
EDS File device you must first obtain the EDS file from the following web page:
http://www.ab.com/networks/eds.
Figure 6.3
3. Choose Register an EDS file(s) as shown above and then click the Next
button.
DeviceNet™ Commissioning 6-5
4. Choose to Register a Single File and specify the file name or use the
Browse button to locate the EDS file on your computer. If connected
to the Internet you may use the Download EDS file button to
automatically search for the correct EDS file.
Figure 6.4
Figure 6.5
8. When asked if you would like to register this device, click the Next
button.
9. Click the Finish button. After a short while RSNetWorx will update your
online screen by replacing the Unrecognized Device with the name and
Icon given by the EDS file you have just registered.
Using the Node 1. Choose Node Commissioning from the Tools menu at the top of the
screen.
Commissioning Tool Inside
RSNetWorx for DeviceNet
DeviceNet™ Commissioning 6-7
Figure 6.6
Figure 6.7
3. Select the ArmorStart located at node 63, and then click OK. The Node
Commissioning screen will have the Current Device Settings entries
completed. It will also provide the current network baud rate in the New
ArmorStart Settings area. Do not change the baud rate unless you
absolutely sure that this value needs to be changed.
4. Enter the desired Node Address in the New Device Settings section. In
this example, the new node address will be 5. Click Apply to apply the
new node address.
6-8 DeviceNet™ Commissioning
5. When the new Node Address has been successfully applied, the Current
Device Settings section of the window will be updated as follows. If an
error occurs, check to make sure the device is properly powered up and
connected to the network.
Figure 6.8
System Configuration Produced and Consumed I/O Assemblies (sometimes referred to as Input and
Output Assemblies) define the format of I/O message data that is exchanged
Information between the ArmorStart and other devices on the network. The consumed
information is generally used to command the state of its outputs, and
produced information typically contains the state of the inputs and the current
fault status of the device.
The default Consumed and Produced assemblies are shown below. For
additional formats refer to Electronic Data Sheets, page B-1. The ArmorStart
default configuration varies depending on the type of starter.
DeviceNet™ Commissioning 6-9
Choosing the size and format of the I/O data that is exchanged by the
ArmorStart is done by choosing a Produced or Consumed Assembly instance
number. These instance numbers are written to the Produced IO Assy or
Consumed IO Assy parameters. The different instances/formats allow for
user programming flexibility and network optimization.
Using Automap Feature The Automap feature available in all Rockwell Automation scanners will
automatically map the information as shown below. If manual mapping is
with Default Input and required, the information below can be used to map a device based on the
Output (I/O) Assemblies default configuration.
The I/O assembly formats for the ArmorStart are identified by the values in
Parameter 11 (Consumed IO Assy.) and Parameter 12 (Produced IO Assy.).
These values determine the amount and arrangement of the information
communicated to and from the master scanner. The Tables 6.B and 6.C
identify the default information produced and consumed by the Bulletin 284
devices. For additional formats and advance configurations, refer to Table B.K
on page B-6:
6-10 DeviceNet™ Commissioning
Table 6.B Instance 164 — Default Consumed Inverter Type Distributed Motor
Controller (4 bytes)
Table 6.C Instance 165 Default Produced Inverter Type Distributed Motor Controller
(4 bytes)
Setting the Motor OL The product should now be configured and communicating on the network.
The last step is to program the Motor OL Current setting (Parameter# 133).
Current This can be accomplished by using software such as RSNetWorx for
DeviceNet or a handheld DeviceNet tool.
Using the software, access the device parameters screen as shown below.
Notice that by default the Motor OL Current is set to the minimum setting for
the device.
Notes:
Chapter 7
Logic Controller This chapter is designed to demonstrate programming and explicit message
examples for both the SLC™ family of programmable controllers and
Application with Explicit ControlLogix® family of programmable controllers. The examples will show
Messaging how to develop a program for simple control and use a simple explicit message
to retrieve data that is not automatically acquired based on the input and
output assembly of the device. The user of the device can use this example as a
guide in developing, their own programs.
Below is the RSNetWorx™ view of the simple network used in this example.
To assist in the development of the example the network will consist only of
the ArmorStart® and scanner. Therefore the only mapped information in the
scanner will be the ArmorStart. Refer to Chapter 6, DeviceNet™ Commissioning
for assistance in mapping.
Programming the Cat. The following example will utilize the Standard Distributed Motor Controller
and the factory default input and output assembly of 165 and 164. Refer to
No. 1747-SLC™ I/O Mapping Appendix B for additional assembly formats. The default input and output
assembly are shown in Table 7.A with the corresponding data size.
7-1
7-2 Explicit Messaging on DeviceNet™
If a different I/O assembly is selected the data size may change. It is important
to understand that the I/O assembly selected here will directly affect the Input
and Output mapping in the scanners scan-list and the amount of PLC™
memory reserved for this information.
Instance 164 — Default Consumed Inverter Type Distributed Motor Controller (4 bytes)
Byte 0 Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
Address O:1.23 O:1.22 O:1.21 O:1.20 O:1.19 O:1.18 O:1.17 O:1.16
Data User Out B User Out A — Jog Rev Jog Fwd Fault Reset Run Rev Run Fwd
Byte 1 Bit 15 Bit 14 Bit 13 Bit 12 Bit 11 Bit 10 Bit 9 Bit 8
Address O:1.31 O:1.30 O:1.29 O:1.28 O:1.27 O:1.26 O:1.25 O:1.24
Data Drive In 4 Drive In 3 Drive In 2 Drive In 1 Decel 2 Decel 1 Accel 2 Accel 1
Enable Enable Enable Enable
Byte 2 Bit 23 Bit 22 Bit 21 Bit 20 Bit 19 Bit 18 Bit 17 Bit 16
Address O:1.39 O:1.38 O:1.37 O:1.36 O:1.35 O:1.34 O:1.33 O:1.32
Data Comm Frequency Command (Low)
Byte 3 Bit 31 Bit 30 Bit 29 Bit 28 Bit 27 Bit 26 Bit 25 Bit 24
Address O:1.47 O:1.46 O:1.45 O:1.44 O:1.43 O:1.42 O:1.41 O:1.40
Data Comm Frequency Command (High)
The example PLC™ program for the SLC will utilize the Tripped and the
140M On bit from the produced assembly and the Fault Reset, User Out A,
and Run Fwd bit from the consumed assembly.
Explicit Messaging on DeviceNet™ 7-3
Explicit Messaging with The Cat. No. 1747-SDN module uses the M0 and M1 file areas for data
transfer. Only words 224…256 are used to execute the Explicit Message
SLC Request and Response function. The minimum data size for the explicit
message request is six words and the maximum is 32 words. Tables 7.D and
7.E illustrate the standard format of the explicit message request and response.
Command — This code instructs the scanner how to administer the request.
A listing of these codes can be found in the Cat. No. 1747-SDN User Manual,
Publication 1747-5.8. The Command data size is one byte.
Status — The Status code provides the communication module’s status and
its response.
Size — This identifies the size of the transaction body in bytes. The
transaction body begins at word 3. The maximum size is 58 bytes. The Size
data size is one byte.
Service — This code specifies the type of request being delivered. The Service
data size is one byte.
MAC ID — The DeviceNet network node address of the device for which
the transaction is intended is identified here. The slave device must be listed in
the scanner module’s scan list and be on-line for the Explicit Message
transaction to be completed.
Instance — This code identifies the specific instance within the object class
towards which the transaction is directed. The value zero is reserved to denote
that the transaction is directed towards the class itself versus a specific instance
within the class.
Setting up the Data File Table 7.F lists the most common transaction types (get information and set
information), and the appropriate Service, Class, Instance, and attribute that
corresponds to the type.
Sequence of Events Use the following sequence of events as a guide for establishing explicit
messages in your SLC ladder logic.
1. Put the Explicit Message Request data into an integer (N) file of the
SLC-500 processor.
2. Use the file copy instruction (COP) to copy the Explicit Message
Request data entered in Step 1 to the M0 File, words 224…256.
4. Copy the data from the M1 file, words 224…256, into a file in the
SLC-500 processor using the file copy instruction (COP).
The following example shows the exact data format to perform a Get
Attribute Single request. This message will specifically access Parameter 104,
Output Voltage. The first three words are shown segmented into two bytes,
corresponding to the upper and lower bytes shown in the Explicit Message
Request table (refer to Table 7.D).
WD2 Writer Designed tag 2SLC Example of Ladder Logic Program, Continued
Note: The addressing is different between the SLC 1747 and ControlLogix
1756 program. It is important that the user understand how to create and use
tags in order to properly follow the example. See the RSLogix™ 5000
programming manual for additional help with defining tags.
7-8 Explicit Messaging on DeviceNet™
Tables 7.I and 7.J list the data configuration for the ControlLogix platform and
include the Tag Name as used in the example program.
Explicit Messaging with The ControlLogix platform requires significantly less structure to initiate an
explicit message. The explicit message Request and Response is configured
ControlLogix within the MSG function. The MSG function can be found in the
Input/Output tab of RSLogix 5000. Notice that in the ControlLogix program
example, rung 6 is the only required logic to complete the explicit message
request.
Figure 7.3
Setting Up the MSG 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
Instruction explicit_mess. After the instruction has been named, click on the gray box
to define the rest of the instruction.
The following example shows the exact data format to perform a Get
Attribute Single request. This message will specifically access Parameter 104,
Output Voltage. See Table 7.F, Common Configuration Examples for
ArmorStart, for additional configurations.
7-10 Explicit Messaging on DeviceNet™
Message Type — Select CIP Generic from pull down menu to configure an
explicit message.
Destination Element — This is the tag name of the location you are going to
place the response information. In this example a tag was created with the
name explicit_data.
Service Type — The pull down menu has several options, however only the
Get Attribute Single is used for this example.
The Class, Instance, and Attribute define the actual information being
requested. Additional configurations of these parameters can be found in
Appendix B.
After the above information has been entered, click on the communication
tab.
Path — The path will define the route the message will take to get to the
device it is intended for. In this example the path is Scanner,2,4; where scanner
is the name of the Cat. No. 1756-DNB in the rack, 2 represents the DeviceNet
port, and 4 represents the physical node address of the ArmorStart.
Using DeviceLogix™
• If both overrides are disabled and the logic is enabled, the only time
DeviceLogix will drive the state of outputs, 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 will be running the logic, but will not control the
status of the outputs.
• If the Network Override is enabled and the logic is enabled then
DeviceLogix controls the state of the outputs when the PLC™ is in Run
mode and if a network fault such as Duplicate MAC ID or Module Bus
Off condition occurs.
• If the Communications Override is enabled and the logic is enabled, the
device does not need any I/O connection to run the logic. As long as
there is control power and a DeviceNet power source connected to the
device, the logic will control the status 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.
8-1
8-2 Using DeviceLogix™
There are many reasons to use the DeviceLogix functionality, but some of the
most common are listed below:
Example
The following example will show how to program a simple logic routine to
interface the ArmorStart with a remote hard-wired start-stop station. In this
case the I/O is wired as shown in the table.
Table 8.A Hardware Bit Assignments and Description for the ArmorStart
2. Click on the DeviceLogix tab. If you are on-line with a device, a dialog
box will appear asking you to upload or download. Click on Upload.
6. Move the cursor into the grid, and left-click to drop the function onto
the grid.
7. From the toolbar, click on the Discrete Input button and select
Input 0 from the pull-down menu. This is the remote start button based
on the example I/O table.
8. Place the input to the left of the RSL function. To drop the input on the
page, left-click on the desired position.
9. Place the mouse cursor over the tip of Input 0. The tip will turn green.
Click on the tip when it turns green.
8-4 Using DeviceLogix™
10. Move the mouse cursor toward the input of the RSL function. A line
will follow the cursor. When a connection can be made, the tip of the
RSL function will also turn green. Click the on Input and the line will be
drawn from Input 0 to the Set Input of the RSL function.
Note: If this was not a valid connection, one of the pin tips would have
turned red rather than green. Left-double-clicking on the unused
portion of the grid or pressing the Esc key at any time will cancel the
connection process.
Figure 8.1
11. From the toolbar, click on the Discrete Input button and select
Input 1 from the pull-down menu. This is the remote stop button based
on the example I/O table.
13. Connect the input to the reset input of the RSL latch.
Figure 8.2
Using DeviceLogix™ 8-5
14. From the toolbar, click on the Discrete Output button and select Run
Fwd from the pull-down menu. Click OK.
15. Move the cursor into the grid and place the Output to the right of the
RSL function block.
16. Connect the output of the RSL function block to Run Fwd.
Figure 8.3
17. Click on the Verify button located in the toolbar or select Logic Verify
from the Tools pull-down menu.
18. Click on the Edit button to toggle out of edit mode if online with a
device.
19. Go to the pull-down menu in the right corner of the toolbar and select
Download.
Note: Ensure that the PLC key switch is in the Program position. If in
any other position, the download will not occur and an error will be
generated.
21. Now from the same pull-down menu select Logic Enable On.
Notes:
Chapter 9
Figure 9.1 Connectivity Diagram for one ArmorStart Distributed Motor Controller
9-1
9-2 ArmorStart® to ArmorPoint® Connectivity
Figure 9.2 Connectivity Diagram for two ArmorStart Distributed Motor Controllers
!
parameters.
Theory of Operation
It is possible to connect an ArmorStart product to the Point I/O based subnet
of the ArmorPoint I/O system. This allows the ArmorStart to be connected to
EtherNetIP and ControlNet, along with the original DeviceNet. The easiest
way to program these ArmorStarts is to use RSNetWorx for DeviceNet
software, bridging through the appropriate network. This ladder logic has
been developed as an alternate method of configuration.
Once a system wide read is done, the raw data of the individual parameters in
the data array can be modified and a system wide write function activated from
a bit in the ladder logic. Only parameters that changed will be written to the
ArmorStart devices, and after a write is done the parameter is read back and
stored in the data array for comparison. If the write and reread value do not
match, an Error Report is generated.
If an error occurs for any reason, during a system wide read or write, an error
report will be logged, containing the device and parameter it occurred on. Also
the status and extended status of the message block is logged in case the error
originated there.
The only configuration that the user needs to be concerned with for the
ArmorPoint communication adapter is either the EtherNet IP address or the
ControlNet node address.
ArmorStart® to ArmorPoint® Connectivity 9-5
Since there currently is no profile for an ArmorStart device in the I\O Tree,
the 1738-MODULE profile needs to be used as a generic profile. The standard
configuration for an ArmorStart 284A, using this profile is shown below.
Note: The Logix memory that contains the structure will also
change size proportionally.
9-6 ArmorStart® to ArmorPoint® Connectivity
Shown below is the array size that will also need to be changed to match the
Armor_Start_System.Max_Devices value.
It is to the users best advantage to trim the structures down to the minimum
values that match their system because this will save a considerable amount of
Logix processor memory. However, some room should be left in the
structures to handle any future additions of ArmorStart devices to the system.
ArmorStart® to ArmorPoint® Connectivity 9-7
Once the three major System level parameters are entered, it is up to the user
to enter in, each of the ArmorStart devices configuration information. These
parameters are defined by the slot in the Logix chassis where the EtherNetIP
or ControlNet communication card resides. The next parameter is the
EtherNetIP IP or ControlNet node address of the 1738 communication
adapter containing the ArmorStart. Lastly, the slot number on the ArmorPoint
subnet where the ArmorStart is connected also needs to be entered. An
optional parameter is a string that can be entered with a description of the
function of the ArmorStart device. Each device will be configured by entering
its data into a different block of the Armor_Start_System.Device[] array.
The Following shows the configuration for a communication card in the Logix
chassis 2, AENT IP address 192.168.1.10 and Point I/O slot 3. The logic
determines whether the network is EtherNetIP or ControlNet depending on
whether the ENET_IP_Addr field is blank or the CNET_Address is zero. One
of these two fields must be filled out for the logic to work correctly. The
Armor_Descriptor field is optional and is used to more easily identify the
ArmorStart as to its function in the system.
Note: To easily edit an ASCII string, click on the string value field
and a small icon with three dots appears.
Click on the three dots icon and a String Browser box appears. Modify the text
to what is desired and click on Apply, then click on OK. This works for ALL
strings throughout the entire data array.
The value to be modified is the .data element of the structure. For reference,
the Min_value, Max_value, and Name_String for the parameter is also in
the structure, so that the user knows what the minimum and maximum
allowable values are for the data. It is important to realize that the data is in a
raw format. In other words, this data could be considered a Boolean, a bit
mask, an ASCII string, an integer, a byte, etc., depending on the definition of
the parameter in the ArmorStart. Also, there could be an implied decimal
point, scaling, and different units involved. It is important that the user fully
understand and verify the raw data value being modified with the user
manual, so that it is correctly interpreted by the ArmorStart or undesired
operation in the ArmorStart may occur.
Once the data is written, during a System Wide Write function, the ladder logic
will read it back and put into the .Last_Read_Value of the structure. This will
be a handy visual verification that the data was written correctly.
Once the system configuration has been done, a System Wide Read must be
initiated. The logic to trigger both a System Wide Read and Write is contained
in a subroutine called Handle_All_Armor. The rungs are shown below for
reference.
9-10 ArmorStart® to ArmorPoint® Connectivity
The first element of this structure is .Local_Error and will contain a number
corresponding to an error interpretation. The error numbers are described in
the next table.
Notes
Chapter 10
ArmorStart® ZIP Configuration
Overview This chapter describes the steps necessary to configure the Zone
Interlocking Parameters (ZIP) to configure peer-to-peer
communication between an ArmorStart and another ZIP enabled
device such as another ArmorStart or a 1977-ZCIO module. First, an
overview of the ZIP parameter set is presented. Then the steps
necessary to enable peer-to-peer data production are described. Next,
the steps necessary to enable peer-to-peer data consumption are
described. Finally, the steps necessary to map the consumed peer-to-
peer data to the DeviceLogix™ data table for use in local logic are
described.
ZIP Parameter Overview Each ArmorStart can consume ZIP data from up to 4 other devices.
The 4 devices are referred to as “zones” of data and these zones are
numbered from 1 to 4. The following parameters are used to
configure a device for ZIP peer-to-peer communication:
10-2 ArmorStart® ZIP Configuration
Data Production In a typical ZIP system, each device on the network automatically
produces IO data using “Change of State” (COS) triggering. The
automatic production of this COS data by an ArmorStart is enabled
by setting Parameter 67 (AutoRun ZIP) to a value of 1 = Enable.
Then COS data will be produced automatically when the global ZIP
enable parameter (Zone Ctrl Enable, Parameter 99) is set to the value
of 1 = Enable. Data production will take place at a rate specified by
Parameter 68 (Zone ProducedEPR). The minimum period between
Change of State productions is determined by the value of Parameter
68 (Zone ProducedPIT)
Data Consumption In the ArmorStart data from up to 4 other devices can be consumed
for use in the local logic. The 4 devices whose data is to be consumed
are logically referred to by zone number, i.e. zones 1 – 4. To
configure an ArmorStart to consume data from another node on the
network, the node address or “MacId” is placed in the proper “Zone
MacId” parameter (parameters 70-73). For example to configure an
ArmorStart to consume data for zone 1 from node number 11 on the
network, the value 11 is placed in Parameter 70 (Zone #1 MacId).
Mapping Consumed Data to the Consumed data for the 4 zones is placed in an 8 byte section of the
DeviceLogix Data Table. DeviceLogix Data Table. Individual bits in this section of the
DeviceLogix Data Table can be used in DeviceLogix programs. The
table below shows the organization of the 8 bytes of the data table
Instance 163 Standard Produced Starter with Network Outputs and ZIP CCV
Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
1 Ready Running Rev Running Fwd Warning Tripped
2 140M On HOA User In 4 User In 3 User In 2 User In 1
3 Net Out 8 Net Out 7 Net Out 6 Net Out 5 Net Out 4 Net Out 3 Net Out 2 Net Out 1
4 Net Out 15 Net Out 14 Net Out 13 Net Out 12 Net Out 11 Net Out 10 Net Out 9
5 Device Value Key (low)
6 Device Value Key (high)
The user can choose to place only bytes 1 and 2 of the above
consumed data in the DeviceLogix Data Table by selecting a Zone
Mask value of 00000011 binary as shown in the following
RSNetWorx™ for DeviceNet™ screen:
ZIP Example
Consider the following network with 4 ArmorStarts and a 1799-ZCIO module.
10-6 ArmorStart® ZIP Configuration
For the 1799-ZCIO module (shown below) this is done by setting parameter 13 “AutoRun Zip” to “Enabled”.
We will set the “Zone Masks” to the value of 00000011 binary. This
tells each zone to map bytes 1 and 2 to the DeviceLogix Data Table.
ArmorStart® ZIP Configuration 10-9
We will set the “Zone Offsets as shown below. This maps zone 1 data
to byte 0 of the DeviceLogix Data Table, zone 2 data to byte 2 of the
DeviceLogix Data Table, zone 3 data to byte 4 of the DeviceLogix
Data Table and zone 4 data to byte 6 of the DeviceLogix Data Table.
Instance 163 Standard Produced Starter with Network Outputs and ZIP CCV
Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
1 Ready Running Rev Running Fwd Warning Tripped
2 140M On HOA User In 4 User In 3 User In 2 User In 1
3 Net Out 8 Net Out 7 Net Out 6 Net Out 5 Net Out 4 Net Out 3 Net Out 2 Net Out 1
4 Net Out 15 Net Out 14 Net Out 13 Net Out 12 Net Out 11 Net Out 10 Net Out 9
5 Device Value Key (low)
6 Device Value Key (high)
And assuming that the 1799-ZCIO module is producing the following
data:
Finding ZIP bits in the DeviceLogix The 64 ZIP bits are available for use in DeviceLogix programs in the
Editor list of “Network Input Points”.
Network
Input Points
Diagnostics
This chapter describes the fault diagnostics of the Bulletin 284 ArmorStart®
Distributed Motor Controller. Further, this section describes 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, refer to Chapter 3,
Programmable Parameters for Volts per Hertz Controllers, and Chapter 4,
Programmable Parameters for Sensorless Vector Controllers.
Fault Display The ArmorStart Distributed Motor Controller comes equipped with a built-in
LED status indication which provides four status LEDs and a Reset button.
The LEDs provides status indication for the following:
11-1
11-2 Diagnostics
IMPORTANT Resetting the fault will not correct the cause of the fault
condition. Corrective action must be taken before resetting
the fault.
Clear Fault You may clear a fault using the following methods:
Fault Codes Table 11.A provides a complete reference of the Fault LED indications for
Bulletin 284 ArmorStart Distributed Motor Controllers.
Fault Definitions 140M Trip — 140M Trip indicates that the Bulletin 140M Motor Protector
has tripped. The Fault LED will flash a one-blink pattern. This fault cannot be
disabled.
Overload Trip — The load has drawn excessive current and based on the
overload trip class selected, the device has tripped. The Fault LED will flash a
two-blink pattern. This fault cannot be disabled.
Phase Short — Indicates the drive has detected a phase short. The Fault LED
will flash a three-blink pattern. This fault cannot be disabled.
Ground Fault — Indicates the drive has detected a ground fault. The Fault
LED will flash a four-blink pattern. This fault cannot be disabled.
Stall — Indicates the drive has detected a stall condition, indicating the motor
has not reached full speed. The Fault LED will flash a five-blink pattern. This
fault cannot be disabled.
Over Current — Indicates the drive has detected an over current fault. The
Fault LED will flash a nine-blink pattern. This fault cannot be disabled.
DeviceNet™ Power Loss — DeviceNet power has been lost or has dropped
below the 12V threshold. The Fault LED will flash a 10-blink pattern.
DC Bus Fault — Indicates the drive has detected a DC Bus Fault. The Fault
LED will flash a 12-blink pattern. This fault cannot be disabled.
Restart Retries — This fault is generated when the drive detects that the auto
retries count has been exceeded. The Fault LED will flash a 15-blink pattern.
This fault cannot be disabled.
Troubleshooting
!
actuation of controlled industrial equipment may cause
death or serious injury. For safety of maintenance
personnel as well as others who might be exposed to
electrical hazards associated with maintenance activities,
follow the local safety related work practices (for example,
the NFPA70E, Part II in the United States). Maintenance
personnel must be trained in the safety practices,
procedures, and requirements that pertain to their
respective job assignments.
!
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.
!
drive, ensure 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.
12-1
12-2 Troubleshooting
!
implement the installation, startup, and subsequent
maintenance of the system. Failure to comply may result in
personal injury and/or equipment damage.
!
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, refer to Allen-Bradley
Publication 8000-4.5.2, Guarding against Electrostatic Damage,
or any other applicable ESD protection handbook.
!
or application errors, such as undersizing the motor,
incorrect or inadequate AC supply, or excessive ambient
temperatures may result in malfunction of the system.
Fault Definitions Some of the Bulletin 284 ArmorStart Distributed Motor Controller faults are
detected by the internal hardware of the ArmorStart, while others are detected
by the internal drive. For internal drive faults, the internal hardware of the
ArmorStart simply polls the drive for the existence of faults and reports the
fault state. No fault latching is done by the internal hardware of the
ArmorStart for these faults. The Pr FltReset Mode parameter (Parameter 23)
determines the Auto Resettability of only the faults that are detected on the
main control board. These faults are listed as “param 23” autoresettable in
12.A. The Auto Resettability of the faults that are detected in the internal drive
is controlled by internal drive parameters. These faults are listed as drive
controlled in 12.A.
Troubleshooting 12-3
Figure 12.1
Yes
Faulted Display
No
Fault Network
LED LED Define Nature
of Problem
Motor
a rtr
will not
Start
See Common
Symptoms
See See and
Table 11.A Table 11.B Corrective Actions
12-4 Troubleshooting
DeviceNet™ Table 12.B identifies possible causes and corrective actions when
troubleshooting DeviceNet related failures using the NETWORK STATUS
Troubleshooting LED.
Procedures
Table 12.B DeviceNet Troubleshooting Procedures
Network Definition Possible
Status Causes
LED
Off The device has not completed the initialization, is not on an active Check to make sure the product is properly wired and configured
network, or may not be powered up. on the network.
Flashes While waiting to detect the network baud rate, the LED will flash If the product stays in this state, it means that there is no set baud
green-red- this pattern about every 3 seconds. rate. Ensure that at least one device on the network has a set baud
off rate.
Solid The device is operating in a normal condition, and is No action required.
Green communicating to another device on the network.
Flashing The device is operating in a normal condition, and is on-line, but The device may need to be mapped to a master scanner, placed in
Green has no connection to another device. This is the typical state for a scanlist, or have another device communicate to it.
new devices.
Flashing Recoverable fault has occurred. Check to make sure the PLC™ and scanner are operating
Red correctly and that there are no media/cabling issues. Check to see
if other networked devices are in a similar state.
Solid Red The device has detected a major error that has rendered it Troubleshooting should be done to ensure that the network is
incapable of communicating on the network (Duplicate MAC ID, correct (terminators, lengths, etc.) and there is not a duplicate
Bus-off, media issue). node problem. If other devices on the network appear to be
operating fine and power cycling the device does not work, contact
Technical Support.
Flashing The device has detected a network access error and is in a This is not a common state for DeviceNet products. Power cycling
Red and communication faulted state. The device has subsequently the device may resolve the problem; however, if the problem
Green received and accepted an Identify Communication Faulted Request continues, it may be necessary to contact technical support.
Long Protocol message.
12-6 Troubleshooting
ArmorPoint® Backplane Table 12.C identifies possible causes and corrective actions when
troubleshooting ArmorPoint Backplane failures using the NETWORK
Troubleshooting STATUS LED.
Procedures
Table 12.C ArmorPoint Backplane Troubleshooting Procedures
Network Definition Possible
Status Causes
LED
Off The device has not completed the initialization, is not on an active Check to make sure the product is properly wired and configured
network, or may not be powered up. on the network.
Flashes While waiting to detect the network baud rate, the LED will flash If the product stays in this state, it means that there is no set baud
green-red- this pattern about every 3 seconds. rate. Ensure that at least one device on the network has a set baud
off rate.
Solid The device is operating in a normal condition, and is on-line, but No action required
Green has no connection to another device.
Flashing The ArmorPoint module cannot successfully establish a connection The wrong connection parameter for the ArmorStart was entered
Green on the backplane. in the “Module Properties” page in RS Logix 5000 or the I/O Tree
was not properly configured.
Flashing The ArmorPoint module has stopped communicating over the Check control power connections to the ArmorPoint Module and
Red backplane with ArmorStart. ArmorStart.
Solid Red Backplane media issue. Check backplane media and ArmorStart backplane cable
connections.
Flashing The device is in a communication faulted state. Power cycling the device may resolve the problem; however, if the
Red and problem continues, it may be necessary to contact Technical
Green Support.
Troubleshooting 12-7
Internal Drive Faults A fault is a condition that stops the drive. There are two fault types.
Type Description
1 Auto-Reset/Run
When this type of fault occurs, and Parameter 192 (Auto Rstrt Tries) Related
Parameter(s): 155, 158, 161, 193 is set to a value greater than 0, a
user-configurable timer, Parameter 193 (AutoRstrt Delay) Related Parameter(s):
192, begins. When the timer reaches zero, the drive attempts to automatically
reset the fault. If the condition that caused the fault is no longer present, the fault
will be reset and the drive will be restarted
2 Non-Resettable
This type of fault may require drive or motor repair, or is caused by wiring or
programing errors. The cause of the fault must be corrected before the fault can
be cleared.
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 are not resettable.
12-8 Troubleshooting
Caution should be used when enabling this feature, since the drive will attempt
to issue its own start command based on user selected programming.
Type
No. Fault Description Action
➊
F2 Auxiliary Input 1 Auxiliary input interlock is open. 1. Check remote wiring.
2. Verify communications.
F3 Power Loss 2 DC bus voltage remained below 1. Monitor the incoming AC line for low voltage or line power interruption.
85% of nominal. 2. Check input fuses.
F4 UnderVoltage 1 DC bus voltage fell below the Monitor the incoming AC line for low voltage or line power interruption.
minimum value.
F5 OverVoltage 1 DC bus voltage exceeded Monitor the AC line for high line voltage or transient conditions. Bus
maximum value. overvoltage can also be caused by motor regeneration. Extend the decel time
or install dynamic brake option.
F6 Motor Stalled 1 Drive is unable to accelerate Increase Parameter 139…167 (Accel Time x) or reduce load so drive output
motor. 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 1 Heatsink temperature exceeds a 1. Check for blocked or dirty heat sink fins. Verify that ambient
OvrTmp predefined value. temperature has not exceeded 40°C.
2. Replace internal fan.
F12 HW OverCurrent 2 The drive output current has Check programming. Check for excess load, improper programming of
exceeded the hardware current Parameter 184 (Boost Select), DC brake volts set too high, or other causes of
limit. excess current.
F13 Ground Fault 2 A current path to earth ground Check the motor and external wiring to the drive output terminals for a
has been detected at one or more grounded condition.
of the drive output terminals.
F33 Auto Rstrt Tries Drive unsuccessfully attempted to Correct the cause of the fault and manually clear.
reset a 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 2. Check motor for grounded phase.
F40 Phase W to Gnd motor in this phase. 3. Replace starter module if fault cannot be cleared.
F41 Phase UV Short 2 Excessive current has been 1. Check the motor and drive output terminal wiring for a shorted
F42 Phase UW Short detected between these two condition.
F43 Phase VW Short output terminals. 2. Replace starter module if fault cannot be cleared.
F48 Params 2 The drive was commanded to 1. Clear the fault or cycle power to the drive.
Defaulted write default values to EEPROM. 2. Program the drive parameters as needed.
F63 SW OverCurrent 2 Programmed Parameter 198 (SW Check load requirements and Parameter 198 (SW Current Trip) setting.
Current Trip) has been exceeded.
F64 Drive Overload 2 Drive rating of 150% for 1 min. or Reduce load or extend Accel Time.
200% for 3 sec. has been
exceeded.
➊ See Table 12.D for internal drive fault types.
Troubleshooting 12-9
Type
No. Fault Description Action
➊
F70 Power Unit 2 Failure has been detected in the 1. Cycle power.
drive power section. 2. Replace starter module if fault cannot be cleared.
F80 SVC Autotune The autotune function was either 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 Set Parameter 141 (Reset To Defaults) to option 1 Reset Defaults.
Checksum board does not match the
checksum calculated.
F122 I/O Board Fail 2 Failure has been detected in the 1. Cycle power.
drive control and I/O section. 2. Replace starter module if fault cannot be cleared.
➊ See Table 12.D for internal drive fault types.
12-10 Troubleshooting
Table 12.H Motor and/or Drive Will Not Accelerate to Commanded Speed
Cause(s) Indication Corrective Action
Acceleration time None Reprogram Parameter 139 (Accel Time 1) or
is excessive. Parameter 167 (Accel Time 2).
Excess load or None • Compare Parameter 103 (Output Current) with
short acceleration Parameter 189 (Current Limit1).
times force the • Remove excess load or reprogram
drive into current Parameter 139 (Accel Time 1) or
limit, slowing, or Parameter 167 (Accel Time 2).
stopping • Check for improper setting of Parameter 184
acceleration. (Boost Select).
Speed command None • Verify Parameter 102 (Commanded Freq).
source or value is • Check Parameter 112 (Control Source) for the
not as expected. proper Speed Command.
Programming is None Check Parameter 135 (Maximum Freq) to insure that
preventing the speed is not limited by programming.
drive output from
exceeding limiting
values.
Torque None • Set motor nameplate full load amps in
performance does Parameter 226 (Motor NP FLA).
not match motor • Use Parameter 227 (Autotune) to perform
characteristics. Static Tune or Rotate Tune procedure.
• Set Parameter 225 (Torque Perf Mode) to
option 0V/Hz.
!
on drive, ensure 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.
The control module is not intended for intended for field repair. The entire
module must be replaced if a failure occurs. Follow the applicable procedure
for control module removal.
Fuse Replacement
Power Requirements
Units No Options Brake or Output Contactor With Brake and Output Contactor
Control Voltage Volts 24V DC 120V AC 240V AC 24V DC 120V AC 240V AC 24V DC 120V AC 240V AC
Power Supply (Nom) Amps 0.425 0.225 0.113 0.425 0.225 0.113 0.425 0.225 0.113
Total Control (Pick Up) VA (W) (10.0 W) 27 27 (12.7 W) 49 49 (15.2 W) 71 71
Total Control (Hold In) VA (W) (10.0 W) 27 27 (12.7 W) 28 28 (15.2 W) 30 30
External Devices powered by Control Voltage
Outputs (2) 1 A max. each Amps 2 2 2 2 2 2 2 2 2
Total Control VA (Pick Up)
VA (W) (58.0 W) 267 507 (60.7 W) 289 551 (60.7 W) 311 551
with max. outputs
Total Control VA (Hold In)
VA (W) (58.0 W) 267 507 (60.7 W) 289 510 (60.7 W) 270 510
with max. outputs
A-1
Specifications
Line Voltage Frequency 3-Phase kW Rating 3-Phase Hp Rating Output Current (A) Input Current (A)
Drive Ratings 0.4 — 2.3 3.65
200 50 0.75 — 4.5 6.40
1.5 — 7.6 10.65
— 0.5 2.3 3.10
230 60 — 1 4.5 5.70
— 2 7.6 9.45
0.4 — 1.4 2.15
0.75 — 2.3 3.80
380 50 1.5 — 4.0 6.40
2.2 — 6.0 9.00
3.0 — 7.6 12.40
— 0.5 1.4 1.85
— 1 2.3 3.45
460 60 — 2 4.0 5.57
— 3 6.0 8.20
— 5 7.6 12.5
— 1 1.7 2.78
— 2 3.0 4.73
575 60
— 3 4.2 6.64
— 5 6.6 10.75
Specifications
Pin 1: +V Out
Pin 2: Input 1 or 3
Pin 3: Comm
Pin 4: Input 0 or 2
Pin 5: NC (No Connection)
Pin 1: PE
Pin 2: Return
Pin 3: Relay Out
Pin 1: T1 - Black
Pin 2: T2 - White
Pin 3: T3 - Red
Pin 4: Ground - Green/Yellow
Pin 1: L1 - Black
Pin 2: GND - Green/Yellow
Pin 3: L2 - White
Specifications
Pin 1: 10V DC
Pin 2: 0…10V Input
Pin 3: Analog Common
Pin 4: Analog Output
Pin 5: RS485 Shield
Dimensions
Dimensions are approximate. Illustrations are not drawn to scale.
Female straight
Male straight
88.9 (3.50)
88.9 (3.50)
38.6
38.6 (1.52)
(1.52)
74.7 74.7
(2.94) (2.94)
38.6 38.6
(1.52) (1.52)
1 4 1 4
2 3 2 3
Female Male
1 Black 3 Red
Color Code
2 Green/Yellow Expanded PIN 4 White
Specifications
Drop Cables
Specifications
Certifications UL
Standards Compliance UL 2237
Mechanical
Coupling Nut Black Anodized Aluminum or 316 Stainless Steel
Housing Black PVC
Insert Black PVC
Cable Diameter 0.43 in. +/- 0.12 in. (10.9 mm +/- 0.5 mm)
Electrical
Contacts Brass with Gold over Nickel Plating
Cable Black PVC, dual rated UL TC/Open Wiring and STOOW
Cable Rating 600V AC/DC
600V @ 10 or 15 A, Symmetrical Amps RMS Fault: 65 kA
Assembly Rating
when used with Class CC, T, or J type fuses
Environmental
Enclosure Type Rating IP67, NEMA 4; IP69K 1200 psi washdown
UL Type TC 600V 90 °C Dry 75 °C Wet, Exposed Run (ER) or
Operating Temperature MTW 600V 90 °C or STOOW 105 °C 600V -
CSA STOOW 600V FT2
Dimensions
Dimensions are approximate. Illustrations are not drawn to scale.
25.4 25.4
(1.00) (1.00)
40.4
(1.59) 43.2
(1.70)
25.4
25.4
(1.00)
(1.00)
Female Male
1 Black 3 Red
Color Code
2 White 4 Green/Yellow Extended PIN
Specifications
Dimensions
Dimensions are approximate. Illustrations are not drawn to scale.
Reducer
M35 M22
112.5
MALE FEMALE
(4.43)
38.1
(1.50) #1 BLACK #1
#2 #2
#3 RED #3
#4 GREEN/YELLOW #4
WHITE
25.4
(1.00)
WIRING DIAGRAM
Power Tee
108.0
(4.25) #3 RED
FEMALE
#1-BLACK
MALE
EXTENDED PIN 2
#1 BLACK
#2-GREEN/YELLOW KEYWAY GREEN/YELLOW LEAD #2 GREEN/YELLOW
#4 WHITE
#2 GREEN/YELLOW
73.7 (2.90)
#1 BLACK
#4 WHITE
#3 RED
#4-WHITE
#3-RED
19.0 FEMALE
(0.75)
38.0
(1.50) WIRING DIAGRAM
MALE
#2- WHITE
#1-BLACK
#3 -RED
#1-BLACK
#2-WHITE
19.0
(0.75) FEMALE
38.0
(1.50)
WIRING DIAGRAM
Specifications
Trunk Tee: 25 A A
Female Male
1 Black 3 Red
2 Green/Yellow Extended PIN 4 White
Reducing Tees
Trunk: 25 A B
Drop: 15 A
Female Male Female
1 Black 3 Red 1 Black
2 Green/Yellow Extended PIN 4 White 2 Green/Yellow Extended PIN
3 Red
4 White
Reducer
Trunk: 25 A C
Drop: 15 A
Male Female
1 Black 3 Red 1 Black
2 Green/Yellow Extended PIN 4 White 2 Green/Yellow Extended PIN
3 Red
4 White
Specifications
Power Receptacles
Specifications
Certifications UL
Standards Compliance UL 2237
Mechanical
Insert Black PVC
Black Anodized Aluminum (female) and Zinc DieCast, Black
Receptacle Shell Material
E-Coat (male), or 316 Stainless Steel
Electrical
Copper Alloy with Gold over Nickel Plating (Trunk), Brass
Contacts
with Gold over Nickel Plating (Drop)
Cable Rating 600V AC/DC
4 pin - 16 AWG, 600V @ 10 A
4 pin - 16 AWG, 600V @ 15 A
Assembly Rating 4 pin - 10 AWG, 600V @ 25 A
Symmetrical Amps RMS Fault: 65 kA when used with Class
CC, T, or J type fuses
Environmental
Enclosure Type Rating IP67, NEMA 4; IP69K 1200 psi washdown
Dimensions
Dimensions are approximate. Illustrations are not drawn to scale.
18.49 45.26
(0.728) (1.782)
280-M22F-M1
280-M35F-M1
3.81
(0.150)
12.09 (0.476)
7.62 +/-2.54 11.89 (0.468)
7.32 1000
(0.288)
(0.30 +/- 0.10)
(39.37) 6.35 (0.25)
15.95 1000
(0.628) (39.37)
51.61
(2.032)
280-M22M-M1
280-M35M-M1
28.04
(1.104) 6.35 (0.25)
11.89 (0.468)
4.75 1000 1000
(0.187) (39.37) (39.37)
Dimensions
Dimensions are approximate. Illustrations are not drawn to scale.
Female Male
1Red/Not used 4 Blank/Not used
Color Code 2 Black (-) 5 Blue (+)
3 Green (GND) 6 White (S2)
Specifications
T-Ports
Specifications
Mechanical
Coupling Nut Black epoxy-coated zinc or 316 Stainless Steel
Housing Riteflex TPE
Insert Yellow Riteflex TPE
Contacts Brass / gold over palladium Nickel
Electrical
Assembly Rating 600V, 10 A
Environmental
Enclosure Type Rating IP67, IP69K 1200 psi washdown
Operating Temperature -20…90°C (-4…194°F)
Dimensions
Dimensions are approximate. Illustrations are not drawn to scale.
Pin 1
Pin 5
Pin 2 Blank
14.6
Pin 4 (0.57)
Female Male
1Red/Not used 4 Blank/Not used
Color Code 2 Black (-) 5 Blue (+)
3 Green (GND) 6 White (S2)
Specifications
Receptacles
Specifications
Mechanical
Male: Black epoxy coated zinc diecast or
Receptacle Shell 316 Stainless Steel
Female: Black anodized Aluminum or 316 Stainless Steel
Insert Yellow PVC
Contacts Brass / gold over palladium Nickel
Electrical
Assembly Rating 600V, 10 A
Environmental
Enclosure Type Rating IP67, IP69K 1200 psi washdown
Operating Temperature -20…90°C (-4…194°F)
Dimensions
Dimensions are approximate. Illustrations are not drawn to scale.
28.1 (1.11)
177.8 (7.0)
12.2 (0.48) 3.81 (0.15)
3.81 (0.15)
7.32 (0.28)
1/2 in. 14 NPT thread 21.3 (0.84)
Dia.
25.07
(0.98) Dia.
Epoxy Filled
Female Male
1Red /Not used 4 Blank/Not used
Color Code 2 Black (-) 5 Blue (+)
3 Green (GND) 6 White (S2)
Specifications
Shorting Plugs
Specifications
Mechanical
Coupling Nut Black epoxy-coated zinc or 316 Stainless Steel
Housing Riteflex TPE
Insert Yellow Riteflex TPE
Contacts Brass / gold over palladium Nickel
Electrical
Assembly Rating 600V, 10 A
Environmental
Enclosure Type Rating IP67, IP69K 1200 psi washdown
Operating Temperature -20…90°C (-4…194°F)
Dimensions
Dimensions are approximate. Illustrations are not drawn to scale.
25.4
(1.0) Dia.
50.1 (1.97)
Female Male
1 Red (+) 4 Blank/Not used
Color Code 2 Black (-) 5 Blue (S1)
3 Green (GND) 6 White (S2)
Specifications
E-Stop Circuit
A-16 Specifications
Notes:
Appendix B
CIP Information
Electronic Data Sheets Electronic Data Sheets (EDS) files are specially formatted ASCII files that
provide all of the information necessary for a configuration tool (e.g.,
RSNetWorx™ for DeviceNet™ Revision 3.21 Service Pack 2 or later) to
access and alter parameters of the device. The EDS file contains all of the
device information: number of parameter, groupings, parameter name,
minimum, maximum, and default values, units, data format, and scaling.
EDS files for all the ArmorStart® Distributed Motor Controllers units are
available from the Internet at www.ab.com/networks/eds.
They may also be built automatically by some configuration tools since much
of the information necessary for an EDS file may be extracted from the
ArmorStart Distributed Motor Controller.
B-1
B-2 CIP Information
VFD Type Product Codes Product codes for the Bulletin 284 variable frequency drives are based on the
Horse Power Rating and Supply Voltage rating of the Distributed Motor
and Name Strings Controller. Table B.A lists the product codes and name strings for the
Bulletin 284 Distributed Motor Controllers:
DeviceNet Objects The ArmorStart Distributed Motor Controller supports the following
DeviceNet object classes:
The following class attributes are supported for the Identity Object:
Identity Object
The following common services are implemented for the Identity Object:
No class or instance attributes are supported. The message router object exists
only to rout explicit messages to other objects.
CIP Information B-5
The following class attributes are supported for the DeviceNet Object:
The following class attributes are supported for the Assembly Object:
All of the various instances of the assembly object will support Attribute 3.
Table B.K summarizes the various instances that are supported:
Table B.L Custom Parameter Based Word-Wise (Produced) Assembly Instance 120
Instance 120
Word Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
0 0 Value of the parameter pointed to by Produced Word 0 Param (low byte)
1 Value of the parameter pointed to by Produced Word 0 Param (high byte)
1 2 Value of the parameter pointed to by Produced Word 1 Param (low byte)
3 Value of the parameter pointed to by Produced Word 1 Param (high byte)
2 4 Value of the parameter pointed to by Produced Word 2 Param (low byte)
5 Value of the parameter pointed to by Produced Word 2 Param (high byte)
3 6 Value of the parameter pointed to by Produced Word 3 Param (low byte)
7 Value of the parameter pointed to by Produced Word 3 Param (high byte)
Assemblies whose instance numbers are 180 or greater are all one word
(16 bits) long. They can be used stand-alone, but their main use is to assemble
information for EDS file parameters. These Word-Wise assemblies become
the building blocks for the Custom Parameter Based Word-Wise assembly
described in Table B.L.
Instance 160 is the default output (consumed) assembly for Bulletin 280/281
Distributed Motor Controllers.
Table B.X Instance 160 — Default Consumed Standard Distributed Motor Controller
Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
0 User Out User Out Fault Run Rev Run Fwd
B A Reset
Table B.Y Instance 162 — Standard Consumed Starter with Network Inputs
Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
0 User Out User Out Fault Run Rev Run Fwd
B A Reset
1 Net In 8 Net In 7 Net In 6 Net In 5 Net In 4 Net In 3 Net In 2 Net In 1
2 Net In 16 Net In 15 Net In 14 Net In 13 Net In 12 Net In 11 Net In 10 Net In 9
CIP Information B-11
Instance 164 is the default output (consumed) assembly for Inverter Type
Distributed Motor Controllers.
Table B.Z Instance 164 — Default Consumed Inverter Type Distributed Motor
Controller
Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
0 User Out B User Out A — Jog Rev Jog Fault Run Rev Run
Fwd Reset Fwd
1 Drive In 4 Drive In 3 Drive In 2 Drive In 1 Decel 2 Decel 1 Accel 2 Accel 1
2 Comm Frequency Command (Low) (xxx.x Hz)
3 Comm Frequency Command (High) (xxx.x Hz)
Instance 166 is the standard output (consumed) assembly for Inverter Type
Distributed Motor Controllers with network inputs.
Table B.AA Instance 166 — Consumed Inverter Type Starter with Network Inputs
Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
0 User Out User Out — Jog Rev Jog Fwd Fault Run Rev Run Fwd
B A Reset
1 Drive In Drive In Drive In Drive In Decel Decel Accel Accel
4 3 2 1 2 1 2 1
2 Comm Frequency Command (Low) (xxx.x Hz)
3 Comm Frequency Command (High) (xxx.x Hz)
4 Net In 8 Net In 7 Net In 6 Net In 5 Net In 4 Net In 3 Net In 2 Net In 1
5 Net In 16 Net In 15 Net In 14 Net In 13 Net In 12 Net In 11 Net In 10 Net In 9
Instance 161 is the default input (produced) assembly for the Bulletin 280/281
Distributed Motor Controller.
Instance 163 is the standard input (produced) assembly with Network Outputs
for the Bulletin 280/281 Distributed Motor Controller.
Table B.AD Instance 163 — Standard Produced Starter with Network Outputs
Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
0 Ready Running Running Alarm Tripped
Rev Fwd
1 140M HOA User In 4 User In 3 User In 2 User In 1
On Reserved Reserved Reserved Reserved
➊ ➊ ➊ ➊
2 Net Out Net Out Net Out Net Out Net Out Net Out Net Out Net Out
8 7 6 5 4 3 2 1
3 Net Out Net Out Net Out Net Out Net Out Net Out Net Out
15 14 13 12 11 10 9
4 ZIP Device Value Key (Low)
5 ZIP Device Value Key (High)
Instance 165 is the default input (produced) assembly for Inverter Type
Distributed Motor Controllers.
Table B.AE Instance 165 — Default Produced Inverter Type Distributed Motor
Controller
Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
0 At Net Ref Net Ctl Ready Running Running Alarm Tripped
Reference Status Status Rev Fwd
1 Contactor 2 Contactor 1 140M HOA User In 4 User In 3 User In 2 User In 1
➋ ➌ On Reserved Reserved Reserved Reserved
➊ ➊ ➊ ➊
2 Output Frequency (Low) (xxx.x Hz)
3 Output Frequency (High) (xxx.x Hz)
➊ If 284 A is selected.
➋ Refers to output contactor status.
➌ Refers to source brake contactor status.
CIP Information B-13
Table B.AF Instance 167 — Produced Inverter Type Starter with Network Outputs
Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
0 At Net Ref Net Ctl Ready Running Running Alarm Tripped
Reference Status Status Rev Fwd
1 Contactor 2 Contactor 1 140M HOA User In 4 User In 3 User In 2 User In 1
➋ ➌ On Status Reserved Reserved Reserved Reserved
➊ ➊ ➊ ➊
2 Output Frequency (Low) (xxx.x Hz)
3 Output Frequency (High) (xxx.x Hz)
4 Net Out 8 Net Out 7 Net Net Net Out Net Out Net Out Net Out
Out 6 Out 5 4 3 2 1
5 Net Out 15 Net Net Net Out Net Out Net Out Net Out
Out 14 Out 13 12 11 10 9
6 ZIP Device Value Key (Low)
7 ZIP Device Value Key (High)
➊ If 284A is selected.
➋ Refers to output contactor status.
➌ Refers to source brake contactor status.
These assembly instances have the same data format as the Power Flex Drives
with a DNet adapter.
Table B.AG Instance 170 — Power Flex Native Format Consumed Assembly
Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
0 MOP Inc reserved Direction Cmd Flt Reset Jog Start Stop
1 MOP Dec Freq Select Freq Select Freq Select Decel Decel Accel Accel
3 2 1 2 1 2 1
2 Comm Frequency Command (Low)
3 Comm Frequency Command (High)
B-14 CIP Information
Table B.AI Instance 171 — Power Flex Native Format Produced Assembly
Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
0 Faulted Alarm Deceling Acceling Rot Fwd Cmd Running Ready
Fwd
1 Drv In 4 Drv In 3 Drv In 2 Drv In 1 Param Ctl fm Ref fm At Ref
Stat Stat Stat Locked Net Net
2 Drive Error Code (low)
3 Drive Error Code (high)
CIP Information B-15
Instances 5…6 will be available Group 3 explicit message connections that are
allocated through the UCMM. The following attributes are supported:
Instances 8…11 are ZIP Consumers. The following instance attributes will be
supported:
The following class attributes are supported for the Discrete Input Point
Object:
➊ Note: This assembly does not exist for the Bulletin 284A.
Four instances of the Discrete Input Point Object are supported. All instances
will contain the following attributes:
The following common services are implemented for the Discrete Input Point
Object:
The following class attributes are supported for the Discrete Output Point
Object:
Ten instances of the Discrete Output Point Object are supported. Table B.AT
summarizes the DOP instances:
Table B.AU
Attribute ID Access Rule Name Data Type Value
3 Get Value BOOL 0 = OFF, 1 = ON
5 Get/Set Fault Action BOOL 0 = Fault Value
attribute, 1 = Hold
Last State
6 Get/Set Fault Value BOOL 0 = OFF, 1 = ON
7 Get/Set Idle Action BOOL 0 = Fault Value
attribute, 1 = Hold
Last State
8 Get/Set Idle Value BOOL 0 = OFF, 1 = ON
113 Get/Set ➊ Pr Fault Action BOOL 0 = Pr Fault Value
attribute, 1 =
Ignore
114 Get/Set ➊ Pr Fault Value BOOL 0 = OFF, 1 = ON
115 Get/Set Force Enable BOOL 0 = Disable, 1 =
Enable
116 Get/Set Force Value BOOL 0 = OFF, 1 = ON
➊ For DOP Instances 1 and 2, and 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:
There are many sources that can affect an output point’s value: an I/O
message, and explicit message, local logic, network fault and idle conditions,
and protection fault conditions. An output point must know how to select
which source of data to use to drive its value attribute.
An output that is not bound behaves much the same as in the DeviceNet
Specification. One notable addition to DOP behavior for the ArmorStart
implementation is the Protection Fault Action and Protection Fault Value
attributes determine the behavior of the DOP when the ArmorStart faults on
a protection fault.
CIP Information B-23
Non-Existant
Power On
Available
Connection Transitions to Established
Protection Fault
DNet
Idle
Protection Fault
DNet Fault
Receive Idle
DNet Fault
Ready
Connection Transitions to Established
Protection Fault
Protection Fault
Run
B-24 CIP Information
Besides the sources that can affect output points 3 and 4, DOPs 1 and 2 can be
affected by keypad inputs since they double as the Run Forward and Run
Reverse outputs. This adds complexity to their behavior, so their behavior is
defined in this section separately.
The following State Transition Diagram is used for DOP Instances 1, 2, 9, and
10:
Power Off
Non-Existant
Power Up
Auto State = Auto Init
Keyad "Hand"
Button Pressed
Hand State = Hand Stop
Auto Hand
Keyad "Auto"
Button Pressed
Auto State = Auto Init
CIP Information B-25
The following State Transition Diagram is used in Auto State for Unbound
DOP Instances 1, 2, 9, and 10
Auto Init
DNet Fault
Connection Transitions to Established
Protection Fault
Protection Fault
DNet
Idle
Protection Fault
DNet Fault
Receive Idle
DNet Fault
Ready
Connection Transitions to Established
Protection Fault
Protection Fault
Run
B-26 CIP Information
The following State Transition Diagram is used in Hand State for Bound or
Unbound DOPs 1, 2, 9, and 10 with Parameter 45 Keypad Mode set to 1 =
momentary.
Figure 2.4
Protection
Fault
Direction = Direction =
Forward Reverse
Protection Fault
Protection Fault Protection Fault
CIP Information B-27
The following State Transition Diagram is used in Hand State for Bound or
Unbound DOPs 1, 2, 9, and 10 with Parameter 45 Keypad Mode set to 1 =
maintained.
Figure 2.5
Protection
Fault
Direction = Direction =
Forward Reverse
Protection Fault
Protection Fault Protection Fault
B-28 CIP Information
The following class attributes are supported for the Parameter Object:
The number of instances of the parameter object depends upon the type of
Distributed Motor Controller. There will be a standard set of instances
reserved (1…99) for all starters. These instances will be followed by a unique
set of instances for each starter type (Bulletin 280/281 or 284).
The following instance attributes are implemented for all parameter attributes:
The following common services are implemented for the Parameter Object:
The following class attributes are supported for the Parameter Object:
All Motor Starter types will have at least five instances of the parameter group
object:
The following instance attributes are supported for all parameter group
instances:
The following common services are implemented for the Parameter Group
Object:
No class attributes are supported for the Discrete Input Group Object.
The following common services are implemented for the Discrete Input
Group Object:
No class attributes are supported for the Discrete Output Group Object.
Two instances of the Discrete Output Group Object are supported. They
contain the following attributes:
The following common services are implemented for the Discrete Output
Group Object:
The following common services are implemented for the Control Supervisor
Object:
The following common services are implemented for the DeviceNet Interface
Object:
To design the motor circuit using a time delay fuse from NEC Table
430.52 to the rules of NEC 430.53C we start with the largest motor,
10 Hp, and calculate 14 A x 175% = 24.5 A. To this we add the FLC
of the 5 Hp motor, 7.6 A, plus the other calculated drive currents for
the motors controlled by the VFD-ArmorStarts. The calculated drive
currents are given in the following Table:
Motor Motor FLC Drive Input to Output Current Ratio Calculated Drive Current
Hp (A) (See ArmorStart Users Manual) (A)
2 3.4 5.75 A/4.0 A = 1.44 3.4 x 1.44 = 4.89 A
1 2.1 3.45 A/2.3 A = 1.5 2.1 x 1.5 = 3.15 A
1 2.1 3.45 A/2.3 A = 1.5 2.1 x 1.5 = 3.15 A
1 2.1 3.45 A/2.3 A = 1.5 2.1 x 1.5 = 3.15 A
The total current for the fuse ampacity is calculated in the following
Table:
To calculate the wire ampacity and therefore the size of the motor
branch conductor we use NEC 430.24 and calculate the sum of 125%
of the largest motor’s FLC plus the FLC of the other motors in the
group. The conductor ampacity calculation is given in the following
Table:
From NEC Table 310.16 we need to use 8 AWG for the motor branch
circuit. Per NEC 430.28 the individual motor tap conductors can be
sized down to 1/3 the ampacity of the trunk but not less than 125% of
the specific motor’s FLC on the tap. This reduction is further
conditionally based on the tap being not more than 25 feet. NFPA 79,
7.2.10.4 and Table 7.2.10.4 restrict the size reduction by the size of
the branch circuit fuse size and tap conductor size. For the above case
we have used a 40 A time-delay fuse. NFPA 79, Table 7.2.10.4
indicates that the smallest tap conductor can be 12 AWG. NEC Table
310.16 for wire ampacity allows 12 AWG (25 A) to be used in all taps
for this application. See the final Group motor circuit design in the
following figure:
**
If the Group motor design were carried out with the intent to use an
inverse-time circuit breaker from NEC Table 430.52 to the rules of
NEC 430.53C, we start with the largest motor, 10 Hp, and calculate
14A x 250% = 35 A to this we add the FLC of the 5 Hp motor, 7.6 A,
plus the other calculated drive currents for the motors controlled by
the VFD-ArmorStarts. The calculated drive currents are given in the
following table:
The rules and allowances for sizing of the over current protection for
NFPA 79 motor groups is covered by 7.2.10.4, Table 7.2.10.4 and
Table 13.5.6. These rules in Tables 7.2.10.4 and 13.5.6 are intended
to limit the maximum SCPD for a group. Therefore each ArmorStart
controller with its factory-supplied output motor cable is suitable for
single-motor or multiple-motor group installations on industrial
machinery when installed according to NFPA 79, 2002. The
controller and output motor cable have been evaluated as a single
system. The maximum over current device rating or setting is limited
to the value in Table 7.2.10.4 for the smallest user-supplied input line
conductor or by the controller’s maximum ratings.
Max. Ratings
Voltage 480Y/277 480 600Y/347 600
Sym. Amps RMS 65 kA 65 kA 30 kA 30 kA
Circuit Breaker 100 A 100 A 100 A —
Fuse 100 A 100 A 100 A 60 A ➊
ArmorConnect ➋ 60 A ➊ 60 A ➊ 60 A ➊ 60 A ➊
Figure D.1
Conveyor Conveyor Conveyor Conveyor Conveyor
Section 1 Section 2 Section 3 Section 4 Section 5
24V
24 DC
vDC
Power
Power
Supply
Supply
D1 D2 D3 D4 D5
Let us calculate the effective wire lengths.
Equivalent
Distance 1 Distance 2 Distance 3 Distance 4 Distance 5
Distance
Run 1 + 50 ft (15 m)* 5 + 50 ft (15 m) * 4 + 50 ft (15 m) * 3 + 50 ft (15 m) * 2 + 50 ft (15 m) * 1 = 750 ft (229 m)
Based on this calculation, there is no wire gauge that can be taken 750
feet, so the fifth section is required to have its own run.
Equivalent
Distance 1 Distance 2 Distance 3 Distance 4 Distance 5
Distance
Run 1 + 50 ft (15 m) * 4 + 50 ft (15 m) * 3 + 50 ft (15 m) * 2 + 50 ft (15 m) = 500 ft (152 m)
Run 2 + 50 ft (15 m) + 50 ft (15 m) + 50 ft (15 m) + 50 ft (15 m) + 50 ft (15 m) = 250 ft (76 m)
24V
24 DC
vDC
Power
Power # 10 AWG
Supply
Supply # 12 AWG
Example 2
24V DC D4 D5
24 vDC
# 14 AWG Power
Power # 14 AWG
D1 D2 Supply
Supply D3
System Design Considerations The use of #16 AWG requires more consideration when determining
When Using 16 AWG Control Wiring the number and location of the power supplies since it is effectively
limited to 125 feet. Re-working example 1 using #16 AWG shows
that two power supplies will be required.
Figure D.4
Conveyor Conveyor Conveyor Conveyor Conveyor
Section 1 Section 2 Section 3 Section 4 Section 5
24V DC # 16 24V DC
24 vDC 24 vDC
Power AWG Power
# 16 AWG Power # 16 AWG Power # 16 AWG
Supply Supply
Supply Supply
Wire
Distance 1 Distance 2 Distance 3 Distance 4 Distance 5
Length
25 ft = 25 ft
Run 1
(7.6 m) (7.6 m)
25 ft = 25 ft
Run 2
(7.6 m) (7.6 m)
= 50 ft
Run 3 50 ft (15 m)
(15 m)
+50 ft = 50 ft
Run 4 0 ft (0 m)* 2
(15 m) (15 m)
Other System Design To minimize the dc power ampacity requirements staggering the
Considerations starting (sequenced on) of the ArmorStarts is recommended but only
if the application does not require all the ArmorStarts to be
commanded to start at the same time.
Accessories
E-1
E-2 Accessories
➋ To achieve IP67 rating, sealing caps must be installed on all unused connections.
➌ To achieve IP69k/NEMA 4X rating, sealing caps must be installed on all unused connections.
The clam shell design clips over the ArmorStart motor 10 280-MTR22-LC
connector and motor cable to limit customer access. 10 280-MTR35-LC
Accessories E-3
US
C
SURFACES MAY BE
AUTOMATION
ROCKWELL
13.0
(0.51)
Table E.G
Communications Option 3
D DeviceNet™ A10 0…10 mA Analog Input
A ArmorPoint® EMI EMI Filter
OC Output Contactor
SM Safety Monitor
Enclosure Type
F Type 4 (IP67)
S Type 4X
Option 2
CB Control Brake Connector
Torque Performance Mode Control Module
DB DB Brake Connector
H Volts per Hz N Control Module Only
SB Source Brake Connector
(Sensorless Vector
Performance)
V Sensorless Vector Control Voltage
Control Volts per Hz Z 24V DC
D 120V AC
B 240V AC Option 1
Output Current 3 Hand-Off-Auto Selector Keypad
with Jog Function
Blank Status Only
Output
Code Current kW Hp
[A]
Motor Media Type
230V Drive R Round
F-1
F-2 Renewal Parts
Table F.A Bulletin 284 Control Module with Sensorless Vector Performance, IP67/NEMA 4, Up to 480V
Input Voltage kW Hp Output 24 V DC 120 V AC 240 V AC
Current Control Voltage Control Voltage Control Voltage
0.4 0.5 2.3 A 284D-FHB2P3Z-N-R 284D-FHB2P3D-N-R 284D-FHB2P3B-N-R
240V 50/60 Hz
0.7.5 1.0 4.5 A 284D-FHB4P5Z-N-R 284D-FHB4P5D-N-R 284D-FHB4P5B-N-R
3-Phase
1.5 2.0 7.6 A 284D-FHB7P6Z-N-R 284D-FHB7P6D-N-R 284D-FHB7P6B-N-R
0.4 0.5 1.4 A 284D-FHD1P4Z-N-R 284D-FHD1P4D-N-R 284D-FHD1P4B-N-R
0.75 1.0 2.3 A 284D-FHD2P3Z-N-R 284D-FHD2P3D-N-R 284D-FHD2P3B-N-R
480V 50/60 Hz
1.5 2.0 4.0 A 284D-FHD4P0Z-N-R 284D-FHD4P0D-N-R 284D-FHD4P0B-N-R
3-Phase
2.2 3.0 6.0 A 284D-FHD6P0Z-N-R 284D-FHD6P0D-N-R 284D-FHD6P0B-N-R
3.0 5.0 7.6 A 284D-FHD7P6Z-N-R 284D-FHD7P6D-N-R 284D-FHD7P6B-N-R
0.4 0.5 2.3 A 284A-FHB2P3Z-N-R 284A-FHB2P3D-N-R 284A-FHB2P3B-N-R
240V 50/60 Hz
0.7.5 1.0 4.5 A 284A-FHB4P5Z-N-R 284A-FHB4P5D-N-R 284A-FHB4P5B-N-R
3-Phase
1.5 2.0 7.6 A 284A-FHB7P6Z-N-R 284A-FHB7P6D-N-R 284A-FHB7P6B-N-R
0.4 0.5 1.4 A 284A-FHD1P4Z-N-R 284A-FHD1P4D-N-R 284A-FHD1P4B-N-R
0.75 1.0 2.3 A 284A-FHD2P3Z-N-R 284A-FHD2P3D-N-R 284A-FHD2P3B-N-R
480V 50/60 Hz
1.5 2.0 4.0 A 284A-FHD4P0Z-N-R 284A-FHD4P0D-N-R 284A-FHD4P0B-N-R
3-Phase
2.2 3.0 6.0 A 284A-FHD6P0Z-N-R 284A-FHD6P0D-N-R 284A-FHD6P0B-N-R
3.0 5.0 7.6 A 284A-FHD7P6Z-N-R 284A-FHD7P6D-N-R 284A-FHD7P6B-N-R
Table F.B Bulletin 284 Control Module with Sensorless Vector Performance, NEMA 4X, Up to 480V
Table F.C Bulletin 284 Control Module with Sensorless Vector Control , IP67/NEMA 4, Up to 600V
Input Voltage kW Hp Output 24 V DC 120 V AC 240 V AC
Current Control Voltage Control Voltage Control Voltage
0.4 0.5 2.3 A 284D-FVB2P3Z-N-R 284D-FVB2P3D-N-R 284D-FVB2P3B-N-R
200..240V
50/60 Hz 0.75 1.0 5.0 A 284D-FVB5P0Z-N-R 284D-FVB5P0D-N-R 284D-FVB5P0B-N-R
3-Phase
1.5 2.0 7.6 A 284D-FVB7P6Z-N-R 284D-FVB7P6D-N-R 284D-FVB7P6B-N-R
0.4 0.5 1.4 A 284D-FVD1P4Z-N-R 284D-FVD1P4D-N-R 284D-FVD1P4B-N-R
0.75 1.0 2.3 A 284D-FVD2P3Z-N-R 284D-FVD2P3D-N-R 284D-FVD2P3B-N-R
380…480V
50/60 Hz 1.5 2.0 4.0 A 284D-FVD4P0Z-N-R 284D-FVD4P0D-N-R 284D-FVD4P0B-N-R
3-Phase
2.2 3.0 6.0 A 284D-FVD6P0Z-N-R 284D-FVD6P0D-N-R 284D-FVD6P0B-N-R
3.0 5.0 7.6 A 284D-FVD7P6Z-N-R 284D-FVD7P6D-N-R 284D-FVD7P6B-N-R
0.75 1.0 1.7 A 284D-FVE1P7Z-N-R 284D-FVE1P7D-N-R 284D-FVE1P7B-N-R
460…600V 1.5 2.0 3.0 A 284D-FVE3P0Z-N-R 284D-FVE3P0D-N-R 284D-FVE3P0B-N-R
50/60Hz
3-Phase 2.2 3.0 4.2 A 284D-FVE4P2Z-N-R 284D-FVE4P2D-N-R 284D-FVE4P2B-N-R
4.0 5.0 6.6 A 284D-FVE6P6Z-N-R 284D-FVE6P6D-N-R 284D-FVE6P6B-N-R
0.4 0.5 2.3 A 284A-FVB2P3Z-N-R 284A-FVB2P3D-N-R 284A-FVB2P3B-N-R
200..240V
50/60 Hz 0.75 1.0 5.0 A 284A-FVB5P0Z-N-R 284A-FVB5P0D-N-R 284A-FVB5P0B-N-R
3-Phase
1.5 2.0 7.6 A 284A-FVB7P6Z-N-R 284A-FVB7P6D-N-R 284A-FVB7P6B-N-R
0.4 0.5 1.4 A 284A-FVD1P4Z-N-R 284A-FVD1P4D-N-R 284A-FVD1P4B-N-R
0.75 1.0 2.3 A 284A-FVD2P3Z-N-R 284A-FVD2P3D-N-R 284A-FVD2P3B-N-R
380…480V
50/60 Hz 1.5 2.0 4.0 A 284A-FVD4P0Z-N-R 284A-FVD4P0D-N-R 284A-FVD4P0B-N-R
3-Phase
2.2 3.0 6.0 A 284A-FVD6P0Z-N-R 284A-FVD6P0D-N-R 284A-FVD6P0B-N-R
3.0 5.0 7.6 A 284A-FVD7P6Z-N-R 284A-FVD7P6D-N-R 284A-FVD7P6B-N-R
0.75 1.0 1.7 A 284A-FVE1P7Z-N-R 284A-FVE1P7D-N-R 284A-FVE1P7B-N-R
Table F.D Bulletin 284 Control Module with Sensorless Vector Performance, IP67/NEMA 4, Up to 480V
Input Voltage kW Hp Output 24 V DC 120 V AC 240 V AC
Current Control Voltage Control Voltage Control Voltage
0.4 0.5 2.3A 284D-SVB2P3Z-N-R 284D-SVB2P3D-N-R 284D-SVB2P3B-N-R
200..240V
50/60 Hz 0.75 1.0 5.0A 284D-SVB5P0Z-N-R 284D-SVB5P0D-N-R 284D-SVB5P0B-N-R
3-Phase
1.5 2.0 7.6A 284D-SVB7P6Z-N-R 284D-SVB7P6D-N-R 284D-SVB7P6B-N-R
0.4 0.5 1.4A 284D-SVD1P4Z-N-R 284D-SVD1P4D-N-R 284D-SVD1P4B-N-R
0.75 1.0 2.3A 284D-SVD2P3Z-N-R 284D-SVD2P3D-N-R 284D-SVD2P3B-N-R
380…480V
50/60 Hz 1.5 2.0 4.0A 284D-SVD4P0Z-N-R 284D-SVD4P0D-N-R 284D-SVD4P0B-N-R
3-Phase
2.2 3.0 6.0A 284D-SVD6P0Z-N-R 284D-SVD6P0D-N-R 284D-SVD6P0B-N-R
3.0 5.0 7.6A 284D-SVD7P6Z-N-R 284D-SVD7P6D-N-R 284D-SVD7P6B-N-R
0.75 1.0 1.7A 284D-SVE1P7Z-N-R 284D-SVE1P7D-N-R 284D-SVE1P7B-N-R
284 D – F N – 10 – C – Options
Bulletin
Number
Option 2 & 3 — Brake Cable Options
Communications SM Safety monitor
D DeviceNet™
A ArmorPoint®
Line Media
Enclosure Type C Conduit
F Type 4 (IP67) R ArmorConnect™ Power Media
S Type 4X
Short-Circuit Protection
Bulletin 140 Current Rating (A)
Base
10 10 A Rated Device
N Base Only — no starter
25 25 A Rated Device
Renewal Parts F-5
Base Module Renewal Part Table F.5 Bulletin 284 Base Module Renewal Part, IP67/NEMA 4,
Product Selection Up to 600V AC With Conduit Entrance
Table F.F Bulletin 284 Base Module Renewal Part, IP67/NEMA 4, Up to 600V AC
With Conduit Entrance
Table F.G Bulletin 284 Base Module Renewal Part, IP67/NEMA 4, Up to 600V AC with ArmorConnect™ Connectivity
Table F.H Bulletin 284 Base Module Renewal Part, NEMA 4X, 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-SN-10-C
50/60 Hz
3-Phase 1.5 2.0 7.6 A 280D-SN-25-C
380…480V 0.4…2.2 0.5…3.0 1.4…4.0 A 280D-SN-10-C
50/60 Hz
3-Phase 3.0 5.0 6.0…7.6 A 280D-SN-25-C
460…600V 0.75…1.5 1.0…2.0 1.7....3.0 A 280D-SN-10-C
50/60Hz
3-Phase 2.2...4.0 3.0...5.0 4.2...6.6 A 280D-SN-25-C
Table F.I Bulletin 284 Base Module Renewal Part, NEMA 4X, Up to 600V AC with ArmorConnect Connectivity
Notes:
Appendix G
PID Setup
PID Loop The Bulletin 284 ArmorStart® Distributed Motor with sensorless vector
control has a built-in PID (proportional, integral, differential) control loop.
The PID loop is used to maintain a process feedback (such as pressure, flow,
or tension) at a desired set point. The PID loop works by subtracting the PID
feedback from a reference and generating an error value. The PID loop reacts
to the error, based on the PID Gains, and outputs a frequency to try to reduce
the error value to 0. To enable the PID loop, Parameter 232 (PID Ref Sel)
must be set to an option other than 0 PID Disabled.
Exclusive Control and Trim Control are two basic configurations where the
PID loop may be used.
Exclusive Control
In Exclusive Control, the Speed Reference becomes 0, and the PID Output
becomes the entire Freq Command. Exclusive Control is used when
Parameter 232 (PID Ref Sel) is set to option 1, 2, 3, or 4. This configuration
does not require a master reference, only a desired set point, such as a flow rate
for a pump.
Figure G.1
PID Loop
PID Ref PID Prop Gain
+ PID + PID
– Error + Output Accel/Decel Freq
PID Fdbk PID Integ Time Ramp Command
+
PID Diff Rate
PID Enabled
G-1
G-2 PID Setup
Example
Figure G.2
PID Feedback =
Pressure Transducer Signal
Pump
PID Reference =
Desired System Pressure
Trim Control
In Trim Control, the PID Output is added to the Speed Reference. In Trim
mode, the output of the PID loop bypasses the accel/decel ramp as shown.
Trim Control is used when Parameter 232 (PID Ref Sel) is set to option 5, 6, 7,
or 8.
Figure G.3
Speed Ref
PID Loop Accel/Decel
PID Ref Ramp
PID Prop Gain
+ PID + PID +
– Error + Output + Output
PID Fdbk PID Integ Time Freq
+
PID Diff Rate
PID Enabled
PID Setup G-3
Example
Figure G.4
0 Volts
10 Volts
Speed Reference
G-4 PID Setup
PID Reference and Parameter 232 (PID Ref Sel) is used to enable the PID mode (Parameter 232 ¦
0 PID Disabled) and to select the source of the PID Reference. If A132 (PID
Feedback Ref Sel) is not set to 0 PID Disabled, PID can still be disabled by select
programmable digital input options (Parameters 151…154) such as Jog, Local,
or PID Disable.
Parameter 233 (PID Feedback Sel) is used to select the source of the PID
feedback.
Option Description
2 The Consumed Assembly (Instance 164 — Default Consumed Inverter
Comm Port Type Distributed Motor Controller) from a communication network (see
page B-11 for details on the Consumed Assembly) which becomes the
PID Feedback. The value sent over the network is scaled so that
Parameter 135 (Maximum Freq) x 10 = 100% Feedback. For example,
with (Maximum Freq) = 60 Hz, a value of 600 sent over the network
would represent 100% Feedback.
PID Setup G-5
PID Deadband
Parameter 238 (PID Deadband) is used to set a range, in percent, of the PID
Reference that the drive will ignore.
Example
PID Preload
The value set in Parameter 239 (PID Preload), in Hertz, will be pre-loaded into
the integral component of the PID at any start or enable. This will cause the
drive’s frequency command to initially jump to that preload frequency, and the
PID loop starts regulating from there.
Figure G.5
PID Enabled
Freq Cmd
PID Limits
Parameter 230 (PID Trim Hi) and Parameter 231 (PID Trim Lo) are used to
limit the PID output and are only used in trim mode. (PID Trim Hi) sets the
maximum frequency for the PID output in trim mode. (PID Trim Lo) sets the
reverse frequency limit for the PID output in trim mode. Note that when the
PID reaches the Hi or Lo limit, the PID regulator stops integrating so that
windup does not occur.
G-6 PID Setup
PID Gains
The proportional, integral, and differential gains make up the PID regulator.
The proportional gain (unitless) affects how the regulator reacts to the
magnitude of the error. The proportional component of the PID
regulator outputs a speed command proportional to the PID error. For
example, a proportional gain of 1 would output 100% of maximum
frequency when the PID error is 100% of the analog input range. A
larger value for (PID Prop Gain) makes the proportional component
more responsive, and a smaller value makes it less responsive. Setting
(PID Prop Gain) to 0.00 disables the proportional component of the
PID loop.
The integral gain (units of seconds) affects how the regulator reacts to
error over time and is used to get rid of steady state error. For example,
with an integral gain of 2 seconds, the output of the integral gain
component would integrate up to 100% of maximum frequency when
the PID error is 100% for 2 seconds. A larger value for (PID Integ
Time) makes the integral component less responsive, and a smaller value
makes it more responsive. Setting (PID Integ Time) to 0 disables the
integral component of the PID loop.
• If the response is too slow increase Parameter 234 (PID Prop Gain).
• If the response is too quick and/or unstable (see Figure G.6),
decrease Parameter 234 (PID Prop Gain).
• Typically, Parameter 234 (PID Prop Gain) is set to some value below
the point where the PID begins to go unstable.
2. Adjust the integral gain (leave the proportional gain set as in Step 1).
After a step change in the PID Feedback:
• If the response is too slow (see Figure G.7), or the PID Feedback
does not become equal to the PID Reference, decrease
Parameter 235 (PID Integ Time).
• If there is a lot of oscillation in the PID Feedback before settling out
(see Figure G.8), increase Parameter 235 (PID Integ Time).
3. At this point, the differential gain may not be needed. However, if after
determining the values for Parameter 234 (PID Prop Gain) and
Parameter 235 (PID Integ Time):
• Response is still slow after a step change, increase Parameter 236
(PID Diff Rate).
• Response is still unstable, decrease Parameter 236 (PID Diff Rate).
The following figures show some typical responses of the PID loop at
different points during adjustment of the PID Gains.
PID Reference
PID Feedback
Time
G-8 PID Setup
PID Reference
PID Feedback
Time
PID Reference
PID Feedback
Time
PID Reference
PID Feedback
Time
Appendix H
• Timer Function
A digital input can be programmed for Timer Start. A digital output can
be programmed as a Timer Out with an output level programmed to the
desired time. When the timer reaches the time programmed into the
output level the output will change state. The timer can be reset via a
digital input programmed as Reset Timer.
• Counter Function
A digital input can be programmed for Counter In. A digital output can
be programmed as Counter Out with an output level programmed to
the desired number of counts. When the counter reaches the count
programmed into the output level the output will change state. The
counter can be reset via a digital input programmed as Reset Counter.
H-1
H-2 Step Logic, Basic Logic and Timer/Counter Functions
Step Logic Using Timed To activate this function, set Parameter 138 (Speed Reference) to 6 Stp Logic.
Three parameters are used to configure the logic, speed reference, and time for
Steps each step.
Forward
0
Reverse
Time
Step Logic Using Basic Digital input and digital output parameters can be configured to use logic to
transition to the next step. Logic In1 and Logic In2 are defined by
Logic Functions programming Parameters 151…154 …Digital Inx Sel… to Option 23 Logic
In1 or Option 24 Logic In2.
Step Logic, Basic Logic and Timer/Counter Functions H-3
Example
• Run at Step 0.
• Transition to Step 1 when Logic In1 is true.
Logic senses the edge of Logic In1 when it transitions from Off to On.
Logic In1 is not required to remain On.
• Transition to Step 2 when both Logic In1 and Logic In2 are true.
The drive senses the level of both Logic In1 and Logic In2 and
transitions to Step 2 when both are On.
Inputs are not required to remain in the On condition except under the
logic conditions used for the transition from Step 2 to Step 3.
Figure H.2
Start Step 0 Step 1 Step 2 Step 3
Frequency
Logic In1
Logic In2
Time
The step time value and the basic logic may be used together to satisfy
machine conditions. For instance, the step may need to run for a minimum
time period and then use the basic logic to trigger a transition to the next step.
Figure H.3
Start Step 0 Step 1
Frequency
Logic In1
Logic In2
Time
H-4 Step Logic, Basic Logic and Timer/Counter Functions
Timer Function Digital inputs and outputs control the timer function and are configured with
Parameters 151…154 (Digital Inx Sel) set to 18 Timer Start and 20 Reset
Timer.
Digital outputs (relay and opto type) define a preset level and indicate when
the level is reached. Level Parameters 156 (Relay Out Level), 159 (Opto Out1
Level), and 162 (Opto Out2 Level) are used to set the desired time in seconds.
Parameters 155 (Relay Out Sel), 158 (Opto Out1 Sel), and 161 (Opto Out2
Sel) are set to option 16 Timer Out and cause the output to change state when
the preset level is reached.
Counter Function Digital inputs and outputs control the counter function and are configured
with Parameters 151…154 (Digital Inx Sel) set to 19 Counter In and 21 Reset
Counter.
Digital outputs (relay and opto type) define a preset level and indicate when
the level is reached. Level Parameters 156 (Relay Out Level), 159 (Opto Out1
Level), and 162 (Opto Out2 Level) are used to set the desired count value.
Parameters 155 (Relay Out Sel), 158 (Opto Out1 Sel), and 161 (Opto Out2
Sel) are set to 17 Counter Out which causes the output to change state when
the level is reached.
Example
Table H.B Digit 3 — Defines the Action during the Step Currently Executing
Table H.C Digit 2 — Defines what Step to Jump to or how to End Program when the
Logic Conditions Specified in Digit 1 are Met
Setting Logic
0 Jump to Step 0
1 Jump to Step 1
2 Jump to Step 2
3 Jump to Step 3
4 Jump to Step 4
5 Jump to Step 5
6 Jump to Step 6
7 Jump to Step 7
8 End Program (Normal Stop)
9 End Program (Coast to Stop)
A End Program and Fault (F2)
H-6 Step Logic, Basic Logic and Timer/Counter Functions
Table H.D Digit 1 — Defines what Logic must be Met to Jump to a Step other than the Very Next Step
Table H.E Digit 0 – Defines what Logic must be Met to Jump to the Very Next Step
Publication 284-UM001F-EN-P - December 2007 Copyright ©2007 Rockwell Automation, Inc. All Rights Reserved. Printed in USA.
Supercedes Publication 284-UM001E-EN-P - June 2007