Rexroth Tightening System 350 System Documentation - Rhino ...

84/316 Bosch Rexroth AG | Tightening Technology 7 Data Services7.2 Ethernet communication7.2.1.2 DescriptionData exchange between the Compact System and the partner controllers takes place physically via Ethernet.The File Transfer Protocol (FTP) based on TCP/IP is the protocol used for transferring data betweenthe units.FTP offers suitable mechanisms for secure data transfer in Ethernet. High transfer quality is guaranteedby error protocols, check sums, and, if necessary, retransferring data blocks.FTP is based on a client/server architecture, i.e. an FTP server provides an FTP client with its services(access to mass storage). The client is the active participant and can write data on the FTP server or readdata from it. Only write access is used in the Tightening System 350.The Compact System has both an FTP client as well as an FTP server at its disposal.– FTP server: Using the FTP server, the Compact System receives ID codes for further processing.The FTP client from an external control unit (partner controller) sends the ID codes to the FTP serverwith the PUT command. Other commands are not permitted and may have a negative influence onthe system.– FTP client: Using the FTP client, the Compact System sends tightening results to the FTP server onan external control unit (partner controller), thus accessing its FTP server to write the results.Access to the Compact System's FTP server is protected by assigned user names and correspondingpasswords. The protocol for data transfer is defined in RFC-959 (File Transfer Protocol).Tightening result IDs and storage locations can be provided by various participants in Ethernet. For example,the ID codes can be received by the partner controller, but the tightening results sent to a centraldata server.7.2.1.3 Exchanged dataTightening results, which are supposed to be transferred via FTP, are summarized in a file. Tightening resultsoutput takes place for each tightening sequence and channel. Thus, a specific ID for the tighteningresults is necessary, in order to be able to reassign archived tightening results at a later stage, for example.The CS351 Compact System enables identification of every tightening result record with an ID providedby the partner controller.After the tightening process has been completed, the tightening results are transferred via FTP from thetightening system (in this case the FTP client) to the partner controller (in this case the FTP server).7.2.1.4 Data transfer/data bufferTightening results transfer can be integrated into the tightening process in various ways:– Before sequence endor– After sequence endData transfer before sequence endThe results data is buffered in the controller during data processing after tightening. Transfer of tighteningresults via FTP takes place after the end of the sequence. Consequently, the results are not available onthe FTP server after the end of the sequence.Data transfer after sequence endIf the tightening results are transferred after the end of the sequence, the data records are stored in themass storage before the end of the sequence. Transmission via FTP is done independently of the tightening.Thanks to this decoupled data transfer (buffering), no data is lost if the Ethernet connection is disruptedand the tightening system remains ready for operation.NoteIn this operating mode, the tightening results data are not available on the FTP server once the sequencehas ended.System 350 | 3 608 878 040/05.2008