Fixed as of: -
Behavior of the new version: No revision is planned.
Description of the behavior:
0x3103819A “Network Identification: Initialization with Safety Option Failed”
appears in the i950 logbook, even though the setting “No safety bus [0]” is selected in the safety parameter set under 0x2128:001 “Safety Bus.”
This message may occur if the higher-level controller continues to transmit safety process data to the i950. This applies, for example, to FSoE PDOs in EtherCAT or PROFIsafe data in PROFINET. The drive and safety functions are not necessarily affected by this. In this case, the log entry indicates an inconsistency between the i950’s safety parameter set and the safety configuration in the master.
Conditions under which this behavior occurs:
- i950 Extended Safety with onboard EtherCAT or "EtherCAT / PROFINET" fieldbus module
- In the safety parameter set, “No safety bus [0]” isselected in 0x2128 Sub001.
- The third-party master PLC sends safety PDOs
Affected products:
- i950 with Extended Safety
- In conjunction with:
- Onboard EtherCAT
- EtherCAT fieldbus module
- PROFINET fieldbus module
Short-term measures, recommendations, evaluation:
If the i950 Extended Safety is to be operated without FSoE or PROFIsafe:
- In the configuration of the higher-level controller, remove or deactivate the safety modules or safety process data configured for the i950.
- For EtherCAT, ensure that no FSoE PDOs are transmitted to the i950.
- For PROFINET, ensure that no PROFIsafe communication is configured or established for the i950.
- Load the modified configuration into the controller and reinitialize the i950 and the fieldbus communication.
Once the master no longer transmits any safety process data to the i950, the logbook entry will no longer appear.
[Automatic Translation]
