Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: V1.2.0.0, V1.3.0.0, V1.4.0.0 , V1.5.0.0, V1.6.0.0
    • Fix Version/s: V1.4.0.7, V1.5.0.5, V1.6.0.1, V1.7.0.0
    • Component/s: None
    • Labels:
      None
    • Sprint:
      PI Sprint 2017 KW 50-51
    • Account:
      SPC Profinet Core (SPCPROFINET)

      Description

      When the alarm implementation receives a new alarm DATA while still waiting for the ACK of a former alarm transfer an unexpected alarm error is raised and the AR will be aborted. The sequence is as follows:

      1. Reception of Alarm Data Frame with new Alarm Data
      2. Transmission of Alarm Ack Frame for (1)
      3. Transmission of Alarm Data Frame with Alarm Data Acknowledge
      4. Not Reception of Alarm Ack Frame for (3) due to network errors, high network load etc.
      5. Reception of Alarm Data Frame with another new Alarm Data
      6. Alarm error is detected

      In current implementation, step (5) causes an error event in ALPMR statemachine because it is still waiting for the acknowledge of (3).

      It is expected that in such case no error is detected because according to specification step (5) also implicitly acknowledges (3).

        Attachments

          Expenses

            Activity

              Status Description

                People

                • Reporter:
                  AMesser Andreas Messer
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  0 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: