Differences in Workflows and Functions
The following table gives an overview of the differences in the operation of CODESYS and e!COCKPIT and indicates where certain e!COCKPIT functions and settings can be found in CODESYS.
The biggest difference between the two tools is the user interface, especially the graphical representation of the network view that e!COCKPIT offers. For project engineering, devices can be dragged and dropped into the project in the form of graphical device tiles and connected to each other to form a network by drawing lines. Graphical aids (colored connectors) are also used to specify fieldbuses. Many functions can be accessed directly from the graphical network view through the context menu.
In contrast, in CODESYS, all operations are performed from the device tree. For example, here you can connect a network’s devices by entering the IP address, and fieldbuses are also added and configured through the device tree.
The fieldbus configurators are similar because many CODESYS functions and interfaces are used in e!COCKPIT. The basic use of various fieldbuses is described in Fieldbus Configuration in CODESYS. You can find more information on fieldbus configuration in CODESYS in the CODESYS online help at help.codesys.com (up to service pack 17) and helpme-codesys.com (current service pack).
e!COCKPIT | CODESYS |
---|---|
Licenses | |
You can activate the license for e!COCKPIT itself via the Backstage view, “Licensing” page, [License Management] > [Enter Licenses]. | Entering a CODESYS license is not required. CODESYS itself is available free of charge and license-free. |
Licenses for additional functions can be purchased, assigned to devices and synchronized on devices via the “Project Licensing” panel. | Licenses for WAGO libraries or additional functions can be displayed in CODESYS via the “WAGO Licensing” add-on and transferred with WAGOupload (see Installing the “WAGO Licensing” Add-on and Transferring Licenses with WAGOupload. |
Downloading Additional Components | |
Updates for e!COCKPIT, as well as add-ons and firmware, can be downloaded and installed via the Backstage view on the “Updates & Add-ons” page. | CODESYS updates appear on the software’s start page when available. |
Importing Devices | |
Device descriptions for WAGO devices are automatically integrated when e!COCKPIT is installed. | Required device descriptions are first downloaded through WAGO Download Center and integrated via the “Tools” tab > CODESYS Installer... (see Installing WAGO Components collectively via Package Files). |
Adding Devices in the Project | |
Devices can be added to the project by dragging and dropping them from the product catalog. | Devices are offered for selection in a dialog when a new project is created. For this to work, the corresponding device descriptions must already have been installed. |
I/O modules can be connected to the device by dragging and dropping them. | I/O modules can be added by right-clicking on “Kbus (Kbus)” in the device tree and Insert Device .... |
Selecting and Configuring a Fieldbus | |
The fieldbus is defined in a graphical network view by drawing connecting lines between fieldbus-specific connectors. | The fieldbus is added via Insert Device ... in the context menu of the device. Only the fieldbuses that the device supports are displayed in the dialog. |
Establishing a Connection between Devices | |
In e!COCKPIT, devices are connected by drawing connecting lines between them. | As a general rule, in CODESYS, a connection is established between devices by adding/nesting elements in the device tree and (depending on the fieldbus) by entering the slave IP address for the master device. Fieldbus Configuration in CODESYS describes how devices are integrated/connected depending on the fieldbus used. |
Mapping Data Points | |
For Modbus couplers, the I/O image is created automatically. | The I/O image/mapping of a Modbus coupler can be created manually with the help of the CODESYS manual (the Modbus configuration) and the product manuals (the structure of the I/O data). |
Replacing Devices | |
In e!COCKPIT, devices of a project of the same type can be replaced via the menu ribbon, “DEVICE” tab, or by right-clicking in the device’s context menu and clicking [Replace Device]. | In CODESYS, a device can be replaced by right-clicking in the device tree and selecting Update Device .... Functions that the new device does not support are eliminated; additional functions that the new device supports are added (see also “Adjusting Device Type Versions/Device Descriptions” in this table). |
Network Scan | |
The network scan for devices is performed in e!COCKPIT via the menu ribbon > “NETWORK” tab > [Scan]. Here you can also set the PC interface and IP range. | In CODESYS, scanning the entire network is not supported, but searching for an individual device is. To perform the scan, double-click on the device in the device tree > “Communication” tab > [Scan Network ...] |
Module Scan | |
You can perform a module scan in e!COCKPIT via the menu ribbon >“DEVICE” tab > [Scan Modules], or in a device’s context menu. | You can find I/O modules by right-clicking on “Kbus (Kbus)” in the device tree and selecting Scan for Devices. |
Compiler Version, Visualization Profile, Device Description and Firmware Compatibility | |
In e!COCKPIT, message windows appear in the event of incompatibility and provide recommendations for changes. A compatibility list is available for guidance: https://techdocs.wago.com/Software/eCOCKPIT/en-US/index.html#1889686667. | The following versions are compatible for devices using CODESYS Runtime: |
Adjusting Compiler Version/Visualization Profile | |
The compiler version/visualization profile can be adjusted in the Backstage view, “Project Settings” page > “CODESYS Project Settings” > “Project Settings.” | The compiler version and the visualization profile can be adjusted on the “Project” tab under Project Settings ... > Compiler Options or Visualization Profile. |
Adjusting Device Type Versions/Device Descriptions | |
Device type versions/device descriptions can be modified in the menu ribbon > “DEVICE” tab > “Version Information” tab group with the [Replace] button. | Device type versions/device descriptions are displayed for selection in the “Update Devices” dialog (right-click on the device > Update Devices ...). To display all available versions of a device, the “Show All Versions (Experts Only)” option must be enabled in the dialog. |
Updating Firmware | |
The firmware can be downloaded in the Backstage view > “Updates & Add-ons” page and installed via the menu ribbon > “DEVICE” tab > “Replace Firmware.” | The firmware is downloaded via the WAGO Download Center. However, replacing the firmware is done not with CODESYS, but rather with WAGOupload or via SD card (see Updating Firmware for Use in CODESYS). |
Compiling, Connecting and Launching an Application | |
You can compile an application via the “PROGRAM” tab > “Compile.” | You can compile the application via the “Build” tab > Generate Code. |
Debug Mode | |
After login, you can start the execution and verification of the source code via the menu ribbon > “PROGRAM”/“DEBUG” tab > [Simulate Application]. | After login, you can start execution and verification of source code via the “Debug” tab > Start. |
Creating a Visualization | |
You can create a visualization by right-clicking on an application and selecting the new “Visualization” element. | You can create a visualization by right-clicking on an application and choosing Add Object > Visualization. |
Program Download | |
A program can be downloaded via the menu ribbon > “PROGRAM” tab > “Program Download” or “Multiple Download,” for example. | A program can be downloaded via the “Online” tab > Source Download to Connected Device or Multiple Download. |
Adding Libraries | |
Libraries are added via the “Program Structure” panel by double-clicking “Library Manager” and [Add Library]. | Required libraries are first downloaded via the WAGO Download Center and installed via the “Tools” tab > CODESYS Installer ... (see Installing WAGO Components collectively via Package Files). |
Add-ons | |
License-based additional components (add-ons) appear on the “Updates & Add-ons” page of the Backstage view together with other components such as firmware, service packs, libraries and visualization styles. They can be downloaded, installed and licensed there. | License-based additional components (add-ons) can be downloaded via CODESYS Professional Developer Edition and installed via the “Tools” tab > CODESYS Installer ... (see Installing CODESYS Add-ons). Unlike e!COCKPIT, CODESYS bundles the add-ons together; they are not available individually. |
Configuring I/O Modules | |
WAGO I/O-CHECK is already integrated into e!COCKPIT for I/O module configuration. | The stand-alone WAGO I/O-CHECK software is used for I/O module configuration (see Installing and Using WAGO I/O-CHECK). |
Importing/Exporting Program Elements (PLCopen XML) | |
Program elements can be imported/exported in the Backstage view on the “Import/Export” page. | Program elements can be imported/exported on the “Project” tab > Import PLCopenXML .../Export PLCopenXML .... |
Documenting/Printing a Project | |
The “Document Project” function can be found in the Backstage view > “Print” page. | The “Document Project” function can be found on the “Project” tab. |
Version Management (SVN) | |
If the “e!COCKPIT SVN” add-on has been installed and licensed (Backstage view, “Updates & Add-ons” page), different versions of a project can be managed via the “SUBVERSION” tab. | CODESYS version management for projects is included in the CODESYS Professional Developer Edition (fee-based; see Installing and Launching). |
Python | |
e!COCKPIT can be operated via Python scripts in the Backstage view, “Scripting” page. | Python scripts can be executed from the Tools tab > Scripting. |