| Driver Manual |
| |
|
|
|
|
|
| 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. |
|
|
| The following codes are generated by the driver. They all indicate |
|
|
| errors. |
|
|
|
|
|
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 ... ie. 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. |
|
|
|
|
|
|
|
|
|
6.4Optomux Commands
The following provides a list of commands supported by the driver. The Command Name’s provided in the table must be used in providing values for the opto22_function parameter. The notes provided only apply when module positions are specified dynamically.
FieldServer Technologies 1991 Tarob Court, Milpitas, California 95035 (408)
Visit our website: www.fieldserver.com
Page 19
