penelitian 4

DeviceLogix1791D, 1792D, 1799

Technical Data

DeviceLogix is a function that has been added to a number of Rockwell Automation devices to control outputs and manage status information locally within the device. This is accomplished through the DeviceLogix Editor.

The DeviceLogix Editor is the configuration tool for DeviceLogix-capable devices. It is a software tool that provides a graphical interface for configuring Function Blocks to provide local control within DeviceLogix-capable devices. The tool is an applet of RSNetWorx for DeviceNet™ which means that DeviceLogix is launched from within RSNetWorx for DeviceNet. The DeviceLogix Editor works with all DeviceLogix-capable devices.

A DeviceLogix-capable device operates as a slave device on a DeviceNet™ network. You can enable a logic operation using the DeviceLogix Editor to provide local control over outputs on a device. The DeviceLogix device consists of:

• a specific number of inputs and/or outputs

• local logic that determines its behavior

2 DeviceLogix

Important User Information Because of the variety of uses for the products described in this publication, those responsible for the application and use of these products 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. In no event will Allen-Bradley be responsible or liable for indirect or consequential damage resulting from the use or application of these products.

Any illustrations, charts, sample programs, and layout examples shown in this publication are intended solely for purposes of example. Since there are many variables and requirements associated with any particular installation, Allen-Bradley does not assume responsibility or liability (to include intellectual property liability) for actual use based upon the examples shown in this publication.

Allen-Bradley publication SGI-1.1, Safety Guidelines for the Application, Installation and Maintenance of Solid-State Control (available from your local Allen-Bradley office), describes some important differences between solid-state equipment and electromechanical devices that should be taken into consideration when applying products such as those described in this publication.

Reproduction of the contents of this copyrighted publication, in whole or part, without written permission of Rockwell Automation, is prohibited.

Throughout this publication, notes may be used to make you aware of safety considerations. The following annotations and their accompanying statements help you to identify a potential hazard, avoid a potential hazard, and recognize the consequences of a potential hazard:

Inputs and Outputs Inputs and outputs can be one of two types:

• Physical - Inputs and outputs realized by physical connections to the device. These are referred to as Discrete Inputs or Discrete Outputs.

• Networked - Inputs consumed by the device from the network and outputs produced by the device onto the network.

ATTENTION

!Identifies information about practices or circumstances that can lead to personal injury or death, property damage, or economic loss.

Publication ACIG-TD001A-EN-P - March 2002

DeviceLogix 3

Local Logic The local logic of a DeviceLogix device consists of Function Blocks, inputs, outputs, and connections (wires) between them. Function Blocks contain connection points (hereafter called pins) and perform a specific function. Inputs and outputs also have connection pins and represent the actual hardware devices, networked data, and fault and status bits that are available for use in the local logic.

A connection (hereafter call wire) between Function Blocks is defined when an input pin of one Function Block is bound to an output pin of another Function Block. A pin can be bound to a:

• pin of another Function Block

• physical input

• networked input

• fault or status bit

Function Blocks may also have attributes that influence their function.

Configuring a DeviceLogix device consists of defining or editing the local logic that is present on the device along with the EDS parameters for that device.

DeviceLogix and RSNetWorx for DeviceNet

You will configure DeviceLogix features through RSNetWorx for DeviceNet. The DeviceLogix Editor ships as part of RSNetworx for DeviceNet starting with revision 3.0. EDS files that enable DeviceLogix are shipped with the release of RSNetworx in a separate folder labeled Additional EDS Files.

RSNetWorx for DeviceNet’s Operating Modes

RSNetWorx for DeviceNet operates in one of two modes:

• offline - RSNetWorx for DeviceNet is not connected to the network.

• online - RSNetWorx for DeviceNet is connected to the network and is capable of communicating with devices on the network.

RSNetWorx for DeviceNet lets you select online or offline mode. Whichever mode RSNetWorx for DeviceNet is in directly affects the way DeviceLogix behaves when it is launched.


4 DeviceLogix

Features and Benefits Key features of DeviceLogix are discussed in the following section.

Improved Performance Coupled with Low-Cost Distributed Control

Low-cost logic solving capability in I/O, motors, push buttons, and other control components improve the performance of distributed control while lowering its cost.

DeviceLogix-enabled smart components such as I/O, motor controls, and push buttons are well suited for applications where you need a quick, local response to an input without the sense-to-activation delays imposed by network round-trip polling times. They are also well suited when you need to assure that an interruption in the network doesn’t stop a portion of the control system from functioning as it should.

Improved Reaction Time

Allen-Bradley DeviceLogix-enabled distributed I/O can perform simple control functions locally without the performance constraints typically imposed by a centralized controller and a communication network. Input sense-to-output actuation times in the 2 ms range can be achieved with several Allen-Bradley I/O families. DeviceLogix capability can be found in the following I/O products

• 1791D CompactBlock

• 1792D High Current ArmorBlock

• 1792D ArmorBlock MaXum

• 1799 Embedded

• 1799 Zone Control I/O Card

Minimize Use of Extra Components

A Motor Starter with a DeviceNet Starter Auxiliary™ (DSA) can perform a “pump anti-backspin” function, or a “star-delta sequence” motor start without extra timers and relays. A Distributed Starter™ with a DSA can now improve time-sensitive activities such as positioning or sortation activities on a conveyor.


DeviceLogix 5

Local Input and Processing with Push Buttons

Allen-Bradley 800E Push Button Stations with DeviceLogix components technology allow for local input and processing with response times under 2 ms. This feature is perfect for applications where response time is critical, such as motor E-stop or jogging a slide. Yet these push buttons can still provide feedback to the master system in both diagnostic bits and hardwired connections. The multiple configuration options of 800E push button stations offer you flexibility in choosing push button styles and field wiring methods.

DeviceLogix Capability The Function Block Editor, accessed through RSNetWorx for DeviceNet, lets you create local logic using boolean logic (AND, OR, etc.), set and reset latches, as well as a variety of timers and counters. User support for the editor can be found in the DeviceLogix Users Manual, publication number ACIG-UM001, and online help.

DeviceLogix has some device-specific capabilities and capacities as identified in the following table.

Optional I/O Assemblies The DeviceLogix-capable versions of I/O products let you choose how much data the modules produce or consume over DeviceNet. Two new parameters have been added to the EDS files that let you select the amount of data that will be transmitted or received.

Capability/Capacity I/O Product

Function Blocks supported • boolean - AND, OR, XOR, NOT, NAND, NOR, XNOR• latches - RSL and SRL• timers - PUL, OND, and OFD• counters - UPC and UPD

maximum number of function blocks included in a configuration

48

Function Block processing time

1msec./24 blocks2msec./48 blocks

network input bits 32

network output bits 8

logic status indication • logic disabled - none• logic enabled - solid green• local forces are applied and local logic is

enabled - flashing green


6 DeviceLogix

Produced I/O Assembly

There are three options for Produced Data:

• Default assembly - Produces the device’s input data and any fault/status data the device has.

• Input only assembly - Produces only the state of the device’s inputs. This lets those who do not make use of the Diagnostic bits reduce their network traffic.

• DeviceLogix assembly - Produces all of the standard information from the Default assembly plus the data that is available as a result of invoking DeviceLogix.

The new DeviceLogix data that is available includes:

– Logic Enabled bit - This bit is high when DeviceLogix is running on a device and has been enabled. This can be used, for example, in the PLC program or on a DeviceNet MMI, to indicate the presence of local logic control.

– Network Output bits - These bits are used in the DeviceLogix configuration to send information back over the network. For example, the output of any Function Block can be connected to a network output bit.

– Hardware Output bits - DeviceLogix lets you locally control the state of hardware outputs. Therefore these bits are produced by the device so that the state of the outputs can be sent back to the network master. If an output in the device is not under DeviceLogix control, its status is still controlled by the normal consumed data.

1791D CompactBlock I/O Family

CompactBlock products that support DeviceLogix have specific status bits as identified below.

• explicit message connection

• polled connection

• change-of-state/cyclic connection

• network fault

• minor module fault

• polled connection fault

• polled connection idle

• change-of-state/cyclic connection fault


DeviceLogix 7

1791D CompactBlock I/O DeviceLogix Assemblies

The following sections list the 1791D CompactBlock DeviceLogix assemblies.

1791D-4B0 DeviceLogix Assembly

1791D-4B4P DeviceLogix Assemblies

1791D-4B0

Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

Byte 0 Logic Ena In 3 In 2 In 1 In 0

Byte 1 NetOut 7 NetOut 6 NetOut 5 NetOut 4 NetOut 3 NetOut 2 NetOut 1 NetOut 0

Logic Ena = DeviceLogix Enable, NetOut = Network Output

1791D-4B4P


Byte 0 Logic Ena In 3 In 2 In 1 In 0

Byte 1 Out 3 Out 2 Out 1 Out 0



1791D-4B4P with a 1791D-16B0X or 1791D-16V0X expansion


Byte 0 In 7 In 6 In 5 In 4 In 3 In 2 In 1 In 0


Byte 2 Exp Fault Logic Ena In 19 In 18 In 17 In 16



Exp Fault = Expansion Fault, Logic Ena = DeviceLogix Enable, NetOut = Network Output

1791D-4B4P with a 1791D-0B16PX or 1791D-0V16PX expansion


Byte 0 Exp Fault Logic Ena In 3 In 2 In 1 In 0

Byte 1 Out 7 Out 6 Out 5 Out 4 Out 3 Out 2 Out 1 Out 0






8 DeviceLogix

1791D-8B8P or 1791D-8V8P DeviceLogix Assemblies

1791D-8B8P or 1791D-8V8P



Byte 1 Logic Ena




1791D-8B8P or 1791D-8V8P with a 1791D-16B0X or 1791D-16V0X expansion





Byte 3 Exp Fault Logic Ena




1791D-8B8P or 1791D-8V8P with a 1791D-0B16PX or 1791D-0V16PX expansion










DeviceLogix 9

1791D-16B0 or 1791D-16V0 DeviceLogix Assemblies

1791D-16B0 or 1791D-16V0




Byte 2 Logic Ena


Input Status bits - when the bit is set (1), the input is on. Logic Ena = DeviceLogix Enable, NetOut = Network Output

1791D-16B0 or 1791D-16V0 with a 1791D-16B0X or 1791D-16V0X expansion









1791D-16B0 or 1791D-16V0 with a 1791D-0B16PX or 1791D-0V16PX expansion










10 DeviceLogix

1791D 0B8P DeviceLogix Assemblies

1791D-0B8P


Byte 0 Logic Ena




1791D-0B8P with a 1791D-16B0X or 1791D-16V0X expansion








1791D-0B8P with a 1791-0B16PX or 1791-0V16PX expansion









DeviceLogix 11

1791D-0B16P or 1791D-0V16P DeviceLogix Assemblies

1791D-0B16P or 1791D-OV16P


Byte 0 Logic Ena





1791D-0B16P or 1791D-OV16P with a 1791-16B0X or 1791-16V0X expansion









1791D-0B16P or 1791D-OV16P with a 1791-0B16PX or 1791-0V16PX expansion










12 DeviceLogix

1792D ArmorBlock I/O Family

The ArmorBlock Series B and High Current modules now have DeviceLogix. The products that support DeviceLogix have some unique device-specific capabilities and capacities, which are identified in the following table.

1792D ArmorBlock I/O DeviceLogix Assemblies

The following sections list the 1792D ArmorBlock DeviceLogix assemblies.

Capability/Capacity ArmorBlock MaXum (Series B)

High Current ArmorBlock

available fault bits • input short circuit• input off-wire• output fault

• output short circuit• output no-load

available status bits • explicit message connection • polled connection• change-of-state/cyclic

connection exists• change-of-state/cyclic fault• network fault• minor module fault• auxiliary power status

• explicit message connection • polled connection• change-of-state/cyclic

connection exists• change-of-state/cyclic fault• network fault• minor module fault• bank 1 auxiliary power status• bank 2 auxiliary power status

1792D-2BV0D

OW-D OW-A ISC-D ISC-A RSVD RSVD In 1 In 0

Logic Ena

NetOut 7 NetOut 6 NetOut 5 NetOut 4 NetOut 3 NetOut 2 NetOut 1 NetOut 0

OW = Off Wire ISC = Input Short Circuit in Sensor Source Voltage RSVD = ReservedLogic Ena = DeviceLogix Enabled NetOut = Network Output

1792D-4BV0D

ISC-D ISC-C ISC-B ISC-A In 3 In 2 In 1 In 0

Logic Ena OW-D OW-C OW-B OW-A


ISC = Input Short Circuit in Sensor Source Voltage Logic Ena = DeviceLogix EnabledOW = Off Wire NetOut = Network Output


DeviceLogix 13

1792D-8BVT0D

In 7 In 6 In 5 In 4 In 3 In 2 In 1 In 0

OW-D OW-C OW-B OW-A ISC-D ISC-C ISC-B ISC-A

Logic Ena


OW = Off Wire ISC = Input Short Circuit in Sensor Source Voltage Logic Ena = DeviceLogix Enabled NetOut = Network Output

1792D-16BVT0D



ISC-H ISC-G ISC-F ISC-E ISC-D ISC-C ISC-B ISC-A

OW-H OW-G OW-F OW-E OW-D OW-C OW-B OW-A

Logic Ena


ISC = Input Short Circuit in Sensor Source Voltage OW = Off Wire Logic Ena = DeviceLogix Enabled NetOut = Network Output

1792D-0B4D

OPWR Logic Ena OFLT 3 OFLT 2 OFLT 1 OFLT 0

Out 3 Out 2 Out 1 Out 0


OPWR = Output Power (Auxiliary Power) Logic Ena = DeviceLogix EnabledOFLT = Output Fault NetOut = Network Output

1792D-0B8D

OFLT 8 OFLT 7 OFLT 6 OFLT 5 OFLT 4 OFLT 3 OFLT 2 OFLT 1

OPWR Logic Ena

Out 7 Out 6 Out 5 OUt 4 Out 3 Out 2 Out 1 Out 0


OFLT = Output Fault OPWR = Output Power (Auxiliary Power) Logic Ena = DeviceLogix Enabled, NetOut = Network Output


14 DeviceLogix

1792D-0VT16E

OPWR Logic Ena

Out 7 Out 6 Out 5 Out 4 Out 3 Out 2 Out 1 Out 0



OPWR = Output Power (Auxiliary Power), Logic Ena = DeviceLogix Enabled, NetOut = Network Output

1792D-2BVA2D

OW-B OW-A ISC-B ISC-A Alarm 1 Alarm 2 In 1 In 0

OPWR Logic Ena Out 2 Out 1 OFLT 2 OFLT 0


OW = Off Wire, ISC = Input Short Circuit in Sensor Source Voltage, OPWR = Output Power (Auxiliary Power), Logic Ena = DeviceLogix Enabled, OFLT = Output Fault, NetOut = Network Output

1792D-4BVT4D

OW-B OW-A ISC-B ISC-A In 3 In 2 In 1 In 0




OW = Off Wire, ISC = Input Short Circuit in Sensor Source Voltage, OPWR = Output Power (Auxiliary Power), Logic Ena = DeviceLogix Enabled, OFLT = Output Fault, NetOut = Network Output

1792D-8BVT8D


OW-D OW-C OW-B OW-A ISC-D ISC-C ISC-B ISC-A

OFLT 7 OFLT 6 OFLT 5 OFLT 4 OFLT 3 OFLT 2 OFLT 1 OFLT 0

OPWR Logic Ena



OW = Off Wire, ISC = Input Short Circuit in Sensor Source Voltage, OFLT = Output Fault, OPWR = Output Power (Auxiliary Power), Logic Ena = DeviceLogix Enabled, NetOut = Network Output


DeviceLogix 15

1799 Embedded I/O Family

The Embedded I/O family has some unique device-specific capabilities and capacities, which are identified in the following table.

1792D-8BIO8E


ISC Logic Ena OFLT



ISC = Input Short Circuit in Sensor Source Voltage, Logic Ena = DeviceLogix Enabled, OFLT = Output Fault, NetOut = Network Output

1792D-12BVT4D


ISC-D ISC-C ISC-B ISC-A In 12 In 11 In 10 In 9

OW-F OW-E OW-D OW-C OW-B OW-A ISC-F ISC-E




ISC = Input Short Circuit in Sensor Source Voltage, OW = Off Wire, OPWR = Output Power (Auxiliary Power), Logic Ena = DeviceLogix Enabled, OFLT = Output Fault, NetOut = Network Output

1792D-88HC

OL 7 OL 6 OL 5 OL 4 OL 3 OL 2 OL 1 OL 0

NL 7 NL 6 NL 5 NL 4 NL 3 NL 2 NL 1 NL 0


Logic Ena



OL = Output Overload, NL = Output No Load, Logic Ena = DeviceLogix Enabled, NetOut = Network Output

Capability/Capacity Embedded I/O

available fault bits • output fault (16U16B/BL only)

available status bits • explicit message connection • polled connection• change-of-state/cyclic

connection exists• change-of-state/cyclic fault• network fault• minor module fault


16 DeviceLogix

1799 Embedded I/O DeviceLogix Assemblies

The following sections list the 1799 Embedded DeviceLogix assemblies.

1799-D10U10BL and 1799-D10U10VL



Byte 1 Logic Ena In 9 In 8


Byte 3 Out 9 Out 8


Logic Ena = DeviceLogix Enabled, NetOut = Network Output

1799-D16U16BL and 1799-D16U16VL




Byte 2 Logic Ena OFLT1 OFLT0



Byte 5


Logic Ena = DeviceLogix Enabled, OFLT Output Group Fault, NetOut = Network Output

1799-ZCIOB and 1799-ZCIOV

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

Produced 0 In 7 In 6 In 5 In 4 In 3 In 2 In 1 In 0

Produced 1 RSVD Logic Ena RSVD In 9 In 8

Produced 2 Out 7 Out 6 Out 5 Out 4 Out 3 Out 2 Out 1 Out 0

Produced 3 Out 9 Out 8

Produced 4 NetOut 7 NetOut 6 NetOut 5 NetOut 4 NetOut 3 NetOut 2 NetOut 1 NetOut 0

Produced 5 CCV 7 CCV 6 CCV 5 CCV 4 CCV 3 CCV 2 CCV 1 CCV 0

Produced 6 CCV 15 CCV 14 CCV 13 CCV 12 CCV 11 CCV 10 CCV 9 CCV 8

Consumed 0 Output 7 Output 6 Output 5 Output 4 Output 3 Output 2 Output 1 Output 0

Consumed 1 RSVD Output 9 Output 8

RSVD = Reserved, Logic Ena = DeviceLogix Enabled, NetOut = Network Output,CCV = Configuration Consistency Value. The CCV appears in the EDS file as a number. The individual bits shown here are compiled to create that number.


DeviceLogix 17

Consumed I/O Assembly

DeviceLogix gives the device the ability to consume data from the network master other than the normal state of the hardware outputs. These are called Network Input Bits. Up to 32 of these bits can be consumed by the device. Five options exist for the variable amount of consumed data: 0, 1, 2, 3, or 4 bytes.

• A standard 16 output CompactBlock I/O module, for instance, consumes 16 bits (2 bytes). With DeviceLogix, you can choose to consume an additional 2 bytes of Network Inputs.

• A standard MaXum 8x8 module, for instance, consumes 8 bits (1 byte), the desired state of the 8 outputs. With DeviceLogix, you can choose to consume an additional 3 bytes of network inputs.

• A standard Embedded I/O module, for instance, consumes 16 bits (2 bytes). With DeviceLogix, you can choose to consume an additional 2 bytes of Network Inputs.

• If a hardware output is controlled by local logic, its state is no longer consumed and that bit becomes available to be used as a network input. For more on this concept, please see the DeviceLogix User Manual, publication no. ACIG-UM001.

Related Publications Refer to the DeviceLogix User Manual, publication no. ACIG-UM001, for more information about DeviceLogix.


18 DeviceLogix

Notes:


DeviceLogix 19

Notes:


Publication ACIG-TD001A-EN-P - March 2002 1 PN 957603-67 Copyright © 2002 Rockwell Automation. All rights reserved. Printed in the U.S.A.

Allen-Bradley is a trademark of Rockwell Automation.

DeviceNet is a trademark of Open DeviceNet Vendor Association (ODVA).

RSNetWorx for DeviceNet is a trademark of Rockwell Software, Inc.

DeviceNet Starter Auxiliary and Distributed Starter are trademarks of Rockwell Automation.

penelitian 4

Documents

devicelogix device

outputs inputs

devicelogix editor

devicelogixcapable devices

discrete outputs

slave device

local control

allenbradley publication