11.07.2015 Views

Rexroth Tightening System 350 System Documentation - Rhino ...

Rexroth Tightening System 350 System Documentation - Rhino ...

Rexroth Tightening System 350 System Documentation - Rhino ...

SHOW MORE
SHOW LESS
  • No tags were found...

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

7 Data Services <strong>Tightening</strong> Technology | Bosch <strong>Rexroth</strong> AG 169/3167.6 DeviceNet communication7.6.4 Chronological sequence of ID code processingNoteAll chronological sequences are listed in chapter 6, “Control Signals” on page 55. In this chapter you canfind several examples for clarification of the function of DeviceNet communication.7.6.5 Troubleshooting for the DeviceNet connection7.6.5.1 Testing the connection to the partner controllerWith a configured IMdev interface module, a “No DeviceNet master” class 4 system error (self-acknowledged)will be output by the controller until the interface module is recognized by the master.The contents of the storage sections on the IMdev interface module can be displayed and analyzed viathe <strong>System</strong> test → DeviceNet data… function. You can thus check in the BS<strong>350</strong> that an ID code hasbeen correctly transferred.The control signals transmitted via DeviceNet can be viewed under <strong>System</strong> test → I/O interface.The IMdev interface module contains a mod./net status LED on the front panel with the following signalingin accordance with the ODVA specification:When connecting thepower supplyDuring operationThe following sequence is used to check the proper function of the interface module.– 1/4 second red– 1/4 second greenIt is highly probable that the interface module is defective if this sequence fails while connecting power.Further information can be found in the BS<strong>350</strong> operating system under <strong>System</strong> test → SE/CS errorlist… (see Table 7–46 on page 170 for error messages in connection with DeviceNet ).Table 7–44: Meaning of the LED NS (network status) displaysLED displayOffGreenFlashing green (1 Hz)RedFlashing red (1 Hz)MeaningAfter the device has been started and during the test for double MAC IDs; no power or connectionin the networkNetwork available, connection to master established, data exchange takes placeNetwork available, but no connection to master established; device waits for the master toset up a connectionError in the interface module, critical connection error, device has detected a network error(double MAC ID or bus off)Communication has failed, severe communication errorTable 7–45: Meaning of the LED MS (module status) displaysLED displayOffGreenFlashing green (1 Hz)RedFlashing red (1 Hz)MeaningNo powerReady for operationMissing or incomplete configurationThe IMdev interface module can only be made ready for operation through measures performedby the user.Fault is self-acknowledged after the IMdev interface module has remedied it.<strong>System</strong> <strong>350</strong> | 3 608 878 040/05.2008

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!