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

FS-8700-17_Opto22.doc Manual Page 21 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]
Read/
Write/
Both
COMMAND NAME
OPTO22_FORMAT
OPTION
MASTER
LENGTH
CONSIDERED
(See Notes)
NOTES
r
CALCULATE AND
SET GAIN
1
Only specified module positions get
calculated and read. Data read gets put in
corresponding positions of Data Array.
w
SET OUTPUT
WAVEFORM R
4
Uses opto22_modifier1/2 from the CSV file
set waveform rates and types. Only
specified positions get affected. 2
elements of Data Array are used.
w
IMPROVED
OUTPUT
WAVEFORMS
4
Uses opto22_modifier1/2 from the CSV file
set waveform rates and types. Only
specified positions get affected. 3
elements of Data Array are used.
Appendix B.2. Command Response Status
If a Data Array is specified using the DA_Byte_Array parameter then the driver will store a response status code i n
the array, updating the value each time a command is executed.
Value Description
0 Command completed successfully.
1 Used to trigger a command.
All other values indicate error conditions. For Responses 128 to 255 the Optomux literature should be read for
additional information as these are codes returned by the Optomux device.
128
Nak from Optomux Device. Power Up Clear Expected. Command Ignored.
129 Nak from Optomux Device. Undefined Command
130 Nak from Optomux Device. Checksum Error
131 Nak from Optomux Device. Input Buffer Overun
132 Nak from Optomux Device. Non Printable Ascii character received
133 Nak from Optomux Device. Data Field Error
134 Nak from Optomux Device. Communication watchdog timeout
135 Nak from Optomux Device. Specified limits invalid.
250 An ack with no data was expected. Ack with Data was received.
251 The driver Complete function returned an error, could be checksum, bad 1st char ... i.e. The message
was badly formatted.
252 Driver Timeout
253 An ack was received but it was badly formatted
254 A nak was received but was badly formatted
255 Message was not acknowledged correctly.
Appendix B.3. Driver Stats