Functionality A PROFINET Controller opens a separate connection (AR = Application Relation) to each individual PROFINET Device for the purpose of data exchange, parameterization, and diagnosis. The de
Establishing a Connection The connection is established in several steps By means of a DCP identify request, the controller scans the network for a PROFINET Device with the defined station name. The c
PROFINET Diagnosis This chapter describes how the diagnosis mechanisms from PROFINET can be used in CODESYS . The detection and correction of system-related malfunctions (for example, caused by firewa
Diagnosis Database Every error that occurs in a PROFINET Device (for example, of type "broken cable" or "power surge") is stored in a local diagnosis database in the PROFINET Device. The error is also
Troubleshooting This section describes the troubleshooting of technical problems when using the CODESYS PROFINET drivers (Controller and Field Device). In particular, it covers problems that can occur
Alarms In the case of a change to the entries of the diagnosis database, the PROFINET Device sends an alarm to the PROFINET Controller. This immediately signals the coming or going of a malfunction. T
Runtime Configuration (CIFX) For the CIFX version, the corresponding runtime component must be specified in the PROFINET configuration file (*.cfg). In the configuration file, additional settings for
Validity of I/O Data For both incoming and outgoing data, PROFINET devices (Controller and Device) send a status byte in submodule granular form, which marks the I/O data as valid or invalid. From an
Configuring a PROFINET Device Linux The following configuration steps are necessary in Linux for a standard-compliant behavior (here as an example for Debian/Raspi) : In the CODESYS project, disable t
Runtime Configuration For communication with the PROFINET RT protocol, the PROFINET IEC stacks use a special runtime interface (SysEthernet) that allows the transmission of RAW Ethernet frames. This r
