Summary of the content on the page No. 1
A Sierra Monitor Company
Driver Manual
(Supplement to the FieldServer Instruction Manual)
FS-8700-133 Genisys
APPLICABILITY & EFFECTIVITY
Effective for all systems manufactured after January 2009
Driver Version: 1.00
Document Revision: 3
Summary of the content on the page No. 2
FS-8700-133 Genisys Manual Table of Contents TABLE OF CONTENTS 1 GENISYS DESCRIPTION ................................................................................................................................... 3 2 DRIVER SCOPE OF SUPPLY .............................................................................................................................. 3 2.1 Supplied by FieldServer Technologies for this driver ............................................................
Summary of the content on the page No. 3
FS-8700-133 Genisys Manual Page 3 of 13 1 GENISYS DESCRIPTION The Genisys driver allows the transfer of data to and from devices over RS-232 Genisys protocol. Vital Harmon Logic Controller (VHLC) supports Genisys protocol. IM-188 VHLC GENISYS SOFTWARE MANUAL 100188-008 AB0.PDF is the basis of the Genisys driver. The FieldServer can be configured as a Client. Limited Server side functionality has been implemented for FieldServer’s quality assurance requirements only. Max Nodes S
Summary of the content on the page No. 4
FS-8700-133 Genisys Manual Page 4 of 13 3 HARDWARE CONNECTIONS The FieldServer is connected to the VHLC as shown in the following connection drawing. Port C VHLC RS-232 Interface Module DB25F 8917-04 Tx 8 3 7 6 5 GND 7 4 3 2 Rx 2 1 FS-8915-10 RJ45 FieldServer VHLC Server Connect to one of the RS-232 Ports on the FieldServer RJ45 8 1 P1 FieldServer FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com Tel: (408) 262 2299 Fax: (408)
Summary of the content on the page No. 5
FS-8700-133 Genisys Manual Page 5 of 13 4 CONFIGURING THE FIELDSERVER AS A GENISYS CLIENT 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 configuring the Fie
Summary of the content on the page No. 6
FS-8700-133 Genisys Manual Page 6 of 13 4.2 Client Side Connection Descriptions Section Title Connections Column Title Function Legal Values Specify which port the device is connected to the 1 Port P1-P8 FieldServer Protocol Specify protocol used Genisys 300 ,600, 1200, 2400, 4800, 9600 (Vendor Baud* Specify baud rate limitation) Parity* Specify parity None, Even, Odd (Vendor limitation) Data_Bits* Specify data bits 8 (Vendor limitation) Stop_Bits* Specify stop bits 1, 2 (Ve
Summary of the content on the page No. 7
FS-8700-133 Genisys Manual Page 7 of 13 4.3 Client Side Node Descriptors Section Title Nodes Column Title Function Legal Values Up to 32 Node_Name Provide name for Node alphanumeric characters Node_ID VHLC station address of physical Server Node 1-255 Protocol Specify protocol used Genisys Specify which port the device is connected to the 1 Connection P1-P8 FieldServer If OFF, the FieldServer configures VHLC to apply controls from the FieldServer without verification. Genis
Summary of the content on the page No. 8
FS-8700-133 Genisys Manual Page 8 of 13 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 to be One of the Data Array names from “Data Data_Array_Name stored in the FieldServer Array” section above 0 to maximum specified in “Data Array” Data_Array_Offset Starting location in Data Array section above
Summary of the content on the page No. 9
FS-8700-133 Genisys Manual Page 9 of 13 4.5 Map Descriptor Example: Read Indications The following Map Descriptors will read indication words from physical Server Genisys_01 and Genisys_02 (described in Client Side Node Descriptors section). The Cos_Poller Map Descriptor polls VHLC for any indication word changes and returned data is stored on the Data Array under the COS_READ Map Descriptor for the same Node. The rate of polling is determined by the Scan_Interval. The Cos_Read Map
Summary of the content on the page No. 10
FS-8700-133 Genisys Manual Page 10 of 13 4.6 Map Descriptor Example: Write Controls The following Map Descriptor will write controls to physical Server Genisys_01 and Genisys_02 (described in Client Side Node Descriptors section) whenever any of the control statuses changes/updates. One such Map Descriptor is required per Node. If Data_Type is Byte, 32 consecutive locations from the Data Array will be written to VHLC. Data at any location would be considered as one control word. If
Summary of the content on the page No. 11
FS-8700-133 Genisys Manual Page 11 of 13 5 CONFIGURING THE FIELDSERVER AS A GENISYS SERVER The Server side has been implemented only for FieldServer’s quality assurance requirements. 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
Summary of the content on the page No. 12
FS-8700-133 Genisys Manual Page 12 of 13 Appendix A. Advanced Topics Appendix A.1. Storage Structure for Data Type Bit and Byte st LSB bit in Indication/Control Byte is the1 status/control value st nd If the Data_Type is ‘Byte’ and only the 1 and 2 indication status values are 1 (out of 8 statuses), all others being zero, the Driver will store a numeric value of 3 in the Data Array. FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.co
Summary of the content on the page No. 13
FS-8700-133 Genisys Manual Page 13 of 13 Appendix B. Error Messages Most error messages are associated with errors in parsing an incoming message from the VHLC panel. The most likely cause is a mismatch in expected message format. The driver will flag one of the following error messages and continue. In most cases the message currently being processed by the driver will also be printed so that any problems can be easily diagnosed. The following Error Messages appear upon the ‘Dri
