User’s Manual Pub. 0300272-01 Rev. A.
ii Point IO™ 2 Channel Isolated Output Analog HART Module User’s Manual Pub. 0300272-01 Rev. A.
Point IO™ 2 Channel Isolated Output Analog HART Module iii Important Notes 1. 2. 3. Please read all the information in this owner’s guide before installing the product. The information in this owner's guide applies to hardware Series A and firmware version 1.1 or later. This guide assumes that the reader has a full working knowledge of the relevant processor. Notice The products and services described in this owner's guide are useful in a wide variety of applications.
iv Point IO™ 2 Channel Isolated Output Analog HART Module Microsoft and Microsoft Windows are registered trademarks of Microsoft Corporation. The Encompass logo, ControlLogix, RSLinx, RSLogix, and EtherNet/IP are trademarks of Rockwell Automation. Other brands and their products are trademarks or registered trademarks of their respective holders and should be noted as such. User’s Manual Pub. 0300272-01 Rev. A.
Point IO™ 2 Channel Isolated Output Analog HART Module v Table of Contents IMPORTANT NOTES .............................................................................................................................................. III NOTICE ................................................................................................................................................................. III LIMITED WARRANTY .................................................................................
vi Point IO™ 2 Channel Isolated Output Analog HART Module 4.2.6 DeviceNet Object ...................................................................................................................................... 4-6 4.2.7 Assembly Object........................................................................................................................................ 4-6 TECHNICAL ASSISTANCE ............................................................................................................
Point IO™ 2 Channel Isolated Output Analog HART Module vii Preface Read this preface to familiarize yourself with the rest of the manual.
viii Point IO™ 2 Channel Isolated Output Analog HART Module Related Documentation The table below provides a listing of publications that contain important information about Allen-Bradley PLC systems. For Refer to this Document Allen-Bradley Pub. No. A description and overview of the 1734 and 1734D series POINT I/O modules and compatible control platforms. Also includes an overview of how to specify a POINT I/O system.
Chapter 1 Module Overview Section 1.1 Before You Begin The 1734sc-OE2CIH module has two isolated analog current output channels with HART communication on each channel. Each channel can be configured for current only or current with HART.
1-2 Chapter 1: Module Overview Section 1.3 Output Types The OE2CIH module supports two, user-selectable, current outputs of 4 to 20 mA and 0 to 20 mA. Section 1.4 Data Formats User-defined scaling is provided that allows you to scale any data send to the module to any 16-bit number. Section 1.5 Hardware Features The module contains a DeviceNet communications bus that uses a Controller Area Network (CAN) that connects to an Ethernet adapter for communication with an external PLC that uses RSLogix 5000.
Chapter 1: Module Overview 1-3 User’s Manual Pub. 0300272-01 Rev. A.
1-4 Chapter 1: Module Overview 1.5.1 LED Indicators The 1734 analog HART module uses several LEDs to show operational status. The LEDs for the module consist of four Red/Green LEDs representing Module Status, Network Status, and two Output Connection Status LEDs. The status LEDs are defined below: Table 1-1 (LED Status Indicators) Indicator Module Status Network status Channel status User’s Manual Pub. 0300272-01 Rev. A.
Chapter 1: Module Overview 1-5 Section 1.6 System Overview The module communicates to the controller via an Ethernet adapter. The module receives 5 and 24 VDC power through the PointBus backplane bus interface. 1.6.1 Module Power-up At power-up, the module performs a check of its internal circuits, memory, and basic functions. If no faults are found during power-up diagnostics, the module status LED is turned on.
1-6 Chapter 1: Module Overview See the block diagram below. User’s Manual Pub. 0300272-01 Rev. A.
Chapter 2 Installation and Wiring This chapter will cover: Compliance to European Union directives Power requirements General considerations Mounting Field wiring connections Section 2.1 Compliance to European Union Directives This product is approved for installation within the European Union and EEA regions. It has been designed and tested to meet the following directives. 2.1.
2-2 Chapter 2: Installation and Wiring Section 2.2 Power Requirements The module receives power through the bus interface from the +5 VDC/+24 VDC system power supply. The maximum current drawn by the module is shown in the table below. 5 VDC 24 VDC Field Supply 55 mA 175 mA at 12 VDC (2.1 VA max) 77 mA at 24 VDC is typical (1.
Chapter 2: Installation and Wiring WARNING 2-3 Explosion Hazard Substitution of components may impair suitability for Class I Division 2. Wear an approved wrist-strap grounding device. Do not touch the backplane connector or connector pins. Do not touch circuit components inside the module. If available, use a static-safe work station. When not in use, keep the module in its static-shield box. 2.3.2 Prevent Electrostatic Discharge WARNING Hazard of damage to equipment.
2-4 Chapter 2: Installation and Wiring analog module. Position the module: Away from sources of electrical noise such as hard-contact switches, relays, and AC motor drives Away from modules which generate significant radiated heat. Refer to the module’s heat dissipation specification. In addition, route shielded, twisted-pair analog input wiring away from any high-voltage I/O wiring. Section 2.4 Mounting 2.4.
Chapter 2: Installation and Wiring 2-5 2.4.2 Install Mounting Base WARNING Hazard of damage to module on power up. Debris that falls into the module could cause damage when power is applied to the module. During panel or DIN rail mounting of all devices, be sure that all debris (such as metal chips or wire strands) is kept from falling into the module. To install the mounting base on the DIN rail, proceed as follows: 1.
2-6 Chapter 2: Installation and Wiring 2.4.3 Install the Output Module The module can be installed before, or after, base installation. Make sure that the mounting base is correctly keyed before installing the module into the mounting base. In addition, make sure the mounting base locking screw is positioned horizontal referenced to the base. User’s Manual Pub. 0300272-01 Rev. A.
Chapter 2: Installation and Wiring 1. 2. 3. 2-7 Using a bladed screwdriver, rotate the key switch on the mounting base clockwise until the number required for the type of module being installed aligns with the notch in the base. Make certain the DIN rail locking screw is in the horizontal position. (You cannot insert the module if the locking mechanism is unlocked.) Insert the module straight down into the mounting base and press to secure. The module will lock into place. 2.4.
2-8 Chapter 2: Installation and Wiring Section 2.5 Field Wiring Connections Consider the following when wiring your system: General Power and input wiring must be in accordance with Class 1, Division 2 wiring methods, Article 501-4(b) of the National Electric Code, NFPA 70, and in accordance with the authority having jurisdiction. Use Belden™ 8761 or equivalent, shielded wire. To ensure optimum accuracy, limit overall cable impedance by keeping a cable as short as possible.
Chapter 2: Installation and Wiring 2-9 Noise Prevention Route field wiring away from any other wiring and as far as possible from sources of electrical noise, such as motors, transformers, contactors, and AC devices. As a general rule allow at least 15.2 cm (6 in.) of separation for every 120 V of power. Routing field wiring in a grounded conduit can reduce electrical noise. If field wiring must cross AC or power cables, ensure that they cross at right angles.
2-10 Chapter 2: Installation and Wiring User’s Manual Pub. 0300272-01 Rev. A.
Chapter 3 Configuring the Module with RSLogix™ 5000 This chapter covers software configuration of the module. More detailed information about ControlLogix I/O Modules in general, and additional information about features described below can be found in the ControlLogix Digital I/O Modules User Manual Publication 1756-UM058F-EN-P–April 2012, and in the RSLogix 5000 Online Help. The add-on profile may be downloaded at www.spectrumcontrols.com.
3-2 Chapter 3: Configuring the Module 3. From the Controller Organizer:I/O Configuration folder, select the 1756 backplane in which you just installed the new module: 4. Right click the selected backplane or controller, and from the popup menu, select New Module: User’s Manual Pub. 0300272-01 Rev. A.
Chapter 3: Configuring the Module 3-3 The Select Module dialog appears: 5. From this dialog, select the appropriate communications module and click OK. (In this example, it is the 1756-ENBT Ethernet Bridge): User’s Manual Pub. 0300272-01 Rev. A.
3-4 Chapter 3: Configuring the Module The Select Major Revision dialog appears: 6. 7. 8. Select the major software revision (4 in this example) for the new module and click OK. Select the major software revision you need for the new module and click OK. A listing for the selected module appears in the Controller Organizer tree, and the following New Module dialog appears: Specify the following: Name. Specify name for the module. The name must be IEC 1131-3 compliant.
Chapter 3: Configuring the Module DANGER 3-5 Revision. Revision is divided into major and minor revision values. The major revision indicates the revision of the interface to the module. Valid values are in the range 0 to 127. The minor revision is used to indicate the firmware revision. Valid values are in the range 0 to 255, with 1 being the default value. As releases occur, these numbers will be incremented. Address/Host Name. Enter the IP address or host name for the module. Electronic Keying.
3-6 Chapter 3: Configuring the Module Example dialog filled in: 9. After you have added the local Ethernet communication module, you must add a remote Ethernet communication module. This module resides in a separate chassis from the controller. 10. From the Local Ethernet Module you have just added from the Ethernet option, select New Module: 11. From the Select Module dialog that opens, select the module type and click OK: User’s Manual Pub. 0300272-01 Rev. A.
Chapter 3: Configuring the Module 3-7 12. The Select Major Revision dialog appears. Enter or select Major Revision value and click OK: 13. Configure the remote Ethernet communication module as follows, and then click OK. The following New Module dialog appears: 14. View or specify the following options: Name. Enter name of new module. Description. If needed, enter a description for the module. Comm Format. Select the communication format.
3-8 Chapter 3: Configuring the Module Example Completed Dialog: 15. You may see another dialog for Connection parameters appear. Close the dialog by clicking OK. 16. From the hierarchical list that appears, select PointIO 2 Slot Chassis. Right click and select New Module. The Select Module dialog appears: User’s Manual Pub. 0300272-01 Rev. A.
Chapter 3: Configuring the Module 3-9 17. Make sure the By Vendor tab at the base of the dialog is selected: 18. From the Allen-Bradley list, select the 1734-Module (Generic 1734 Module) and click OK: User’s Manual Pub. 0300272-01 Rev. A.
3-10 Chapter 3: Configuring the Module The New Module dialog appears: View or specify the following options: Name. Enter name of new module. Description. If needed, enter a description for the module. Comm Format. Select the communication format. When you select a communication format, you are also selecting the configuration formats for the module. For an OE2CIH module, select Data – INT. Slot. Enter the slot number in which the module resides. Connection Parameters.
Chapter 3: Configuring the Module 3-11 The new module appears in your hierarchy: User’s Manual Pub. 0300272-01 Rev. A.
3-12 Chapter 3: Configuring the Module User’s Manual Pub. 0300272-01 Rev. A.
Chapter 4 OE2CIH and HART This chapter describes how to read and write HART data using the OE2CIH module. The chapter includes the following sections: HART features Detecting HART devices Auto scanning of HART dynamic variables Supported HART CIP messages Section 4.1 HART Features The OE2CIH module functions as a HART master and communicates with HART devices running HART revision 5 or greater.
4-2 Chapter 4: OE2CIH and HART If the channel is HART-enabled, to determine if a HART device is present on a given channel, the module continuously sends out HART Command 0 (Read Unique Identifier, which returns the expanded device code type, revision levels, and device identification number).
Chapter 4: OE2CIH and HART 4-3 has been refreshed by the module, and you should re-send the Read Additional Status CIP message to the class instance (Instance=0) that returns all channels at once. (Sending a request for an individual channel does not reset the tag.) The data returned by the Read Additional Status is in the original order as received from the HART device. This means any multi-byte elements in the data will not be in the correct order for use in RSLogix, and will be reversed in the PLC.
4-4 Chapter 4: OE2CIH and HART Commands sent at Initial Device Connection Command: 2 Definition: Read Loop Current Comment: Only sent if Cmd 9 is being used If any information within a device is changed, the device sets its Configuration Changed bit (bit 6 of Field Device Status byte), which is detected by the module. The module then automatically resends the appropriate HART commands to refresh this set of data stored in the module.
Chapter 4: OE2CIH and HART 4-5 All three interface types have equal priority: The User Ladder interface uses a simplified HART interface (EZ-HART) that only requires the user to send the HART Command number along with its data bytes (if any) in the request data for the Init Pass-through message without having to know how to format a real HART message. In addition the Ladder interface has a MsgReady indicator tag in the Input table to facilitate determining when the pass-through is complete.
4-6 Chapter 4: OE2CIH and HART 4.2.6 DeviceNet Object This object class configures port attributes such as baud rate and MAC ID. Table 4-4 Device Net Object Class Code: 0×03 Instances: #1 Class Attributes: None Class Services: None Instance Attributes: Attr Name (Data Type) 1 MAC ID (USINT) 2 Baud (USINT) Value G/S Description 0-63 G The current MAC ID 3 G Baud rate. The baud is fixed at 1 Mbps and cannot be changed.
Chapter 4: OE2CIH and HART 4-7 Table 4-5 Assembly Object Class Code: 0×04 OE2CIH Instances: #100 = Status Assembly #101 = Status + Hart Ch 0,1 Assembly #102 = Output Assembly #110 = Build number #225 = Configuration Assembly Class Attributes: None Class Services: None Instance Attributes: Attr Name (Data Type) Value G/S Description 3 Data (STRUCT) See following tables G/S See following tables Instance Services: Code Service Name Description 14 0×0E Get Single Read the assembly insta
4-8 Chapter 4: OE2CIH and HART 15 Enable Disable Enable Disable 4-20 mA 0-20 mA Disable Enable Low Clamp High Clamp Hold Last State Fault Value Low Clamp High Clamp Hold Last State Program Value Ignored X 14 X HART Pass-Through Hold Time This is a module-wide parameter. Valid values are 1 to 155 seconds. A value of 0 will default to 20 seconds. All other values are an error.
Chapter 4: OE2CIH and HART 4-9 Fault Value uses the value set by the user (see below). Program Action. While the system is idle or in program mode, the user may choose the behavior of the outputs: Low Clamp uses the Low Clamp Value (see below). If clamping has been disabled, this setting is not allowed. High Clamp uses the High Clamp Value (see below). If clamping has been disabled, this setting is not allowed.
4-10 Chapter 4: OE2CIH and HART It is considered a configuration error if the values are equal. Negative scaling is also not allowed which means the High Value must always be greater than the Low Value. The scaling formula is as follows: output_mA = user * gain + offset Where: output_mA = The current present at the terminal block in Milliamps user = The user value in the channels Output Word gain = (range_high–range_low)/(user_high–user_low) - range_high = (20.0 for both range settings).
Chapter 4: OE2CIH and HART 4-11 To allow the highest resolution for full end-to-end output limits use the following values: 4 to 20 mA Range: - High Value = 29126 - Low Value = -29127 The result is: - 32767 = 21.0 mA - 29126 = 20.0 mA - -29127 = 4.0 mA - -32768 = 3.0 mA 0 to 20 mA Range: - High Range = 29646 - Low Range = -32768 High/Low Clamp Values High/Low Clamp Values are signed 16-bit integers.
4-12 Chapter 4: OE2CIH and HART Table 4-8 Input-Only Assembly Instance: ID: Description: Total Size: 100 3 Channel Status Only 12 Bytes RSL 5 K (DeviceNet 8 bytes) Bit 15 Analog data 4 bytes 0×00-0×03 14 13 12 11 10 09 08 07 06 05 04 03 02 01 00 CM CF Module Status - UINT High Byte–Channel 1 Status HF Bits 13-14 not used OC HCA LCA Low Byte–Channel 0 Status CM CF HF Bits 0506 not used OC HCA LCA Channel Status Bits CF = Channel Fault status; 0 = no error; 1 = any
Chapter 4: OE2CIH and HART 4-13 Watchdog Fault In the case where the main CPU experiences a watchdog failure, the following will take place: 1. The module resets. 2. Once the watchdog reset is detected at startup, both channels are held in reset. 3. The Module Status is set to 1. 4. Both Channel Statuses are set to the HF bit. 5. The Module Status LED blinks Red, and Channel Status LEDs are solid Red. 6. Any configuration sent to the module is ignored. 7. Firmware updates are allowed when in this state.
4-14 Chapter 4: OE2CIH and HART HART STATUS BITS: INIT = HART device detected FAIL = No device found or communication failed MAFLT = HART does not match analog loop current MSGRDY = Ladder pass-through message available DDLDR = Device Data update Ladder DDLGX = Device Data update Logix SUA = Status Update Available, Cmd 48 data changed FAULT= HART device reports a fault HART STATUS BYTE 1: Communication Status / Response Code This if the first status byte returned in a Slave-to-Master fr
Chapter 4: OE2CIH and HART 4-15 HART STATUS BYTE 3: Extended Device Status This is the first byte returned with Command 9 by HART revision 6 and 7 devices.
4-16 Chapter 4: OE2CIH and HART HART Object CIP HART services will use a subset of the HART Object used in the modules.
Chapter 4: OE2CIH and HART 4-17 HART Pass-through “Reason Code” definitions The HART Pass-through Reason Code is a value that is reported when a Pass-through reply message returns the general Status value as DR_DEAD(35). It provides you with a diagnostic code to look up more detail on why the pass-through message failed. This code is returned in Offset 3 of the reply message for Pass-through Init or Query messages whenever the Status value at Offset 0 is set to DR_DEAD(35).
4-18 Chapter 4: OE2CIH and HART Table 4-13 Read Dynamic Variables (Service Code = 4B) Unconnected Message Field Value Definition Message Type CIP Generic Service Code 0×4B Get Device Information Class Name 0×035D HART Object Instance 1 to n Selects channel n-1 Object Attribute None, leave this field blank Request Size 0 No Request Data Reply Size 2 to 36 bytes (2) Size when information not available (36) Size when valid Information returned Number of Data bytes returned Request Data
Chapter 4: OE2CIH and HART 4-19 Request Succeeded Reply HART Read Dynamic Variables - Reply packet structure Reply Size = 36 bytes Offset Field Value Definition 0 Status (1 byte) Command status, 00 = SUCCESS 1 HART Command Status (1 byte) HART Device reply Status Byte # 1 2 HART Field Device Status (1 byte) HART Device reply Status Byte # 2 3 HART Ext Device Status (1 byte) Status Byte returned from Cmd 9 or 0 for HART rev 5 devices 4-7 PV (Float–4 bytes) HART Primary variable 8-11
4-20 Chapter 4: OE2CIH and HART Request Succeeded Reply HART Read Dynamic Variables - Reply packet structure Reply Size = 36 bytes Offset Field Value Definition 31 FV Status (1 byte) 1 byte status from Command 9 OR if Rev 5 device: 0×C0 = Connected and Device provides this value in CMD 3 (that is, does not truncate) 0×00 = Not Connected 32-35 Loop Current (Float–4 bytes) Device reported digital loop current value.
Chapter 4: OE2CIH and HART 4-21 Request Failed Reply HART Read Additional Status - Reply packet structure Reply Size = 2 Offset Field Value Definition 0 Status 34 = DR_RUNNING (No Device or connection process not completed or regathering device info is in progress) 35 = DR_DEAD (Channel is not HART enabled) Command status 1 Pad 0 Pad byte Request Succeeded Reply HART Read Extended Status - Reply packet structure Instance n Reply Size = 2-28 bytes (pad byte may be attached to end for 16 bit ali
4-22 Chapter 4: OE2CIH and HART Table 4-15 Ladder Get Device Information (Service Code = 0×4D) Unconnected Message Field Value Definition Message Type CIP Generic Service Code 0×4D Get Device Information Class Name 0×035D HART Object Instance Name 1 no n Selects channel n-1 Object Attribute None, leave this field blank Request Size 0 No Request Data Reply Size 2-120 bytes (2) Size when Device information not available (120) Size when valid Device Information returned Number of Data by
Chapter 4: OE2CIH and HART 4-23 Request Succeeded Reply HART Get Device Information - Reply packet structure Reply Size = 120 bytes Offset Field Value Definition 8 HARTFlags (1 byte) CMD#0, Byte 8 9 Pad_1 for 32 bit alignment (1 byte) 10-11 HARTManufacturerID16Bit (2 byte) CMD#0, Byte 1 if HART rev later than 7 CMD#0, Bytes 17-18 if HART rev later than or equal to 7 12-15 HARTDeviceIDNumber (4 bytes–UINT) CMD#0, Bytes 9-11 Bytes re-ordered into Intel Format (LSB 1st ) from HART format (M
4-24 Chapter 4: OE2CIH and HART Request Succeeded Reply HART Get Device Information - Reply packet structure Reply Size = 120 bytes Offset Field Value Definition 112 to 115 DampingValue (4 bytes–Float) CMD#15, Bytes 11-14 116 WriteProtectCode (1 byte) CMD#15, Byte 15 117 Pad_2 for alignment (1 byte) 118 to 119 PrivateLabelMfg16Bit (2 bytes) CMD#0, Byte 1 if HART Rev earlier than 7 CMD#0, Bytes 19-20 if HART Rev greater than or equal to 7 Table 4-16 Ladder Pass-through Init (Service Code
Chapter 4: OE2CIH and HART 4-25 Reply Data HART Ladder Passthrough Init - Reply packet structure Reply Size = 4 bytes Offset Field Value Definition 0 Status 32 = Busy (Queues full) 33 = DR_INITIATE (passthrough success) 35 = DR_DEAD Command Status Note: HART Commands 59, 107, 108, and 109 are not allowed and will always return DR_DEAD.
4-26 Chapter 4: OE2CIH and HART Reply Data HART Ladder Passthrough Query - Reply packet structure Reply Size = 6 to 260 bytes Offset Field Value Definition 0 Status 00 = Success 34 = DR_RUNNING 35 = DR_DEAD Query Status 1 HART Command 0 to 255 (1 byte) Echo of HART command 2 HART CommStatus (1 byte) HART Reply Status Byte #1 3 HART FieldDeviceStatus OR Reason Code if status = 35 (1 byte) HART Reply Status Byte #2 4 Data Size 0 to 255 (1 byte) 5 to 257 HART Reply Data … Reason Code
Chapter 4: OE2CIH and HART 4-27 Table 4-19 Suspend Normal HART Acquisitions (Service Code = 0×51) Unconnected Message Field Value Definition Message Type CIP Generic Service Code 0×51 Suspend HART Class Name 0×035D HART Object Instance 0 = All Channels 1 to n = Single Channel(n-1) All channels suspended or a single channel Object Attribute None, leave this field blank Request Size 0 No Request Data Reply Size 2 Number of Data bytes returned Request Data Suspend Normal HART acquisitio
4-28 Chapter 4: OE2CIH and HART Request Data Resume Normal HART acquisitions - Request packet structure Request Size = 0 Offset Field Value Definition 0 No Request Data Reply Data Resume Normal HART acquisitions - Reply packet structure Reply Size = 2 bytes Offset Field Value Definition 0 Status (1 byte) 00 = SUCCESS 35 = DR_DEAD 1 Pad 0 Table 4-21 Get Channel(s) Device Status (Service Code = 0×62) Unconnected Message Field Value Definition Message Type CIP Generic Service Code 0×62
Chapter 4: OE2CIH and HART 4-29 Reply Data Get Single Channel Device - Reply packet structure Reply Size = 12 or (12*n) Offset Field Value Definition 0 Communication Established 0×00 (1 byte)– Not established 0×01 (1 byte)– Established Indicates presence of HART device 1 HART Comm/Cmd Response Status byte (1 byte) HART Communication Status byte (First Status byte from device) 2 HART Field Device Status byte (1 byte) HART field device Status byte (Second Status byte from device) 3 Manufact
4-30 Chapter 4: OE2CIH and HART HART Processor Detects an Error During startup, the main processor sets a timeout (200 ms) and a DAC value for the HART processor to use if it ever stops receiving communications. Once the HART processor detects this timeout, the DAC value is used. The DAC value is determined by the configuration of the channel Fault Mode setting. Main CPU Failure In the case where the main CPU does not run on power up, the outputs remain disabled.
Appendix A This appendix contains configuration information as follows: Table A-1 Environmental Specifications Environmental Tests Industry Standards Test Level Limits IEC60068-2-1: (Test Ad, Operating Cold), Temperature (Operating) IEC60068-2-2: (Test Bd, Operating Dry Heat), (Performance Criteria A) IEC60068-2-14: (Test Nb, Operating Thermal Shock) 0°C to 55°C (-4°F to 131°F) (natural convection cooling) IEC60068-2-1: (Test Ab, Unpackaged Non-operating Cold), Temperature IEC60068-2-2: (Non-operating)
A-2 Appendix A: Configuration Information Environmental Tests Industry Standards Test Level Limits Radiated RF immunity IEC 61000-4-3: Level 3 (Performance Criteria A) 10 V/M with 1 kHz sine wave 80% AM from 80 MHz to 2000 MHz 10 V/M with 200 Hz sine wave 50% Pulse 100% AM at 900 MHz 10 V/M with 200 Hz sine wave 50% Pulse 100% AM at 1890 MHz 1 V/M with 1 kHz sine wave 80% AM from 2000 MHz to 2700 MHz EFT/B immunity IEC 61000-4-4 (Performance Criteria B) Signal Ports: ±3 kV at 5 kHz for 5 minutes Cri
Appendix A: Configuration Information A-3 Table A-2 Safety Tests and Test Limits Safety Tests Industry Standards UL Safety UL 508 Industrial Control Equipment Seventeenth Edition Dated January 28 1999, with revisions through July 11, 2005 (ANSI/UL 508-2005) (NRAQ, NRAQ7) cUL CSA C22.2 No. 142 -M1987 Process Control Equipment May 1987 UL Hazardous Locations UL ANSI/ISA–12.12.
A-4 Appendix A: Configuration Information Table A-4 General Electrical Specifications Parameter Specification Module location 1734-TBxx Isolation Voltage 50 V (continuous) Functional Insulation Type, channels to backplane and between channels (tested at 707 VDC for 1 minute) 5 V PointBus current 55 mA External DC power Supply Voltage 24 VDC nominal 10 VDC-28.
Index Add On Profile software 3-1 Assembly Object 4-7 Base 1734-TOPS installation 2-7 1734-TOPS removal 2-7 mounting base removal 2-7 Before you begin information about your module 2-1 Block diagram 1-6 Channel Configuration Assembly 4-8 Communications inter-processor 4-30 Configuration software 2-1 Conventions used in the manual viii Data scaling 1-2 Declaration of Conformity 4-31 Device automatically gathering HART Device information 4-3 automatically gathering status 4-2 DeviceNet Object 4-7 Documentatio
I-2 Index dialog 3-3, 3-6, 3-8 Technical Assistance 4-31 Technical support contact information vii Who should use this manual vii User’s Manual Pub. 0300272-01 Rev. A.
User’s Manual Pub. 0300272-01 Rev. A.
©2013 Spectrum ControlsInc. All rights reserved. Specifications subject to change without notice. The Encompass logo and ControlLogix are trademarks of Rockwell Automation. Corporate Headquarters Spectrum Controls Inc. P.O. Box 6489 BellevueWA 98006 USA Fax: 425-641-9473 Tel: 425-746-9481 Web Site: www.spectrumcontrols.com E-mail: spectrum@spectrumcontrols.com User’s Manual Pub. 0300272-01 Rev. A.