FieldServer Optomux FS-8700-17 - Manual (Page 9)

FS-8700-17_Opto22.doc Manual Page 7 of 24
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.3.2 Driver Related Map Descriptor Parameters
Column Title Function Legal Values
Node_Name Name of Node to fetch data from
One of the
Node names
specified in
Section 5.2
Length
Length of Map Descriptor. Commands and queries that use the value of
this Map Descriptor parameter are indicated in Appendix B.1 The driver
uses a maximum of 16 elements of data.
The FieldServer kernel uses this parameter to ensure that no more than
one Client Map Descriptor has control of a range of array data
elements. It is therefore recommended that the parameter is set even
if not required by the command/query.- in these cases set it to 1.
1 - 1000
Opto22_Function
This parameter is specified using one of the functions listed in Appendix
B.1. The parameter must be spelled and spaced exactly as provided in
the table. Leading and trailing spaces are not important but inter-word
spaces are very important. Tabs are not permitted.
See Appendix
B.1
Address*
This field is only required if the address/length method of module
position specification is used. Refer to Appendix A.2
1..16
Opto22_Format*
This parameter only has meaning when the function is a read of digital
data. The parameter instructs the driver to unpack this data into
separate bit states, writing each module position’s state to a
consecutive Data Array element. Refer to Appendix A.2
Bit, Packed
Opto22_Trigger*
An optional parameter used in conjunction with the Da_Byte_Name
parameter. If the parameter is set, a poll will only be sent when the
trigger value is set. More information is provided in Appendix A.1.4.
No, Yes
Opto22_modifier1*
Some Opto22_Functions require one or more additional arguments.
SET TIME DELAY
GENERATE N PULSES
READ AND AVERAGE INPUTS
See Appendix
B.1
Opto22_modifier2*
Opto22_Mask*
This parameter allows the user to statically specify the positions (1-16)
of a module that will be affected by a command. When this parameter
is used and its value is non zero then the driver does not consider the
data contained in the position defining array even if it is also defined.
Refer also to Appendix A.1.1
0-65535
or
0x0000 – 0xffff
Da_Bit_Name*
This parameter is only required for dynamic module position
specification. The Data Array is used to tell the driver which module
positions to affect by a command. Additional information is provided in
Appendix A.1.3
One of the Data
Array
names
from Section 4.
Da_Byte_Name*
This driver uses DA_Byte_Name exclusively as a location for the
commands to trigger Map Descriptors and in which to store poll
response status. Refer to Appendix A.1.4
One data element is used per Map Descriptor. The element is
determined by the Data_Array_Offset parameter.
One of the Data
Array
names
from Section 4.