Sercos III Slave Status mapped to IO data is not always updated

Test Description:

Test scenario:

• Check, if Base / Sub network protocol stacks can exchange cyclic data and status information for a predetermined period of time;
• Check, if data volume, location and execution time defined in the configuration software are observed;
• Check, if safety values are applied for data in case of terminated cyclic communication and status information remains actual.

Bug Description from Tester:

Sercos III Slave Status mapped to IO data of the secondary protocol is not updated, when Ethernet network cable is disconnected from port X2.

Steps to reproduce:

1. Download S3SOMB firmware combination to NT151 device.
2. Configure X2 and X3 networks for communication with DTM default values.
3. Create simple mapping including S3S Status signals.
4. Ensure that Gateway COM flag is set and then disconnect port X2 network cable.
5. Check mapped Status signals state on the secondary network.

Expected result:

Mapped S3S Status signals are updated.

Actual result:

Mapped S3S Status signals are not updated.