Rexroth Tightening System 350 System Documentation - Rhino ...

7 Data Services Tightening Technology | Bosch Rexroth AG 79/3167.1 Overview of the tightening results communication7.1.2 Protocols for results outputIn the Tightening System 350, the tightening results can be transferred to output devices or devices forfurther processing or storage with the following protocols:– Printer (serial interface X3C1 and IMser)– 3964R communication (serial interface X3C1 and IMser)– FTP (Ethernet interface X7E1)– Profibus data (IMpdp)– DeviceNet data (IMdev)You can also use the protocols in parallel, e.g. for simultaneous output via FTP and data Profibus. Theprotocols “Printer” and “3964R communication” can also be used double.Further information can be found in the descriptions on the respective data service.NoteEach data service requires time to calculate and thus lengthens the duration of the tightening cycle. Thisis why it makes sense to only activate the necessary data services to avoid delays.7.1.3 Identification codesThe results data record of a tightening is clearly identified for further internal or external processing withan identification code (IC code) and can thus be assigned to the tightened component. The ID code cancontain up to 64 ASCII characters, such as parts of a part number, production number, serial number,chassis number, etc.The ID code is transferred to the controller before the tightening is begun. The internal cycle counter canbe used for identification as an alternative to an ID code.7.1.3.1 Selection of the source for ID codesThe source of the ID codes is defined in the BS350 operating system under System → Tightening celldata → ID code by selecting the desired source in the Device selection field.Figure 7–2:Select ID code sourceThe exact number of available options depends on the configuration of your communication unit. Thereare the following options:– No ID code: No ID code will be entered in the results data record.– Cycle counter: The internal cycle counter numbers are used to create the ID code.– Ethernet/FTP: A file with a character sequence to create the ID code is expected (see page 85).– PLC 3964R: ID codes can be transferred to the controller via a serial interface that has been configuredfor protocol 3964R (see page 120).– Profibus DP: An ID code can be transferred to the controller via Profibus DP (see page 141).– DeviceNet: The ID code can be transferred to the controller via DeviceNet (see page 162).System 350 | 3 608 878 040/05.2008