Page 27 of | Page 27 of 29 |
| |||
|
|
|
|
|
|
| Decimal | Hex | Description |
|
|
| 0F6 | Invalid sweep state to set. |
|
| |
| 0F5 | Invalid password. |
|
| |
| 0F4 | Invalid input parameter in request. |
|
| |
| 0F3 | I/O configuration mismatch. |
|
| |
| 0F2 | Invalid program cannot log in. |
|
| |
| 0F1 | Request only valid from programmer. |
|
| |
| 0F0 | Request only valid in stop mode. |
|
| |
| 0EF | Programmer is already attached. |
|
| |
| 0EE | Could not return block sizes. |
|
| |
| 0ED | VMEbus error encountered. |
|
| |
| 0EC | Task unable to be created. |
|
| |
| 0EB | Task unable to be deleted. |
|
| |
| 0EA | Not logged in to process service request. |
|
| |
| 0E9 | Segment selector not valid in context. |
|
| |
| 0E8 | No user memory is available to allocate. |
|
| |
| 0E7 | Configuration is not valid. |
|
| |
| 0E6 | CPU model number does not match. |
|
| |
| 0E5 | DOS file area not formatted. |
|
| |
| 0E4 | Segment for this selector does not exist. |
|
| |
| 0E3 | CPU revision number does not match. |
|
| |
| 0E2 | IOS could not delete configuration or bad type. |
|
| |
| 0E1 | No I/O configuration to read or delete. |
|
| |
| 0E0 | Service in process cannot login. |
|
| |
| 0DF | Invalid Datagram connection address. |
|
| |
| 0DE | Size of Datagram connection invalid. |
|
| |
| 0DD | Unable to locate given connection ID. |
|
| |
| 0DC | Unable to find connection address. |
|
| |
| 0DB | Invalid segment selector in Datagram. |
|
| |
| 0DA | Null pointer to data in segment selector. |
|
| |
| 0D9 | Transfer type invalid for this selector. |
|
| |
| 0D8 | Point length not allowed. |
|
| |
| 0D7 | Invalid Datagram type specified. |
|
| |
| 0D6 | Datagram connection boundary exceeded. |
|
| |
| 0D5 | Invalid block name specified in Datagram. |
|
| |
| 0D4 | Mismatch of configuration checksum. |
|
| |
| 0D3 | User Program Module (UPM) read or write exceeded block end. |
|
| |
| 0D2 | Invalid write mode parameter. |
|
| |
| 0D1 | Packet size or total program size does not match input. |
|
| |
| 0D0 | One or more PLC modules configured have unsupported revision. |
|
| |
| 49 | 0CF | Specified device is unavailable in the system (not present). |
|
|
| 0CE | Specified device has insufficient memory to handle request. |
|
| |
| 0CD | Attempt was made to read a device but no data has been stored on it. |
| ||
| 0CC | Data stored on device has been corrupted and is no longer reliable. |
| ||
| 0CB | A comm or write verify error occurred during save or restore. |
|
| |
| 0CA | Device is write protected. |
|
| |
| 0C9 | Login using |
|
| |
| 0C8 | Password(s) already enabled and cannot be forced inactive. |
|
| |
| 0C7 | Passwords are set to inactive and cannot be enabled or disabled. |
|
| |
| 0C6 | Control Program (CP) tasks exist but requestor not logged into main CP. |
| ||
| 0C5 | No |
|
| |
| 0C4 | Verify with FA Card or EEPROM failed. |
|
| |
| 0C3 | Text length does not match traffic type. |
|
|
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldServer.com Tel: (408)