General Status 0x01 – Connection Manager Extended Status Codes
Error Corde | Code hex / (decimal) | Description/Meaning |
|---|---|---|
— (obsolete) | 0x0000–0x00FF / (0–255) | Obsolete, no longer used. |
CONNECTION IN USE OR DUPLICATE FORWARD_OPEN | 0x0100 / (256) | A matching connection to this target already exists. Use a different connection or close the existing one. |
— (reserved) | 0x0101–0x0102 / (257–258) | Reserved by CIP. |
TRANSPORT CLASS AND TRIGGER COMBINATION NOT SUPPORTED | 0x0103 / (259) | The requested combination of transport class and trigger is not supported by the target application. |
— (reserved) | 0x0104 / (260) | Reserved by CIP. |
CIP SAFETY | 0x0105 / (261) | See CIP Safety Specification (Volume 5, Chapter 3). |
OWNERSHIP CONFLICT | 0x0106 / (262) | A required resource is already exclusively allocated by another connection; a further (exclusive-owner) connection is not possible. |
TARGET CONNECTION NOT FOUND | 0x0107 / (263) | The connection referenced in the Forward_Close is no longer present at the target device. |
INVALID NETWORK CONNECTION PARAMETER | 0x0108 / (264) | A connection parameter (type, priority, redundant owner or fixed/variable) is not supported. (Replaced by more specific codes on newer devices.) |
INVALID CONNECTION SIZE | 0x0109 / (265) | The requested connection size is not supported by target or router. Check your settings. |
— (reserved) | 0x010A–0x010F / (266–271) | Reserved by CIP. |
TARGET FOR CONNECTION NOT CONFIGURED | 0x0110 / (272) | The target has not been configured and the connection request contains no configuration data. |
RPI NOT SUPPORTED | 0x0111 / (273) | The requested RPI value (O→T or T→O) is not supported. Frequently the task cycle time does not fit: the EL6652 works internally with 1 ms, which can be set via the Cycle Time Multiplier; otherwise adjust the task cycle time. |
RPI VALUE(S) NOT ACCEPTABLE | 0x0112 / (274) | The RPI value(s) are outside the range accepted by the device. The device returns acceptable RPI values. |
OUT OF CONNECTIONS | 0x0113 / (275) | The Connection Manager cannot accept any more connections; the maximum number has been reached. |
VENDOR ID OR PRODUCT CODE MISMATCH | 0x0114 / (276) | Vendor ID or product code in the electronic key do not match the device. |
DEVICE TYPE MISMATCH | 0x0115 / (277) | The device type in the electronic key does not match the device. |
REVISION MISMATCH | 0x0116 / (278) | The revision (major/minor) in the electronic key does not correspond to a valid device revision. |
INVALID PRODUCED OR CONSUMED APPLICATION PATH | 0x0117 / (279) | The specified produced/consumed application path is invalid at the target or missing. (Replaced by more specific codes.) |
INVALID OR INCONSISTENT CONFIGURATION APPLICATION PATH | 0x0118 / (280) | The configuration application path is invalid or inconsistent with the produced/consumed paths. |
NON-LISTEN ONLY CONNECTION NOT OPENED | 0x0119 / (281) | A listen-only connection is not possible because no non-listen-only connection with the same T→O path exists yet. |
TARGET OBJECT OUT OF CONNECTIONS | 0x011A / (282) | The maximum number of connections for this target object instance has been exceeded. |
THE PRODUCTION INHIBIT TIME IS GREATER THAN THE RPI | 0x011B / (283) | The production inhibit time is greater than the T→O RPI. |
TRANSPORT CLASS NOT SUPPORTED | 0x011C / (284) | The requested transport class is not supported. |
T→O PRODUCTION TRIGGER NOT SUPPORTED | 0x011D / (285) | The requested T→O production trigger is not supported. |
DIRECTION NOT SUPPORTED | 0x011E / (286) | The direction specified in the transport type/trigger is not supported. |
INVALID ORIGINATOR TO TARGET NETWORK CONNECTION FIXVAR | 0x011F / (287) | The O→T fixed/variable flag is not supported. |
INVALID TARGET TO ORIGINATOR NETWORK CONNECTION FIXVAR | 0x0120 / (288) | The T→O fixed/variable flag is not supported. |
INVALID ORIGINATOR TO TARGET NETWORK CONNECTION PRIORITY | 0x0121 / (289) | The O→T priority code is not supported. |
INVALID TARGET TO ORIGINATOR NETWORK CONNECTION PRIORITY | 0x0122 / (290) | The T→O priority code is not supported. |
INVALID ORIGINATOR TO TARGET NETWORK CONNECTION TYPE | 0x0123 / (291) | The O→T connection type is not supported. |
INVALID TARGET TO ORIGINATOR NETWORK CONNECTION TYPE | 0x0124 / (292) | The T→O connection type is not supported. |
INVALID ORIGINATOR TO TARGET NETWORK CONNECTION REDUNDANT_OWNER | 0x0125 / (293) | The O→T redundant-owner flag is not supported. |
INVALID CONFIGURATION SIZE | 0x0126 / (294) | The data segment size does not fit the requested configuration. An additional word reports the maximum supported size. |
INVALID ORIGINATOR TO TARGET NETWORK CONNECTION SIZE | 0x0127 / (295) | The O→T connection size does not match or is not supported. An additional word reports the maximum size. |
INVALID TARGET TO ORIGINATOR NETWORK CONNECTION SIZE | 0x0128 / (296) | The T→O connection size does not match or is not supported. An additional word reports the maximum size. |
INVALID CONFIGURATION APPLICATION PATH | 0x0129 / (297) | The configuration application path is invalid at the target or missing. |
INVALID CONSUMING APPLICATION PATH | 0x012A / (298) | The consuming application path is invalid at the target or missing. |
INVALID PRODUCING APPLICATION PATH | 0x012B / (299) | The producing application path is invalid at the target or missing. |
CONFIGURATION SYMBOL DOES NOT EXIST | 0x012C / (300) | The specified configuration tag name does not exist on the target. |
CONSUMING SYMBOL DOES NOT EXIST | 0x012D / (301) | The specified consuming tag name does not exist on the target. |
PRODUCING SYMBOL DOES NOT EXIST | 0x012E / (302) | The specified producing tag name does not exist on the target. |
INCONSISTENT APPLICATION PATH COMBINATION | 0x012F / (303) | The combination of configuration, consume and produce paths is inconsistent. |
INCONSISTENT CONSUME DATA FORMAT | 0x0130 / (304) | The data in the segment does not match the format of the consumed data. |
INCONSISTENT PRODUCE DATA FORMAT | 0x0131 / (305) | The data in the segment does not match the format of the produced data. |
NULL FORWARD_OPEN FUNCTION NOT SUPPORTED | 0x0132 / (306) | The function requested via the Null Forward_Open (ping, configure, reconfigure) is not supported. |
CONNECTION TIMEOUT MULTIPLIER NOT ACCEPTABLE | 0x0133 / (307) | The connection timeout multiplier is reserved or yields a timeout value that is too large. |
MISMATCHED T→O NETWORK CONNECTION SIZE | 0x0134 / (308) | For a multicast connection the size in the T→O parameter does not match the already existing connection. |
MISMATCHED T→O NETWORK CONNECTION FIXVAR | 0x0135 / (309) | For a multicast connection the fixed/variable bit does not match the existing connection. |
MISMATCHED T→O NETWORK CONNECTION PRIORITY | 0x0136 / (310) | For a multicast connection the priority does not match the existing connection. |
MISMATCHED TRANSPORT CLASS | 0x0137 / (311) | For a multicast connection the transport class does not match the existing connection. |
MISMATCHED T→O PRODUCTION TRIGGER | 0x0138 / (312) | For a multicast connection the T→O production trigger does not match the existing connection. |
MISMATCHED T→O PRODUCTION INHIBIT TIME SEGMENT | 0x0139 / (313) | For a multicast connection the production inhibit time (PIT) does not match the existing connection. |
SERIAL NUMBER MISMATCH | 0x013A / (314) | The serial number in the electronic key does not match the device. |
UNSUPPORTED CONCURRENT CONNECTIONS PROTOCOL VERSION | 0x013B / (315) | The concurrent connections protocol version specified in the Concurrent_Forward_Open is not supported. |
CONCURRENT CONNECTIONS PROTOCOL VERSION MISMATCH | 0x013C / (316) | The concurrent connections protocol version does not match the open concurrent connection. |
CONCURRENT CONNECTIONS CONNECTION TIMEOUT MULTIPLIER MISMATCH | 0x013D / (317) | The connection timeout multiplier does not match the open concurrent connection. |
CONCURRENT CONNECTIONS O→T RPI MISMATCH | 0x013E / (318) | The O→T RPI does not match the open concurrent connection. |
CONCURRENT CONNECTIONS O→T NETWORK CONNECTION PARAMETERS MISMATCH | 0x013F / (319) | The O→T network parameters do not match the open concurrent connection. |
CONCURRENT CONNECTIONS T→O RPI MISMATCH | 0x0140 / (320) | The T→O RPI does not match the open concurrent connection. |
CONCURRENT CONNECTIONS T→O NETWORK CONNECTION PARAMETERS MISMATCH | 0x0141 / (321) | The T→O network parameters do not match the open concurrent connection. |
CONCURRENT CONNECTIONS TRANSPORT CLASS AND TRIGGER MISMATCH | 0x0142 / (322) | Transport class and trigger do not match the open concurrent connection. |
INVALID CONCURRENT CONNECTION PATH | 0x0143 / (323) | The concurrent connection path could not be decoded or contains invalid values (e.g. link address type, IPv4 address, hostname). |
DEVICE TYPE REVISION MISMATCH | 0x0144 / (324) | The device type revision in the electronic key does not correspond to a valid revision of the device. |
PROFILE VENDOR ID FORWARD_OPEN MISMATCH | 0x0145 / (325) | A Forward_Open using the Profile Vendor ID has a product code other than 1 or a cleared compatibility bit. |
CONCURRENT CONNECTIONS CONNECTION PATH MISMATCH | 0x0146 / (326) | The Connection_Path does not match the open concurrent connection. |
— (reserved) | 0x0147–0x0202 / (327–514) | Reserved by CIP. |
CONNECTION TIMED OUT | 0x0203 / (515) | A connection has timed out. |
UNCONNECTED REQUEST TIMED OUT | 0x0204 / (516) | An Unconnected_Send/Forward_Open/Forward_Close could not be delivered or answered in time. |
PARAMETER ERROR IN UNCONNECTED REQUEST SERVICE | 0x0205 / (517) | A parameter combination (e.g. tick time / timeout) in the unconnected request is not supported by a router. |
MESSAGE TOO LARGE FOR UNCONNECTED_SEND SERVICE | 0x0206 / (518) | The Unconnected_Send is too large to be sent over the network. |
UNCONNECTED ACKNOWLEDGE WITHOUT REPLY | 0x0207 / (519) | An acknowledge but no data reply was received for an unconnected message. |
THIS SERVICE REQUIRES A CONNECTION | 0x0208 / (520) | The service was sent unconnected but must be sent over a connection. |
— (reserved) | 0x0209–0x0300 / (521–768) | Reserved by CIP. |
NO BUFFER MEMORY AVAILABLE | 0x0301 / (769) | Insufficient connection buffer memory is available in the device. |
NETWORK BANDWIDTH NOT AVAILABLE FOR DATA | 0x0302 / (770) | A device in the path cannot allocate enough bandwidth for a scheduled connection. |
NO CONSUMED CONNECTION ID FILTER AVAILABLE | 0x0303 / (771) | A link consumer in the path has no free consumed-connection-id filter. |
NOT CONFIGURED TO SEND SCHEDULED PRIORITY DATA | 0x0304 / (772) | A device cannot send packets during the scheduled time window. |
SCHEDULE SIGNATURE MISMATCH | 0x0305 / (773) | The scheduling information of originator and target network do not match. |
SCHEDULE SIGNATURE VALIDATION NOT POSSIBLE | 0x0306 / (774) | The scheduling information could not be validated on the target network. |
STROBE OUTPUT NOT SUPPORTED | 0x0307 / (775) | A DeviceNet router does not support application data in the O→T direction for strobe-triggered connections. |
— (reserved) | 0x0308–0x0309 / (776–777) | Reserved by CIP. |
PARTICIPANT CONNECTION OPEN | 0x0310 / (784) | At least one participant connection is open. |
PORT NOT AVAILABLE | 0x0311 / (785) | The port specified in a port segment is not available or does not exist. |
LINK ADDRESS NOT VALID | 0x0312 / (786) | The link address specified in the port segment is invalid for the target network type. |
DUPLICATE PARTICIPANT ID | 0x0313 / (787) | Duplicated participant ID. |
PARTICIPANT ID NETWORK SEGMENT IS MISSING | 0x0314 / (788) | The participant ID network segment is missing. |
INVALID SEGMENT IN CONNECTION PATH | 0x0315 / (789) | A segment type or value in the connection path could not be decoded. Used only when no more specific code applies. |
FORWARD_CLOSE SERVICE CONNECTION PATH MISMATCH | 0x0316 / (790) | The connection path in the Forward_Close does not match the connection to be closed (code is deprecated). |
SCHEDULING NOT SPECIFIED | 0x0317 / (791) | The schedule network segment is missing or contains an invalid value. |
LINK ADDRESS TO SELF INVALID | 0x0318 / (792) | A link address pointing to the device itself (loopback) may be invalid. |
SECONDARY RESOURCES UNAVAILABLE | 0x0319 / (793) | In a redundant system the secondary could not duplicate the connection request. |
RACK CONNECTION ALREADY ESTABLISHED | 0x031A / (794) | A module connection is refused because part of the data is already contained in a rack connection. |
MODULE CONNECTION ALREADY ESTABLISHED | 0x031B / (795) | A rack connection is refused because part of the data is already contained in a module connection. |
MISCELLANEOUS | 0x031C / (796) | Connection-related error for which no other extended status code applies. |
REDUNDANT CONNECTION MISMATCH | 0x031D / (797) | When establishing a redundant-owner connection the RPI/connection parameters or transport type do not match. |
NO MORE USER CONFIGURABLE LINK CONSUMER RESOURCES AVAILABLE IN THE PRODUCING MODULE | 0x031E / (798) | The configured number of consumers for the producing application is already in use. |
NO USER CONFIGURABLE LINK CONSUMER RESOURCES CONFIGURED IN THE PRODUCING MODULE | 0x031F / (799) | No consumers are configured for the producing application. |
— (vendor specific) | 0x0320–0x07FF / (800–2047) | Vendor specific. |
NETWORK LINK OFFLINE | 0x0800 / (2048) | A network link in the path to the module is offline. |
— (CIP Safety) | 0x0801–0x080F / (2049–2063) | See CIP Safety Specification (Volume 5, Chapter 3). |
NO TARGET APPLICATION DATA AVAILABLE | 0x0810 / (2064) | The target application has no valid data for the requested connection. |
NO ORIGINATOR APPLICATION DATA AVAILABLE | 0x0811 / (2065) | The originator application has no valid data for the requested connection. |
NODE ADDRESS HAS CHANGED SINCE THE NETWORK WAS SCHEDULED | 0x0812 / (2066) | A router in a scheduled network has a different node address than configured. |
NOT CONFIGURED FOR OFF-SUBNET MULTICAST | 0x0813 / (2067) | Producer and consumer are in different subnets, but the producer is not configured for off-subnet multicast. |
INVALID PRODUCE/CONSUME DATA FORMAT | 0x0814 / (2068) | The format of the produced/consumed data per the data segment is invalid (code is deprecated). |
— (CIP Safety) | 0x0815–0x0834 / (2069–2100) | See CIP Safety Specification (Volume 5, Chapter 3). |
— (reserved) | 0x0835–0x08FF / (2101–2303) | Reserved by CIP. |
(D)TLS FATAL ALERT 0: CLOSE NOTIFY | 0x0900 / (2304) | One side of the (D)TLS connection requested connection teardown. |
(D)TLS FATAL ALERT 10: UNEXPECTED MESSAGE | 0x0901 / (2305) | An out-of-sequence message was received during the (D)TLS handshake. |
(D)TLS FATAL ALERT 20: BAD RECORD MAC | 0x0902 / (2306) | A (D)TLS record was received with an incorrect MAC or decrypted improperly. |
(D)TLS FATAL ALERT 22: RECORD OVERFLOW | 0x0903 / (2307) | A (D)TLS record exceeds the permitted maximum size. |
(D)TLS FATAL ALERT 30: DECOMPRESSION FAILURE | 0x0904 / (2308) | The (D)TLS decompression received invalid input. |
(D)TLS FATAL ALERT 40: HANDSHAKE FAILURE | 0x0905 / (2309) | No acceptable set of security parameters could be negotiated. |
(D)TLS FATAL ALERT 42: BAD CERTIFICATE | 0x0906 / (2310) | A certificate was corrupt or its signature could not be verified. |
(D)TLS FATAL ALERT 43: UNSUPPORTED CERTIFICATE | 0x0907 / (2311) | A certificate was of an unsupported type. |
(D)TLS FATAL ALERT 44: CERTIFICATE REVOKED | 0x0908 / (2312) | A certificate was revoked by its issuer. |
(D)TLS FATAL ALERT 45: CERTIFICATE EXPIRED | 0x0909 / (2313) | A certificate is expired or not yet valid. |
(D)TLS FATAL ALERT 46: CERTIFICATE UNKNOWN | 0x090A / (2314) | Some other issue occurred while validating the certificate. |
(D)TLS FATAL ALERT 47: ILLEGAL PARAMETER | 0x090B / (2315) | A field in the handshake was out of range or inconsistent. |
(D)TLS FATAL ALERT 48: UNKNOWN CA | 0x090C / (2316) | The CA of the received certificate is unknown or not trusted. |
(D)TLS FATAL ALERT 49: ACCESS DENIED | 0x090D / (2317) | A valid certificate was rejected by access control. |
(D)TLS FATAL ALERT 50: DECODE ERROR | 0x090E / (2318) | A message could not be decoded (field out of range or wrong length). |
(D)TLS FATAL ALERT 51: DECRYPT ERROR | 0x090F / (2319) | A cryptographic handshake operation (signature/finished) failed. |
(D)TLS FATAL ALERT 70: PROTOCOL VERSION | 0x0910 / (2320) | The offered protocol version is not supported. |
(D)TLS FATAL ALERT 71: INSUFFICIENT SECURITY | 0x0911 / (2321) | The server requires stronger ciphers than the client offers. |
(D)TLS FATAL ALERT 80: INTERNAL ERROR | 0x0912 / (2322) | An internal error (e.g. out of memory) prevents continuation. |
(D)TLS FATAL ALERT 86: INAPPROPRIATE FALLBACK | 0x0913 / (2323) | The server detected an illegal protocol downgrade. |
(D)TLS FATAL ALERT 110: UNSUPPORTED EXTENSION | 0x0914 / (2324) | The server hello contained an extension not requested by the client. |
(D)TLS FATAL ALERT: UNKNOWN PSK IDENTITY | 0x0915 / (2325) | The PSK identity sent during the handshake is unknown. |
EGRESS RULE DENY | 0x0916 / (2326) | An egress rule explicitly prohibits the attempted connection origination. |
EGRESS RULE CIPHER NOT ALLOWED | 0x0917 / (2327) | An egress rule requires a cipher suite that is not in the list of allowed ciphers. |
NO MATCHING INGRESS RULE | 0x0918 / (2328) | No ingress rule permits the communication (default: deny). |
INGRESS RULE DENY | 0x0919 / (2329) | An ingress rule explicitly prohibits the attempted communication. |
INGRESS RULE DENY NON-SECURE | 0x091A / (2330) | An ingress rule permits only CIP Security communication, but non-secured communication was attempted. |
NO MATCHING EGRESS RULE | 0x091B / (2331) | No egress rule permits the attempted communication (default: deny). |
— (reserved, security) | 0x091C–0x09FF / (2332–2559) | Reserved for security related status. |
UDP PORT FOR CLASS 0/1 NOT OPEN | 0x0A00 / (2560) | The UDP port required for the requested Class 0/1 connection is disabled. |
— (reserved, EtherNet/IP) | 0x0A01–0x0AFF / (2561–2815) | Reserved for EtherNet/IP. |
— (reserved) | 0x0B00–0xFCFF / (2816–64767) | Reserved by CIP. |
— (do not use) | 0xFD00–0xFFFF / (64768–65535) | Do not use. |
Error Corde | Code hex / (decimal) | Description/Meaning |
|---|---|---|
SUCCESS | 0x00 / (0) | The service completed successfully. |
RESOURCE UNAVAILABLE FOR UNCONNECTED_SEND | 0x02 / (2) | The device lacks the resources to fully process the Unconnected_Send. |
PATH SEGMENT ERROR IN UNCONNECTED SEND | 0x04 / (4) | The router could not correctly parse the embedded explicit messaging request. |
ERROR IN DATA SEGMENT | 0x09 / (9) | Error in the data segment of a Forward_Open. The extended status is the index of the error position within the data segment. |
OBJECT STATE ERROR | 0x0C / (12) | The state of the target object prevents the service from being handled. The extended status optionally reports the current object state. |
DEVICE STATE ERROR | 0x10 / (16) | The state of the device prevents the service from being handled. The extended status optionally reports the current device state. |
NOT ENOUGH DATA | 0x13 / (19) | The service did not supply enough data for the requested operation. |
Sollten Sie die Fehler nicht selbstständig lösen können, benötigt der Support folgende Informationen:
- TwinCAT Versions- und Build-Nummer und eine
- Wireshark®-Aufzeichnung