Performance
The cycle time achievable with an EtherNet/IP master depends on some basic environmental conditions, some of which can differ significantly depending on the specific project. The following notes provide some guidance on what needs to be taken into account during project engineering and how you can tell whether the required functionality can be performed by the device.
The following factors have to be considered:
- What device hardware is the software used on?
- How many slaves are connected to the master?
- How many connections do the slaves provide in total?
- How much data is exchanged via the connections?
- What RPI values must be set for the individual connections, and what task cycle time does this lead to?
- What task priority can be assigned to the EtherNet/IP task?
- How much of the device capacity is already being utilized by other tasks?
The specific answers to the questions above entail different performance limits. The following procedure is recommended for commissioning:
Assumptions
- A PFC200 (2nd generation) is used as the controller.
- The application allows use of a task cycle time >= 1 ms for the EtherNet/IP task.
Procedure
- Configure and parameterize your application according to the description in this manual.
- Write an application, create a Visu application etc.
- Set the cycle time of the EtherNet/IP task according to the requirements of your application. The value should not be less than 1 ms.
- Set the priority of the EtherNet/IP task to the value “6.”
- Download the application onto the device.
- Launch the application.
- Check whether your application is running. You can use the online functions of e!COCKPIT for this purpose.
- Change the Task Cycle Time parameter or the priority of the EtherNet/IP task.
- Test whether the application runs with the new settings.
(You can find status messages on the “Communication Status” Tab of the fieldbus configurator.)