GOOSE subscriber is not able to distinguish if a publisher was never sending GOOSE or is sending without errors.

GOOSE subscriber is not able to distinguish if a publisher was never sending GOOSE or is sending without errors.

Summary

Diagnosis engineering issue in zenon Logic I/O driver 'IEC61850 Server with GOOSE': the initial value of GOOSE supervision variable (ControlObject variable = 0) is the same as value when there are no errors. Thus, if remote GOOSE Publisher was never launched before - so the GOOSE Subscriber never receives a GOOSE messages from it, the driver cannot show if remote Publisher is down or not.

Description

Diagnosis engineering issue in zenon Logic I/O driver 'IEC61850 Server with GOOSE': the initial value of GOOSE supervision variable (ControlObject variable = 0) is the same as value when there are no errors. Thus, if remote GOOSE Publisher was never launched before - so the GOOSE Subscriber never receives a GOOSE messages from it, the driver cannot show if remote Publisher is down or not.

Solution

Introduced handling for one more bit in ControlObject variables for GOOSE Supervision: now when bit 2 is set then it means that there was received at least one GOOSE message from remote Publisher. Initial value is still 0, and bits 0 and 1 are handled like before, so: value = 0 - Publisher is not present (yet) then:
  • Bit 0 = TRUE (error) - the period received in the “TimeAllowedToLive” item of the preveus GOOSE message is elapsed; e.g. connection loss;
  • Bit 1 = TRUE (error) - received GOOSE message has a wrong sequence number; e.g. publisher was restarted or Network switches are losing packages (traffic overflows);
  • Bit 2 = TRUE (OK) - the GOOSE Publisher is/was detected (Publisher is present in Network)
For example value 5 means that publisher is/was present but currently there is unexpected delay (probably connection loss).    

Issue Number: 35686
Fixed on Date: 3.12.2015
Versions: 7.20 0 BUILD 24884