FieldServer Genisys FS-8700-133 Driver Manual Download Page 13

FS-8700-133 Genisys Manual 

 

 

 

 

 

 

 

Page 13 of 13 

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] 

Appendix B.

 

Reference 

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 

GENISYS:#1 

FYI. 

Connection  params  are 
%d %d %d Even 

If  a  connection  is  declared  in 
section 

4.2 

without 

Baud, 

Data_Bits, Stop_Bits or Parity, the 
displayed parameter values will be 
in use. 

Check  if  connection  parameter  matches  the 
setting at VHLC. 

GENISYS:#2 

FYI. 

MD 

required  to  store  data 
from Node(%d) 

A  Map  Descriptor  with  function 
COS_Poller  has  been  declared  for 
a  Node  but  the  COS_Read  Map 
Descriptor  required  to  store  the 
data is missing. 

Edit configuration file and add Map Descriptor 
with COS_Read function. 

GENISYS:#3  FYI.  MD(%s) 
length  required=%d,  now 
Only  %d  statuses  will  be 
stored 

The  COS_Read  Map  Descriptor  is 
of  insufficient  length  to  store  all 
indication words from VHLC.  

If  all  indication  words  need  to  be  stored,  edit 
the configuration file and change the length of 
the Map Descriptor to the reported value. 

GENISYS:#4  ERR  %dth 
word  number  %d  is 
invalid 

The indication data response from 
VHLC  contains  an  invalid  word 
number. 
Valid range is 0-31 
No data will be stored. 

Call tech support. 

GENISYS:#5 

FYI. 

Indications  can  not  be 
written 

The  FieldServer  received  an 
instruction from a Server device to 
write 

indications 

to 

VHLC.  

FieldServer can only write controls 
to VHLC. 

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. 

GENISYS:#11FYI.  MD(%s) 
length  required=%d,  now 
Only  %d  statuses  will  be 
stored 

The  Driver  is  acting  as  a  Server 
rather than a Client. 

Call tech support. 

GENISYS:#12  ERR  %dth 
word  number  %d  is 
invalid 

The  Driver  is  acting  as  a  Server 
rather than a Client. 

Call tech support. 

 

Summary of Contents for Genisys FS-8700-133

Page 1: ...r Company APPLICABILITY EFFECTIVITY Effective for all systems manufactured after January 2009 Driver Manual Supplement to the FieldServer Instruction Manual FS 8700 133 Genisys Driver Version 1 01 Document Revision 1 ...

Page 2: ... 4 4 DATA ARRAY PARAMETERS 5 5 CONFIGURING THE FIELDSERVER AS A GENISYS CLIENT 6 5 1 Client Side Connection Descriptions 6 5 2 Client Side Node Descriptors 7 5 3 Client Side Map Descriptors 8 5 3 1 FieldServer Related Map Descriptor Parameters 8 5 3 2 Driver Related Map Descriptor Parameters 8 5 3 3 Timing Parameters 8 5 4 Map Descriptor Example Read Indications 9 5 5 Map Descriptor Example Write ...

Page 3: ...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 Nodes Comments Client 1 Only 1 virtual client per port allowed on multidrop systems Server 255 Maximum device addresses pollable by Client protocol limita...

Page 4: ...2269 Toll Free 888 509 1970 email support fieldserver com 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 7 3 2 8 7 6 5 4 3 1 VHLC Server RJ45 FieldServer 2 Tx GND Rx FS 8915 10 8917 04 FieldServer RJ45 Connect to one of the RS 232 Ports on the FieldServer P1 1 8 ...

Page 5: ... storage of the relevant data Section Title Data_Arrays Column Title Function Legal Values Data_Array_Name Provide name for Data Array Up to 15 alphanumeric characters Data_Array_Format Provide data format Each Data Array can only take on one format FLOAT BIT UInt16 SInt16 Packed_Bit Byte Packed_Byte Swapped_Byte Data_Array_Length Number of Data Objects Must be larger than the data storage area re...

Page 6: ... 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 5 1 Client Side Connection Descriptions Section Title Connections C...

Page 7: ...isys Connection Specify which port the device is connected to the FieldServer P1 P8 1 Genisys_Check_Controls 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 OFF ON Genisys_Intra_Poll_Delay Specify time that FieldServer should wait before sending AC...

Page 8: ...al Values Node_Name Name of Node to fetch data from One of the Node names specified in Client Node Descriptor above Data_Type 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 Byte each byte of Indication statuses will be stored as an 8 Bit Integer at ...

Page 9: ...e 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 1 00s DA_COS_01 0 COS_Poller Genisys...

Page 10: ...HLC Data at 8 consecutive locations would be considered as one control word 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_01b DA_8O_01 0 Wrbx Genisys_01 Byte 0 32 CMD_02 DA_DO_01 0 Wrbx Genisys_02 Bit 0 256 Name of one of the Data Arrays defined in Data_Array sect...

Page 11: ...t 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 6 CONFIGURING THE FIELDSERVER AS A GENISYS SERVER The Server side has been implemented only for FieldServer s quality assurance requirements ...

Page 12: ...e 888 509 1970 email support fieldserver com Appendix A Useful Features Appendix A 1 Storage Structure for Data Type Bit and Byte LSB bit in Indication Control Byte is the1 st status control value If the Data_Type is Byte and only the 1 st and 2 nd 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 ...

Page 13: ...ith function COS_Poller has been declared for a Node but the COS_Read Map Descriptor required to store the data is missing Edit configuration file and add Map Descriptor with COS_Read function GENISYS 3 FYI MD s length required d now Only d statuses will be stored The COS_Read Map Descriptor is of insufficient length to store all indication words from VHLC If all indication words need to be stored...

Reviews: