www.dadehpardazan.ir 88594014-15Network Maintenance6.4.1 Masters6-866.4 TroubleshootingWhen the 260IF Module detects an error during DeviceNet communications, it reports the errorvia the LED indicators, I/O status function, and status function. The following table gives prob-able causes and possible solutions.6.4.1 MastersThe following table gives the status of indicators and status functions for normal operationwhen the 260IF Module is set as a Master.The following table gives possible solutions for errors that occur when the 260IF Module isset as a Master.Table 6.3 Troubleshooting the MasterLED Status I/O StatusMS lit greenNS lit green8004 8000Problem Locations to Check ProbableCause Possible SolutionIndicators Status I/O StatusNo DeviceNetcommunicationsMS not litNS not lit- - No power tothe 260IF Mod-ule.Check the rack or system bus cable connection tothe 260IF Module.MS lit redNS not lit- - Hardware mal-functionReplace the 260IF Module.MS lit redNS lit red- - Hardware mal-functionReplace the 260IF Module.MS lit greenNS lit res1010 0000 DuplicateMAC ID1. Change the MAC ID address for the 260IFModule and cycle the power.2. Change the MAC ID addresses for otherDeviceNet devices and cycle the power to the260IF Module.1008 - Bus-off 1. Check the wiring and connections forDeviceNet cables and connectors.2. Check the power supply voltage and connectionfor communications power supply.3. Check the communications power supply volt-age for each DeviceNet connector on the 260IFModule (11 to 24 V).4. Check the baud rate for each DeviceNet devicein the network.5. Check the terminator (121 Ω) and connectionstatus.6. Check the length of the network.7. Replace the 260IF Module. Then either cyclethe power for the 260IF Module or disconnectand re-insert the DeviceNet connectors.