Micom P243 61850 Communication issue and Database Locked question

[AsherHsu]

Hello everyone,

I am an engineer from a Schneider Electric distributor in Taiwan, providing protection relay configuration, testing, and maintenance services.

I have encountered a communication issue with the Easergy P243 relay in a PRP (Parallel Redundancy Protocol) network. During characteristic testing using Omicron injection, with SCADA simultaneously receiving data from the relay, the IEC 61850 functionality of the P243 fails. In some cases, even third-party software like IED Scout cannot connect, although the relay still responds to ping requests. However, the P241 relay in the same network does not exhibit this issue, which I find puzzling. Has anyone experienced a similar problem?

Additionally, when the IEC 61850 function fails, I attempted to re-upload the CID file via the RS232 port and operate the switch bank function from the panel. The relay then displayed a "Database Locked" status. The only way to resolve this was by rebooting the relay. Could you clarify the possible causes of the "Database Locked" condition?

Attached are the configuration files and a recorded video of the "Database Locked" issue for reference.

Thank you for your insights.

[Arun-kumar_PS]

Hello @AsherHsu 

I am Arun from the MiCOM P40 Level 3 support team. I do not have an immediate answer to the issues you are facing. It must be investigated with all relevant files and traces. 

I suggest you contact Schneider Electric technical support to investigate it.  Please use the below given link to contact the Taiwan support centre.

https://www.se.com/tw/zh/work/support/customer-care/contact-schneider-electric.jsp

[JuanRayo]

Could be many reasons for that behaviour, perhaps wireshark traces could help us to clarify.

One of the reasons could be a wrong use of the different instances of an indexed report. What I mean is every instance of a report should be used by only one client at a time so if you try to subscribe more than one to the same instance something bad happens.

I am just guessing, need more info like log files and wireshark traces of the entire pub/sub process.