PM8000 IEC61850 Time Sync

[jryang_SAM-A]

Hello everyone?

I have a question regarding the PM8000 IEC61850 communication.
I am reading PM8000 data from other SCADA through IEC61850 communication.

However, voltage, current, etc.. The time zone for reading data is formed strangely.

Currently, the meters are synchronizing time with the NTP Server.

The meter time is also correct and seems to be synchronizing normally.

However, when reading with IEC61850 communication data, a value other than NTP Server time is displayed. (Is the .t value wrong?)

Did you have any of the above symptoms? Is there a workaround?

[Tom_Stevenson]

The time looks fine in ION Setup then?  Clock settings are all OK?

[Charles_Murison]

Hello @jryang_SAM-A ,

To say the meter is "reading data from other SCADA through IEC61850 communication." is leavening out a lot of information. The PM8000 meters support poll response as well as report block. If using report block what are the triggers?

Something I have seen often is that report block is used where the only trigger is dead band threshold. In this case, the meter will only send new data once the meter sees the value cross the threshold. If the system is stable, this could take a long time. Note that the meter will only see measurements with new information with each report and that attribute "time" for each measurement is not sent (timestamp of the report is the new timestamp).

Regards,

Charles

[jryang_SAM-A]

Hi Tom
Time was also normal in ION Setup, and time was also normal in Meter screen. However, Timezone is set to +09:00.

And the final TimeSync was done with the NTP Server.

[jryang_SAM-A]

Hi Charles

Thank you for a detailed description.

I know that there is a .t value in the IEC61850 communication data.

I don't know if I understand the answer to you.

Meter data shown in the picture is being transmitted to a custom tag for convenience. Therefore, only the data the user wants is expressed.

Can you answer the question?

[Charles_Murison]

Hello @jryang_SAM-A ,

I am sorry I do not understand the question. How is the IEC 61850 communication setup? Poll response or Report block data set?

Can you read data using other IEC61850 clients like IEDscout or IEDExplorer?

Charles

[jryang_SAM-A]

Hi Charles

The answer is very late. Sorry.

It is read normally as an IEC Client file.

However, even in the SCADA system used by the user, data is read as shown in the picture above, but time is jumbled.
The tag that communicates with the meter in SCADA is M3.LD0.CUS1_GGIO6.AnIn1.mag. We produced and sent a separate Custom Tag.

Is it necessary to set the time separately in IEC61850?

[Charles_Murison · Accepted solution]

Hello @jryang_SAM-A ,

"It is read normally as an IEC Client file." In the IEC61850 protocol there are 2 different ways of getting data from the meter. The first is a one time request to the meter getting current state data also know as a poll. This is a request sent to the meter with specific tags desired. It requires the client software to send a request to the meter each time there is a desire for information. In this configuration the .t tag will update for each request.

The second option for communication with IEC61850 is with Report blocks. In this setup the client with subscribe to a report and provide the meter a list of triggers that will cause the meter to send a report when a trigger condition is met. For example, one of the triggers is when a measurement is outside a dead band threshold.

When a report is triggered, only measurements that match the trigger are sent. Inside the "report package", there is a timestamp. This timestamp applies to all measurements in the report. The .t tag does not update.

So there could be 2 things happening.
A) The measurement does not have any triggers so the measurement "timestamp" will only update after the next trigger
B) Customer is looking only at the .t tag and not capturing the timestamp in the report package.

Regards,

Charles

[jryang_SAM-A]

HI Charles

We were unable to visit the site due to the corona problem, but now we have visited and solved it.
In conclusion, it was confirmed as a SCADA problem.

Thank you.