PLC Related Errors

The remaining portion lists the values and interpretations for the most common network error situations. Note that some codes are derived directly from standard error codes supported by specific protocols. The documentation for those products is then necessary for interpretation.

 

 

Code

Description

 

0

No error condition detected

 

350

Net address entered incorrectly

 

351

Rc flag not recognized, attempt to write a read only address

 

352

Specified net is invalid

 

353

Packet did not fit in buffer

 

354

Protocol does not support the net address format

 

355

Protocol does not fit this data type

 

356

Request timed out with no feedback

 

357

Node address is invalid for selected protocol

 

358

Driver got into an unknown state

 

359

Node/driver incompatible with address mode

 

360

Miscellaneous error parsing address string

 

361

Some field was duplicated in address string

 

362

File type specified in address string no supported

 

363

Couldn't parse file number field in address string

 

364

Couldn't map the I/O slot specified in address string

 

365

Couldn't parse element field in address string

 

366

Couldn't parse sub-element field in address string

 

367

Couldn't parse bit field in address string

 

368

Too many routing nodes specified in address string

 

369

Some routing node has illegal syntax

 

370

Transaction aborted at user request

 

371

Hardware does not support the protocol

 

372

Alarm criteria flag not recognized

 

373

Error function called with no config error

 

374

Created/transmitted a null packet

 

390

Source channel data not available for channel link

MODBUS-SPECIFIC ERRORS: (Also applicable for ModbusTCP and EtherNet/IP)

 
 

410

No traffic received from the net

 

420

UART serialization error

 

430

Time-out with no recognizable response

 

431

Time-out with no response at all

 

440

CRC error

 

450

Valid framing, unknown command or response

 

500

Enqueued transaction not transmitted

 

501

Transaction took too long to transmit

 

502

Attempt to transmit a null packet

 

 

MODBUS, ModbusTCP or EtherNet/IP EXCEPTION RESPONSES: The last 2 digits come directly from the MODBUS protocol exception responses.  The occurrence of these codes is sufficient to conclude that the remote node received the command but could not execute it.

 
 

600

Offset for Modbus exception responses

 

601

Modbus exception: Illegal function

 

602

Modbus exception: Illegal data address

 

603

Modbus exception: Illegal data value

 

604

Modbus exception: Failure in associated device

 

605

Modbus exception: Acknowledge

 

606

Modbus exception: Slave device busy

 

607

Modbus exception: Negative acknowledge

 

608

Modbus exception: Memory parity error

 

609

Could not convert data to correct type

DEVICE SELF-TEST CODES:

 
 

700

Device has not been opened

 

705

DUART not present

 

710

Net not configured with PLC-type protocol

 

715

Bad serial IO configuration parameter

 

725

Background noise on network substrate

 

730

Another Modbus master already active

 

731

MBPLUS peer in monitor-on-line state

 

732

MBPLUS peer never getting token

 

733

MBPLUS peer in unknown state

 

734

MBPLUS driver not responding

 

735

Diagnostic loop-back test failed

 

750

A remote node has same node address

 

755

Could not find any nodes on network

Note: See Modicon documentation for further details.