How to troubleshoot an Error 77 (I/O Size Mismatch) on DeviceNet

using the Class Instance Attribute Editor in RSNetworx for DeviceNet.

A DeviceNet Scanner will declare an Error 77 for a Slave node when the I/O size that the
Scanner expects for that Slave node does not match the connection size parameters
received from that Slave node.
Use the following steps to determine the I/O size the Scanner expects from a given
node and the exact I/O size used by the Slave node itself. This example will select a
node that uses Polled I/O data. Codes for other I/O types will be given.
Important:
Not all Nodes will respond to all of the Class Instance Editor codes that are listed
in this document. In those cases, you will have to look at the information that is
displayed in the Properties window for that particular device or consult the
manual provided by the Vendor that supplied the particular device.
_______________________________________________________________________
1. Open RSNetworx for DeviceNet.
2. Double-Click on the scanner that is displaying the 77 Error. You should be Online
with the Scanner or can use the Offline mode if the Offline file has been saved with
the correct Scanlist information.
3. Select the Scanlist Tab and then highlight the Node Number that is causing the Error
77.
4. Click the Edit I/O Parameter command Box to view:
A. The I/O Type (Polled, Strobed, or Change of State/Cyclic)
B. The Input (to the Scanner) Size in Bytes
C. The Output (from the Scanner) Size in Bytes.
D. Record this information to be used in subsequent steps.

Display showing I/O Connection Size expected by the Scanner:

Note:
I/O sizes are shown in Bytes.
5. Go online with the DeviceNet Network.
6. Highlight the Node that is reported as having the Error 77 (I/O Size).
A. Right-Click on the Menu Entry Class Instance Editor

Display showing how to start Class Instance Editor:

B. Click Yes to acknowledge the Warning Message regarding the Editors usage.
We will be reading information only. We will not be writing data to the
device.
The following codes will allow us to read the Input data size:
C.
D.
E.
F.
G.
H.

Use Service Code E Get Single Attribute which is the default value.
Use 5 for the Class Code:
Use 2 for the Instance Code:
Use 7 for the Attribute Code:
Press the Execute Command Button
Record the value returned in the Data received from the device: box. This
is the polled input data size. This is input into the controllers DeviceNet
scanner.

Display showing Input I/O connection Size:

Note:
I/O size display defaults to Byte. Data is displayed in Low Byte High Byte
format.
For example, 4 Bytes defaults to a display of 4 0
We will now read the Output size, still using E as the service Code:
I.
J.
K.
L.
M.

Use 5 for the Class Code:

Use 2 for the Instance Code:
Use 8 for the Attribute Code:
Press the Execute Command Button
Record the value returned in the Data received from the device: box. This
is the polled output data size. This is output from the controllers DeviceNet
scanner.

Display showing Output I/O connection Size:

Note:
I/O size display defaults to Byte. Data is displayed in Low Byte High Byte
format.
For example, 4 Bytes defaults to a display of 4 0
Now you should compare the data obtained in Step 4-D with the data obtained from Step
6-H (Input Size) and Step 6-M (Output Size).
Any differences found must be reconciled by:
Changing the Scanners I/O size value to match the values obtained from the
Class Instance Editor. Go to Steps to Change the I/O Parameters in a
DeviceNet Scanner at the end of this document for more information.
or
Changing the Devices configuration by adjusting parameters in the Device.
Go to Steps to Change the I/O Parameters in a DeviceNet Node at the end of
this document for more information.

Note:
You can convert the Class Instance Editor to display this data in Word format to
eliminate the Low Byte High Byte confusion. Remember, the data values will
still always represent the number of bytes, not works, being transferred between
the Scanner and the Slave nodes.
Displaying data in Word format in the Class Instance Editor:

The above example shows the Class Instance Attribute information for a Polled Input
connection.
The table below shows the Class Instance Attribute information for all I/P connection
types; Polled, Strobed, COS/Cyclic.

Note:
Polled and COS/Cyclic use the Class 2 Instance to determine the output
connection size. Strobed I/O when used, is fixed at 8 bytes.
Even though only 1 bit will get mapped:

Strobed O/P Bit Data Mapping:

The Strobed Output connection Object still reports 8 Bytes:

These are the appropriate DeviceNet Objects for the different DeviceNet Connection
Objects:
DeviceNet Object
Polled I/O Connection Object
Input (to the Scanner)
Output (to the Slave)
Strobed I/O Connection Object
Input (to the Scanner)
Output (to the Slave)
Note: The only type of
data typically sent to

Valid Possible Values

Description
Class 5
Instance 2
Attribute 7
Class 5
Instance 2
Attribute 8

Connection Object.
Polled I/P Connection
Bytes produced by the slave.
Connection Object.
Polled/COS/Cyclic O/P Connection.
Bytes consumed by the slave.

Class 5
Instance 3
Attribute 7
Class 5
Instance 3
Attribute 8

Connection Object.
Strobed I/P Connection
Bytes produced by the slave.
Connection Object.
Strobed O/P Connection.
Bytes consumed by the slave.
Value returned will always be a fixed
size of 8 Byes.

this type of device is a

HeartBeat bit.

Mapping will only occur if the Use

Output Bit checkbox is checked.
Only 1 bit will be mapped.
COS/Cyclic I/O Connection
Object
Input (to the Scanner)
Output (to the Slave)

Class 5
Instance 4
Attribute 7
Class 5
Instance 2
Attribute 8

Connection Object.
COS/Cyclic I/P Connection
Bytes produced by the slave.
Connection Object.
Polled/COS/Cyclic O/P Connection.
Bytes consumed by the slave.

Appropriate Return Values for different DeviceNet Connection Objects.

DeviceNet Object

Class-Instance-Attribute
Value

Expected Return Value

Polled I/O Connection

Input (to the Scanner)
Output (to the Slave)

5-27
5-37
5-47
5 - 2- 8
5-38
5-48

Actual size in bytes.

N/A
N/A
Actual size in bytes.
N/A
N/A

5-27
5-37
5-47
5-28
5-38

N/A
Actual size in bytes.
N/A
N/A
Will always return a value of 8
Bytes.

Strobed I/O Connection

Input (to the Scanner)
Output (to the Slave)

5-4-8

1 Bit of data will actually be

mapped only if the Use Output
Bit Checkbox is checked.
N/A

COS/Cyclic I/O Connection

Input (to the Scanner)

5-2-7

Output (to the Slave)

5-3-7
5-4-7
5-2-8
5-3-8
5-4-8

N/A But, it will be a

recognized command by the
device.
N/A
Actual size in bytes.
Actual size in bytes.
N/A
N/A But, it will be a
recognized command by the
device.

Where: N/A may return as a valid number or as a Comm Error #12 Object does not
exist.
The actual value that gets returned for a given Device Object depends on the device itself,
some devices support multiple connection methods (Polled/Strobed/COS/Cylic) and may
provide an appropriate DeviceNet Size Value for a connection method that is not
currently used. But, the device should reply with the correct connection size for the
connection method that is being used.

Steps to Change the I/O Parameters in a DeviceNet Scanner

1. Upload the Configuration from the Scanner displaying Error 77.
2. Remove the Device with the 77 Error from the Scanlist.
3. Download the change to the Scanner.
4. Re-upload the Configuration from the Scanner.
5. Add the Node back to the Scanlist.
6. Before applying the changes, Click on the Edit I/O Parameters command box.
7. Change the Input Size to the correct number of Bytes.
8. Change the Output Size to the correct number of Bytes,
9. Check the Input tab to ensure of the correct Input Mapping.
10. Check the Output tab to ensure of the correct Output Mapping.
11. Apply the changes and download to the Scanner.
12. Put the Scanner in the Run Mode to ensure that the 77 Error has been corrected.

Steps to Change the I/O Parameters in a DeviceNet Node:

1. Upload the existing Configuration from the Scanner displaying Error 77.
2. Remove the Device with the 77 Error from the Scanlist.
3. Download the change to the Scanner and close the Scanner Properties Window.
4. Double-Click on the Node to be changed.
5. Click on the Parameters Tab.
6. Make the required changes to the Node (For example: add/remove datalinks, add
modules to a subnet device (Flex I/O or Point I/O with a 1734-ADN module.)
7. Apply the changes to the Node and Close the Node Properties Window.
8. Upload the existing Configuration from the Scanner from Step 1.
9. Add the Node back to the Scanlist.
10. Before applying the changes, Click on the Edit I/O Parameters command box.
11. Verify the correct Input and Output Size in Bytes.
12. Check the Input tab to ensure of the correct Input Mapping.
13. Check the Output tab to ensure of the correct Output Mapping.
14. Apply the changes and download to the Scanner.
15. Put the Scanner in the Run Mode to ensure that the 77 Error has been corrected.