IEC60870-104-5 Triggering of Spontaneous message on Point Quality changings

[sesa45892]

Hi Geo SCADA Expert Community,

Perhaps one of you has a solution to my problem.
I work using EcoStruxure Geo SCADA Expert 2019 June 2021 Update
I try to communicate with EcoStruxure Substation Operation (ESO) using IEC60870-104-5 protocol

I use DNP3 Slave driver from one hand to cummunicate with M580 PLC and IEC60870-104-5 server driver on the other to communicate with ESO.
I transfer a DNP3 Generic Binary Input Point to the IEC60870-104-5 server through a Filtered Bit Value Map. The exchange with ESO is mainly based on the spontaneous messages feature.
This is working fine. Each time the DNP3 BI change of value, a spontaneous message is sent to ESO.
My concern is that if the DNP3 BI becomes Invalid (because of a link failure with the PLC for example) no spontaneous message is sent by the IEC60870-104-5 server to ESO.

My Question: What is the way allow Geo SCADA to trig a spontaneous message reporting the Invalid flag each time the quality of the DNP3 BI changes.

All suggestions is welcomed.
Thanks

[BevanWeiss]

I'm unsure exactly how you have your connections configured.

I'm confused by the concept of the DNP3 _slave driver to an M580.

Or "IEC60870-104-5 server driver"

If you are using the DNP3 _slave driver (where GSE behaves like a DNP3 _slave device), then if the Quality of the mapped point indicates a non-Good state this should be reflected in the DNP3 point value exposed by the DNP3 _slave driver's 'device'.

If your source point doesn't provide a reliable Quality value that you'd use for this, then you may need to use an Internal Point, and use Logic to manipulate the CurrentQuality of the point to reflect the 'reality'.

[sesa45892]

Hi @BevanWeiss 

First, thanks to pay attention to my issue.

Let me be more precise.

EcoStruxure GeoScada Expert receives information from the M580 PLC using DNP3 protocol.

EcoStruxure Substation Operation (ESO) receives information from GeoScada Expert using IEC104 protocol.

The GeoSCADA driver is acting like a gateway. The received data from the M580 PLC is sent to ESO by using a Filtered Bit Value Map at the GeoScada Expert level.

Each time a bit changes of value in the M580 PLC, a DNP3 Unsolicited message is sent to GeoScada Expert by the M580 PLC and GeoScada Expert retransmits it to ESO through a IEC104 spontaneous message. This is working fine.

Now if the communication between GeoScada Expert and the M580 PLC is broken, the quality of the point changes to “no-good” at the GeoScada Expert level but no IEC104 spontaneous message is sent by GeoScada Expert to ESO.

Consequence: the data remains with a “good” quality bit at the ESO level. That is not consistent with the reality.

My question is how to configure the IEC104 driver of GeoScada Expert to have a sending of the quality bit when the quality bit changes at the GeoScada Expert Level.

Thanks.

[BevanWeiss]

Ok, that diagram helps.

So you are using the DNP3 driver (GeoSCADA Expert acts as the Master), which means you then get DNP3 points.

These are the items which are showing bad quality due to the comms issue.

Then you are using IEC60870 _Slave Driver (GeoSCADA Expert acts as the _Slave/Outstation), which is where the Filtered Value Maps come in.

Unfortunately I haven't used the IEC60870 _Slave Driver, and the Value Maps around this fashion.

It might be something that your local Tech Support could answer relatively easily.

If the Value Maps don't currently support this then you may need to raise a feature request (or use the Idea Forum here https://community.se.com/t5/EcoStruxure-Geo-SCADA-Expert/idb-p/geo-scada-expert-ideas) for this idea.

The typical way that I'd suggest solving this is to have an integrity poll (period explicit poll) performed from the ESO system.  This should then report the quality state of the point (which should match the referenced DNP3 point quality, i.e. 'bad').

If it doesn't, then you may want to look into the settings you have for the Filtered Value Map to make sure that you don't have it filtering out non-good quality data records.

[sesa45892]

Hi @BevanWeiss 

Again, thanks a lot having considered my requests.

Unfortunately, I’ve already explored your proposed solutions before to post.

1: An integrity poll on a regular basis seems not possible from the ESO side (I am not aware about ESO, but this was reported to me)

2: The setting of the Filtered Bit Value Map proposes only a generation of event on Value Change, Status Change, Report, End of Period, End of Period Reset, Override or Release but nothing on Quality Change.

I hoped for a hidden setting, somewhere …

I am going to follow your suggestion and consult the Idea forum.

Thanks.

[BevanWeiss]

If ESO can't perform an Integrity poll / period retrieval, then how would it detect if the Geo SCADA Expert server crashed (or was shut down)?

What was the result when you tested with the 'Reason for Logging' Event Change Detection and with the Reason Mask set to everything? (you would also need to assign a Class to it for events to be captured).