Rexroth Tightening System 350 System Documentation - Rhino ...

164/316 Bosch Rexroth AG | Tightening Technology 7 Data Services7.6 DeviceNet communication7.6.1.2 Function diagramCS351PartnercontrollerInputsID codeControl signalsID codeEN CW CCW ABCD1 1 0 41 42 43 44OutputsControl signalsCyCmp OK NOK1 1 0Figure 7–55:Function diagram of data exchange via DeviceNet7.6.1.3 Exchanged dataThe following data can be exchanged via DeviceNet:– Control signals from/to the partner controller– ID codesA description of the control signals and their applications can be found in chapter 6, “Control Signals” onpage 55.NoteData exchange via DeviceNet can only take place if the input data area is configured and at least one controlsignal has been set.7.6.1.4 Layout of the data buffer for transferring ID codes and control signalsThe data buffer in the IMdev interface module is divided into an area for control signals and one forID codes.All data (control signals, ID codes) are located in the linear memory in a specific place determined by theconfiguration (see page 143). During the planning phase, the partner controller is informed of the databuffer layout via the so-called “Electronic Data Sheet” (EDS).Control signal inputs Control signal outputs ID codeSize 2 to 8 bytes 2 to 8 bytes 0 to 64 bytesFigure 7–56:Division of the data buffer7.6.1.5 Network topology in DeviceNetA DeviceNet network usually consists of a linear main line with (branched) stub lines. Wiring is done withspecial DeviceNet cables. Round cables in varying diameters and a flat cable are available. The choice ofcable also determines the maximum expansion of the DeviceNet.System 350 | 3 608 878 040/05.2008