A Sierra Monitor Company Driver Manual (Supplement to the FieldServer Instruction Manual) FS-8700-82 Carrier DataLink APPLICABILITY & EFFECTIVITY Effective for all systems manufactured after May 1, 2001 Driver Version: 1.03 Document Revision: 5 FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com Tel: (408) 262-2299 Fax: (408) 262-9042 Toll_Free: 888-509-1970 email: support@fieldserver.
FS-8700-82 Carrier DataLink Table of Contents TABLE OF CONTENTS 1. Carrier DataLink Description..........................................................................................3 2. 2.1. 2.2. Driver Scope of Supply...................................................................................................4 Supplied by FieldServer Technologies for this driver ..................................................4 Provided by Suppler of 3rd Party Equipment.....................................
FS-8700-82 Carrier DataLink 1. Page 3 of 31 Carrier DataLink Description The Carrier DataLink driver allows the FieldServer to transfer data to and from devices over either RS-232 or RS-485 using Carrier DataLink protocol. The FieldServer can emulate either a Server or Client. The Carrier DataLink Serial Driver allows variables to be read and written in system elements connected to a Carrier Comfort Network communication bus. Up to 15 system elements may be connected to a DataLink Device.
FS-8700-82 Carrier DataLink 2. Page 4 of 31 Driver Scope of Supply 2.1. Supplied by FieldServer Technologies for this driver FieldServer Technologies PART # FS-8915-10 FS-8917-17 FS-8700-82 2.2. PART # DESCRIPTION UTP cable (7 foot) for RS-232 use RJ45 to DB25M connection adapter Driver Manual. Provided by Suppler of 3rd Party Equipment DESCRIPTION Carrier DataLink Card FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.
FS-8700-82 Carrier DataLink 3. Page 5 of 31 Hardware Connections The FieldServer is connected to the Carrier DataLink device as shown below. Ensure that the device to be connected to is in fact the DataLink device and not the DataPort device which is similar looking. Configure the DataLink Device according to manufacturer’s instructions. This driver requires that the DataLink device’s DTPCONFIG table has been configured prior to connection with a FieldServer.
FS-8700-82 Carrier DataLink 4. Page 6 of 31 Configuring the FieldServer as a Carrier DataLink Client It is not possible to configure communication with a DataLink device until familiar with the data available from the devices connected to the DataLink. The DataLink device does not provide a method for discovering the data tables and variables that are available in all the Carrier devices.
FS-8700-82 Carrier DataLink Page 7 of 31 Example // Data Arrays Data_Arrays Data_Array_Name, DA_AI_01, DA_AO_01, DA_DI_01, DA_DO_01, 4.2. Data_Format, UInt16, UInt16, Bit, Bit, Data_Array_Length 200 200 200 200 Client Side Connection Descriptions Section Title Connections Column Title Port Function Specify which port the device is connected to the FieldServer Baud* Specify baud rate Parity* Specify parity.
FS-8700-82 Carrier DataLink 4.3. Page 8 of 31 Client Side Node Descriptors Section Title Nodes Column Title Node_Name Function Legal Values Up to 32 alphanumeric characters Provide name for node Modbus station address of physical server node. These correspond to the ‘devices’ configured in the DTPConfig. Thus the Node_ID is not the address of the final CCN device. The DataLink 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-82 Carrier DataLink 4.4.2. Driver Related Map Descriptor Parameters Column Title Node_Name Page 9 of 31 Function Name of Node to fetch data from Legal Values One of the node names specified in “Client Node Descriptor” above Data type. This parameter is not required except when defining Map Descriptors which write DOW (Day of Week) and Time value to the Carrier devices.
FS-8700-82 Carrier DataLink 4.4.4. Page 10 of 31 Map Descriptor Example 1 – Read a Table This example illustrates how to read the entire contents of a table called ‘DISPLAY’. The Map Descriptor is connected to a node using 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 which will be generated every 5 seconds.
Map Descriptor Example 2 – Read a Variable Page 11 of 31 Data_Array_Name, DA_TEMPS , DA_TEMPS , Data_Array_Offset, 0 , 1 , Node_Name, FAN01 , FAN01 , Length, 1 , 1 , Table_Name, DISPLAY , DISPLAY , Field_Name RAT SAT Map Descriptor Example 3 – Write A Variable The variable names are supplied by the Carrier Corporation. Refer to Appendix A.2 for assistance in determining version names. RAT SAT Scan_Interval, 5.0s , 5.0s , The pneumonic variable name. Space Temperature -40.
Map Descriptor Example 4 – Write Day of Week (DOW) or Time Page 12 of 31 Map_Descriptors Map_Descriptor_Name, MapDesc13 , MapDesc14 , Data_Array_Name, TABLE_OCCPC64S, TABLE_OCCPC64S, Data_Array_Offset, 100 , 101 , Function, wrbx , wrbx , Node_Name, Node_A , Node_A , Table_Name, OCCDEFCS OCCPC64S, OCCDEFCS OCCPC64S, Length, 1 , 1 , Data_Type Occupancy_DOW Occupancy_Time The Data type tells the driver how to format the value for the write.
FS-8700-82 Carrier DataLink 5. Page 13 of 31 Configuring the FieldServer as a Carrier DataLink Server For a detailed discussion on FieldServer configuration, please refer to the FieldServer Instruction 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-82 Carrier DataLink Page 14 of 31 Example // Server Side Connections Connections Port, Baud, Parity, Data_bits, Stop_Bits, P8, 9600, None , 8 , 1 , 5.2. Protocol , CarrierDL, Handshaking, None , Poll_Delay 0.100s Server Side Nodes Section Title Nodes Column Title Node_Name Node_ID Protocol Function Legal Values Up to 32 alphanumeric characters Provide name for node Modbus station address of physical server node. These correspond to the ‘devices’ configured in the DTPConfig.
FS-8700-82 Carrier DataLink 5.3. Page 15 of 31 Server Side Map Descriptors 5.3.1. FieldServer Specific Map Descriptor Parameters Column Title Function Map_Descriptor_Name Name of this Map Descriptor Data_Array_Name Name of Data Array where data is to be stored in the FieldServer Data_Array_Location Starting location in Data Array Function Map Descriptor function 5.3.2.
FS-8700-82 Carrier DataLink Column Title Function as a time value formatted as hh:mm (keyword=TIME) or as a string of bytes (keyword=STRING) or as an occupancy string (keyword=DOW). When using the string keyword the driver reads x consecutive array elements and treats them like ASCII character values in forming the response. X is defined by the length parameter. If the variable has a discrete state, use this parameter to define the word that describes the state when the variable’s value is zero.
Map Descriptor Example.
FS-8700-82 Carrier DataLink 5.4. Page 18 of 31 Driver Limitations and Exclusions As a client: • The Carrier DataLink driver is not capable of polling for alarm data. (The RA and AV functions are not implemented). • The Carrier DataLink driver dos not validate table or variable names. • The Carrier DataLink driver does not support the Read Table command with the /C or /N options.
FS-8700-82 Carrier DataLink Page 19 of 31 Appendix A. Advanced Topics Appendix A.1. Table Names The following list of table names is provided as a reference. Carrier may add tables and new devices may become available.
FS-8700-82 Carrier DataLink Equipment Type 19XR PIC II CHILLER: 30GTN CHILLER: 30GXNHXA CHILLER: 33CS VVT MONITOR: 40UV UNIT VENTILATOR 48/50F SERIES ROOFTOP: Table Name SETPT03 SETPOINT SETPT04 SETPOINT SETPT05 SETPOINT SETPT06 SETPOINT SETPT07 SETPOINT SETPT08 OCCPCxxC OCCPC01 COMPRESS CVC_PSWD HEAT_EX ISM_STAT MAINSTAT POWER STARTUP SETPOINT OCCDEFCS OCCPC01S OCCDEFCS OCCPC02S OCCDEFCS OCCPC03S A_UNIT CIRCADIO CIRCA_AN CIRCBDIO CIRCB_AN OPTIONS SETPOINT OccDefcS OCCPC01S A_UNIT CIRCADIO CIRCA_AN CIR
Page 21 of 31 Function, rdbc , Node_Name, FAN01 , Scan_Interval, 5.0s, Table_Name DISPLAY , Field_Name, EVERYTHING, This is what tells the driver to dump the table, its variables names and variable descriptions in ASCII format. Length, 1000 , FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com Tel: (408) 262-2299 Fax: (408) 262-9042 Toll_Free: 888-509-1970 email: support@fieldserver.com The s=data array DA_DUMP has been defined with format BYTE.
Page 22 of 31 Function, rdbc , Node_Name, FAN01 , Length, 1000 , Scan_Interval, 5.0s , Table_Name, DISPLAY , These are variable names. Use these names in your Map Descriptors. Field_Name , EVERYTHING, FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com Tel: (408) 262-2299 Fax: (408) 262-9042 Toll_Free: 888-509-1970 email: support@fieldserver.com Variable descriptions.
FS-8700-82 Carrier DataLink Page 23 of 31 Appendix A.3. Map Descriptor Length Explained The Length parameter is specified as part of the Map Descriptor. Appendix A.3.1. Client Reads a Table: The length determines the number of table variables 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 large number (e.g. 100).
FS-8700-82 Carrier DataLink Page 24 of 31 State Word Value State Word Value OFF OPEN CLOSE CLOSED ABNORMAL NORMAL ALARM STOP START YES NO 0 1 0 0 1 0 1 0 1 1 0 OFF-CCN OFF-time Emergency ON-local ON-CCN ON-time Redline Shed DSABLE LOCAL REMOTE 2 3 4 5 6 7 1 2 0 0 1 If the driver doesn’t recognize the state word it stores the characters of the state word as decimal values based on their ASCII value. The number of characters stored is dependent on the length parameter.
FS-8700-82 Carrier DataLink Appendix A.4.3. Page 25 of 31 Time Values If the driver receives a variable value reported in the format hh:mm then the driver stores a number obtained by multiplying the hours by 60 and adding the minutes. The driver recognizes a time value by checking the 3rd character for a colon and checking that the 1st character is a digit. Value_Stored = hh * 60 + mm Eg. 5:30pm is reported as 17:20 and is stored as 17*60 + 20 = 1040. Appendix A.4.4.
FS-8700-82 Carrier DataLink Page 26 of 31 Appendix B. Carrier DataLink Device Error Response The following notes are provided from the protocol specification. Message Explanation Action Check the spelling of the #1 Invalid The last command sent to the DataLink command and verify that it contains the required Command device is not recognized. parameters. Check the spelling of the table name(s).
FS-8700-82 Carrier DataLink Page 27 of 31 Appendix C. Driver Notes Appendix C.1. 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-82 Carrier DataLink OFFSET 0 1 2 3 4 5 6 Page 28 of 31 9 8 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 DESCRIPTION Number of Read Table messages sent Number of Read Variable messages sent Number of Write Table messages sent Number of Write Var Messages sent Number of bytes sent by client driver Number of messages sent by client Number of response messages received by client Number of times client tries write with alternate format because original method failed Most recent response error Numbe
FS-8700-82 Carrier DataLink Page 29 of 31 Appendix D. Driver Error Messages The driver reports information and errors 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 Carrier:#1 FYI. The MapDesc called <%s> is too short Carrier:#2 FYI. You could have used a MapDesc called <%s> to expose diagnostic info. Carrier:#3 Err. Illegal Node_ID=%d Valid=1..15 Carrier:#4 FYI. Address has no meaning.
FS-8700-82 Carrier DataLink Error Message Carrier:#15 Err. Alarm commands not supported. Carrier:#16 Err. Alarm commands not supported. Carr:#17 Err. MD=<%s> discrete state word not recognized. CarrDL:#18 FYI. Timeout probably too short. Read Manual. CarrDL:#19 Err. Diagnostic. Call Support. CarrDL:#20* FYI. Invalid Time(%02d:%02d) being written. MD=%s CarrDL:#21* FYI. Invalid Time(%02d:%02d) being stored. MD=%s CarrDL:#23* Err. CarrDL device reported errors. Check exposed stats 8-23. CarrDL:#22* FYI.
FS-8700-82 Carrier DataLink Page 31 of 31 THIS PAGE INTENTIONALLY LEFT BLANK FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com Tel: (408) 262-2299 Fax: (408) 262-9042 Toll_Free: 888-509-1970 email: support@fieldserver.
