Rockwell Automation 1792-IB2XOB2EB User Manual

Installation Instructions
 
Cat. No. 1792-IB2XOB2E Series B
To: See page:
Install
the ArmorBlock Module Connect the Wiring to the ArmorBlock Module Communicate with Y Configure Y
Manager Configuration T Configure Y
Manager Configuration T Reset Faults 25
Configure Y
For this reference information
Default Configuration Status indicators Troubleshooting 32 Specifications 34
our ArmorBlock Module
our ArmorBlock Module Of
ool
our ArmorBlock Module Online Using the DeviceNet
ool
our ArmorBlock Module with EDS Files
fline Using the DeviceNet
3
8 10 11
17
27
See page:
14 32
This 1792 ArmorBlock I/O block module (Cat. No. 1792-IB2XOB2E) contains I/O circuits, a built-in power supply, and a built-in DeviceNet I/O adapter. Because of its sealed housing, this 1792 I/O block requires no enclosure. It is compatible with PLC or SLC programmable controllers using DeviceNet scanners. The I/O values are accessible from the PLC or SLC programmable controller data table.
This ArmorBlock module has no switches to set. You set module parameters using the DeviceNet Manager Software (cat. no. 1787-MGR) or similar configuration tool.
ArmorBlock is a trademark of Allen-Bradley Co. Inc.
Publication 1792-5.5 – October 1996
ArmorBlock 2 Input/2 Output Module2
European Union Directive Compliance
If this product is installed within the European Union or EEA regions and has the CE mark, the following regulations apply.
EMC Directive
This apparatus is tested to meet Council Directive 89/336/EEC Electromagnetic Compatibility (EMC) using a technical construction file and the following standards, in whole or in part:
EN 50081-2 EMC – Generic Emission Standard, Part 2 –
Industrial Environment
EN 50082-2 EMC – Generic Immunity Standard, Part 2 –
Industrial Environment
The product described in this manual is intended for use in an industrial environment.
Low Voltage Directive
This apparatus is also designed to meet Council Directive 73/23/EEC Low Voltage, by applying the safety requirements of EN 61131–2 Programmable Controllers, Part 2 – Equipment Requirements and Tests.
For specific information that the above norm requires, see the appropriate sections in this manual, as well as the following Allen-Bradley publications:
Industrial Automation Wiring and Grounding Guidelines,
publication 1770-4.1
Automation Systems Catalog, publication B111
Publication 1792-5.5 – October 1996
ArmorBlock 2 Input/2 Output Module
Install Your ArmorBlock Module
Installation of the ArmorBlock module consists of:
setting the node address in the ArmorBlock module
mounting the ArmorBlock module
connecting the wiring
communicating with your module
configuring the parameters
Set the Node Address
Each ArmorBlock comes with its internal program set for node address
63. To set the node address, you need the following:
host computer with DeviceNet Manager Software (or similar
configuration software tool)
1770-KFD RS-232 module (or similar interface)
suitable cables to connect the 1770-KFD to your module and to
connect the 1770-KFD to your host computer
3
Set the node address to meet your system requirements as follows:
1. Set up a system (as shown below) to communicate with your
ArmorBlock module.
Power
from 9V DC Power-Supply Adapter
1770-KFD
RS-232 module
open style connector to sealed mini-female cable
host computer with the DeviceNet Manager software
power supply
Publication 1792-5.5 – October 1996
ArmorBlock 2 Input/2 Output Module4
2. Using DeviceNet Manager Software, go online using the “Setup
Online Connection” selection on the utility pulldown menu.
3. The DeviceNet Driver selection screen appears.
Select the driver for your application and click on .
4. The Driver configuration screen lets you:
set the data rate
set the interface adapter node address
select the interface adapter serial port
set interface adapter baud rate
Click on to go online.
Publication 1792-5.5 – October 1996
ArmorBlock 2 Input/2 Output Module
5
5. The bar at the bottom of the screen will tell you when you go online.
6. At the utility pulldown, select “Node Commissioning.”
7. You can set the node address on the “Device Configuration – Node
Commissioning” screen. Note that the node address “out of the box” setting is 63. Set the desired node address per your system requirements.
Set new node address here.
You can also set the data rate on this screen, if required. However, your module is shipped with the “autobaud” parameter enabled. This assures that the module will be at the correct data rate for any network to which it is connected. To change the data rate, you must first disable autobaud on the parameter screen, then return to the “Device Configuration – Node Commissioning” screen and enter the new data rate.
8. Click on
to apply the new node settings.
9. Repeat the above procedure to set the node addresses of any
additional ArmorBlock modules you want to install.
Publication 1792-5.5 – October 1996
ArmorBlock 2 Input/2 Output Module6
Mount the ArmorBlock Module
Mount the block module directly to the machine or device. Complete mounting dimensions are shown below. Note that the block dimensions allow direct connection of a T-port tap (cat. no. 1485P-P1N5-j) to the DeviceNet connector. (Refer to publication 1485-6.7.1 for cabling details.)
The ArmorBlock module has a sloping top and a gap at the rear to allow water or other liquids to run off during washdowns. The flow through the gap prevents buildup of debris under the block.
Preferred mounting position is with the microconnectors pointing down. However, the block can be mounted in any orientation.
Publication 1792-5.5 – October 1996
Mounting Dimensions
.
1.90
(48.3)
3.055 (77.6)
Inches
(Millimeters)
2.63
(66.7)
2.5
(63.5)
ADDRESS
NODE
ArmorBlock 2 Input/2 Output Module
25
7
7
(184.2)
ARMORBLOCK
MOD/NET
INPUT
STATUS
FAULT
TE RA
DATA
1792-IB2XOB2E
I/O
4
mounting holes
for #10 screws
6.24
(158.5)
Block dimensions allow T
-port tap
connection directly onto connector
For washdown installations, or excessively moist areas, mount block with micro connectors down.
7.74
(196.6)
Direction
of liquid flow
Publication 1792-5.5 – October 1996
ArmorBlock 2 Input/2 Output Module8
Connect the Wiring to the ArmorBlock Module
The block module uses quick disconnect, screw-on style connectors for:
I/O input wiring
I/O output wiring
power wiring for I/O outputs
the DeviceNet connector
DeviceNet
mini connector
2 micro connectors for output wiring
0101
Output power
mini connector
2 micro connectors for input wiring
4 micro plugs – these seal unused ports
Micro plugs are included with your module. Use these plugs to cover and seal unused ports.
Pinout diagrams for these connectors are shown below.
ATTENTION: All connectors must be securely tightened to properly seal the connections against leaks
!
Publication 1792-5.5 – October 1996
and maintain NEMA 4X and 6P requirements.
ArmorBlock 2 Input/2 Output Module
Connecting the Input Wiring
Connect input wiring to the micro connectors which screw into mating connectors on the side of the block.
Make connections as shown below.
I/O Input Micro Connector
9
4
1
3
2
(View into socket)
Pin 1 = Sensor Source Voltage Positive Pin 2 = Not used Pin 3 = Negative/Return Pin 4 = Signal
Connecting the Output Wiring
Connect individual output wiring to micro connectors which screw into mating connectors on the side of the block. Make connections as shown below.
I/O Output Micro Connector
4
1
3
2
(View into socket)
Connect the output power wiring to the 3-pin mini connector on the end of the block.
Important: The
Output Power Mini Connector
outputs use electronic overcurrent fault protection. Make certain
your output power supply can handle overcurrent events.
Pin 1 = Not used Pin 2 = Not used Pin 3 = Negative Pin 4 = Output
1
23
(View into pins)
Pin 1 = Not used Pin 2 = Positive Pin 3 = Negative
Publication 1792-5.5 – October 1996
ArmorBlock 2 Input/2 Output Module10
Connecting the DeviceNet Wiring
Connect DeviceNet wiring to the 5-pin mini connector on the end of the block. Connections are shown below.
DeviceNet Mini Connector
Pin 1 = Drain (Bare)
1
2
3
(View into pins)
5
4
Pin 2 = V+ (Red) Pin 3 = V– (Black) Pin 4 = CAN–HI (White) Pin 5 CAN–LO (Blue)
Note: Colors are DeviceNet standard
Communicate with Your ArmorBlock Module
This ArmorBlock module acts as a slave in a master/slave environment. It is both a “polled device” and a “change of state device.”
When configured as a polled device, a master initiates communication by sending its polled I/O message to the ArmorBlock module. The 2 input/2 output module scans the inputs and fault bits producing a response, and consumes the message, updates outputs, and produces a response that reflects their status.
When configured as a “change of state” device, productions occur when an input changes, or an output fault occurs. If neither has occurred within the “expected packet rate,” a heartbeat production occurs. This heartbeat production tells the scanner module that the ArmorBlock module is alive and ready to communicate.
Publication 1792-5.5 – October 1996
ArmorBlock 2 Input/2 Output Module
11
Bit
Produces IS Reserved OF1 OF0 I1 I0
Consumes Reserved O1 O0
Where: I = Input
IS = Sensor source voltage fault O = Output OF = Output fault
Word Bit Description
Produces
Consumes
00–01 Input bits – bit 00 corresponds to input 0, bit 01 to input 1. When the
02–03 Output fault bits – Shows fault status of each output. OS0
04–06 Reserved 07 Sensor source voltage fault bit – this bit is set (1) when the sensor
00–01 Output bits – Bit 00 corresponds to output 0, bit 01 corresponds to
02–07 Reserved
07 06 05 04 03 02 01 00
bit is set (1), the input is on.
corresponds to output 0, and OS1 corresponds to output 1. When the bit is set (1), the output is faulted.
source voltage is faulted.
output 1. 0 = output off; 1 = output on
Configure Your Armor Module Offline Using the DeviceNet Manager Configuration Tool
To configure your ArmorBlock module offline:
add the device to the network
set the parameters for the device
save the parameters to a file
Note: You cannot actually configure your device offline. You can set and save the parameters to a file for downloading to the device when you go online.
Publication 1792-5.5 – October 1996
Loading...
+ 25 hidden pages