117
Identifying Errors Detected by Functions
Section 7-2
7-2
Identifying Errors Detected by Functions
This section lists the errors that can be identified using the Board’s Master
API functions. The return value returned by API functions indicates when an
error has occurred during execution of the function. (Refer to
Error Codes
All of the Board’s Master API functions are bool-type functions, so FALSE is
returned as the return value when an error has occurred during execution.
When FALSE is returned, the GetLastError() function can be used to read
more detailed error information (the error code.)
No
change
OFF
Send error:
Network power supply error
The communications power supply isn’t being supplied properly.
Check the network power supply and network cable wiring.
Send error:
Transmission timeout
A transmission couldn’t be completed successfully for one of the
following reasons:
• There are no Slaves in the network.
• There is another Master in the Network.
• There is an error in the CAN controller.
• The Master and Slave baud rate settings don’t agree.
Check the following:
• Check the communications baud rate settings in all of the nodes.
• Check that the cable lengths (trunk and drop lines) are within
specifications.
• Check for loose or broken cables.
• Check that there are Terminating Resistors at each end of the
trunk line and nowhere else in the network.
• Check for excessive noise.
No
change
Flashing
(red)
Verification error:
Slave doesn’t exist
A Slave registered in the scan list does not exist in the network.
Check the following:
• Check the communications baud rate settings in all of the nodes.
• Check that the cable lengths (trunk and drop lines) are within
specifications.
• Check for loose or broken cables.
• Check that there are Terminating Resistors at each end of the
trunk line and nowhere else in the network.
• Check for excessive noise.
Unsupported Slave
A Slave is connected that has an I/O size exceeding 200 bytes.
Remove Slaves from the network if they have an I/O size greater
than 200 bytes.
Verification error:
Slave I/O size mismatch
The I/O size of a Slave registered in the scan list doesn’t match the
actual Slave in the network.
Check the Slave and create the scan list again.
I/O Communications error
A timeout occurred in I/O communications. Check the following:
• Check the communications baud rate settings in all of the nodes.
• Check that the cable lengths (trunk and drop lines) are within
specifications.
• Check for loose or broken cables.
• Check that there are Terminating Resistors at each end of the
trunk line and nowhere else in the network.
• Check for excessive noise.
OFF
OFF
System error
Replace the Board.
Indicator status
Error
Probable cause and remedy
MS
NS
Summary of Contents for DeviceNet 3G8F7-DRM21-E
Page 1: ...OPERATION MANUAL Cat No W381 E1 02 3G8F7 DRM21 E DeviceNet PCI Board ...
Page 2: ...3G8F7 DRM21 E DeviceNet PCI Board Operation Manual Revised July 2005 ...
Page 3: ...iv ...
Page 5: ...vi ...
Page 29: ...12 Preparation for Operation Section 1 8 ...
Page 67: ...50 PC Watchdog Timer Management Function Section 3 11 ...
Page 115: ...98 Maintenance API Functions Section 4 7 ...
Page 131: ...114 Remote I O Communications Characteristics Section 6 1 ...
Page 145: ...Index 128 ...
Page 147: ...130 Revision History ...