Issue when IEC61850 Client driver (zenon driver or Logic I/O driver) are configured to use redundant IP addresses or by reconnect - when IED does not set free RCBs; when after connection loss, on IED, the RptEna stay TRUE.
When previously the driver has enabled an statically configured RCB successfully then after switch to alternative IP or reconnect after connection loss, when the RCB has RptEna=true, then the driver does not sent GI for this RCB nor polls variables. Thus all variables for previously reported data attributes have INVALID status bit until new switch/reconnect.
Issue when IEC61850 Client driver (zenon driver or Logic I/O driver) are configured to use redundant IP addresses or by reconnect - when IED does not set free RCBs; when after connection loss, on IED, the RptEna stay TRUE.
When previously the driver has enabled an statically configured RCB successfully then after switch to alternative IP or reconnect after connection loss, when the RCB has RptEna=true, then the driver does not sent GI for this RCB nor polls variables. Thus all variables for previously reported data attributes have INVALID status bit until new switch/reconnect.
The driver now, also for previously reported variables, starts polling when by reconnect or IP switch the RCB cannot be re-enabled as it has RptEna=TRUE (or Resv ).
Typically such situation can happen because IED (an IEC61850 Server) hasn't detect connection loss.
Issue can also be reproduced when during connection break the Data Model on IED changes (no RCB anymore) or another client uses this break to enable this RCB.