Post on 15-Jan-2022
Smart Transmitter Interface (STI) User’s Guide
Section Title Page
1-2-3
2-1-22-32-4-4-5
2-6
3-1-2
-4-5
-8-101213-157
18323335-37
Section 1. Introduction
1-1. Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11-2. Contents of this Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3. Additional Reference Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Section 2. Smart Transmitter Interface Overview
2-1. Section Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2. Definitions of Terms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-3. Purpose of Smart Transmitter Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4. Features of Smart Transmitter Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-4.1. Features of an STI Using Group 1 QST Cards . . . . . . . . . . . . . . . . . . . . . . 22-4.2. Features of an STI Using Group 2 QST Cards . . . . . . . . . . . . . . . . . . . . . . . 2
2-5. Requirements of Smart Transmitter Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Section 3. Hardware Configuration and Installation
3-1. Section Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2. Hardware Configuration Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33-3. QLC Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
3-3.1. Installing the QLC Card. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33-3.2. Setting the DIOB Card Address Switch. . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3-4. SST Card. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-83-4.1. Installing the SST Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33-4.2. J1 Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33-4.3. SST LED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3-4.4. Using the SST Service Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-
3-5. QST Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3153-5.1. QST Card Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3-5.2. HART Device Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13-5.3. Installing the QST Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3-5.4. QST Transfer of Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3-5.5. Communication Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3-5.6. QST LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-
3-6. Smart Transmitter Interface Start-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
9/98 i U0-1115
Table of Contents, Cont’d
Section Title Page
4-1-2
2-344-4-5-5-6-7-9100-12134
-1-2-2
-3-3-3-4-4-56
-1B-2B-4
Section 4. Software Configuration
4-1. Section Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2. Configuring the QLC Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
4-2.1. Modifying the AUTOEXEC.BAT File . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24-2.2. Copying Initialization Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4-2.3. Using Rosemount Device Description Language . . . . . . . . . . . . . . . . . . . . 44-2.4. Running BAKFLASH. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-
4-3. QST Card Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-4. Transferring Information to the DPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
4-4.1. QLC Algorithms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44-4.2. Reading Value and Quality of Dynamic Process Variables . . . . . . . . . . . . 44-4.3. Reading Device Status Bytes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44-4.4. Reading the Communication Channel Status Bit . . . . . . . . . . . . . . . . . . . . 4
4-5. Enabling On-Demand Communication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4-5.1. Setting the HW Field for On-Demand Communication . . . . . . . . . . . . . . 4-14-5.2. Sending Messages to the Smart Transmitter Interface . . . . . . . . . . . . . . . 44-5.3. Receiving Messages from the Smart Transmitter Interface. . . . . . . . . . . . 4-4-5.4. Translating STI Communication Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Appendix A. Smart Transmitter Interface Specifications
A-1. Section Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AA-2. STI System Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AA-3. STI Power Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AA-4. HART Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A
A-4.1. Basic Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AA-4.2. Transmitted Waveforms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AA-4.3. Received Waveforms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AA-4.4. Impedance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A
A-5. Field Wiring Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AA-6. Current Loop (Network) Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-
Appendix B. Sample Graphics
B-1. Section Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BB-2. Sample Subscreen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3. Sample Main Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
U0-1115 ii 9/98
Table of Contents, Cont’d
Section Title Page
-1-2
Appendix C. Smart Transmitter Interface ConfigurationExample
C-1. Section Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC-2. QLC Algorithms Used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC-3. Points Used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2C-4. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-3
Glossary
Index
9/98 iii U0-1115
9/98 iv U0-1115
Table of Contents, Cont’dList of Figures
Figure Title Page
Section 3. Hardware Configuration and Installation
3-1. Smart Transmitter Interface Hardware Configuration. . . . . . . . . . . . . . . . . . . . . . . 3-33-2. Example DIOB Address Switch Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-63-3. QLC Card. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-73-4. SST Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-93-5. QST/SST (J1) Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-103-6. LED on SST Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-123-7. SST Card Service Switch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-143-8. STI Containing Multiple QST Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-193-9. QST Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-203-10. Jumper Locations on P2 Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-243-11. Wiring Diagram for QST Group 1 Field Connections. . . . . . . . . . . . . . . . . . . . . . 3-263-12. Wiring Diagram for QST Group 2 Field Connections. . . . . . . . . . . . . . . . . . . . . . 3-283-13. Examples of Configuration Jumper Settings for QST Card . . . . . . . . . . . . . . . . . 3-303-14. HART Device Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-313-15. Transmitted Waveform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-343-16. LEDs on QST Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-36
Appendix A. Smart Transmitter Interface Specifications
A-1. Transmitted Waveform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3
Table of Contents, Cont’dList of Tables
1-3
-1117-212223
-4-64-7-8-91-1213-1567
-2-2-5
4
Table Title PageSection 1. Introduction
1-1. Reference Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Section 3. Hardware Configuration and Installation
3-1. QST/SST Interface Connector (J1) Pin Assignments . . . . . . . . . . . . . . . . . . . . . . 33-2. HART Device Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3-3. QST Front Card Edge Connector (P2) Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . 33-4. Field Wiring Cable Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3-5. QST Card Assignment to the QLC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-
Section 4. Software Configuration
4-1. Smart Transmitter Interface Identification Numbers. . . . . . . . . . . . . . . . . . . . . . . . 44-2. QLC Register Locations for Dynamic Variables (Registers 0-435) . . . . . . . . . . . . 44-3. Mapping Channels to Status Byte Registers (Registers 512 - 529) . . . . . . . . . . . . .4-4. HART Device Condition Status Byte (Registers 512 - 529) . . . . . . . . . . . . . . . . . . 44-5. Communication Condition Status Bit (Registers 544 - 561) . . . . . . . . . . . . . . . . . . 44-6. Setting Analog Point HW Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14-7. Smart Transmitter Interface Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44-8. Smart Transmitter Interface Block Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4-9. Data Translation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44-10. HART/WDPF Translation Example (Command 0). . . . . . . . . . . . . . . . . . . . . . . . 4-14-11. HART/WDPF Translation Example (Command 18). . . . . . . . . . . . . . . . . . . . . . . 4-1
Appendix A. Smart Transmitter Interface Specifications
A-1. DIOB Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AA-2. External Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AA-3. Field Wiring Cable Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A
Appendix B. Sample Graphics
B-1. HART/WDPF Translation (Command 0) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-
U0-1115 iv 9/98
Table of Contents, Cont’dList of Tables, Cont’d
Table Title Page
-2-3
Appendix C. Smart Transmitter Interface ConfigurationExample
C-1. Point Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC-2. Smart Transmitter Interface Configuration Example . . . . . . . . . . . . . . . . . . . . . . . C
U0-1115 iv 9/98
italeld.l
m the
n.
edse
Section 1. Introduction
1-1. Overview
Smart transmitters represent the transition from analog technology to digital digtechnology for the devices that collect and transmit process values from the fiThese digital devices transmit their process values from the field to the controsystem as digital representations of the values rather than as analog values.
These smart transmitters are microprocessor controlled and are able to perforfollowing:
• Provide highly accurate process values to the controller from the field.
• Periodically transmit these process values over existing field wiring.
• Permit the user to query the device for diagnostic information.
• Permit the user to configure and calibrate the device from a remote locatio
This document describes the WDPF ® Smart Transmitter Interface (STI).
The STI is a multicard I/O interface that allows the WDPF controller, a DistributProcessing Unit (DPU), to receive digitized process values from the field. Thevalues are collected by HARTTM smart transmitter sensor devices in the field(Rosemount® sensor devices are described in this document, althoughHART-compatible devices are available from other manufacturers).
The interface also allows on-demand communication, as well as periodiccommunication, between the HART device and the WDPF system.
The Smart Transmitter Interface consists of the following three printed circuitcards:
• QLC card.
• SST card.
• QST card.
Refer toSection 3 for details on the interface cards.
7/99 1-1 U0-1115
1-2. Contents of this Document
n ofitter
e
ing,
LC
1-2. Contents of this Document
This document is organized into the following sections:
• Section 1. Introduction provides an overview of the Smart TransmitterInterface and its operation.
• Section 2. Smart Transmitter Interface Overview provides backgroundinformation, and describes features of the Smart Transmitter Interface.
• Section3. HardwareConfiguration and Installation describes the hardwareused in the STI and the procedures required for configuration and installatiothe hardware. An overview of the start-up procedure for the Smart TransmInterface is also included.
• Section4.SoftwareConfiguration describes the configuration of the softwarused to communicate between a HART device and a DPU.
• Appendix A. Smart Transmitter Interface Specificationsprovides systemspecifications such as power requirements, HART specifications, field wirand current loop specifications.
• Appendix B. Sample Graphic Programsprovides two sample graphicsprograms that demonstrate methods of communicating with the STI.
• AppendixC. Smart Transmitter Interface Configuration Exampleprovidesa configuration example of a Smart Transmitter Interface that uses one Qcard and two QST cards.
U0-1115 1-2 7/99
1-3. Additional Reference Documents
1-3. Additional Reference Documents
Additional reference documents that will be helpful to the Smart TransmitterInterface user are listed inTable 1-1 .
Table 1-1. Reference Documents
DocumentNumber 1 Title Description
D9000047Rev. 5.1
HART - Smart CommunicationsProtocol Specification(Rosemount manual)
Describes the use of HARTcommunications protocol with theHART devices.
M0-0053 Q-Line Installation Manual Describes installation ofQ-Line I/O.
U0-0106 Control Algorithms Describes algorithms available for usewith the DPU.
U0-0131 Record Types User’s Guide Describes the point record types andfields.
U0-0136 MAC Application Utilities User’sGuide
Describes the use of controlalgorithms to obtain data stored in Q-cards.
U0-1100 QLC User’s Guide Describes QLC card configuration andoperation.
1 Standard Westinghouse user documents are identified by U0 or M0 numbers.
7/99 1-3 U0-1115
fines
Section 2. Smart Transmitter InterfaceOverview
2-1. Section Overview
This section describes the purpose of the Smart Transmitter Interface and determs used in this document. The following topics are discussed:
• Terms applicable to the Smart Transmitter Interface (Section 2-2).
• Purpose of the Smart Transmitter Interface (Section 2-3).
• Features of the Smart Transmitter Interface (Section 2-4).
• Requirements for a Smart Transmitter Interface (Section 2-5).
7/99 2-1 U0-1115
2-2. Definitions of Terms
itter
rol
-e.
T
ce.
as
analon-
e
e
by
us
2-2. Definitions of Terms
The following terms are used in this document and pertain to the Smart TransmInterface:
Burst mode HART device periodically transmits its values to the STIwithout being polled.
DPU Distributed Processing Unit (DPU) is a drop in the WDPFsystem that contains Q-Line I/O, including the SmartTransmitter Interface printed circuit cards. The DPU’sprocessor runs ladder diagram logic and continuous contloops.
HART Highway Addressable Remote Transducer defines thecommunication specifications (protocol) between the QSTcard and the HART device.
HARTDevice
An input or output device that uses HART communicationprotocol to communicate digital representations of analogprocess point values. Typically, HART devices perform preprocessing of the received signal before sending the valu
Network Power supply and communications loop between the QScard and a HART device in the field.
Polling mode STI periodically requests the values from the HART devi
Q-Crate Input/Output cabinet chassis that contains Q-Cards suchQLC and QST cards.
QLC Card A Q-card that functions as a single-board computer and cinterface to the WDPF DPU. The QLC can serve as a digitlink between a DPU and an external device, can provide line plant performance calculations, and can executeprograms designed to operate in a DOS environment (se“QLC User’sGuide”(U0-1100) for more information on theQLC card). In the STI, the QLC is dedicated to executing thSTI software.
QLC Sharedmemory
Segment of memory on the QLC card that can be accessedthe DPU and the QLC card.
UART Universal Asynchronous Receiver/Transmitter is anintegrated circuit that provides an interface between amicroprocessor or microcomputer and a serial asynchronocommunications channel.
U0-1115 2-2 7/99
2-3. Purpose of Smart Transmitter Interface
opsvicesome
ital
n totion
field
o
vice
2-3. Purpose of Smart Transmitter Interface
Typically, process control devices transmit values from the field using current loor other analog methods. As process control I/O technology has advanced, deused to communicate process values from the field to the control units have becmore intelligent. Thesesmart devices can transmit pre-processed data over a diglink.
HART devices superimpose a digital communication output signal on top of aanalog signal. The WDPF Smart Transmitter Interface provides the capabilitymonitor this digital signal and utilize these values for control and data acquisiapplications.
This interface allows process point values from a HART sensor device in the to be transmitted periodically over a digital link to a DPU.
In addition to the periodic communication of process values, the interface alsallows on-demand communication with the HART device.
This document describes the Smart Transmitter Interface that uses the HARTcommunication protocol to transfer process point values between a HART deand a DPU.
7/99 2-3 U0-1115
2-4. Features of Smart Transmitter Interface
heses that
.
m
ides).
er
2-4. Features of Smart Transmitter Interface
Three types of printed circuit cards make up the Smart Transmitter Interface. Tare QLC cards, SST cards, and QST cards. There are two types of QST cardcan be used: Group 1 and Group 2.
Features common to all QST card groups of the Smart Transmitter Interfaceinclude:
• Six communication channels are supported on each QST card.
• One HART device is supported for each QST card channel.
• Up to three QST cards are supported by each QLC/SST card combination
• Field communications meet the HART Smart Communication ProtocolSpecifications, Revision 5.1.
• Both burst mode and polling mode are supported.
2-4.1. Features of an STI Using Group 1 QST Cards
Special features of Group 1 QST cards include:
• Each QST card channel is individually isolated from the digital logic and froevery other channel in the interface.
• Each channel on a QST card has a separate 24VDC power supply to provpower to the 4-20mA loop the HART device (which transmits analog value
• In the event of a component failure, internal current limiting protects the powsupply.
U0-1115 2-4 7/99
2-4. Features of Smart Transmitter Interface
on
pply,
ply
2-4.2. Features of an STI Using Group 2 QST Cards
Special features of Group 2 QST cards include:
• Each card channel is isolated from the digital logic. The channels are commto each other.
• The channels of the QST card are powered by a single external power suwhich also provides power to the 4-20 mA loop of the Smart TransmitterInterface.
• In the event of a component failure or short circuit in the field, the power supis protected by the use of on-card fuses for each channel.
Note
The wiring and fuse arrangements used forGroup 2 QST cards are unique. Typically,Group 2 QST cards are only used in speciallydesigned systems.
7/99 2-5 U0-1115
2-5. Requirements of Smart Transmitter Interface
ter)
is).the
he
ce toLC
n. Ards.
vice.s 0
d to
2-5. Requirements of Smart Transmitter Interface
The Smart Transmitter Interface consists of a WDPF DPU (level 7.1EE or greathat must contain the following additional components (seeSection3 for details onhardware configuration):
• QLC card (Group 1, Rev. D or later) that resides in the Q-Crate (I/O chassThis card is the interface with the DPU and processes the data provided byHART communication protocol.
• SST iSBXTM daughter card that is mounted on the QLC card. This card is tinterface between the QLC card and the QST cards.
• QST cards that reside in the Q-Crate. These cards are the physical interfathe HART devices. These cards interface to the DPU through the SST and Qcards.
Up to three QST cards can be supported by a single QLC/SST combinatiosingle Q-crate (12 slots) can therefore support a maximum of nine QST ca
Each QST card has six channels and each channel supports one HART deTherefore, an STI can currently support up to 18 HART devices (identified ato 17).
• Westinghouse designed software that resides on the QLC card in order toimplement the HART communication protocol (seeSection 4).
• Device Description Language (DDL) files that are provided by themanufacturers of the particular HART-compatible devices that are connectethe interface.
• Applicable cabling between the SST and the QST cards.
U0-1115 2-6 7/99
ace,
Section 3. Hardware Configuration andInstallation
3-1. Section Overview
This section describes the hardware required for the Smart Transmitter Interfthe configuration necessary for that hardware, and installation procedures.
The following topics are discussed:
• Hardware configuration overview (Section 3-2).
• QLC card (Section 3-3).
• SST card (Section 3-4).
• QST card (Section 3-5).
7/99 3-1 U0-1115
3-2. Hardware Configuration Overview
, ano thede in
3-2. Hardware Configuration Overview
The STI is a multicard interface consisting of the following cards:
• QLC - Q-Line Serial Link Controller card.
• SST - iSBXTM Smart Transmitter Interface QLC-daughter card.
• QST - Q-Line Smart Transmitter Interface card.
The hardware portion of the Smart Transmitter Interface consists of a QLC cardSST iSBX card attached to the QLC card, and up to three QST cards linked tSST card through a ribbon cable. The QLC card and the QST cards must resiadjacent slots within a Q-crate.
Figure 3-1 provides a simplified illustration of the Smart Transmitter Interfacehardware.
U0-1115 3-2 7/99
3-2. Hardware Configuration Overview
Figure 3-1. Smart Transmitter Interface Hardware Configuration
7/99 3-3 U0-1115
3-3. QLC Card
faceh the).
IN,ot
cardards.
ter
3-3. QLC Card
The QLC card provides the processing control for the Smart Transmitter Interand executes the software necessary to enable the DPU to communicate witHART devices (seeSection4 for required software configuration of the QLC card
The use of the QLC card requires the use of QLC algorithms (QLCAIN, QLCGPand QLCDIN) to read in the HART device values, since the device values will nbe automatically processed (if additional information is needed, refer to“QLCUser’sGuide”(U0-1100) and“Control Algorithms” (U0-0106) for information anddescriptions of the QLC algorithms).
3-3.1. Installing the QLC Card
The QLC card used in the Smart Transmitter Interface must be a Group 1 QLCand must be Revision D or later to properly function with the SST and QST c
Figure 3-1 illustrates the location of the QLC card in a typical Smart TransmitInterface hardware configuration.
If necessary, refer to“QLC User’sGuide”(U0-1100) for additional instructions oninstalling the QLC card in the Q-Line I/O rack of the DPU cabinet.
U0-1115 3-4 7/99
3-3. QLC Card
us
see
.
ses.
LC
:
3-3.2. Setting the DIOB Card Address Switch
The QLC card provides the connection to the DPU through the Distributed I/O B(DIOB). The DIOB address is set by a 7-position DIP switch (seeFigure3-2 for anexample of setting the DIOB switch). This address is required in the QLCalgorithms and in AI or AL analog points used for on-demand communication (Section 4).
Each DIOB address is a hexadecimal number in the range 08H through FBH
The Group 1 QLC card (required in the STI) uses two consecutive DIOB addresThe first (or base) address must end with one of the followingeven hexadecimaldigits:
x0H, x2H, x4H, x8H, xAH, xCH, or xEH
where x = any hexadecimal digit.
Example
The following is an example of assigning addresses 52H - 53H to the Group 1 Qcard (53H - 54H could not be used, since 53H is an odd hexadecimal digit).
The binary equivalents for hexadecimal values 52H and 53H are shown below
Because the base address is always an even hexadecimal number, the leastsignificant bit (bit 0) will always equal 0 (no switch setting is required). Theremaining bits (bits 1 - 7) determine the switch settings.
For each bit that equals 1, the corresponding switch is closed (1 = closed).
For each bit that equals 0, the corresponding switch is open (0 = open).
The switch settings for base address 52H are illustrated inFigure 3-2 .
Bits - Set bits 1 through 7 on the DIOB switch.
76543210
52H = 01010010↑ Disregard bit 0
←For even hexadecimal numbers, bit 0 = 0
53H = 01010011 ↑ Disregard bit 0
←For odd hexadecimal numbers, bit 0 = 1
7/99 3-5 U0-1115
3-3. QLC Card
X
Note
When assigning the QLC address, verify thatthe selected address will not conflict withaddresses required by or assigned to other Q-Line cards. For additional information on Q-Line addressing, see“QLC User’sGuide”(U0-1100).
Figure3-3 illustrates the QLC card, including the DIOB address switch, the iSBconnector where the SST card is mounted, and the board reset switch.
7 6 5 4 3 2 1
Switch number = Bit number
0 1 0 1 0 0 1 0
52HTop of QLC
Bit 0 always = 0(No switch required)
Open = Off = Logic 0(Towards Q-Crate Backplane)
Note: Switch markings may vary.
Figure 3-2. Example DIOB Address Switch Settings
U0-1115 3-6 7/99
3-3. QLC Card
Figure 3-3. QLC Card
DIOB Address Switch
iSBX Connector
Board Reset Switch
7/99 3-7 U0-1115
3-4. SST Card
cardQLC
M
ect
the
e Q-talled
ctor
3-4. SST Card
The Smart Transmitter Interface (SST) card is an extended size iSBX daughterthat mounts on the QLC card. The SST card then provides the link between thecard and up to three QST cards.
The SST card also contains the buffers, line drivers, and receivers needed tocommunicate (through a cable) the iSBX signals to the QST cards.
3-4.1. Installing the SST Card
The installation of the SST card is similar to the installation of the standard SCOdaughter board (if necessary, see“QLC User’s Guide” (U0-1100) for installationinstructions).
Use the following procedure to install the SST card:
1. Plug the SST card into the iSBX connector (seeFigure 3-3 ) on the QLC card.
Note that the upper eight locations of the QLC’s iSBX connector do not connto the SST card.
2. Use the nylon screw and standoff provided with the SST card to secure it toQLC card.
3. After the SST card is attached to the QLC card, and both are installed in thCrate, any QST cards that are to be connected to the SST card must be insin adjacent slots to the left of the QLC/SST card.
4. Connect the QST cards in daisy-chain fashion to the SST card using aribbon-cable assembly (Westinghouse part number 3A98850).
Figure3-4 illustrates the SST card and the location of the SST card conne(J1) for the ribbon-cable assembly that connects to the QST card(s).
SeeSection 3-5 for additional details on QST card installation.
U0-1115 3-8 7/99
3-4. SST Card
Figure 3-4. SST Card
J1Connector
7/99 3-9 U0-1115
3-4. SST Card
ctorspinThisrds,
3-4.2. J1 Connector
The J1 connectors are identical on both the QST and SST cards. The J1 conneconsist of a 40-position right angle latching connector which mates with a 40-ribbon cable assembly (connectors are polarized to ensure proper installation).connector is used to link the SST (mounted on the QLC) to one or more QST caas shown inFigure 3-5 .
Figure 3-5. QST/SST (J1) Connector
U0-1115 3-10 7/99
3-4. SST Card
Table 3-1 identifies the 40 pin assignments of the QST/SST connector.
Table 3-1. QST/SST Interface Connector (J1) Pin Assignments
Signal Name Pin Number Pin Number Signal Name
GROUND 40 39 QSTCHADR5
QSTCHADR4 38 37 QSTCHADR3
QSTCHADR2 36 35 QSTCHADR1
QSTCHADR0 34 33 CARDSEL0
CARDSEL1 32 31 GROUND
QSTDATA7 30 29 GROUND
QSTDATA6 28 27 GROUND
QSTDATA5 26 25 GROUND
QSTDATA4 24 23 GROUND
QSTDATA3 22 21 GROUND
QSTDATA2 20 19 GROUND
QSTDATA1 18 17 GROUND
QSTDATA0 16 15 GROUND
RD,WR/+ 14 13 RD,WR/-
DS/+ 12 11 DS/-
GROUND 10 9 QSTINT0+
QSTINT0- 8 7 QSTINT1+
QSTINT1- 6 5 QSTINT2+
QSTINT2- 4 3 QSTINT3+
QSTINT3- 2 1 GROUND
7/99 3-11 U0-1115
3-4. SST Card
,ve.
3-4.3. SST LED
A bus-enabled LED is located at the front of the SST card. This LED, when litindicates that the connection between the SST card and the QST card is actiFigure 3-6 illustrates the location of this LED.
Figure 3-6. LED on SST Card
LED
U0-1115 3-12 7/99
3-4. SST Card
, thisrd
the
e
d (as
. lit
3-4.4. Using the SST Service Switch
A toggle switch is located on the SST card (seeFigure 3-7 for switch location).When a QST card in an STI configuration must be removed, added, or replacedswitch must be set to BUS DISABLED. This sends a signal to notify the QLC cato stop accessing the QST cards.
The switch positions on the SST card are labeledBUS ENABLED (switch state =1) andBUS DISABLED (switch state = 0).
Perform the following steps when the SST service switch must be used:
1. Set the SST service switch to the BUS DISABLED position when servicingSTI. The BUS ENABLED LED on the SST will turn off. During this period, theQLC does not access any QST card since data may be corrupted while thconnectors are being removed or installed.
In a live system, all QST cards are reset when the service switch is disableindicated by the QST configuration LED being turned off).
Note
While disabled, the quality for process pointsis reported from the QLC to the DPU asbad .Also, the link status is set to zero (nocommunication).
2. Remove, add, or replace the applicable QST card.
3. After the card change is made, set the SST service switch to the BUSENABLED position to resume operation of the Smart Transmitter Interface(This switch state is indicated by the status LED on the SST card which iswhen the switch is enabled, and not lit when the switch is disabled.)
7/99 3-13 U0-1115
3-4. SST Card
Figure 3-7. SST Card Service Switch
ServiceSwitch
U0-1115 3-14 7/99
3-5. QST Card
hput,d, for
ed
3-5. QST Card
The QST card provides the interface to the HART device. To increase througthe Smart Transmitter Interface supports one HART device for each QST carcommunication channel (with six channels per card, and three cards maximuma possible total of 18 smart devices supported per interface).
3-5.1. QST Card Types
There are two types of QST cards that can be used: Group 1 and Group 2.
Features common to all QST card groups of the Smart Transmitter Interfaceinclude:
• Three QST cards are supported by each QLC/SST card combination.
• Six communication channels are supported on each QST card.
• One HART device is supported for each QST card channel.
• Field communications meet the HART Smart Communication ProtocolSpecifications, Revision 5.1.
Note
If the Rosemount Model 268 hand-held unitis connected to the communication linkbetween a QST card channel and a HARTdevice, communication errors may occur inthe QST. These errors may occur because ofdiscrepancies between the HARTcommunication specifications and the hand-held unit’s implementation.
• The channels convert logic-level signals from the QST card to HART-specifiwaveforms.
• Both burst mode and polling mode are supported.
7/99 3-15 U0-1115
3-5. QST Card
m
ides).
er
on
hichhas
ply
Special Features of Group 1 QST Cards
• Each QST card channel is individually isolated from the digital logic and froevery other channel in the interface.
• Each channel on a QST card has a separate 24VDC power supply to provpower to the 4-20mA loop of the HART device (which transmits analog valueEach channel has a loop resistance of 300 ohms.
• In the event of a component failure, internal current limiting protects the powsupply.
Special Features of Group 2 QST Cards
• Each card channel is isolated from the digital logic. The channels are commto each other.
• The channels of the QST card are powered by an external power supply, walso provides power to the 4-20 mA loop of the HART device. Each channela loop resistance of 300 ohms.
• In the event of a component failure or short circuit in the field, the power supis protected by the use of on-card fuses for each channel.
Note
The wiring and fuse arrangements used forGroup 2 QST cards are unique. Typically,Group 2 QST cards are only used in speciallydesigned systems.
U0-1115 3-16 7/99
3-5. QST Card
of
ring
3-5.2. HART Device Types
There are four types of HART devices currently in use (A, B, C, and D). Eachthese types have different power supply requirements.
When installing the QST card (Section3-5.3), the specific type of HART device canbe determined by either reading the manufacturer’s documentation or by compathe HART device’s power supply requirement withTable 3-2 .
Table 3-2. HART Device Types
Device Type Network Supply Description
A Required. Sinks direct current from the Network and receives operatingpower from the Network.
B Required. Sinks direct current from the Network but receives nooperating power from the Network.
C Must not be used. Sources direct current to the Network and receives nooperating power from the Network.
D Not required, butmay be used.
Neither sinks nor sources direct current from the Network,nor receives operating power from the Network.
7/99 3-17 U0-1115
3-5. QST Card
acent
ST
are
le
e
the
rd
ard
r).
3-5.3. Installing the QST Card
Use the following procedure to install the QST card(s):
1. Insert the QST cards that are to be connected to the SST card into the adjQ-Crate slots to the left of the QLC/SST card.
Refer toFigure 3-8 for an illustration of a Smart Transmitter Interfacecontaining three QST cards linked in daisy-chain fashion to a single QLC/Sunit.
Caution
When installing QST cards in a powered-up system, be certain the service switch onthe SST card is in the disabled position.
2. Termination resistors are supplied on all QST cards. If multiple QST cardsused,remove termination resistors (R283 and R286) from the QST cardspositioned between the SST card and the last QST card on the ribbon cabconnection.
3. Donot remove the resistors from the last QST card in the ribbon cableconnection (as illustrated inFigure 3-8 ).
Refer toFigure3-9 for an illustration of the QST card and the location of thesresistors on the QST card.
4. Connect the QST cards in daisy-chain fashion to the SST card by using aribbon-cable assembly (Westinghouse part number 3A98850) to connect toSST card (J1 connector).
If necessary, refer toSection3-4.2 for details on the SST card and the SST caconnector (J1).
5. Connect the QST cards to the HART devices in the field by using the front cedge connector (P2) on the QST card (refer toFigure3-8 for the location of theP2 connector and toTable 3-3 for the card edge signals for the P2 connecto
U0-1115 3-18 7/99
3-5. QST Card
7/99 3-19 U0-1115
3-5. QST Card
Figure 3-8. STI Containing Multiple QST Cards
U0-1115 3-20 7/99
3-5. QST Card
Figure 3-9. QST Card
R283R286
Resistors J1 Connector
P2 Connector
7/99 3-21 U0-1115
3-5. QST Card
Table 3-3. QST Front Card Edge Connector (P2) Signals
Signal Name on ComponentSide of QST
Pin Number Pin NumberSignal Name on Solder Side of
QST
No Connection 28B 28A GROUND
No Connection 27B 27A GROUND
No Connection 26B 26A GROUND
No Connection 25B 25A GROUND
No Connection 24B 24A GROUND
No Connection 23B 23A GROUND
CARDSEL1 22B 22A GROUND
CARDSEL0 21B 21A GROUND
CARD ENABLE/ 20B 20A GROUND
No connection1
External Power Supply (+)219B 19A CHANNEL 5 +
CHANNEL 5 SHLD 17B 17A CHANNEL 5 -
CHANNEL 4 + 15B 15A CHANNEL 4 SHLD
CHANNEL 4 - 13B 13A CHANNEL 3 +
CHANNEL 3 SHLD 11B 11A CHANNEL 3 -
CHANNEL 2 + 9B 9A CHANNEL 2 SHLD
CHANNEL 2 - 7B 7A CHANNEL 1 +
CHANNEL 1 SHLD 5B 5A CHANNEL 1 -
CHANNEL 0 + 3B 3A CHANNEL 0 SHLD
CHANNEL 0 - 1B 1A No connection1
External Power Supply (-)2
1 Group 1 QST cards only.
2 Group 2 QST cards only.
U0-1115 3-22 7/99
3-5. QST Card
e
6. Use the following formula orTable3-4 (whichever calculates the shorter cabllength) to determine the wiring requirements (type and length) for theconnections at the HART field device:where:
L = Cable length (feet or meters).
C = Cable capacitance in pF/feet or pF/meters.
Cf = Maximum shunt capacitance of smart field devices in pF.
(216,000)— (Cf + 10,000)
L = C
Table 3-4. Field Wiring Cable Requirements
Cable Length Cable Size Cable Type
Less than 5,000 feet(1524 meters)
24 AWG (minimum) Single or multiple twisted-pair1
with over-all shield
Greater than 5,000 feet, but lessthan 10,000 feet(3048 meters)
20 AWG (minimum) Single twisted-pair with over-allshield.
1 If multiple twisted-pair cable with over-all shield is used, the shieldmust be connected to earth ground at the half-shell in the termination (B) cabinet.
7/99 3-23 U0-1115
3-5. QST Card
see
(see.
ard
cardcifica
the
7. Install the card enable jumper on the QST P2 front card edge connector (Figure 3-10 ). This jumpermust always be installed or the card will not beenabled.
Figure 3-10 illustrates the location of this jumper andTable 3-3 identifies thelocation of this jumper on the P2 front card edge connector.
8. Install the card selection jumpers on the QST P2 front card edge connectorFigure 3-10 ). These jumpers identify a specific QST card to the QLC card
Figure 3-10 illustrates the locations of these jumpers andTable 3-3 identifiesthe locations of these jumpers (CARDSEL0 and CARDSEL1) on the front cedge connector.
These card selection jumpers do not select a DIOB address since the QSTdoes not interface directly to the DIOB. Instead, these jumpers encode a speQST address for the QLC card. Insertion of a card selection jumper encodes1.
Table3-5 illustrates the possible combination of card selection jumpers andQST card assignment they represent.
Table 3-5. QST Card Assignment to the QLC
Pin 22 A/B Pin 21 A/B QST Card Assignment
No jumper installed. No jumper installed. QST 0
No jumper installed. Jumper installed. QST 1
Jumper installed. No jumper installed. QST 2
U0-1115 3-24 7/99
3-5. QST Card
7/99 3-25 U0-1115
3-5. QST Card
Figure 3-10. Jumper Locations on P2 Connector
U0-1115 3-26 7/99
3-5. QST Card
T
9. Connect the QST to the HART field devices as follows (if necessary, refer to“Q-Line Installation Manual” (M0-0053) for field interface wiring conventions).
Proceed toStep 10 when usingGroup 1 QST cards.
Proceed toStep 11 when usingGroup 2 QST cards.
10. Refer toFigure 3-11 for the wiring diagram that illustrates the Group 1 QScard field connections.
Proceed to Step 12.
7/99 3-27 U0-1115
3-5. QST Card
.
Figure 3-11. Wiring Diagram for QST Group 1 Field Connections
U0-1115 3-28 7/99
3-5. QST Card
Tardspply
BIs
11. Refer toFigure 3-12 for the wiring diagram that illustrates the Group 2 QScard field connections. The external power supply is brought to the QST cvia the taper pin bus. For maximum noise protection, a separate power suassembly should be used to power only the QST cards.
If the power supply assembly is used to power other I/O cards (such as Qand/or QBOs), a line filter is recommended for use to minimize the noisebrought to the QST cards (as shown inFigure 3-12 ).
Note
The wiring and fuse arrangement for theGroup 2 QST cards is unique. Group 2 QSTcards are only used in specially designedsystems.
7/99 3-29 U0-1115
3-5. QST Card
.
Figure 3-12. Wiring Diagram for QST Group 2 Field Connections
U0-1115 3-30 7/99
3-5. QST Card
fer
Tance
erop
nels
ers
12. There are four types of HART devices (A, B, C, and D) currently in use (reto Section 3-5.2 to determine what type of device is being used).
Each of these types have different power supply requirements. Most HARdevices (types A, B, and D) use the standard QST channel with a loop resistof 300 ohms and a +24VDC power supply (22.8V minimum).
Verify that the HART device being used (refer to HART device manufacturdocumentation) will function with a 22.8V power supply and a 300 ohm loresistance.
13. When using a Type A, B, or D HART device, confirm that the configuratiojumpers (JU1 through JU6) on the QST card that correspond to the channconnected to A, B, or D type HART devices are in the A, B, D position (seeFigure 3-13 ).
14. Type C HART devices mustnot be connected to the 24VDC power supply.
Therefore, when using a Type C HART device, move the configuration jump(JU1 through JU6) on the QST card to the C,D position (seeFigure 3-13 )
This is doneonly on the channel connected to a type C HART device.
7/99 3-31 U0-1115
3-5. QST Card
3-5. QST Card
Figure 3-13. Examples of Configuration Jumper Settings for QST Card
Configuration JumperSet for Type A, B, or DHART Device
Configuration JumperSet for Type CHART Device
A, B,C, D
A, B,C, D
U0-1115 3-30 7/99
3-5. QST Card
d
see
1. Refer toFigure3-14 for an illustration of the four types of HART devices antheir network connections.
2. Connect the cable shield to earth ground only at the half-shell connector (Figure 3-14 ).
Figure 3-14. HART Device Types
7/99 3-31 U0-1115
3-5. QST Card
ice
tee to
ata
s
nel.
orm
is ofto
3-5.4. QST Transfer of Data
The following information describes the transfer of data between the HART dev(up to 6 for each QST card) and the QLC card.
1. The QST card contains special interface and logic circuitry to communicawith the QLC through the SST card. The logic circuitry routes the messagthe proper QST channel in the UART on the QST card.
2. Six UART channels interface to HART modem chips. When the QSTsendsdatato the HART devices, these HART modem chips convert the UART serial dto Frequency-Shift-Keyed (FSK) data.
When the QSTreceives data from the HART device, the HART modem chipconvert the FSK data to UART serial data.
3. The FSK data is optically coupled to the corresponding HART analog chan
4. The analog channels convert the FSK logic level signals to a voltage wavef(per the HART specification described below) whentransmitting data to theHART devices.
The HART protocol uses the Frequency Shift Keying technique as the basits communication. The signal uses the frequencies of 1200 and 2200 Hz represent the digits 1 and 0, respectively.
The bit sequence for this technique is as follows:
1 start bit, 8 data bits, 1 odd parity, 1 stop bit
Mark (logic 1) frequency 1200 Hz +/- 1%
Space (logic 0) frequency 2200 Hz +/- 1%
5. Communication signals (as described inSection 3-5.5) are converted to FSKlogic level signals whenreceiving data from the HART devices.
U0-1115 3-32 7/99
3-5. QST Card
ge
ices
ard
an
3-5.5. Communication Signals
Data is transferred between the QST card and the HART device through voltawaveforms.
Transmitted Waveform
The waveforms used in the transfer of data from the QST card to the HART devmeet the requirements as defined inFigure 3-15 (transmitted under a test load of1000 ohm +/- 1%).
Received Waveform
The waveforms used in the transfer of data from the HART device to the QST chave the following signal range:
120 mV p-p minimum
1.5 V p-p maximum
The received waveform is qualified by a carrier detect signal. Carrier detect isindication that a valid HART signal is being received by the QST card. Thefollowing are the characteristics of carrier detect:
Carrier Detect Activation 120 mV p-p min
Carrier Detect De-activation 80 mV p-p min
Carrier On to Carrier Detect Assertion 30 bit times max
Carrier Off to Carrier Detect Disassertion 30 bit times max
7/99 3-33 U0-1115
3-5. QST Card3-
5. Q
ST
Car
d
Figure 3-15. Transmitted Waveform
U0-1115 3-34 7/99
3-5. QST Card
lit,
3-5.6. QST LEDs
Two LEDs are located at the front of the QST card. The top LED (LE1), whenindicates the presence of 12 volts of power (PWR) from the DIOB.
The bottom LED (LE2), when lit, indicates that the UART in the QST hadconfiguration (CONFIG) commands written to it.
Figure 3-16 illustrates the location of these LEDs.
7/99 3-35 U0-1115
3-5. QST Card
LEDs
Figure 3-16. LEDs on QST Card
U0-1115 3-36 7/99
3-6. Smart Transmitter Interface Start-up
uired
d in
eing
e.
LC
PU
3-6. Smart Transmitter Interface Start-up
This section is intended to provide the user with an overview of the steps reqto start-up the Smart Transmitter Interface.
Detailed instructions are provided in the referenced sections.
1. Wire the HART devices to the QST card connectors (described inSection 3).
2. Plug the SST card into the iSBX connector on the QLC card (as describeSection 3)before inserting the QLC card into the Q-Crate.
3. Configure the QLC card hardware (described inSection 3) by setting all theswitches and jumpers on the QLC card that are applicable to the system bused.
4. Insert the QLC card (with SST card attached) into the appropriate Q-Crat
5. Configure the QLC card software (described inSection4) as needed for the typeand number of HART devices being used in the system.
6. Disable theBUS ENABLED/BUS DISABLED toggle switch on the SST cardby setting the toggle switch to the BUS DISABLED position.
7. Insert the desired number of QST cards into the Q-Crate to the left of the Qcard and connect the edge connectors and ribbon cable (described inSection 3).
8. Reenable theBUS ENABLED/BUS DISABLED toggle switch on the SSTcard by setting the toggle switch to the BUS ENABLED position.
9. Restart the QLC card by pressing theBOARD RESET switch (SW2) on theQLC card. After the Smart Transmitter Interface is running, program the DQLC algorithms (described inSection 4)
.
7/99 3-37 U0-1115
face
Section 4. Software Configuration
4-1. Section Overview
This section describes the software necessary for the Smart Transmitter Interand the configuration required for that software.
The following topics are discussed:
• QLC card configuration (Section 4-2).
• QST card channels (Section 4-3).
• Transfer of periodic information from the sensor device to the DPU (Section 4-4).
• On-demand communication (Section 4-5).
7/99 4-1 U0-1115
4-2. Configuring the QLC Card
ace.
IN,RT
LC
o the
4-2. Configuring the QLC Card
The QLC card provides the processing control for the Smart Transmitter Interf
The use of the QLC card requires the use of QLC algorithms (QLCAIN, QLCGPand QLCDIN) to read in the Smart Transmitter Interface values, since the HAdevice values will not be automatically processed (if necessary, refer to“QLCUser’s Guide”(U0-1100) and“Control Algorithms” (U0-0106) for additionalinformation and descriptions of the QLC algorithms).
In addition, use the procedures listed in the following sections to configure the Qcard in order to enable the Smart Transmitter Interface.
4-2.1. Modifying the AUTOEXEC.BAT File
In order to enable the interface to start automatically when power is applied tQLC or when the QLC is reset, perform the following:
• Add the following line to the QLC AUTOEXEC.BAT file:
HARTCOMM
4-2.2. Copying Initialization Files
In order to initialize the Smart Transmitter Interface, perform the following:
• Copy the following files to the QLC card:
• HARTCOMM.EXE (an STI executable program).
• CMDS.DAT (a universal command definition file).
The following sample commands are an example of this procedure:
COPY B:HARTCOMM.EXE A:
COPY B:CMDS.DAT A:
U0-1115 4-2 7/99
4-2. Configuring the QLC Card
ef the
k tothe
t be
ame
:
C
the,
4-2.3. Using Rosemount Device Description Language
If any commands are used that are unique to a specific HART device, then thRosemount Device Description Language must be used to define the formats ocommands. Perform the following to use the Device Language:
1. Place the Device Description Language binary file onto the QLC card’s disimplement these HART device specific commands (this file is available frommanufacturer of the device).
2. Rename the manufacturer’s filename.
In order for the QLC card to match the Device Description files with theappropriate HART devices, a unique filename is required (this filename musdifferent from the manufacturer’s filename).
The format for the construction of a unique filename is shown below:
xxxyyy.OUT
where:
xxx= Decimal representation of the manufacturer ID code.
yyy= Decimal representation of the device type code.
For example:
If a Rosemount 3051C pressure transmitter is used, then the applicable filenis determined by the following:
Rosemount’s Manufacturer ID code =38.Rosemount’s 3051C pressure transmitter device code =6.
Therefore, the new filename for the Device Description binary file will be038006.OUT.
3. The following sample command is an example of the renaming procedure
COPY B:3051CRZ.OUT A:038006.OUT
This command will copy the manufacturer’s file (3051CRZ.OUT) to the QLcard using the correct filename (038006.OUT).
Manufacturer ID and device type codes for Rosemount devices are listed inRosemount manual “HART - Smart Communications Protocol” (D9000051Revision A, Common Tables). Values for HART devices from othermanufacturers are available from those manufacturers.
7/99 4-3 U0-1115
4-3. QST Card Channels
theardviceC
e perART
ed to
ector
4-2.4. Running BAKFLASH
In order to copy all the QLC configuration changes to non-volatile RAM, thefollowing must be performed:
1. Load the required files and update AUTOEXEC.BAT as described in thepreceding sections.
2. Run BAKFLASH as described in“QLC User’s Guide” (U0-1100).
4-3. QST Card Channels
The QST card provides the actual physical connection to the HART device infield. The data gathered from the HART device is transmitted through the QST cto the QLC shared memory where it can be accessed by the DPU. The HART desending the data must be identified so that the DPU can locate the data in QLshared memory.
The HART devices are identified by the QST card channels to which they areconnected. Each QST card has six channels and can support one HART devicchannel. Since the software currently has provisions for three QST cards, 18 Hdevices can be used for each STI.
Table 4-1 lists the possible QST card assignment names and the numbers usidentify the HART devices connected to the QST cards. The card names aredetermined by setting card selection jumpers on the QST card front edge conn(refer to ‘Installing the QST Card’ inSection 3 for QST card jumperconfigurations).
Table 4-1. Smart Transmitter Interface Identification Numbers
QST Card HART Device Channel Number
QST 0 0 to 5
QST 1 6 to 11
QST 2 12 to 17
U0-1115 4-4 7/99
4-4. Transferring Information to the DPU
STI
icmitterng.
(see
4-4. Transferring Information to the DPU
The HART devices collect dynamic variables (process values) in the field. Thetransfers these dynamic variables to the QLC shared memory where they areaccessed by the DPU.
Devices, using the HART protocol, are capable of returning up to four dynamvariables on a periodic basis. For example a Rosemount 3051C pressure transnot only provides a pressure reading, it can also provide a temperature readi
4-4.1. QLC Algorithms
The algorithms QLCAIN, QLCGPIN and QLCDIN are used to obtain theinformation from the QLC shared memory (refer to“Control Algorithms” (U0-0106) for descriptions of these algorithms and instructions on their use).
The QLCAIN algorithm is used to read in the dynamic process variables (seeSection 4-4.2).
The QLCGPIN algorithm is used to read in the device status byte(seeSection 4-4.3).
The QLCDIN algorithm is used to read in the communication channel status bitSection 4-4.4).
7/99 4-5 U0-1115
4-4. Transferring Information to the DPU
ues)LCsed
teced
real
the
n-
4-4.2. Reading Value and Quality of Dynamic Process Variables
The Smart Transmitter Interface will read all the dynamic variables (process valavailable from a HART device and place these values into fixed locations in Qshared memory. The values returned will be in the normal floating point format uthroughout the WDPF system. These values have already been converted toengineering units by the smart device.
In addition, a two-bit quality value will also be updated by the QLC card to indicathe quality of the associated variable. The process values and quality will be plainto shared memory (two QLC registers for the value and one register for thequality) in the locations listed inTable 4-2 .
TheQLCAIN algorithm is used to read in the process variables. The QLCAINalgorithm must be used with an FRMT parameter of 3 which indicates an Intelformat value with quality bits (seeAppendix C for an example of using theQLCAIN algorithm).
When using the QLCAIN algorithm, the DIOB address of the process point isdetermined by the PHW parameter in the algorithm, not from the HW field of point record.
SeeSection 4-5.1 for configuration of the point record’s HW field when using odemand functions.
Table 4-2. QLC Register Locations for Dynamic Variables (Registers 0-435)
ChannelNumber
Primary(First) Variable
Secondary(Second) Variable
Tertiary(Third) Variable
FourthVariable
0 Register 0 Register 128 Register 256 Register 384
1 Register 3 Register 131 Register 259 Register 387
2 Register 6 Register 134 Register 262 Register 390
. . . . .
. . . . .
. . . . .
16 Register 48 Register 176 Register 304 Register 432
17 Register 51 Register 179 Register 307 Register 435
U0-1115 4-6 7/99
4-4. Transferring Information to the DPU
e ofbyte
into
d is
4-4.3. Reading Device Status Bytes
Two status bytes are included within each response from the HART devices. Onthese is a communication status byte used internally in the QLC software. Thisis not available to the user.
The second is a device status byte which is available to the DPU and is placedQLC shared memory registers 512 to 529 as shown inTable 4-3 .
This device status byte indicates various conditions within the HART device anformatted as shownTable 4-4 (for more information on the status byte, see theHART protocol specification).
Table 4-3. Mapping Channels to Status Byte Registers (Registers 512 - 529)
Channel Number Register Number
0 Register 512
1 Register 513
2 Register 514
. .
. .
. .
16 Register 528
17 Register 529
7/99 4-7 U0-1115
4-4. Transferring Information to the DPU
ise
TheQLCGPIN algorithm is used to access this information (seeAppendixC for anexample of using the QLCGPIN algorithm).
When using the QLCGPIN algorithm, the DIOB address of the process point determined by the PHW parameter of the algorithm, not by the HW field of thpoint record.
Table 4-4. HART Device Condition Status Byte (Registers 512 - 529)
Bit Number Description
0 Primary variable out of limits.
1 Non-primary variable out of limits.
2 Primary variable analog output saturated.
3 Primary variable analog output fixed.
4 More status available.
5 Cold start.
6 Configuration changed.
7 Field device malfunction.
8 through 15 Not used.
U0-1115 4-8 7/99
4-4. Transferring Information to the DPU
iscedoodd as
see
the
after
4-4.4. Reading the Communication Channel Status Bit
The status of the communication channel is available to the DPU. The statusindicated by a QST card channel communication status bit. This bit will be plainto QLC shared memory registers 544 to 561. Each register will be set to 1 for gchannel communication or 0 for bad channel communication, and is formatteshown inTable 4-5 .
TheQLCDIN algorithm is used to read in the communication channel status bit (Appendix C for an example of using the QLCDIN algorithm).
When using the QLCDIN algorithm, the DIOB address of the process point isdetermined by the PHW parameter of the algorithm, not from the HW field of point record.
The communication channel status bit is set to 0 if the device does not respondthree requests, or if no burst mode message is received after three seconds.
Table 4-5. Communication Condition Status Bit (Registers 544 - 561)
Channel Number Register Number Register Value (1 = Good; 0 = Bad)
0 Register 544 1 or 0
1 Register 545 1 or 0
2 Register 546 1 or 0
. . .
. . .
. .
16 Register 560 1 or 0
17 Register 561 1 or 0
7/99 4-9 U0-1115
4-5. Enabling On-Demand Communication
vice
PF
TI (see
U’s
art the
4-5. Enabling On-Demand Communication
The Smart Transmitter Interface provides the ability to use on-demandcommunication to access the extended capabilities of the HART devices. Anycommands or requests that the HART device supports may be sent to the dethrough the interface. These commands allow the user to read/write theconfiguration of the HART devices from any man-machine interface on the WDsystem.
General Purpose Messages (GPM) are used to send these commands to the SSection 4-5.2 for more information on GPM).
In order to enable this on-demand communication, some configuration of the DPdatabase is required (if necessary, refer to“MA C Application Utilities User’sGuide” (U0-0136) for procedures on database configuration).
4-5.1. Setting the HW Field for On-Demand Communication
The HW field of an analog point record (AI or AL records) must be properlyconfigured to enable on-demand communication for that point. The following ch(representing bits in an analog point HW field) can be used to help determineapplicable bits to set for a specific system.
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Set Bit 15 for GPM Communication
Channel NumberQST
(2 * QLC DIOB Card Address)
Hardware Address
U0-1115 4-10 7/99
4-5. Enabling On-Demand Communication
llsrd
he
fora
The HW field of the analog points (AI or AL records) coming from the HARTdevices must be set to the values shown inTable 4-6 .
Example
The following is an example of determining the HW field for an analog point.
Use the following formula:
HW = (2 * QLC card address) + (QST channel number * 1024) + 8000H
Insert the following values into the formula:
Using the above values in the equation provides the following HW field value:
HW = (2 * 80H) +(3 * 1024) + 8000H
HW = (100H) +(3072) + 8000H
HW = 100H + C00H + 8000H
HW = 8D00H
Note
In systems with extended I/O, an offset must beadded to the HW field value. Consult the system-specific documentation to determine this offset.
Table 4-6. Setting Analog Point HW Field
Bit Number Action Required
0 through 9 Set these bits to two times the DIOB card address of the QLC card. This tethe DPU where to transfer incoming messages (refer to ‘Setting the DIOB CaAddress Switch‘ inSection 3 for instructions on determining QLC address).
10 through 14 Set these bits to indicate the channel number of the HART device. This tells tQLC software which device is to receive the message.
15 This bitmust be set in order that GPM messages can be sent to the deviceon-demand communication. This tells the DPU that this point comes from QLC and is not to be read in during the normal scan.
QLC card address = 80H
QST channel number = 3 (valid range is 0 through 17).
7/99 4-11 U0-1115
4-5. Enabling On-Demand Communication
tion
nd
d to
romThe to the
atedent
rmat
4-5.2. Sending Messages to the Smart Transmitter Interface
After the necessary DPU configuration is completed, on-demand communicacan be performed using General Purpose Messages (GPM). Typically, customgraphics (displayed on a station acting as an Operator Station) are used to semessages to the DPU and receive responses from the HART devices(seeAppendixB for sample graphics). User-designed programs can also be usesend messages.
The GPM message contains the System ID (SID) of a process point coming fthe STI. This directs the message to the correct DPU, QLC, and HART device.message also contains any other information necessary to send the messagedevice.
After the message is received at the DPU, it is sent to the QLC, where it is transland processed (as described inSection 4-5.4). The translated message is then sto a QST card which sends it out to the HART device.
All messages sent to the Smart Transmitter Interface must have the general foshown inTable 4-7 .
Table 4-7. Smart Transmitter Interface Messages
Word Message Format
Word 0 GPM Message Type (75).
Word 1 Prode number (initialized by process diagram).
Word 2 SID of point associated with the HART device.
Word 3 HART command number.
Word 4 Size in bytes of data section to follow.
Word 5 - N Data portion of message.
U0-1115 4-12 7/99
4-5. Enabling On-Demand Communication
STlated
es) is
4-5.3. Receiving Messages from the Smart Transmitter Interface
After the message is received at the HART device, a response is sent to the Qfrom the device. The QST then sends the response to the QLC, where it is transand processed (as described inSection 4-5.4).
The translated message (in the form of block data, and including response codsent to the DPU which returns it to the message originator.
The format of the returned block data is described inTable 4-8 .
Table 4-8. Smart Transmitter Interface Block Data
Word
Response Codefrom DPU or
QLC Description
Word 0 0 Function completed successfully.
1 QLC card busy, try again later.
2 No QLC card associated with SID.
3 DPU cannot pass message to QLC card (buffers full).
4 DPU not on-line.
5 SID is invalid point type (must be analog, digital, oralgorithm).
16 Card to HART device busy.
17 Command not defined for HART device.
18 Internal error - cannot allocate memory.
19 Card not initialized.
20 Device error.
21 No response from device.
Word 1 — Command number from response.
Word 2 — First response code byte.
Word 3 — Second response code byte.
Word 4 — Size in bytes of data section.
Word 5 — Translated data.
7/99 4-13 U0-1115
4-5. Enabling On-Demand Communication
andicesis
unt’sands.
ble
teng
4-5.4. Translating STI Communication Data
In order to ensure that communication is possible between the WDPF systemthe HART devices, the different data types going to and coming from the devmust be translated (seeTable 4-9 ). The QLC card software is able to perform thconversion since the QLC card contains information defining the HARTcommands.
If any commands unique to the specific HART devices are used, then RosemoDevice Description Language must be used to define the formats of the comm
To implement any specific HART device commands, the Device DescriptionLanguage binary file must be placed onto the QLC card’s disk (this file is availafrom the manufacturer of the device).
In order for the QLC card to match Device Description files with the appropriaHART devices, the file must be given a specific filename. Directions for creatithis unique filename are provided in QLC configuration instructions inSection4-2.
U0-1115 4-14 7/99
4-5. Enabling On-Demand Communication
that
Data Translation
Table4-9 describes the translations performed by the QLC software on the datais sent between the WDPF system and the HART devices.
Table 4-9. Data Translation
HART Data TypeClassification Translation Performed
ASCII Bytes are copied as is. If the HART requires an odd number of bytes,the WDPF side is rounded to an even number of bytes.
BIT_ENUMERATED On the HART side, either one or two bytes are used and will beswapped if necessary. One word is used on the WDPF side.
BIT_STRING On the HART side, either one or two bytes are used and will beswapped if necessary. One word is used on the WDPF side.
DATE Three bytes used on the HART side correspond to three words used onthe WDPF side.
DATE_AND_TIME Six bytes used on the HART side correspond to six words used on theWDPF side.
ENUMERATED On the HART side, either one or two bytes are used and will beswapped if necessary. One word is used on the WDPF side.
FLOAT The appropriate translation will be performed to a four-byte realnumber. The data will be aligned on a four-byte boundary.
INDEX One byte is used on the HART side. One word is used on the WDPFside.
INTEGER For a one or two byte integer on the HART side, a word is used on theWDPF side. For three or four byte integers, two words are used on theWDPF side. Double words are aligned on a four-byte boundary.
PACKED_ASCII On the WDPF side, normal ASCII characters are used. These aretranslated into the HART packed ASCII characters.
TIME Three bytes used on the HART side correspond to three words used onthe WDPF side.
UNSIGNED For a one or two byte integer on the HART side, a word is used on theWDPF side. For three or four byte integers, 2 words are used on theWDPF side. Double words are aligned on a four-byte boundary.
7/99 4-15 U0-1115
4-5. Enabling On-Demand Communication
o
t
Data Translation Examples
The following examples illustrate how data is translated from HART protocol tWDPF data.
The commands used are Rosemount commands described in the Rosemounmanual “HART- Smart Communications Protocol” (D8900038, Revision B,Universal Command Specification). Refer toAppendixB for sample graphics usingthis command.
Example 1
Command 0 is used:READ UNIQUE IDENTIFIER
Table 4-10. HART/WDPF Translation Example (Command 0)
BytesUsed
HARTFormat
BytesUsed
WDPFFormat Description of Translated Data
0 254 0-1 254 Constant.
1 byte 2-3 word Manufacturer’s identification code.
2 byte 4-5 word Manufacturer’s device type code.
3 byte 6--7 word Number of preambles required for request usage.
4 byte 8-9 word Universal Command document revision level.
5 byte 10-11 word Translation Specific document revision level.
6 byte 12-13 word Software revision level.
7 byte 14-15 word Hardware revision level of electronics used in thisdevice.
8 byte 16-17 word Flags.
9-11 24-bit 18-211 real device Device identification number.
1 All offsets are within the data section of the block data. For example, the device ID field is located at offset 18 in the data section. However, in the entire block-data, it is at offset 28, a four-byte boundary.
U0-1115 4-16 7/99
4-5. Enabling On-Demand Communication
Example 2
Command 18:WRITE TAG, DESCRIPTOR, DATE
Table 4-11. HART/WDPF Translation Example (Command 18)
BytesUsed
HARTFormat
BytesUsed
WDPFFormat Description of Translated Data
0-5 packed 0-7 ASCII Tag
6-17 packed 8-23 ASCII Descriptor
18-20 DATE 24-29 3 words Date (day, month, year)
7/99 4-17 U0-1115
Appendix A. Smart Transmitter InterfaceSpecifications
A-1. Section Overview
This section provides specifications for the Smart Transmitter Interface.
These specifications include:
• System requirements (Section A-2).
• Power requirements (Section A-3).
• HART specifications (Section A-4).
• Field wiring requirements (Section A-5).
• Current loop (network) specifications (Section A-6).
7/99 A-1 U0-1115
A-2. STI System Requirements
A-2. STI System Requirements
QLC Card, Group 1 Revision D or later
SST Card
QST Card, up to three per QLC/SST, allowing monitoring of up to 18 HARTdevices.
A-3. STI Power Requirements
Table A-1. DIOB Supply
CardMinimumVoltage
NominalVoltage
MaximumVoltage
TypicalCurrent
MaximumCurrent
QLC (with SST) 12.4 V 13.0 V 13.1 V 0.65 A 1.3 A
QST Group 1 12.4 V 13.0 V 13.1 V 0.80 A 1.1 A
QST Group 2 12.4 V 13.0 V 13.1 V 0.25 A 0.40A
Table A-2. External Supply
CardMinimumVoltage
NominalVoltage
MaximumVoltage
TypicalCurrent
MaximumCurrent
QST Group 2 22.8 V 24.0 V 25.2 V 0.24 A 0.30 A
U0-1115 A-2 7/99
A-4. HART Specifications
l
f itssent
A-4. HART Specifications
The STI meets the requirements of the HART Smart Communication ProtocoSpecifications, Revision 5.1. These requirements are listed inSectionA-4.1 throughSection A-4.4.
A-4.1. Basic Communications
The HART protocol uses the Frequency Shift Keying technique as the basis ocommunication. The signal uses the frequencies of 1200 and 2200 HZ to reprethe digits 1 and 0 respectively.
Bit Sequence
1 start bit, 8 data bits, 1 odd parity, 1 stop bit
Mark (logic 1) frequency 1200 Hz +/- 1%
Space (logic 0) frequency 2200 Hz +/- 1%
A-4.2. Transmitted Waveforms
The transmitted waveform meets the requirements as defined in the followingFigure A-1 under a test load of 1000 ohm +/- 1%.
Figure A-1. Transmitted Waveform
7/99 A-3 U0-1115
A-4. HART Specifications
l
m
m
A-4.3. Received Waveforms
Receive Signal Range 120 mV p-p min
1.5 V p-p max
The received signal is qualified by an internally generated carrier detect signawhich meets the following HART requirements:
Carrier Detect Activation 120 mV p-p min
Carrier Detect De-activation 80 mV p-p min
Carrier On to Carrier Detect Assertion 30 bit times max
Carrier Off to Carrier Detect Disassertion 30 bit times max
A-4.4. Impedance
As a HART primary master device, the QST card meets the following HARTrequirements:
Sending Only:
Parameter Limits
Real part (resistance) 0 ohm to 700 ohm
Imaginary part (reactance) -35 ohm to +35 ohm
Receive Only:
Parameter Limits
Real part (resistance) 230 ohm to 1100 oh
Imaginary part (reactance) -350 ohm to +350 oh
U0-1115 A-4 7/99
A-5. Field Wiring Requirements
ions
A-5. Field Wiring Requirements
Use the following formula orTable A-3 (whichever calculates the shorter cablelength) to determine the wiring requirements (type and length) for the connectat the HART field device:
Cable type = Single pair shielded or multiple pair with overall shield
Cable size = 24 AWG minimum below 5000 feet total length
20 AWG minimum above 5000 feet total length
Maximum twisted-pair length = 10,000 feet
Maximum multiple twisted-pair length = 5,000 feet
Cable length formula:
where:
L = Cable length (feet or meters).
C = Cable capacitance in pF/feet or pF/meters.
Cf = Maximum shunt capacitance of smart field devices in pF.
(216,000) — (Cf + 10,000)
L = C
Table A-3. Field Wiring Cable Requirements
Cable Length Cable Size Cable Type
Less than 5,000 feet(1524 meters)
24 AWG (minimum) Single or multiple twisted-pairwith over-all shield.
Greater than 5,000 feet, but lessthan 10,000 feet(3048 meters)
20 AWG (minimum) Single twisted-pair with over-allshield.
7/99 A-5 U0-1115
A-6. Current Loop (Network) Specifications
lyvice
A-6. Current Loop (Network) Specifications
Loop Resistance: 300 ohms maximum
Loop Power Supply:
Group 1: 24V nominal, 22.8V min, 30V max
Group 2: 24V +/- 5%
This information is required for determining the compatibility of the power suppand loop resistance with the particular HART device to be used. Each HART demodel provides a power supply versus loop resistance graph which must beconsulted to ensure proper communication with the QST card.
U0-1115 A-6 7/99
ic to
Appendix B. Sample Graphics
B-1. Section Overview
This section provides two sample graphics that illustrate using a custom graphcommunicate with the Smart Transmitter Interface.
These samples are:
• Subscreen (Section B-2).
• Main screen (Section B-3).
Note
These sample graphics were designed tooperate on 6 or 7-level software systems.
7/99 B-1 U0-1115
B-2. Sample Subscreen
mitter
B-2. Sample Subscreen
This sample is a subscreen which is used to send a request to the Smart TransInterface for information regarding the HART device identification.
************************************************************This sample sends a request to a Smart Transmitter Interface
to send a command 0 to a transmitter to get ID info************************************************************
TITLE ‘Smart Transmitter interface subscreen’
DIAGRAM 800 0 SUBSCREEN
BACKGROUND
COLOR FG MAGENTA
TEXT 30 43 ‘SMART TRANSMITTER INTERFACE’
COLOR FG BLACK BG YELLOW
TEXT 02 45 ‘P1’
COLOR FG CYAN BG BLACK
TEXT 05 45 ‘READ UNIQUE IDENTIFIER’* P1
TEXT 65 45 ‘POINT NAME’ * ENTRY FIELD
************************************************************
KEYBOARD
COLOR FG WHITE BG BLUE
ENTRY_FLD 77 45 8 1 BOTH * POINT NAME ENTRY FIELD
***************************
* READ UNIQUE IDENTIFIER *
***************************
* func_key key# #progs
FUNC_KEY 1 1
* pgm diag #arg
67 3111 19
U0-1115 B-2 7/99
B-2. Sample Subscreen
* blank #arg screen num screen num num
* flag sent index read index read drops
0 3 1 0 2 1 1
* buffer size pointer seg diag displayed
* in K after msg sent
1 5 3111
* drop number screen read type
* entry field index 1 = integer
0 2 $S1 SR * GET DROP # FROM POINT
* msg type msg type
* entry field
0 111
* point id
0 $S1 ID
* hart cmd read unique identifier
0 0
EXIT
7/99 B-3 U0-1115
B-3. Sample Main Screen
e for
ointDPF
B-3. Sample Main Screen
This sample is a main screen that will be displayed when the request messaginformation regarding the HART device identification is returned.
Table B-1 lists the bytes used as returned from the device, and the process pstatements in the sample main screen illustrate the data as it is displayed in Wformat.
Table B-1. HART/WDPF Translation (Command 0)
BytesUsed
HARTFormat
BytesUsed
WDPFFormat Description of Translated Data
0 254 0-1 254 Constant.
1 byte 2-3 word Manufacturer’s identification code.
2 byte 4-5 word Manufacturer’s device type code.
3 byte 6--7 word Number of preambles required for request usage.
4 byte 8-9 word Universal Command document revision level.
5 byte 10-11 word Translation Specific document revision level.
6 byte 12-13 word Software revision level.
7 byte 14-15 word Hardware revision level of electronics used in thisdevice.
8 byte 16-17 word Flags.
9-11 24-bit 18-21 real Device identification number.
U0-1115 B-4 7/99
B-3. Sample Main Screen
************************************************************
TITLE ‘SMART INTERFACE MAIN SCREEN - READ UNIQUE IDENTIFIER’
DIAGRAM 3111 0 MAIN
BACKGROUND
COLOR FG YELLOW BG BLACK
TEXT 40 1 ‘SMART TRANSMITTER INTERFACE’
************************************************************
TRIGGER 1
POINTER $P90 5 0
COLOR FG WHITE BG BLACK
IF ($P90 $I0 = 0)
IF ($P90 $I4 = 0)
IF ($P90 $I2 = 0) * UNIQUE IDENTIFIER
COLOR FG WHITE
TEXT 2 5 ‘FIRST RESPONSE BYTE’
TEXT 2 7 ‘SECOND RESPONSE BYTE’
PROCESS_PT 28 5 5 $P90 $I4 FORMAT HEX
PROCESS_PT 28 7 5 $P90 $I6 FORMAT HEX
TEXT 2 11 ‘MANUFACTURER ID CODE’
TEXT 2 13 ‘DEVICE TYPE CODE’
TEXT 2 15 ‘NUMBER OF PREAMBLES’
TEXT 2 17 ‘UNIVERSAL CMD REV’
TEXT 2 19 ‘TRANSMITTER SPECIFIC REV’
TEXT 2 21 ‘SOFTWARE REV’
TEXT 2 23 ‘HARDWARE REV’
TEXT 2 25 ‘FLAGS’
TEXT 2 27 ‘DEVICE ID NUMBER (LO)’
TEXT 2 29 ‘DEVICE ID NUMBER (HI)’
7/99 B-5 U0-1115
B-3. Sample Main Screen
COLOR FG YELLOW
PROCESS_PT 28 11 5 $P90 $I12
PROCESS_PT 28 13 5 $P90 $I14
PROCESS_PT 28 15 5 $P90 $I16
PROCESS_PT 28 17 5 $P90 $I18
PROCESS_PT 28 19 5 $P90 $I20
PROCESS_PT 28 21 5 $P90 $I22
PROCESS_PT 28 23 5 $P90 $I24 FORMAT BINARY
PROCESS_PT 28 25 5 $P90 $I26 FORMAT BINARY
PROCESS_PT 28 27 5 $P90 $I28
PROCESS_PT 28 29 5 $P90 $I30
END_IF
IF ($P90 $I2 <> 0) * ERRONEOUS COMMAND
COLOR FG RED
TEXT 10 31 ‘ERRONEOUS RESPONSE RECEIVED’
END_IF
END_IF
IF ($P90 $I4 <> 0)
COLOR FG RED
TEXT 10 31 ‘ERROR RESPONSE FROM TRANSMITTER’
END_IF
END_IF
IF ($P90 $I0 <> 0)
COLOR FG RED
TEXT 10 31 ‘ERROR RESPONSE FROM QLC’
PROCESS_PT 35 31 5 $P90 $I0
END_IF
EXIT
U0-1115 B-6 7/99
ith).
Appendix C. Smart Transmitter InterfaceConfiguration Example
C-1. Section Overview
This section provides a configuration example of a Smart Transmitter Interface wone QLC card (address of 52H), and two QST cards (12 channels configured
The following topics are discussed:
• QLC algorithms used in the example (Section C-2).
• Points used in the example (Section C-3).
• Example (Section C-4).
7/99 C-1 U0-1115
C-2. QLC Algorithms Used
C-2. QLC Algorithms Used
The following QLC algorithms are used:
• QLCAIN
• QLCGPIN
• QLCDIN
C-3. Points Used
The points that are used in the example inSection C-4 are described below:
Table C-1. Point Definitions
Point NameRecommendedRecord Type1 Description
P1 through P12 AL or AI Primary analog input values.
S1 through S12 AL or AI Secondary analog input values.
T1 through T12 AL or AI Tertiary analog input values.
F1 through F12 AL or AI Fourth analog input values.
D1 through D12 GP HART device status values.
C1 through C12 DL or DI QST communication channel status.
QLCRUN DX (must be1 toenable)
Run flag.
1 Use a card type of 67 when initializing the process point records for STI points.
U0-1115 C-2 7/99
C-4. Example
C-4. ExampleTable C-2. Smart Transmitter Interface Configuration Example
QLCAIN QLCAIN QLCAIN QLCAIN QLCGPIN QLCDIN
QS
TC
ard
QS
TC
han
Fie
lds
PV
1 QLCRegister P
V2 QLC
Register PV
3 QLCRegister P
V4 QLC
Register Fie
lds
Dev
Sta
t
QLCReg. F
ield
s
Com
mS
tat
QLCReg.
0 0 A1
P1 0 - 2 S1 128 - 130 T1 256 - 258 F1 384 - 386 G1
D1 512 D1
C1 544
1 A2
P2 3 - 5 S2 131 - 133 T2 259 - 261 F2 387 - 389 G2
D2 513 D2
C2 545
2 A3
P3 6 - 8 S3 134 - 136 T3 262 - 264 F3 390 - 392 G3
D3 514 D3
C3 546
3 A4
P4 9 -11 S4 137 - 139 T4 265 - 267 F4 393 - 395 G4
D4 515 D4
C4 547
4 A5
P5 12 - 14 S5 140 - 142 T5 268 - 270 F5 396 - 398 G5
D5 516 D5
C5 548
5 A6
P6 15 - 17 S6 143 - 145 T6 271 - 273 F6 399 - 401 G6
D6 517 D6
C6 549
1 0 A7
P7 18 - 20 S7 146 - 148 T7 274 - 276 F7 402 - 404 G7
D7 518 D7
C7 550
1 A8
P8 21 - 23 S8 149 - 151 T8 277 - 279 F8 405 - 407 G8
D8 519 D8
C8 551
2 A9
P9 24 - 26 S9 152 - 154 T9 280 - 282 F9 408 - 410 G9
D9 520 D9
C9 552
3
A10
P10 27 - 29
S10 155 - 157
T10 283 - 285
F10 411 - 413
G10
D10 521
D10
C10 553
4
A11
P11 30 - 32
S11 158 - 160
T11 286 - 288
F11 414 - 416
G11
D11 522
D11
C11 554
5
A12
P12 33 - 35
S12 161 - 163
T12 289 - 291
F12 417 - 419
G12
D12 523
D12
C12 555
format
FR
MT 3 3 3 3
H1S
T 0 —
NH
RS —
1stReg
RE
G1 0 128 256 384
RE
G1 512
RE
G1 544
QLCAdd P
HW 52H 52H 52H 52H
PH
W 52H
PH
W 52H
SH
W 0 0 0 0
SH
W 0
SH
W 0
RunFlag
PS
TA QLCRUN QLCRUN QLCRUN QLCRUN
PS
TA QLCRUN P
STA QLCRU
N
SS
TA — — — —
SS
TA —
SS
TA —
7/99 C-3 U0-1115
Index
AA Cabinet 3-26, 3-28AUTOEXEC.BAT file 4-2
See also QLC card.
BB Cabinet 3-24, 3-26, 3-28BAKFLASH 4-4
See also QLC card.board reset switch 3-7, 3-37burst mode 2-2, 3-15, 4-9
Ccarrier detect 3-33current loop A-6
See also Network
DData Highway 3-3Device Description Language (DDL) 2-6, 4-3
See also Rosemount and QLC carddigital 1-1, 2-3, 2-5, 3-16DIOB 3-5, 3-7, 4-10DIP switch 3-5
See also DIOB.Distributed I/O Bus
See DIOB.Distributed Processing Unit
See DPU.DPU 1-1, 2-2, 4-5, 4-9dynamic process variable 4-6
FFrequency-Shift-Keyed (FSK) 3-32
GGeneral Purpose Messages (GPM) 4-10graphics B-1
Hhalf shell 3-26, 3-28hardware
address 4-10configuration 3-1, 3-3
9/98 Index-1 U0-1115
Index
HARTdata 4-15description 2-2specifications A-3translation to WDPF data B-4
HART device 2-2, 2-3, 3-15types 3-17, 3-31
hexadecimal 3-5HW field 4-10
IiSBX
card 2-6connector 3-7
JJ1 connector 3-9, 3-20
pin assignments 3-11
LLED
QST card 3-35SST card 3-12
loop 2-4See also Network
NNetwork 2-2, 3-17
See also current loop.See also loop.
Oon-demand communication 4-10
PP2 connector 3-20
jumper locations 3-24signals 3-20
polling mode 2-2, 3-15
QQ-Crate 2-2, 2-6, 3-3, 3-37QLC card
configuring 4-2description 2-2installing 3-4See also QST and SST cards.shared memory 2-2
QLCAIN algorithm 3-4, 4-2, 4-5, 4-6, C-3QLCDIN algorithm 3-4, 4-2, 4-5, C-3QLCGPIN algorithm 3-4, 4-2, 4-5, 4-8, C-3QST card
channels 4-4data transfer 3-32Group 1 2-4, 3-16, 3-26Group 2 2-5, 3-16, 3-28installing 3-18jumper settings 3-30LEDs 3-35pin assignments 3-21See also QLC and SST cards.signals 3-33
Rreference documents 1-3register locations
example C-3for communication channel status 4-9for dynamic variables 4-6status byte 4-7
ribbon cable 3-2, 3-8, 3-19Rosemount 1-1, 3-15
Device Description Language 4-3, 4-14
SSCOM board 3-8shared memory 2-2
See also QLC card.Smart Transmitter Interface (STI)
block data 4-13description 1-1identification numbers 4-4initialize 4-2messages 4-12overview 2-1purpose 2-3requirements 2-6specifications A-1start-up 3-37
SST carddescription 2-6, 3-8installing 3-8LED 3-12See also QLC and QST cards.service switch 3-13
U0-1115 Index-2 9/98
Index
STISee Smart Transmitter Interface.
Ttermination resistors 3-18, 3-20
UUART 2-2, 3-32
Wwaveform
received 3-33, A-4transmitted 3-33, 3-34, A-3
WDPF 1-1data 4-15translation to HART B-4
wiringfor Group 1 QST cards 3-26for Group 2 QST cards 3-28requirements 3-22, A-5
9/98 Index-3 U0-1115