EC-Engineer V3.2: New Features
Integrated EtherCAT Network Simulation
As a perfect supplement to the EtherCAT network simulation software, EC-Simulator has now been integrated into EC-Engineer. Instead of connecting to a physical EtherCAT network using an Ethernet controller, the integrated EtherCAT master within EC-Engineer is connected to a virtual EtherCAT network of simulated slave devices. In order to achieve this setup, the standard Link Layer that interfaces to the physical network is replaced by a Link Layer that simulates the EtherCAT network. This new special EC-Simulator Link Layer DLL (emllSimulator.dll) loads the simulation core, the EC-Simulator DLL (EcSimulator.dll).
This enables the user to switch the master within EC-Engineer into “Diagnosis Mode” without the need for physical slaves devices present on the network. The built-in EtherCAT master will initialize all configured slaves and put them into operational state. This can be monitored in the project explorer view as well as in the other tabs within the program.
Also, EC-Engineer can now establish an online communication via the Remote Access Server (RAS) to the EC-Simulator core. This enables the possibility to inspect the simulated slaves. For example, you can check the state, monitor the master output variables, force the master input variables, and much more.
Select Simulator Link-Layer in EC-Engineer
Simulator Node is Created Upon Link Layer Selection
Online View with EC-Master and Simulator
The new version of EC-Engineer now supports the ability to execute scripts before scanning and switching to diagnosis mode and when switching back to configuration mode. This is useful for Remote Configuration and Remote Diagnosis to start/stop the EC-Master on the controller hardware. This automation is a great way to simplify the workflow and reduce manual steps. It is possible to manage up to eight scripts in a very flexible, user-friendly way, even with the possibility to add a delay between the scripts.
The following screenshot shows the tab within EC-Engineer to select the script.
Procedure 1 is used for scanning the network. There is the possibility of starting two scripts before the scan, and two scripts after the scan. It is also possible to set a delay between them. One use-case for this could be to start LxWin, then start the master on the real-time system and scan the network. Then stop the master and stop LxWin.
Procedure 2 is used for switching the modes (between configuration and diagnosis). A potential use case for this procedure would be to start LxWin, then start the master and switch to diagnosis mode. Upon switching back to configuration mode, the user could stop the master and also stop LxWin. Or it could be setup to not stop LxWin, for example.
The “Configuration” and “Configuration Mode” circles are the starting points. Then the scripts are called clockwise following the arrows and the red numbers.
NDIS Filter Module
The Network Driver Interface Specification (NDIS) is the specification for a network driver architecture that allows transport protocols like TCP/IP to communicate with an underlying physical network adapter. For sending and receiving EtherCAT frames in Windows, EC-Engineer makes use of the well-known Windows packet capture library, WinPcap. However, WinPcap was based on the NDIS 5.x driver model, and development has ceased. The latest versions of Windows 10 do not support this old NDIS 5.x version anymore, so now EC-Engineer V3.2 includes an installation package to install the acontis NDIS 6.x Filter Module (EcatNdis.sys). With this new Filter Module and the new NDIS Link Layer (emllNdis.dll), it is now possible for EC-Engineer to work without WinPcap on all Windows 10 versions.