Ask our Experts
Didn't find what you are looking for? Ask our experts!
Schneider Electric support forum about Protection Relays, Substation Controllers & RTUs, Arc Flash Devices & Systems in Medium Voltage and Low Voltage. A place to get support on product selection, installation, commissioning and troubleshooting.
Search in
Posted: 2025-10-09 04:10 AM . Last Modified: 2025-10-10 01:17 AM
Link copied. Please paste this link to share this article on your social media post.
Hi! I'm in need of some help with a problem that has been happening in while making the configuration on a T500.
For context, this is a system where we have IEC 61850 communication with GOOSE through some PowerLogic P5 and some PowerLogic P7, using edition 2.1.
Also in the system there is the need for the same P5 to send MMS to the T500 through 61850 Ed. 2, because T500 doesn't support 2.1.
While the EPAS-E and CET850 let me create the .scd and .cid files normally, when importing in Easergy Builder I'm hit with several errors like the ones attached.
Have someone gone through these?
Best Regards,
Juan Prieto
Link copied. Please paste this link to share this article on your social media post.
Hello @ArnoniP
Yes, those errors sound me familiar and even more now with edition 2.0 and edition 2.1 devices trying to interact.
Please share with me the entire config and the cid file used to be integrated in T500.
Link copied. Please paste this link to share this article on your social media post.
Hey @JuanRayo Thank you for your support!
Here they go!
I attached the .zip with the .ebc from T500 the .cid from the P5 and the .scd (ed 2.0)
I really appreciate the help!
Cordially.
Juan Prieto
Link copied. Please paste this link to share this article on your social media post.
Hello @ArnoniP
I am attaching a new config without any of those errors. Please take a look the database and correct all of the possible things affected.
Basically I removed the non-necessary Ln´s instances so I forced the system to stop mapping/adding the complete structure , bypassing in this way all of the non-supported cdc´s that still exist in the cid file. This topic is very common nowdays due to the current situation were the most of the data models are still under the edition 2.0 but with the indirect presence of ed2.1, adding common data classes that we do not support.
You’ve reached the end of your document
Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.