- Home
- Domestic appliances
- Climate control
- Temperature & humidity sensors
- Beckhoff
- EL3314-0002
- User manual
ONLINE configuration creation. Beckhoff EL3314-0002, EL3314-0090, EL3312, EL3318, EL3311, EL33-00 Series, EL3314-0010, EL3314
Add to My manuals204 Pages
advertisement
Commissioning
5.2.6
ONLINE configuration creation
Detecting/scanning of the EtherCAT device
The online device search can be used if the TwinCAT system is in CONFIG mode. This can be indicated by a symbol right below in the information bar:
• on TwinCAT 2 by a blue display “Config Mode” within the System Manager window: .
• on TwinCAT 3 within the user interface of the development environment by a symbol .
TwinCAT can be set into this mode:
• TwinCAT 2: by selection of
Mode…”
in the Menubar or by “Actions” → “Set/Reset TwinCAT to Config
• TwinCAT 3: by selection of in the Menubar or by „TwinCAT“ → “Restart TwinCAT (Config Mode)“
Online scanning in Config mode
The online search is not available in RUN mode (production operation). Note the differentiation between TwinCAT programming system and TwinCAT target system.
The TwinCAT 2 icon ( ) or TwinCAT 3 icon ( ) within the Windows-Taskbar always shows the
TwinCAT mode of the local IPC. Compared to that, the System Manager window of TwinCAT 2 or the user interface of TwinCAT 3 indicates the state of the target system.
Fig. 120: Differentiation local/target system (left: TwinCAT 2; right: TwinCAT 3)
Right-clicking on “I/O Devices” in the configuration tree opens the search dialog.
Fig. 121: Scan Devices (left: TwinCAT 2; right: TwinCAT 3)
This scan mode attempts to find not only EtherCAT devices (or Ethernet ports that are usable as such), but also NOVRAM, fieldbus cards, SMB etc. However, not all devices can be found automatically.
Fig. 122: Note for automatic device scan (left: TwinCAT 2; right: TwinCAT 3)
EL33xx-00x0 Version: 4.2
115
Commissioning
Ethernet ports with installed TwinCAT real-time driver are shown as “RT Ethernet” devices. An EtherCAT frame is sent to these ports for testing purposes. If the scan agent detects from the response that an
EtherCAT slave is connected, the port is immediately shown as an “EtherCAT Device” .
Fig. 123: Detected Ethernet devices
Via respective checkboxes devices can be selected (as illustrated in Fig. “ Detected Ethernet devices ” e.g.
Device 3 and Device 4 were chosen). After confirmation with “OK” a device scan is suggested for all selected devices, see Fig.: “ Scan query after automatic creation of an EtherCAT device” .
Selecting the Ethernet port
Ethernet ports can only be selected for EtherCAT devices for which the TwinCAT real-time driver is installed. This has to be done separately for each port. Please refer to the respective
Detecting/Scanning the EtherCAT devices
Online scan functionality
During a scan the master queries the identity information of the EtherCAT slaves from the slave
EEPROM. The name and revision are used for determining the type. The respective devices are located in the stored ESI data and integrated in the configuration tree in the default state defined there.
Fig. 124: Example default state
NOTE
Slave scanning in practice in series machine production
The scanning function should be used with care. It is a practical and fast tool for creating an initial configuration as a basis for commissioning. In series machine production or reproduction of the plant, however, the function should no longer be used for the creation of the configuration, but if necessary for
version of the delivered products for product maintenance reasons, a configuration can be created by such a scan which (with an identical machine construction) is identical according to the device list; however, the respective device revision may differ from the initial configuration.
Example:
Company A builds the prototype of a machine B, which is to be produced in series later on. To do this the prototype is built, a scan of the IO devices is performed in TwinCAT and the initial configuration ‘B.tsm’ is created. The EL2521-0025 EtherCAT terminal with the revision 1018 is located somewhere. It is thus built into the TwinCAT configuration in this way:
116 Version: 4.2
EL33xx-00x0
Commissioning
Fig. 125: Installing EthetCAT terminal with revision -1018
Likewise, during the prototype test phase, the functions and properties of this terminal are tested by the programmers/commissioning engineers and used if necessary, i.e. addressed from the PLC ‘B.pro’ or the
NC. (the same applies correspondingly to the TwinCAT 3 solution files).
The prototype development is now completed and series production of machine B starts, for which Beckhoff continues to supply the EL2521-0025-0018. If the commissioning engineers of the series machine production department always carry out a scan, a B configuration with the identical contents results again for each machine. Likewise, A might create spare parts stores worldwide for the coming series-produced machines with EL2521-0025-1018 terminals.
After some time Beckhoff extends the EL2521-0025 by a new feature C. Therefore the FW is changed, outwardly recognizable by a higher FW version and a new revision -1019 . Nevertheless the new device naturally supports functions and interfaces of the predecessor version(s); an adaptation of ‘B.tsm’ or even
‘B.pro’ is therefore unnecessary. The series-produced machines can continue to be built with ‘B.tsm’ and
to check the built machine.
However, if the series machine production department now doesn’t use ‘B.tsm’, but instead carries out a scan to create the productive configuration, the revision -1019 is automatically detected and built into the configuration:
Fig. 126: Detection of EtherCAT terminal with revision -1019
This is usually not noticed by the commissioning engineers. TwinCAT cannot signal anything either, since virtually a new configuration is created. According to the compatibility rule, however, this means that no
EL2521-00251018 should be built into this machine as a spare part (even if this nevertheless works in the vast majority of cases).
In addition, it could be the case that, due to the development accompanying production in company A, the new feature C of the EL2521-0025-1019 (for example, an improved analog filter or an additional process data for the diagnosis) is discovered and used without in-house consultation. The previous stock of spare part devices are then no longer to be used for the new configuration ‘B2.tsm’ created in this way.Þ if series machine production is established, the scan should only be performed for informative purposes for comparison with a defined initial configuration. Changes are to be made with care!
If an EtherCAT device was created in the configuration (manually or through a scan), the I/O field can be scanned for devices/slaves.
Fig. 127: Scan query after automatic creation of an EtherCAT device (left: TwinCAT 2; right: TwinCAT 3)
EL33xx-00x0 Version: 4.2
117
Commissioning
Fig. 128: Manual triggering of a device scan on a specified EtherCAT device (left: TwinCAT 2; right:
TwinCAT 3)
In the System Manager (TwinCAT 2) or the User Interface (TwinCAT 3) the scan process can be monitored via the progress bar at the bottom in the status bar.
Fig. 129: Scan progressexemplary by TwinCAT 2
The configuration is established and can then be switched to online state (OPERATIONAL).
Fig. 130: Config/FreeRun query (left: TwinCAT 2; right: TwinCAT 3)
In Config/FreeRun mode the System Manager display alternates between blue and red, and the EtherCAT device continues to operate with the idling cycle time of 4 ms (default setting), even without active task (NC,
PLC).
Fig. 131: Displaying of “Free Run” and “Config Mode” toggling right below in the status bar
Fig. 132: TwinCAT can also be switched to this state by using a button (left: TwinCAT 2; right: TwinCAT 3)
The EtherCAT system should then be in a functional cyclic state, as shown in Fig. “Online display example” .
118 Version: 4.2
EL33xx-00x0
Commissioning
Fig. 133: 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 [ } 110] .
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. 134: Faulty identification
In the System Manager such devices may be set up as EK0000 or unknown devices. Operation is not possible or meaningful.
EL33xx-00x0 Version: 4.2
119
Commissioning
Scan over existing Configuration
NOTE
Change of the configuration after comparison
With this scan (TwinCAT 2.11 or 3.1) only the device properties vendor (manufacturer), device name and revision are compared at present! A ‘ChangeTo’ or ‘Copy’ should only be carried out with care, taking into consideration the Beckhoff IO compatibility rule (see above). The device configuration is then replaced by the revision found; this can affect the supported process data and functions.
If a scan is initiated for an existing configuration, the actual I/O environment may match the configuration exactly or it may differ. This enables the configuration to be compared.
Fig. 135: Identical configuration (left: TwinCAT 2; right: TwinCAT 3)
If differences are detected, they are shown in the correction dialog, so that the user can modify the configuration as required.
Fig. 136: Correction dialog
It is advisable to tick the “Extended Information” check box to reveal differences in the revision.
120 Version: 4.2
EL33xx-00x0
Commissioning
Colour green blue light blue red
Explanation
This EtherCAT slave matches the entry on the other side. Both type and revision match.
This EtherCAT slave is present on the other side, but in a different revision. This other revision can have other default values for the process data as well as other/additional functions.
If the found revision is higher than the configured revision, the slave may be used provided compatibility issues are taken into account.
If the found revision is lower than the configured revision, it is likely that the slave cannot be used. The found device may not support all functions that the master expects based on the higher revision number.
This EtherCAT slave is ignored (“Ignore” button)
• This EtherCAT slave is not present on the other side.
• It is present, but in a different revision, which also differs in its properties from the one specified.
The compatibility principle then also applies here: if the found revision is higher than the configured revision, use is possible provided compatibility issues are taken into account, since the successor devices should support the functions of the predecessor devices.
If the found revision is lower than the configured revision, it is likely that the slave cannot be used. The found device may not support all functions that the master expects based on the higher revision number.
Device selection based on revision, compatibility
The ESI description also defines the process image, the communication type between master and slave/device and the device functions, if applicable. The physical device (firmware, if available) has to support the communication queries/settings of the master. This is backward compatible, i.e.
newer devices (higher revision) should be supported if the EtherCAT master addresses them as an older revision. The following compatibility rule of thumb is to be assumed for Beckhoff EtherCAT
Terminals/ Boxes/ EJ-modules: device revision in the system >= device revision in the configuration
This also enables subsequent replacement of devices without changing the configuration (different specifications are possible for drives).
Example:
If an EL2521-00251018 is specified in the configuration, an EL2521-00251018 or higher (1019 , 1020 ) can be used in practice.
Fig. 137: Name/revision of the terminal
If current ESI descriptions are available in the TwinCAT system, the last revision offered in the selection dialog matches the Beckhoff state of production. It is recommended to use the last device revision when creating a new configuration, if current Beckhoff devices are used in the real application. Older revisions should only be used if older devices from stock are to be used in the application.
In this case the process image of the device is shown in the configuration tree and can be parameterised as follows: linking with the task, CoE/DC settings, plug-in definition, startup settings, ...
EL33xx-00x0 Version: 4.2
121
Commissioning
Fig. 138: Correction dialog with modifications
Once all modifications have been saved or accepted, click “OK” to transfer them to the real *.tsm
configuration.
Change to Compatible Type
TwinCAT offers a function “Change to Compatible Type…” for the exchange of a device whilst retaining the links in the task .
Fig. 139: Dialog “ Change to Compatible Type…” (left: TwinCAT 2; right: TwinCAT 3)
This function is preferably to be used on AX5000 devices.
Change to Alternative Type
The TwinCAT System Manager offers a function for the exchange of a device: Change to Alternative Type
Fig. 140: TwinCAT 2 Dialog Change to Alternative Type
122 Version: 4.2
EL33xx-00x0
advertisement
Related manuals
advertisement
Table of contents
- 7 1 Foreword
- 7 Product overview Analog Thermocouple Input Terminals
- 7 Notes on the documentation
- 9 Safety instructions
- 10 Documentation issue status
- 12 Version identification of EtherCAT devices
- 16 2 Product overview
- 16 EL3311, EL3312, EL
- 16 Introduction
- 20 Technical data
- 21 Introduction
- 22 Technical data
- 23 Introduction
- 25 Technical data
- 26 Introduction
- 27 Technical data
- 28 Introduction
- 29 Technical data
- 30 TC technology basics
- 31 Use of EL33xx in the TwinCAT System Manager
- 32 Start
- 34 3 Basics communication
- 34 EtherCAT basics
- 34 EtherCAT cabling – wire-bound
- 35 General notes for setting the watchdog
- 37 EtherCAT State Machine
- 39 CoE Interface
- 44 Distributed Clock
- 45 4 Mounting and wiring
- 45 Safety instructions
- 45 Environmental conditions
- 45 Transport / storage
- 45 Control cabinet / terminal box
- 46 Instructions for ESD protection
- 46 Installation on mounting rails
- 49 Installation instructions for enhanced mechanical load capacity
- 50 Connection
- 50 Connection system
- 52 Wiring
- 53 Shielding
- 54 Positioning of passive Terminals
- 54 4.10 Installation positions 331x
- 56 4.11 Prescribed installation position EL3314-0002/ EL
- 58 4.12 LEDs
- 58 EL3311 - LEDs
- 59 EL3312 - LEDs
- 60 EL3314, EL3314-00xx - LEDs
- 63 EL3318 - LEDs
- 64 4.13 Terminal assignment
- 64 EL3311 - Connection
- 65 EL3312 - Connection
- 66 EL3314-00x0 - Connection
- 69 EL3318 - Connection
- 70 Connection instructions for earthed/potential-free thermocouples
- 71 4.14 UL notice
- 72 4.15 ATEX - Special conditions (standard temperature range)
- 73 4.16 ATEX - Special conditions (extended temperature range)
- 74 4.17 ATEX Documentation
- 75 5 Commissioning
- 75 TwinCAT Quick Start
- 77 TwinCAT
- 99 TwinCAT Development Environment
- 99 Installation of the TwinCAT real-time driver
- 105 Notes regarding ESI device description
- 109 TwinCAT ESI Updater
- 109 Distinction between Online and Offline
- 110 OFFLINE configuration creation
- 115 ONLINE configuration creation
- 123 EtherCAT subscriber configuration
- 133 General Notes - EtherCAT Slave Application
- 141 TwinSAFE SC
- 141 TwinSAFE SC - operating principle
- 141 TwinSAFE SC configuration
- 145 Process data
- 145 Sync Manager
- 146 Process data preselection (predefined PDOs)
- 148 Data processing
- 148 TwinSAFE SC process data EL
- 149 Settings
- 149 Presentation, index 0x80n
- 149 Siemens bits, index 0x80n
- 150 Underrange, Overrange
- 150 Notch filter (conversion times)
- 151 Limit 1 and Limit
- 151 Calibration
- 153 Producer Codeword
- 154 Operation with an external cold junction
- 155 Interference from equipment
- 155 Wire break detection
- 155 5.10 Object description and parameterization
- 156 Restore object
- 157 Configuration data
- 159 Profile-specific objects (0x6000-0xFFFF)
- 159 Configuration data (vendor-specific)
- 159 Input data
- 160 Output data
- 160 Information and diagnostic data
- 161 Standard objects (0x1000-0x1FFF)
- 166 5.11 Status word
- 170 5.12 Notices on analog specifications
- 170 Full scale value (FSV)
- 170 Measuring error/ measurement deviation
- 171 Temperature coefficient tK [ppm/K]
- 172 Single-ended/differential typification
- 177 Common-mode voltage and reference ground (based on differential inputs)
- 177 Dielectric strength
- 178 Temporal aspects of analog/digital conversion
- 182 6 Appendix
- 182 Sample program for individual temperature calculation in the PLC
- 185 EtherCAT AL Status Codes
- 185 Firmware Update EL/ES/EM/EPxxxx
- 186 Device description ESI file/XML
- 189 Firmware explanation
- 190 Updating controller firmware *.efw
- 191 FPGA firmware *.rbf
- 195 Simultaneous updating of several EtherCAT devices
- 196 Firmware compatibility
- 198 Restoring the delivery state
- 199 Support and Service