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: Document Revision: 1.
FS-8700-86 Carrier DataPort Table of Contents TABLE OF CONTENTS 1. 2. CARRIER DATAPORT DESCRIPTION ........................................................................................... 3 DRIVER SCOPE OF SUPPLY.......................................................................................................... 3 2.1. Supplied by FieldServer Technologies for this driver ................................................................. 3 3. 4. HARDWARE CONNECTIONS ..............................
FS-8700-86 Carrier DataPort 1. Page 3 of 32 Carrier DataPort Description The Carrier DataPort driver allows the FieldServer to transfer data to and from devices over either RS232 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.
FS-8700-86 Carrier DataPort 3. Page 4 of 32 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.
FS-8700-86 Carrier DataPort 4. Page 5 of 32 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.
FS-8700-86 Carrier DataPort 4.2. Page 6 of 32 Client Side Connections Section Title Connections Column Title Baud* Specify baud rate. Parity* Data_Bits* Specify parity Specify data bits Legal Values P1-P8, ( R1, R2 with 1 converter) 600 , 1200, 2400, 9600 (Vendor limitation) None (Vendor limitation) 8 (Vendor limitation) Stop_Bits* Specify stop bits.
FS-8700-86 Carrier DataPort 4.3. Page 7 of 32 Client Side Node Descriptors Section Title Nodes Column Title Node_Name Function Legal Values Provide name for node Up to alphanumeric characters 32 These correspond to the ‘devices’ configured in the DTPConfig. Thus the Node_ID is not the address of the final CCN device. Node_ID Protocol Port 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.
FS-8700-86 Carrier DataPort 4.4. Page 8 of 32 Client Side Map Descriptors 4.4.1. FieldServer Related Map Descriptor Parameters Column Title Map_Descriptor_Name Data_Array_Name Function Name of this Map Descriptor Name of Data Array where data is to be stored in the FieldServer Data_Array_Location Starting location in Data Array Function Function of Client Map Descriptor 4.4.2.
Map Descriptor Example 1 – Read Page 9 of 32 The driver generates a read poll continuously. Function, Rdbc , The Node_Name connects the Map Descriptor to a Node definition. Data_Array_Offset, 0 , Length, 100 , The length is set to a number big enough to contain all the table’s variables. Node_Name, FAN01 , FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: support@fieldserver.
FS-8700-86 Carrier DataPort 5. Page 10 of 32 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).
FS-8700-86 Carrier DataPort 5.2.
FS-8700-86 Carrier DataPort 5.4. Page 12 of 32 Server Side Map Descriptors 5.4.1. FieldServer Specific Map Descriptor Parameters Column Title Map_Descriptor_Name Data_Array_Name Function Name of this Map Descriptor Name of Data Array where data is to be stored in the FieldServer Data_Array_Location Starting location in Data Array Function Function of Client Map Descriptor 5.4.2.
FS-8700-86 Carrier DataPort Column Title DA_Byte_Name* On_String Off_String Length 5.4.3. Page 13 of 32 Function If this parameter is defined then its value must be the name of a Data Array. Instead of the driver returning a static Field Status, it will extract the value located at the given offset and use this value as the Field Status. If the variable has a discrete state, use this parameter to define the word that describes the state when the variable’s value is 1.
Map Descriptor Example. Page 14 of 32 Node_Name, Node_1, Node_1, Node_1, Node_1, Node_1, Node_1, Node_1, Node_1, Node_1, Node_1, Field_Name, MODE , ALARM , CSPT , SPT , RAT , SAT , FANSTAT, CCAP , HCAP , FLTSTAT, Field_Description, Desired Mode , Equipment Status, Controlling Setp., Controlling Temp, Space Temp, Supply Air Temp.
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.
FS-8700-86 Carrier DataPort Error Conditions Conditions No Force Fire Safety Service Tool Supervisor Monitor Minimum-off Control BEST Temp Override Loadshed Page 16 of 32 A 0 16 32 48 64 80 96 112 128 144 160 B 1 17 33 49 65 81 97 113 129 145 161 Force Conditions C D 2 3 18 19 34 35 50 51 66 67 82 83 98 99 114 115 130 131 146 147 162 163 E 4 20 36 52 68 84 100 116 132 148 164 F 5 21 37 53 69 85 101 117 133 149 165 Error Conditions: A no error B hardware or communications error C software error D low
Page 17 of 32 Function, rdbc , Node_Name, FAN01 , Length, 1000 , Storet_As ASCII This is what tells the driver to dump the table, its variables names and variable descriptions in ASCII format. Scan_Interval, 5.0s , FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: support@fieldserver.com The s=Data Array DA_DUMP has been defined with format BYTE.
Page 18 of 32 Function, rdbc , Node_Name, FAN01 , Length, 1000 , Scan_Interval, 5.0s , FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: support@fieldserver.com T01> ASCII Dump Requested for MD= T01> Field1 99.0 000 000 Desc1 1 1 T01> Field2 98.
FS-8700-86 Carrier DataPort Appendix A.3. Page 19 of 32 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 discarded.
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 '********' is not being recognized.
FS-8700-86 Carrier DataPort Appendix A.4.3. Page 21 of 32 Numeric Values The driver recognizes numeric values by checking the first character of the value field. If it is a digit then the field is treated as a number. Appendix A.4.4. Occupancy Strings / Values If the value returned for a variable is 8 characters long and each of the characters is a one or a zero then the driver regards this as an occupancy string an converts it to a binary coded decimal value and then stores this value. E.g.
FS-8700-86 Carrier DataPort Page 22 of 32 Appendix B. Trouble Shooting/Connections - Tips and Hints Appendix B.1. Connection problems. Confirm that the device you are trying to attach to the FieldServer is in fact a DataPort device and not a DataLink device which looks very similar but connects differently. A DataLink device will require the DataLink driver – FieldServer part # FS-8700-82. Please contact FieldServer to request an exchange of driver. Appendix B.2.
FS-8700-86 Carrier DataPort Appendix B.4. Page 23 of 32 How to build a script file that tests a customer log. The following brief notes are intended for configuration engineers who are expected to be familiar with the FieldServer. • • • • Take the hex log file and convert to ASCII using special chars (this is an option of the log file converter) Choose a response line from near the end of the log (most recent). Check the line is complete. Place the line inside an INI file.
Data_Array_Name, TABLE_DISPLAY, Data_Array_Offset, 0, Function, Passive, Node_Name, Node_A, Table_Name, DISPLAY, Field_Name, Field1, Field_Description, Desc1 1 1, Page 24 of 32 Field_Units, Length, 202, On_String, NI°UMERIC, Off_String, -, Length 1 FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: support@fieldserver.
Page 25 of 32 FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: support@fieldserver.
FS-8700-86 Carrier DataPort Page 26 of 32 Appendix C. Driver Notes Appendix C.1. Driver Limitations and Exclusions The Carrier DataPort driver does not support the following functions. Send Data Periodically, Stop Sending, Xoff, Xon, Omit 24 Character description, Include 24 Character description, Read Configuration. The Carrier DataPort driver is not capable of configuring the DataPort device. Software provided by the Carrier Corporation is required to do this.
FS-8700-86 Carrier DataPort Page 27 of 32 Appendix D. Driver Error Messages The driver reports information and errors to you in the form of messages printed to the error log. Those messages marked with a * are only printed once even if they occur repeatedly. Error Message CarrierDP:1 FYI. The MapDesc called <%s> is too short CarrierDP:2 FYI. You could have used a MapDesc called <%s> to expose diagnostic info. CarrierDP:3 Err. Illegal Node_ID=%d Valid=1..15 CarrierDP:4 FYI. Address has no meaning.
FS-8700-86 Carrier DataPort Error Message CarrierDP:13 FYI. Diagnostic send error #1 response. CarrierDP:14 FYI. Diagnostic cancelled slave response CarrDP:#15 Err. Field Units required. MapDesc=<%s> CarrDP:#16 FYI. Use DA_Byte_Name for server status values. MD=<%s> CarrDP:#17 FYI. Use DA_Byte_Name for 'status' value storage. MD=<%s> CarrDP:#18 FYI. Use DA_Float_Name for 'units' value storage. MD=<%s> CarrDP:#19 Err. 'Table_Name' has no meaning. MapDesc=<%s> CarrDP:#20 Err. 'Field_Name' has no meaning.
FS-8700-86 Carrier DataPort Error Message works best with timeouts. long CarrDP:#26 FYI. No data was stored for MD=%s CarrDP:#27 Err. Can’t open slave.log CarrDP:#28 FYI. Response was sent from slave.log (Hex file) Page 29 of 32 Explanation each table is different. The driver does not know the length of the responses. The Carrier devices take some time between receiving a poll and sending a response. The amount of time is proportional to the length of the response (and hence, to the size of the table.
FS-8700-86 Carrier DataPort Error Message Page 30 of 32 Explanation There DataPort device responded but the response reports an error. The error number is printed in the message. The message also reports the name of the node that was polled. The following 6 errors are documented. For other errors contact the Carrier Vendor.
FS-8700-86 Carrier DataPort Appendix D.1. Page 31 of 32 Driver Stats The driver reports statistics according to the FieldServer standards. The following notes describe some aspects of standard statistic reporting which are peculiar to this driver.
FS-8700-86 Carrier DataPort Page 32 of 32 Array Offset is based on Port Number P1 P2 P3 P4 P5 P6 P7 0 50 100 150 200 250 300 1 51 101 151 201 251 301 2 52 102 152 202 252 302 3 53 103 153 203 253 303 P8 350 351 352 353 Description Available for future use Available for future use Available for future use Available for future use 4 54 104 154 204 254 304 354 Number of bytes sent by Client driver 5 55 105 155 205 255 305 355 6 7 9 56 57 58 106 156 206 256 306 356 107 157 207 257 307 357 108 158
