General information about PROFINET IO
Note
Refer to the general description for information about the following tabs of the device editor.
Only in the case of special features is there an additional help page for the specific device editor.
If the "<device name> Parameters" tab is not shown, then enable the Show generic device configuration editors option in the CODESYS options (Device editor category).
PROFINET IO is based on the working model of PROFIBUS DP, but it uses Ethernet TCP/IP for cyclic communication between the central PLC and the distributed field devices. It is appropriate for fast transmission of I/O data, as well as required data, IT functions, and parameters.
Even though the PROFIBUS master-slave method is replaced in principle by a provider-consumer model for PROFINET IO, the PROFINET IO real-time communication for cyclic transmission of user data requires a defined master-slave configuration. Therefore, there is a master (PROFINET IO controller), slaves (PROFINET IO devices), and I/O modules below the slaves.
Installing and adding PROFINET IO devices
In order for you to insert and configure PROFINET IO devices as objects in the device tree, you must first install the I/O controller, I/O devices, and I/O modules on the local system. If this does not happen automatically with the installation of the current development system, then you have to do it explicitly by means of the device repository dialog. The GSDML device description files that are supplied with the hardware are used as a basis for this.
You insert a PROFINET IO controller into the device tree below a device that has a PLC logic node. The device description file of the PROFINET IO controller defines which PROFINET IO devices you can insert below it. Similarly, the description of an I/O device defines which PROFINET IO modules you can inserts below the I/O devices. For I/O modules that have a fixed position, CODESYS automatically provides slots in the device tree. The Insert device command is used for inserting devices. Please note that it is also possible to deactivate a device temporarily for network operation.
CODESYS provides two different PROFINET IO controllers:
A variant especially for Hilscher CIFX cards (1)
A variant that runs on any Ethernet adapter (5).
The selection of Ethernet chip sets (such as EtherCAT) is restricted for Windows RTE runtime systems. This controller variant is inserted into the device tree below an Ethernet node.
|
|
|
|
|
CODESYS provides the capability of operating the CODESYS runtime system as a PROFINET IO slave. In this case, another PLC or controller is the PROFINET IO controller.
CODESYS provides two different PROFINET IO slaves
A variant especially for Hilscher CIFX cards (6)
A variant that runs on any Ethernet adapter (7).
The selection of Ethernet chip sets (such as EtherCAT) is restricted for Windows RTE runtime systems. This controller variant is inserted into the device tree below an Ethernet node.
|
|
|
|
|
See also
