Troubleshooting

The different points indicate settings in the configuration of the PROFINET system which, if ignored, can lead to undesirable behavior; we also explain how to diagnose the behavior.

Device description file (GSDML) / DAP (DeviceAccessPoint)

• Is the GSDML available on the system?
• Do the versions of both systems match?
• It is recommended to use the same GSDML/DAP versions on both systems.
• Is the latest version used?
• Is the GSDML in the correct path?
• TwinCAT 2: TwinCAT2: C:\TwinCAT\Io\ProfiNet
• TwinCAT 3: C:\TwinCAT\3.1\Config\Io\Profinet
• Is the correct GSDML being used?
• Version
• It may be necessary to contact the vendor/manufacturer or search for the appropriate GSDML on the vendor's website.

Has the correct PROFINET adapter been created?

• Controller or device (master or slave)?
• 
• Example, wrong / correct

Task configuration

• Was a free running task created?
• Or was a special Sync Task used?
• Cycle time to base 2?
• 1 ms, 2 ms, 4 ms, 8 ms, ….
• 
• Further information in chapter Sync Task

TF6270 – TwinCAT System Message

If the following warning is displayed when activating the project using the TF6270...

“TwinCAT System Message: Source: TCOM Server;  Timestamp: 2/12/2021 9:05:40AM 809 ms  Message: Boot data not found (file: Profinet_Parameters_3010060)”

... this can be ignored, because data of the connection establishment are stored for the PROFINET communication. If no PN connection has been established, no file is created. This warning will automatically disappear as soon as a PROFINET communication has been established.

EtherCAT Terminals EL663x-00x0

• Was the correct terminal used?
• EL663x-0000 cannot be used as device
• EL6631-0010 cannot be used as controller

• EtherCAT diagnostics
• EtherCAT status = operational (OP)
• WcState = 0 (data valid)

BoxStates of the PROFINET devices

• Communication established?