Description

PROFINET (Process Field Network) is an open standard for realtime industrial Ethernet systems in automation technology. It is promoted by the user organization PI (PROFIBUS & PROFINET International as an umbrella group of the PROFIBUS user organization PNO) and is regarded as the successor of PROFIBUS. PROFINET uses UDP/IP and IEEE 802.3 (Standard Ethernet) for acyclic services and/or I/O communication

The fully integrated CODESYS PROFINET Device Solution provides a uniform configurator for different variants of underlying PROFINET Device communication stacks:

CODESYS PROFINET Device (IEC)

Protocol stack in the form of a CODESYS library (in IEC 61131-3 code), operates on standard network interface cards.

The Ethernet adapter is not used exclusively, it’s still available for all other applications using TCP/IP on this adapter (e.g. CODESYS Visualization, Web Browser).

CODESYS PROFINET Device Configurator

Configurator for settings of PROFINET Device
Sample GSDML file included in scope of delivery
Configuration of module’s in- and output-mapping
Status page with detailed view of currently pending diagnostics

Profinet-Stack (IEC)

CODESYS PROFINET Device Stack in principle can run on any standard Ethernet adapter hardware (see requirements and restrictions). This Ethernet adapter is still be used for other services like CODESYS Communication (with IDE), Web-Server, or other CODESYS Fieldbuses (except EtherCAT). The CODESYS Runtime and the operating system (e.g. firewall) have to be configured correctly. For details, see CODESYS Online Help / Fieldbus Support (https://help.codesys.com/)

Feature	CODESYS PROFINET Device (IEC)
PROFINET Specification	V2.46
Conformance Class	B
Max. IO-Data	1440 input and 1440 byte output
Max. acyclic data	16 KB
Platforms / OS (see restrictions)	Windows, Linux, VxWorks
CPU	32/64 Bit Little-/Big-Endian
Provider-/Consumer-Status	yes
Shared Device	no
Device Access AR	no
Dual Port	see below
MRP	Client, see Dual Port

CODESYS PROFINET Device (IEC) and Dual-Port Interface:

With standard Ethernet Adapter hardware only single port devices are possible, i.e. each PROFINET Device can handle just one port. (The system itself may have more than one Ethernet adapter, maybe running a PROFINET Controller on it).

A Dual-Port Device (e.g. for MRP support or a ‘daisy-chain’) may be implemented with special dual-port Ethernet chipsets, but this requires some runtime adaptions by the OEM.

Programming Interface (API for IEC application)

The PROFINET Device provides an API for Profinet related functions and utilities that can be used by the application at runtime.

Function	Description
Generic access on device- and module-configuration	Function Block ProfinetCommon.DeviceIterator and SubmoduleIterator Generic API for iterating Slave- or Module Configuration and Status
Add/Remove Diagnosis Entries	Function Block ProfinetCommon.UpdateDiagnosisEntry Update the device’s local Diagnosis Database, send diagnosis-alarm
Send Alarms	Function Block CommFB.SALARM
Acyclic Services	Function Block CommFB.PRVREC / RCVREC e.g. Receive Parameters from PROFINET Controller
Connection Establishment	Function Block ProfinetCommon.DeviceAR A Profinet Device application uses this function block for controlling all phases of the connection establishment.
Reconfigure	Function Block DED.Reconfigure Enable/Disable modules or the complete PROFINET stack
Programmatic Configuration	Alternatively to the usual configuration with a declaration via the device tree, the PROFINET Device can also be configured purely programmatic. The library ProfinetDeviceConfig provides a programming interface which does not require instances of device objects.