Abort by user.

Warm Start initiated abort.

Communication function block specific error codes.

Communication function block specific error codes.

Communication function block specific error codes.

Communication function block specific error codes.

An operation type that is not supported has been specified in the control block.

One or more control block parameters were modified while the MSTR element was active (this only applies to operations which require several cycles for completion). Control block parameters may only be modified in inactive MSTR components.

Invalid value in the length field of the control block.

Invalid value in the offset field of the control block.

Invalid value in the length and offset fields of the control block.

Unauthorized data field on slave.

Unauthorized network field on slave.

Unauthorized network routing path on slave.

Routing path equivalent to their own address.

Attempt to get more global data words than available.

Peer cop conflict on WR/RD global.

Bad pattern for change address request.

Bad address for change address request.

The control block or data buffer is not assigned, or (incorrect size, parts of the control block or data buffer are located outside of the %MW (4x) range.

Space for response in data buffer is too small.

Control buffer length invalid.

Invalid parameter.

Syntax error in “rail.slot.chan” string.

Module missing, not detected, or not configured.

No channel data (channel out of bound).

Abort on timeout.

Invalid task context.

Ethernet security system service error.

Invalid answer data (received data do not correspond to the expected answer).

Invalid answer checksum.

Compatibility issue (for example, EF or DDT version not compatible with firmware version).

Exceptional response by the Modbus slave with specific ss exception code.

Exceptional Control Expert protocol error response by the Modbus slave with specific ss error code.

Exceptional Control Expert protocol IO request error acknowledgement by the Modbus slave with specific ss error code.

UNI-TE specific report.

Generic communication report (correspond to Communication Report field of Premium/M340 EF Management Parameters).

Generic Operation Report in case of correct exchange (correspond to O

peration Report field of Premium/M340 EF Management Parameters when Communication Report = 16#00).

Generic Operation Report in case of refused message (correspond to Operation Report field of Premium/M340 EF Management Parameters when Communication Report = 16#FF).

CIP General Status Code.

Inconsistent response by the Modbus slave.

Inconsistent Modbus Umas response.

Inconsistent UNI-TE response (depending on the module).

Read request for the status words not accepted by the module channel.

Command parameters not accepted by the module channel.

Adjustment parameters not accepted by the module.

SDO abort code (4 bytes) may be found in data field if data field is available.

TCP/IP Ethernet specific error codes.

Modbus Plus specific routing path error.

The subfield m shows where the error occurred (a 0 value means local node, 2 means 2nd device in route, and so on).

SY/MAX specific error codes.

EtherNet/IP detected error codes.

Wrong destination node was specified for the MSTR operation. Referenced S985 option not present or in reset mode.

Component not fully initialized.

Slave does not support requested operation.

Non-existing slave registers were requested.

An unauthorized data value was requested.

Unrecoverable error detected in the slave.

Slave has accepted a lengthy program command.

Function cannot currently be carried out: lengthy command running.

Slave has rejected lengthy program command.

Gateway unable to allocate an internal communication path.

No response obtained from target device.

Modbus extended exception. Additional data available in data field (if data field provided):

• Exception length: represents the length of the extended exception response, not including these 2 bytes.

• Exception data: error information specific to the function code involved.