A Sierra Monitor Company Driver Manual (Supplement to the FieldServer Instruction Manual) FS-8700-78 Dart APPLICABILITY & EFFECTIVITY Effective for all systems manufactured after January 18, 1999 Instruction Manual Part Number FS-8700-78 2/20/2003
Driver Manual TABLE OF CONTENTS 1 2 3 4 5 6 7 Dart Driver Description ................................................................................................................1 1.1 Performance Issues................................................................................................................1 Driver Scope of Supply ................................................................................................................2 2.1 Supplied by Sierra Monitor for this driver ....
Driver Manual 1 Dart Driver Description The Dart Driver is designed for connection to a Data Air Coporation Dart Device. The Dart device is a active element on a network of Data Air devices such as DAP panels. It manages the devices and provides co-ordination and supervision. In performing these duties the Dart device polls all the devices on the network for all the data. The Dart is capable of ‘echoing’ the responses from these devices on one of its RS232 ports.
Driver Manual 2 2.1 Driver Scope of Supply Supplied by Sierra Monitor for this driver RS485 connection adapter Driver Manual. 2.2 Provided by user Data Aire Dart and documentation RS232 cable for the loop network FieldServer Technologies 1991 Tarob Court, Milpitas, California 95035 (408) 262-2299 fax: (408) 262-9042 Visit our website: www.fieldserver.com E-mail: support@fieldserver.
Driver Manual 3 Hardware Connections Hardware FieldServer Technologies 1991 Tarob Court, Milpitas, California 95035 (408) 262-2299 fax: (408) 262-9042 Visit our website: www.fieldserver.com E-mail: support@fieldserver.
Driver Manual 3.1 Hardware Configuration – Dart Present When a DART device is connected to the Data Aire field devices then the Fieldserver is connected to the serial port of the DART. The DART must be set to ‘Echo’ mode. This is done on the front panel of the DART. FieldServer Technologies 1991 Tarob Court, Milpitas, California 95035 (408) 262-2299 fax: (408) 262-9042 Visit our website: www.fieldserver.com E-mail: support@fieldserver.
Driver Manual 4 Basic Configuration For a detailed discussion on FieldServer configuration, please refer to the instruction manual for the FieldServer. The information that follows describes how to expand upon the factory defaults provided in the configuration files included with the FieldServer (See “.csv” files on the driver diskette). The configuration file tells the FieldServer about its interfaces, and the routing of data required.
Driver Manual 4.2 Client Side Connections Section Title Connections Column Title Port Function Specify which port the device is connected to the FieldServer Legal Values P1-P8, R1-R2 (P1-P8) requires 232/485 converter. This is the port connected to the DART’s RS232 port. Secondary_Port* Using a Dart ? Do not specify this parameter. Baud* Specify baud rate Parity* Data_Bits* Stop_Bits* Protocol Specify parity Specify data bits Specify stop bits Specify protocol used Either keyword may be used.
Driver Manual 4.3 Client Side Nodes Section Title Nodes Column Title Node_Name Function Provide name for node Node_ID This is not the node address of the Dart device ! Legal Values Up to 32 alphanumeric characters 1-259 Specify the node address of the DAP device whose data you wish to monitor.
Driver Manual 4.4 4.4.
Driver Manual DA_Field Only required when the function is a write (wrbc) or when the map descriptor is associated with a write by means of the DA_Assoc parameter value. See Table 4.4.3.3 for a list of permitted values. This is the name of the data field whose value you wish to set in the device. DA_Assoc Other uses of this parameter are permitted. These uses are discussed in the Advanced Topics section of this manual. Use to associate passive map descriptors with an active map descriptor.
Driver Manual FieldServer Technologies 1991 Tarob Court, Milpitas, California 95035 (408) 262-2299 fax: (408) 262-9042 Visit our website: www.fieldserver.com E-mail: support@fieldserver.
Driver Manual 4.4.4 Map Descriptor: Example 1 – Read all possible data Map_Descriptor_Name, Data_Array_Name, Data_Array_Offset, Function, node_name, Address, Length, DA_Func Read_Node_01, DA_01 ,0 , passive , Unit1 ,0 , 1300 , Everything The driver waits passively for the Dart to echo data from the devices. No Scan Interval. The driver will process data as fast as the Dart can serve it.
Driver Manual 4.4.5 Map of How Data Aire Device Data is stored in a Data Array In the example of 4.4.1 the Fieldserver listens passively for all possible data from the device called ‘unit1’ and stores the data in an array called ‘DA_01’. The data that is obtained from ‘unit1’ is dependent on the type of device. Irrespective of the device type the arrangement of data, stored in DA_01, is fixed. If a data field cannot be obtained from ‘unit1’ then the array is left with a zero value for that data field.
Driver Manual 63 64 65 66 67 68 69 70 71 72 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 heat_strip_config hum_config csUtilPct hsUtilPct valveUtilPct humUtilPCT alrm_select_1 alrm_select_2 alrm_select_3 alrm_select_4 x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x Dap-Stat Dap-Stat Dap-Stat Dap-Stat Dap-Stat Dap-Stat Dap-Stat Dap-Stat Dap-Stat Dap-Stat 73 3 56 bitErrors x x x x x Dap-Stat 185 186 187 188 189 190 191 192 193 194 195 196 197 19
Driver Manual 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 1 1 1 2 1 1 1 2 1 1 1 1 1 2 2 1 1 2 1 1 1 1 1 2 1 1 1 1 1 2 2 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 chilled_water compressor_config c_mode fire_lim heat_strip_config hi_cal hi_h_cal hi_t_lim humid_config h_calib lead_lag loc_h_deadband loc_h_setpt loc_t_dband loc_t_setpt lo_cal lo_h_lim lo_t_lim main_int passwd_a passwd_b rst_mode s_dela
Driver Manual 533 534 535 536 584 1 1 1 3 1 1 1 1 48 1 csUtilPct2 csUtilPct3 valveUtilPct errors mode x x x x x x x x x x x x x x x Chiller-Stat Chiller-Stat Chiller-Stat Chiller-Stat Chiller-Stat 585 596 676 6 3 6 11 80 10 runtimes errold errage x x x x x x x x x Chiller-Xtra Chiller-Xtra Chiller-Xtra 854 855 856 857 858 859 860 861 862 863 864 865 866 867 868 869 870 871 872 873 874 875 879 883 887 888 889 890 891 892 893 894 895 896 897 898 4 4 2 4 2 4 4 4 2 2 4 2 2 1 4 1 1 1 4 4 1 4 4 4
Driver Manual 899 900 901 902 903 904 905 906 907 908 909 910 911 912 913 914 915 916 917 918 919 920 921 922 923 924 925 926 927 928 929 930 931 932 933 934 950 966 982 998 1014 1030 1046 1062 1078 1079 1080 4 1 1 1 1 4 4 4 4 4 4 4 4 4 4 4 4 2 4 2 4 1 2 4 2 1 4 2 1 2 2 1 2 1 4 3 3 3 3 3 3 3 3 3 4 4 4 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 16 16 16 16 16 16 16 16 16 1 1 1 adj_rate alrm_delay_1 alrm_delay_2 alrm_delay_3 alrm_delay_4 alrm_select_1 alrm_select_2 alrm_select_3
Driver Manual 4.4.
Driver Manual "7" 7 "8" 8 "9" 9 "10" 10 "11" 11 "12" 12 "13" 13 "E" 14 "F" 15 080 DAP II, no relay expansion 080 Chiller II 080 DAP II, with relay expansion Not Defined Not Defined Not Defined Not Defined 080 DAP II, with analog module 080 DAP II, with relay and analog FieldServer Technologies 1991 Tarob Court, Milpitas, California 95035 (408) 262-2299 fax: (408) 262-9042 Visit our website: www.fieldserver.com E-mail: support@fieldserver.
Driver Manual 4.4.7 Map Descriptor: Example 2 – Writing a Set-Point . A Data Aire device cannot be written to until it has been read. This is a limitation of the Data Aire protocol. This means that you configuration cannot consist only of wrbc map descriptors. It should consist of a at least a map descriptor like example 1for every unit that you wish to write to.
Driver Manual 4.4.8 Map Descriptor: Example 3 – Writing multiple points using one message. Map_Descriptor_Name, Data_Array_Name , Data_Array_Offset, Function, node_name, Address, Length, DA_Field Write_MapDesc_1, DA_ SETPOINTS, 0 Write_MapDesc_1, DA_SETPOINTS , 1 A 'Write' and a passive to the same node. This write will update two fields, the nom_h_setpt and the t_setpt. The write MapDesc. Must precede the passive. This method is only appropriate if you plan to continuosly write to the devices.
Driver Manual 5 Chapter 5 This Chapter is blank. FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 (408) 262-6611 fax: (408) 262-9042 Visit our website: www.sierramonitor.com E-mail: sierra@sierramonitor.
Driver Manual 6 Advanced Topics 6.1 Additional Driver Specific Map Descriptor Parameters What happens if you want to poll for one specific type of data more frequently than others ? What if you want more control of the location of where data is stored ? What happens if you want to do diagnostic polls … ? To be able to achieve solutions to any of these types of questions the driver offers advanced configuration by adding to and extending the map descriptors specific to the Dart Serial Driver.
Driver Manual another value for DA_Assoc. Da_Freq Used only for connection to DART’s. Specify in milliseconds the interval at which you want a wrbc/rdbc map descriptor to be executed. When using wrbc/rdbc’s to a dart device set the scan interval to 5.0s and set this parameter to a number greater than 180000 (3 minutes). An interval of 300000 (5 minutes is recommended). DA_MethodΨ DA_BytcntΨ DA_OffsetΨ DA_ElecntΨ Specifies the extraction method.
Driver Manual IN addition to the ‘Everything’ keyword indicated in chapter 4 the following specific query functions are implemented. Func. ‘1’ ‘2’ '3' '4' '5' '6' '7' '8' 'A' 'B' 'C' ‘D” 'E' 'G' 'H' Description Driver Parameter Protocol Id.
Driver Manual DA_Field Legal Values All Description The whole data record returned by the slave is stored in the data array byte for byte. The number of bytes written is dependent of the DA_Func.
Driver Manual 6.1.3 DA_Method Parameter Values and Notes The DA_Method specifies a method for interpreting a range of bytes when the DA_Field=special. Method 1: Each byte is valid when its contains only one of the following ASCII characters. { 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, A, B, C, D, E, F } Each byte being parsed is considered to be a hexadecimal digit. The most significant digit is the left most byte.
Driver Manual 6.1.
Driver Manual 6.1.5 Advanced Example 2 The DAP-II Status query returns 14 bytes of errors & status information. The arrangement and meaning of these bytes is defined by the Data Aire Corporation and is also dependent on the type of DAPII module being polled.
Driver Manual 6.1.6 Advanced Map Descriptor: Example 3 - Using the 'special' parameter. Map_Descriptor_Name, Data_Array_Name, Data_Array_Offset, Function, node_name, Address, Length, DA_Func, DA_Field, DA_Method ,DA_Bytcnt, DA_Offset, DA_Elecnt Scan_Interval A1, DA_AI3, 0, rdbc, Node_A, 0, 1, dap-stat, special, 1 4, 10, 1, 5 It would be sensible for DA_AI3 to be an array of FLOATs because extraction method(=1) returns a floating point number. You can use specials as rdbc and passive map descriptors.
Driver Manual 6.1.7 Advanced Map Descriptor: Example 4 - Using the 'DA_Assoc' parameter. Map_Descriptor_Name, Data_Array_Name, Data_Array_Offset, Function, node_name, Address, Length, DA_Func, A1, A2, A3, A4, A8, A9, DA_AI3, DA_AI3, DA_AI3, DA_AI3, DA_AI4, DA_AI4, A 'Read' and some passive map descriptors to extract other data fields from the same read. (optimizes communications) Read must precede the passive's.
Driver Manual 6.1.8 Map Descriptor: Example 5 - Using a special / diagnostic command. Map_Descrip tor_Name, Scan_Interval, Data_Array_Name A1, 1.0s, A data array must be associated with the map descriptor even though it will not be used. It may be any data type. , Data_Array_Offset, Function, node_name, Address, Length, DA_Func, UNUSED_ARRAY, This command is sent only once. If you need to do this periodically then change this to a wrbc.
Driver Manual FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 (408) 262-6611 fax: (408) 262-9042 Visit our website: www.sierramonitor.com E-mail: sierra@sierramonitor.
Driver Manual 6.2 Related Documents The driver as specified in this manual is based on Data Aire Poll and Response Protocol Revision 3.2 dated 4 Nov 1997. The driver is compliant with a later release of the specification Revision 3.7 - 21 JUN 00. 6.3 6.3.1 Troubleshooting Tips Bad Values In the event that the driver cannot correctly decode the raw bytes it will generally write an value which indicates bad data. In most cases the indicating value is -1 or 65535 (depending on data type).
Driver Manual 6.4 Writing data to Dap Devices The variables in a DAP device are not individually addressable . When a DAP device is read a data composite is returned. The driver extracts the data you require. When data is written to a DAP device it is not possible to write a value to one individual data element such as a temperature setpoint. Rather, the DAP devices requires the complete data composite (all its variables, states, settings) be written at once.
Driver Manual 7 Revision Change Notices Revision Number Format Explained: 1.05a Rev0 Indicates Driver release this release of the manual corresponds to. 7.1 Revisions to the manual. Each time that the driver release number changes the manual revision is set to zero. Rev1.06a-Rev0 Changes from previous releases This is the first release of this driver since its separation from a combined Dart/Dap driver. Previously this manual was identified as the “Data Aire user Manual Rev1.
