Rexroth Tightening System 350 System Documentation - Rhino ...

170/316 Bosch Rexroth AG | Tightening Technology 7 Data Services7.6 DeviceNet communication7.6.5.2 General troubleshooting in DeviceNetGeneral troubleshooting can be used to identify errors in the wiring or configuration. The following pointsshould be checked:– Is the total power consumption of all DeviceNet participants less than the power provided by thepower supply (per subnetwork)?Note: The IMdev interface module does not require a power supply via DeviceNet.– Is the number of DeviceNet participants less than 64? (The effective limit is 61 participants, whichallows for free addresses for the DeviceNet scanner and a PC connection, as well as the default address63 that is used by unconfigured DeviceNet participants.)– Do all DeviceNet participants have a unique MAC ID and are they all set to the same baud rate?– Is the set baud rate permissible for this network expansion and the selected cables?– Are there no stub lines longer than 6 m? The total length to the main line is decisive for participantsconnected via distributors.– Is the total length of all stub lines less than permitted (see Table 7–43 on page 165)?– Is the line length between the furthest connected DeviceNet participants less than permitted (seeTable 7–42 on page 165)?– Is the main line equipped with a termination resistor on both ends (see Figure 7–57 on page 165)?– Is the DeviceNet grounded at exactly one position, preferably at the physical center (page 166)?– Are there any interruptions or short circuits in the DeviceNet?A multimeter may be used to check the wiring. The voltage between CAN_H and CAN_L in relationto V– is approx. 2.5 to 3.0 V in a DeviceNet without data transfer. If data is being exchanged, thevoltage of CAN_L is slightly lower and that of CAN_H slightly higher.7.6.5.3 Error messages in connection with DeviceNetTable 7–46: Error messages in connection with DeviceNetError number(internal)ErrorclassAffectedcomponentsError text800 1 A slot Unknown module in 801 4 A slot Driver error in 802 1 A slot Driver number in invalid803 1 A slot Invalid I/O number in 804 1 A slot Driver exception in 835 4 IMdev No DeviceNet master availableSystem 350 | 3 608 878 040/05.2008