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
.1.BootloaderFilePath=$Firmware$\HilscherCIFX\Firmware\NETX100-BSL.bin ;Device.1.Channel.0
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
.ProtocolFilter=3 [SysSocket] Adapter.0.Name="eth0 [...] for the profinet device Adapter.0 [...] /network/interfaces auto eth0 iface eth0
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
. If both counters remain at 0
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