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

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

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

Module/Submodule Status The SubmoduleState is a status word that indicates for each individual submodule the presence of diagnosis entries or other malfunctions such as a corrupt configuration. In thi

Libraries: PROFINET Device ProfinetDeviceConfig CommFB ProfinetCommon :

Field Device – State Object: PROFINET Field Device The tab shows the diagnosis data of the device and the subordinate modules. For the device, additional status information about the driver is shown.

Command: Add  PROFINET  Diagnosis Resources Function : The command generates a text list with the diagnostic messages from the GSDML files. Call : Project menu → Add Object ; context menu in the Devic