Commissioning
EL37x2
99
Version: 3.5
Fig. 125:
Online display example
Please note:
• all slaves should be in OP state
• the EtherCAT master should be in “Actual State” OP
• “frames/sec” should match the cycle time taking into account the sent number of frames
• no excessive “LostFrames” or CRC errors should occur
The configuration is now complete. It can be modified as described under
manual procedure [
}
90]
.
Troubleshooting
Various effects may occur during scanning.
• An
unknown device
is detected, i.e. an EtherCAT slave for which no ESI XML description is available.
In this case the System Manager offers to read any ESI that may be stored in the device. This case is
described in the chapter "Notes regarding ESI device description".
•
Device are not detected properly
Possible reasons include:
- faulty data links, resulting in data loss during the scan
- slave has invalid device description
The connections and devices should be checked in a targeted manner, e.g. via the emergency scan.
Then re-run the scan.
Fig. 126:
Faulty identification
In the System Manager such devices may be set up as EK0000 or unknown devices. Operation is not
possible or meaningful.
Summary of Contents for EL3702
Page 2: ......
Page 6: ...Table of contents EL37x2 6 Version 3 5...
Page 83: ...Commissioning EL37x2 83 Version 3 5 Fig 92 Incorrect driver settings for the Ethernet port...
Page 142: ...Commissioning EL37x2 142 Version 3 5 Fig 184 Process data tab SM0 EL37x2...
Page 143: ...Commissioning EL37x2 143 Version 3 5 Fig 185 Process data tab SM1 EL37x2...
