FieldServer Genisys FS 8700 133 User Manual

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
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 Supported  
FieldServer Mode  
Client  
Server  
Nodes  
1
255  
Comments  
Only 1 virtual client per port allowed on multidrop systems.  
Maximum device addresses pollable by Client protocol limitation.  
2
DRIVER SCOPE OF SUPPLY  
2.1 Supplied by FieldServer Technologies for this driver  
FieldServer Technologies PART # Description  
FS-8915-10  
FS-8917-04  
FS-8700-133  
UTP cable (7 foot) for RS-232 use  
RJ45 to DB25F connector adapter  
Driver Manual.  
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: [email protected]  
     
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
4
3
2
1
GND  
7
2
Rx  
FS-8915-10  
RJ45  
FieldServer  
VHLC  
Server  
Connect to one of the RS-232  
Ports on the FieldServer  
RJ45  
1
8
P1  
FieldServer  
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: [email protected]  
 
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 FieldServer to communicate  
with a Genisys Server.  
4.1 Data Arrays/Descriptors  
The configuration file tells the FieldServer about its interfaces, and the routing of data required. In order to enable  
the FieldServer for Genisys communications, the driver independent FieldServer buffers need to be declared in the  
Data Arrays” section, the destination device addresses need to be declared in the “Client Side Nodes” section, and  
the data required from the Servers needs to be mapped in the “Client Side Map Descriptors” section. Details on  
how to do this can be found below.  
Note that in the tables, * indicates an optional parameter, with the bold legal value being the default.  
Section Title  
Data_Arrays  
Column Title  
Function  
Legal Values  
Up to  
15  
Data_Array_Name  
Provide name for Data Array  
alphanumeric  
characters  
Provide data format. Each Data Array can only take on one Float, Bit, UInt16,  
Data_Array_Format  
format.  
SInt16, Byte,  
Number of Data Objects. Must be larger than the data storage  
Data_Array_Length area required by the Map Descriptors for the data being placed in 1-10,000  
this array.  
Example  
// Data Arrays  
Data_Arrays  
Data_Array_Name ,Data_Array_Format ,Data_Array_Length  
DA_8I_01  
,Byte  
,Byte  
,Bit  
,Bit  
,Byte  
,Byte  
,32  
,32  
,256  
,256  
,1  
DA_8O_01  
DA_DI_01  
DA_DO_01  
DA_COS_01  
DA_COS_02  
,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: [email protected]  
   
FS-8700-133 Genisys Manual  
Page 6 of 13  
4.2 Client Side Connection Descriptions  
Section Title  
Connections  
Column Title  
Function  
Legal Values  
P1-P81  
Specify which port the device is connected to the  
FieldServer  
Port  
Protocol  
Baud*  
Specify protocol used  
Genisys  
300 ,600, 1200, 2400, 4800, 9600 (Vendor  
limitation)  
Specify baud rate  
Parity*  
Data_Bits*  
Stop_Bits*  
Specify parity  
Specify data bits  
Specify stop bits  
None, Even, Odd (Vendor limitation)  
8 (Vendor limitation)  
1, 2 (Vendor limitation)  
None  
Handshaking* Specify hardware handshaking  
Poll_Delay*  
Time between internal polls  
0-32000 seconds, 0.05 seconds  
Example  
//  
// Client Side Connections  
//  
Connections  
Port ,Baud ,Data_Bits ,Stop_Bits ,Parity ,Protocol  
P1  
,9600 ,8  
,1  
,None ,Genisys  
1 Not all ports shown are necessarily supported by the hardware. Consult the appropriate Instruction manual for  
details of the ports available on specific hardware.  
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: [email protected]  
   
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  
alphanumeric  
characters  
1-255  
Node_Name  
Provide name for Node  
Node_ID  
Protocol  
VHLC station address of physical Server Node  
Specify protocol used  
Genisys  
Specify which port the device is connected to the  
FieldServer  
Connection  
P1-P81  
If OFF, the FieldServer configures VHLC to apply controls  
from the FieldServer without verification.  
If ON, the FieldServer configures VHLC to verify controls  
supplied by the FieldServer before applying.  
Specify time, that FieldServer should wait before sending  
Genisys_Check_Controls*  
OFF, ON  
Genisys_Intra_Poll_Delay* ACK or Execute message after receiving the last character of 0.010s, 0.025s etc  
response from VHLC.  
Example  
// Client Side Nodes  
//  
Nodes  
Node_Name ,Node_ID ,Protocol ,Port ,Genisys_Check_Controls ,Genisys_Intra_Poll_Delay  
Genisys_01  
Genisys_02  
,1  
,2  
,Genisys ,P1  
,Genisys ,P1  
,ON  
,-  
,0.01s  
,0.01s  
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: [email protected]  
 
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  
Up to 32 alphanumeric characters  
Name of Data Array where data is to be One of the Data Array names from “Data  
Map_Descriptor_Name Name of this Map Descriptor  
Data_Array_Name  
stored in the FieldServer  
Array” section above  
0 to maximum specified in “Data Array”  
section above  
COS_Poller, COS_Read , Wrbx  
Data_Array_Offset  
Function  
Starting location in Data Array  
Function of Client Map Descriptor  
4.4.2 Driver Related Map Descriptor Parameters  
Column  
Function  
Title  
Legal Values  
One of the Node names  
specified in “Client Node  
Descriptor” above  
Node_Name Name of Node to fetch data from  
‘Bit’ each byte of Indication statuses will be stored in 8 consecutive  
locations in the Data Array. Similarly while writing; Control byte  
will be composed from 8 consecutive locations of the Dara Array.  
Data_Type* ‘Byte’ each byte of Indication statuses will be stored as an 8-Bit Bit, Byte  
Integer at the specified location. Similarly while writing; Control  
byte will be composed from a single location of the Data Array.  
Address*  
Internally used parameter, if used specify value 0  
Length of Map Descriptor  
0
Bit: 1-256, 8  
Byte: 1-32, 1  
Length*  
Number of indications to store or number of controls to write as  
per Data_Type.  
4.4.3 Timing Parameters  
Column Title  
Scan_Interval  
Function  
Rate at which data is polled  
Legal Values  
≥0.001s  
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: [email protected]  
       
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 Descriptor also polls VHLC for all indication words irrespective of data change. The rate of polling is determined by the Scan_Interval.  
If Data_Type is Byte, any location in Data Array will hold one indication word from VHLC.  
If Data_Type is Bit, eight consecutive locations in Data Array will hold one indication word from VHLC. Also see Appendix A.1.  
// Client Side Map Descriptors  
//  
Map_Descriptors  
Map_Descriptor_Name ,Scan_Interval ,Data_Array_Name ,Data_Array_Offset ,Function  
,Node_Name ,Data_Type ,Address ,Length  
CMD_01  
CMD_01a  
,1.00s  
,50s  
,DA_COS_01  
,DA_8I_01  
,0  
,0  
,COS_Poller ,Genisys_01  
,COS_Read ,Genisys_01  
,Byte  
,Byte  
,0  
,0  
,1  
,32  
CMD_02  
CMD_02a  
,1.00s  
,50s  
,DA_COS_02  
,DA_DI_01  
,0  
,0  
,COS_Poller ,Genisys_02  
,COS_Read ,Genisys_02  
,Bit  
,Bit  
,0  
,0  
,1  
,256  
Name of one of the Data  
Arrays defined in the  
Data_Array section.  
Indication statuses will be  
stored in this Data Array  
Number of consecutive  
locations in the Data array  
to be used for storing data  
from the Server.  
Frequency (in  
seconds) to read  
Indication Statuses  
Starting offset  
in Data Array to  
hold 1st  
indication  
status  
One of the Nodes  
declared in Node  
Section. Indications  
will be read from the  
station address  
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: [email protected]  
 
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 Data_Type is Bit, 256 consecutive locations from the Data Array will be written to VHLC. Data at 8 consecutive locations would be considered as one control  
word.  
// Client Side Map Descriptors  
//  
Map_Descriptors  
Map_Descriptor_Name ,Scan_Interval ,Data_Array_Name ,Data_Array_Offset ,Function ,Node_Name ,Data_Type ,Address ,Length  
CMD_01b  
CMD_02  
,-  
,-  
,DA_8O_01  
,DA_DO_01  
,0  
,0  
,Wrbx  
,Wrbx  
,Genisys_01  
,Genisys_02  
,Byte  
,Bit  
,0  
,0  
,32  
,256  
Name of one of  
the Data Arrays  
defined in  
Data_Array  
section. This  
Data Array holds  
control statuses  
to be written to  
other devices.  
One of the  
Number of consecutive  
locations in the Data  
array to use when  
issuing the Write  
command.  
Starting offset  
in the Data  
Array which  
holds the 1st  
control status.  
Wrbx: send write command  
to the Server when the  
associated Controls updates  
or changes. To write  
continuously use Wrbc as the  
function and add a  
Scan_Interval parameter to  
configure how often to write.  
Nodes declared  
in the Node  
Section.  
Indications will  
read from the  
station address  
belonging to this  
Node  
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: [email protected]  
 
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: [email protected]  
 
FS-8700-133 Genisys Manual  
Page 12 of 13  
Appendix A. Advanced Topics  
Appendix A.1. Storage Structure for Data Type Bit and Byte  
LSB bit in Indication/Control Byte is the1st status/control value  
If the Data_Type is ‘Byte’ and only the 1st and 2nd 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.com  
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: [email protected]  
   
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 ‘Driver Messages’ Screen  
%d means numeric number  
%s means string  
Messages number 2, 3 and 11 will be displayed just once if generated after rebooting or power cycling the  
FieldServer.  
Error  
Description  
Action  
If a connection is declared in  
FYI. section 4.2 without Baud,  
Connection params are Data_Bits, Stop_Bits or Parity, the  
GENISYS:#1  
Check if connection parameter matches the  
setting at VHLC.  
%d %d %d Even  
displayed parameter values will be  
in use.  
A Map Descriptor with function  
MD COS_Poller has been declared for  
required to store data a Node but the COS_Read Map  
GENISYS:#2  
FYI.  
Edit configuration file and add Map Descriptor  
with COS_Read function.  
from Node(%d)  
Descriptor required to store the  
data is missing.  
GENISYS:#3 FYI. MD(%s)  
length required=%d, now  
Only %d statuses will be  
stored  
The COS_Read Map Descriptor is If all indication words need to be stored, edit  
of insufficient length to store all the configuration file and change the length of  
indication words from VHLC.  
the Map Descriptor to the reported value.  
The indication data response from  
GENISYS:#4 ERR %dth VHLC contains an invalid word  
word number %d is number.  
Call tech support.  
invalid  
Valid range is 0-31  
No data will be stored.  
Inspect the configuration file to determine  
whether the Data Array under the COS_Poller  
or COS_Read Map Descriptor is mapped to  
receive write commands from other protocols.  
Also check that other devices are not  
configured to write data to these Data Arrays.  
The FieldServer received an  
FYI. instruction from a Server device to  
Indications can not be write indications to VHLC.  
GENISYS:#5  
written  
FieldServer can only write controls  
to VHLC.  
GENISYS:#11FYI. MD(%s)  
length required=%d, now The Driver is acting as a Server  
Only %d statuses will be rather than a Client.  
stored  
Call tech support.  
Call tech support.  
GENISYS:#12 ERR %dth  
The Driver is acting as a Server  
word number %d is  
rather than a Client.  
invalid  
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: [email protected]  
 

Memorex MVD2033 User Manual
Memorex iWake Mi4004 User Manual
Maxtor DIAMONDMAXTM PLUS 5120 91536D6 User Manual
La Crosse Technology WS 6118AL IT User Manual
Kompernass KH 1111 User Manual
Kenwood CD 424M User Manual
Hamilton Beach 49464 User Manual
Gemini CD 340 User Manual
Aluratek AUCR204 User Manual
Aiwa XP EV500 User Manual