Summary of the content on the page No. 1
A Sierra Monitor Company
Driver Manual
(Supplement to the FieldServer Instruction Manual)
FS-8700-86 Carrier DataPort
APPLICABILITY & EFFECTIVITY
Effective for all systems manufactured after August 2008
Driver Version: 1.03
Document Revision: 11
Summary of the content on the page No. 2
FS-8700-86 Carrier DataPort Table of Contents TABLE OF CONTENTS 1. CARRIER DATAPORT DESCRIPTION ...........................................................................................3 2. DRIVER SCOPE OF SUPPLY..........................................................................................................3 2.1. Supplied by FieldServer Technologies for this driver .................................................................3 3. HARDWARE CONNECTIONS ...................
Summary of the content on the page No. 3
FS-8700-86 Carrier DataPort Page 3 of 32 1. Carrier DataPort Description The Carrier DataPort driver allows the FieldServer to transfer data to and from devices over either RS- 232 or RS-485 using Carrier DataPort protocol. The FieldServer can emulate either a Server or Client. The DataPort device provides a gateway to CCN devices. This driver polls the DataPort device which in turn reads data from the CCN devices. Up to 15 system elements may be connected to a DataPort Device
Summary of the content on the page No. 4
FS-8700-86 Carrier DataPort Page 4 of 32 3. Hardware Connections The FieldServer is connected to the Carrier DataPort device as shown below. Configure the DataPort Device according to manufacturer’s instructions. This driver requires that the DataPort device’s DTPCONFIG table has been configured prior to connection with a FieldServer. In addition, consult the manufacturer’s information on connecting Carrier Device’s to CCN network. Note: Typical connections are 9600,N,8,1. Fie
Summary of the content on the page No. 5
FS-8700-86 Carrier DataPort Page 5 of 32 4. Configuring the FieldServer as a Carrier DataPort Client It is not possible to complete a configuration for communication with a DataPort device until you are familiar with the data available from the devices connected to the DataPort. The DataPort device does not provide a method for discovering the data tables and variables that are available in all the Carrier devices. Configuring the DataPort driver as a Client is easy; however, you will
Summary of the content on the page No. 6
FS-8700-86 Carrier DataPort Page 6 of 32 4.2. Client Side Connections Section Title Connections Column Title Function Legal Values Specify which port the device is connected to the P1-P8, ( R1, R2 with Port 1 FieldServer converter) 600 , 1200, 2400, 9600 Baud* Specify baud rate. (Vendor limitation) Parity* Specify parity None (Vendor limitation) Data_Bits* Specify data bits 8 (Vendor limitation) Stop_Bits* Specify stop bits. 1 (Vendor limitation) Protocol Specify protoco
Summary of the content on the page No. 7
FS-8700-86 Carrier DataPort Page 7 of 32 4.3. Client Side Node Descriptors Section Title Nodes Column Function Legal Values Title Up to 32 Node_Name Provide name for node alphanumeric characters These correspond to the ‘devices’ configured in the DTPConfig. Thus the Node_ID is not the address of the final CCN device. Node_ID 1-15 The DataPort DTPConfig table maps a device number (1...15) to a bus number (0-239). Use the Node_ID to tell the driver which device to use. P
Summary of the content on the page No. 8
FS-8700-86 Carrier DataPort Page 8 of 32 4.4. Client Side Map Descriptors 4.4.1. FieldServer Related Map Descriptor Parameters Column Title Function Legal Values Map_Descriptor_Name Name of this Map Descriptor Up to 32 alphanumeric characters Name of Data Array where data is One of the Data Array names from Data_Array_Name to be stored in the FieldServer “Data Array” section above 0 to maximum specified in “Data Data_Array_Location Starting location in Data Array Array” section a
Summary of the content on the page No. 9
FS-8700-86 Carrier DataPort Page 9 of 32 4.4.4. Map Descriptor Example 1 – Read This example illustrates how to read data from the DataPort. Some basics first: The Map Descriptor is connected to a node by means of the node name and a node definition provides a connection to a port. Thus this Map Descriptor is connected to a port via its node. The FieldServer will use that port to send this poll. The poll will be generated every 5 seconds in this example. The values extracted
Summary of the content on the page No. 10
FS-8700-86 Carrier DataPort Page 10 of 32 5. Configuring the FieldServer as a Carrier DataPort Server For a detailed discussion on FieldServer configuration, please refer to the FieldServer Configuration Manual. The information that follows describes how to expand upon the factory defaults provided in the configuration files included with the FieldServer (See “.csv” sample files provided with the FieldServer). This section documents and describes the parameters necessary for config
Summary of the content on the page No. 11
FS-8700-86 Carrier DataPort Page 11 of 32 5.2. Server Side Connections Section Title Connections Column Title Function Legal Values Specify which port the device is connected to 4 Port P1-P8, ( R1-R2 with converter) the FieldServer 300, 600 , 1200, 2400, 9600 Baud* Specify baud rate (Vendor limitation) Parity* Specify parity None (Vendor limitation) Data_Bits* Specify data bits 8 (Vendor limitation) Stop_Bits* Specify stop bits 1 (Vendor limitation) Protocol Specify pro
Summary of the content on the page No. 12
FS-8700-86 Carrier DataPort Page 12 of 32 5.4. Server Side Map Descriptors 5.4.1. FieldServer Specific Map Descriptor Parameters Column Title Function Legal Values Map_Descriptor_Name Name of this Map Descriptor Up to 32 alphanumeric characters Name of Data Array where data is One of the Data Array names from Data_Array_Name to be stored in the FieldServer “Data Array” section above 0 to maximum specified in “Data Data_Array_Location Starting location in Data Array Array” section
Summary of the content on the page No. 13
FS-8700-86 Carrier DataPort Page 13 of 32 Column Title Function Legal Values If this parameter is defined then its value must be the name of a Data Array. Instead of the driver The name of Data Array DA_Byte_Name* returning a static Field Status, it will extract the defined in the Data value located at the given offset and use this Arrays section. value as the Field Status. If the variable has a discrete state, use this parameter to define the word that describes the state when t
Summary of the content on the page No. 14
FS-8700-86 Carrier DataPort Page 14 of 32 5.4.4. Map Descriptor Example. This example shows a number of server Map Descriptors used to define a table called ‘DISPLAY’. If a Client sends a read table request the driver responds by sending all the appropriate data for every Map Descriptor with the same table name (provided that the node’s match too. ). The fields are returned in the order in which you define them in the configuration file. // Server Side Map Descriptors
Summary of the content on the page No. 15
FS-8700-86 Carrier DataPort Page 15 of 32 Appendix A. Advanced Topics Appendix A.1. Field Status & Field Engineering Units The following tables duplicate information available from Carrier Corporation. We provide it for reference purposes. It is best to ask the vendor for current data. Value Engineering Units Value Engineering Units Value Engineering Units 000 no units 051 feet per minute 260 Pascal thousands of cubic feet 001 degrees F 052 262 delta degrees C per minute th
Summary of the content on the page No. 16
FS-8700-86 Carrier DataPort Page 16 of 32 Error Conditions Force Conditions Conditions A B C D E F No Force 0 1 2 3 4 5 Fire 16 17 18 19 20 21 Safety 32 33 34 35 36 37 Service Tool 48 49 50 51 52 53 Supervisor 64 65 66 67 68 69 Monitor 80 81 82 83 84 85 Minimum-off 96 97 98 99 100 101 Control 112 113 114 115 116 117 BEST 128 129 130 131 132 133 Temp Override 144 145 146 147 148 149 Loadshed 160 161 162 163 164 165 Error Conditions: A no error B hardware or comm
Summary of the content on the page No. 17
FS-8700-86 Carrier DataPort Page 17 of 32 This example illustrates how to create a Map Descriptor which reads a table and dumps the response in ASCII format to a Data Array so that RUINET( a utility provided with the FieldServer) can be used to browse and read the results. Data_Arrays Data_Array_Name, Data_Format, Data_Array_Length DA_DUMP, BYTE, 2000 Map Descriptors Map_Descriptor_Name, Data_Array_Name, Data_Array_Offset, Function, Node_Name, Length, Scan_Interval, S
Summary of the content on the page No. 18
FS-8700-86 Carrier DataPort Page 18 of 32 This example illustrates how to make a Map Descriptor which reads a table and dumps the response in ASCII format to the error log. The error log can be dumped to a file on your computer using RUIDEBUG (a utility supplied with your FieldServer) Data_Arrays Data_Array_Name, Data_Format, Data_Array_Length DA_DUMP, BYTE, 2000 Map Descriptors Map_Descriptor_Name, Data_Array_Name, Data_Array_Offset, Function, Node_Name, Length, Scan
Summary of the content on the page No. 19
FS-8700-86 Carrier DataPort Page 19 of 32 Appendix A.3. Map Descriptor Length Explained The Length parameter is specified as part of the Map Descriptor. Client Reads: The length means: “The number of table variable’s whose values are to be stored when the response is received.” If you do not know the length of the table in advance, set the length to a larger number (e.g. 100). The driver will process the response; if the table contains more than 100 elements then some data will be
Summary of the content on the page No. 20
FS-8700-86 Carrier DataPort Page 20 of 32 In the following two examples the keywords that are not recognized are 'Reset T' and 'Tripout' respectively CarrDP:#24 Err. MD= discrete state word not recognized. T02> T02> CarrDP:#24 Err. MD= discrete state word not recognized. T02> In the following example the keyword '**
