Using DeviceLogix™ 7-5
ArmorStart Fault Bit, Status Bit,
Outputs and Produced Network
Bits in the DeviceLogix Ladder
Editor
All ArmorStart Distributed Motor Starters support DeviceLogix.
When using the DeviceLogix ladder editor to program logic for an
ArmorStart, the bit names that are associated with fault bits, status
bits, outputs and produced network bits when using the original
DeviceLogix function block editor are not presented by the ladder
editor. Instead, these bits are numbered. Fault bits such as “Overload
Trip” are tagged “FB0, FB1, FB2, etc. Status bits such as “Running
Fwd” are tagged SB0, SB1, SB2, etc. Outputs such as “Run Reverse”
are tagged DOP0, DOP1 etc. Produced Network Bits such as “Fault
Reset” are tagged PNB0, PNB1, etc.
The following steps provide information to program ArmorStart
DeviceLogix programs with the ladder editor.
1. Bulletin 280G and 281G ArmorStart Status Bits
The screen capture below shows how to choose status bits in the
ladder editor.
The following list contains the status bit definitions for Bulletin 280G
and 281G ArmorStart units:
ArmorStart Revision 2.xxx (280G and 281G)
0 = Tripped
1 = Warning
2 = Running Fwd
3 = Running Rev
4 = Ready
5 = Net Ctl Status
6 = Keypad Hand
7 = HOA Status
8 = 140M On
9 = Explicit Msg Cnxn Exists
10 = IO Cnxn Exists
11 = Explicit Cnxn Fault
12 = IO Cnxn Fault
13 = IO Cnxn Idle
14 = Current Flowing
15 = Keypad Hand Direction
16 = ZIP1 Cnxn
17 = ZIP1 Fault
18 = ZIP2 Cnxn
19 = ZIP2 Fault
20 = ZIP3 Cnxn
21 = ZIP3 Fault
22 = ZIP4 Cnxn
23 = ZIP4 Fault
To Next Page
Loading...
Need help?
General
