Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: V5.4.1.0, V5.5.0.0, V5.6.0.0, V5.7.0.0
-
Fix Version/s: V5.6.0.10 (open), V5.7.0.3, V5.7.2.0
-
Labels:None
Description
When the Profinet IO Device stack is communicating in an SR-AR configuration with both SR AR established, the following sequence will not report an APDU status indication
- First SR-AR is Primary, second SR-AR is Backup
- The first SR-AR aborts and the second SR-AR takes over
- The second SR-AR is aborted as well
- The seond SR-AR is restablished
- The second SR-AR becomes primary
It is expected that the stack generated an APDU Status indication after (5).
Attachments
Issue Links
- is blocked by
-
PSPNDIF-348 In certain situations, the APDU status change is ignored and not reported to the application
-
- Closed
-
- relates to
-
PSPNSV4-1625 APDU status change not reported in all expected situations in SystemRedundancy scenarios
-
- Closed
-
- requested
-
PSPNSV5-772 Upgrade Profinet Device Interface to V1.7.0.2
-
- Closed
-