MSTR Block Error Codes

Error Code

(Hex)

Meaning

1001

User-initiated abort

2001

Invalid operation type

2002

User parameter changed

2003

Invalid length

2004

Invalid offset

2005

Invalid length + offset

2006

Invalid slave device data area

2007

Invalid slave device network area

2008

Invalid slave device network routing

2009

Route equal to your own address

200A

Attempting to obtain more global data registers than available

200B

Conflict with Peer Cop (Read Global Data cannot be used if Peer Cop is used)

30xx

Modbus slave exception response. See error values 3001-3007 below for specific errors:

3001

Slave device does not support the requested operation

3002

Nonexistent slave device registers requested

3003

Invalid data value requested

3005

Slave has accepted long-duration program command

3006

Function can’t be performed now—a long-duration command in effect

3007

Slave rejected long-duration program command

4001

Inconsistent Modbus slave response

5001

Inconsistent network response

6mxx

Routing failure. ’r;m’ indicates the routing entry at fault (0=Routing 1, 1=Routing 2, etc). See error values 6m01-6m80 below for specific errors:

6m01

No response received. For a local node, if m is 0, the node address was incorrect; check the node address. If m is 1, the data path was incorrect; ensure that a data path between 1 and 8 is used. See MSTR Block Read or MSTR Block Write for details.

6m02

Program access denied

6m03

Node off-line and unable to communicate

6m04

Exception response received

6m05

Router node data paths busy

6m06

Slave device down

6m07

Bad destination address

6m08

Invalid node type in routing path

6m10

Slave has rejected the command. Check the routing information to see if a valid data path (1-8) has been entered after the node address.

6m20

Initiated transaction forgotten by slave device

6m40

Unexpected master output path received

6m80

Unexpected response received

F001

Wrong destination node specified for the MSTR operation