manualshive.com logo in svg

FieldServer Genisys FS-8700-133, Руководство пользователя

Поделиться
Скачать
FieldServer Genisys FS-8700-133 Скачать руководство пользователя страница 6

FS-8700-133 Genisys Manual 

 

 

 

 

 

 

 

Page 6 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] 

5

 

CONFIGURING THE  FIEL DSERVER 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.

 

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. 

5.1

 

Client S ide Connection Descriptions  

Section Title 
Connections 
Column Title 

Function 

Legal Values 

Port 

Specify which port the device is connected to the 
FieldServer 

P1-P8

1

 

Protocol 

Specify protocol used 

Genisys 

Baud* 

Specify baud rate 

300

 , 600, 1200, 2400, 4800, 9600 (Vendor 

limitation) 

Parity* 

Specify parity 

None

, Even, Odd (Vendor limitation) 

Data_Bits* 

Specify data bits 

8

 (Vendor limitation) 

Stop_Bits* 

Specify stop bits 

1

, 2 (Vendor limitation) 

Handshaking*  Specify hardware handshaking 

None 

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. 

Содержание Genisys FS-8700-133

Страница 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 ...

Страница 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 ...

Страница 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...

Страница 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 ...

Страница 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...

Страница 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...

Страница 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...

Страница 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 ...

Страница 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...

Страница 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...

Страница 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 ...

Страница 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 ...

Страница 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...

Отзывы:

Нет отзывов

Бренды по названию

Популярные бренды

Загрузить еще бренды