- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Link copied. Please paste this link to share this article on your social media post.
Dear all,
For TSO is required to have Main 1 and Main 2 relay protection produced by different manufacturers or by the same manufacturer, but only if the relay protection have different algorithms. The plan is to offer MiCOM P443, P545, P645 (Px40 serie) for Main 1 relay protection and MiCOM P437, P633 (Px30 serie) for Main 2 relay protection. Do these relays have different algorithms for protection and if they have, is there any available docummentation to prove it?
Any help is welcomed.
- Labels:
-
Application cases
-
MiCOM range
Accepted Solutions

Posted: 2020-06-22 01:36 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Link copied. Please paste this link to share this article on your social media post.
Hi the community members can you help this member on this topic, please?
@HenriGRASSET or @Denis-Parnaland do you think you can advise on this topic?
Have a nice day,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Link copied. Please paste this link to share this article on your social media post.
protection application algorithms which are used in Easergy MiCOM P30 and P40 protection devices is different.
Both ranges are part of the High-End protection devices portfolio of Schneider Electric. Due to historical aspects of both ranges, different protection application algorithm was deployed.
Even both ranges are from modular type, they are using different I/O modules because of different hardware concepts.
Therefore, it is possible to use Easergy MiCOM P30 and P40 devices in system applications where Main A and Main B protection applications with different hardware and protection application algorithms are required.

Posted: 2020-06-22 01:36 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Link copied. Please paste this link to share this article on your social media post.
Hi the community members can you help this member on this topic, please?
@HenriGRASSET or @Denis-Parnaland do you think you can advise on this topic?
Have a nice day,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Link copied. Please paste this link to share this article on your social media post.
protection application algorithms which are used in Easergy MiCOM P30 and P40 protection devices is different.
Both ranges are part of the High-End protection devices portfolio of Schneider Electric. Due to historical aspects of both ranges, different protection application algorithm was deployed.
Even both ranges are from modular type, they are using different I/O modules because of different hardware concepts.
Therefore, it is possible to use Easergy MiCOM P30 and P40 devices in system applications where Main A and Main B protection applications with different hardware and protection application algorithms are required.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Link copied. Please paste this link to share this article on your social media post.
Please find attached a letter with confirmation statement about independency of Easergy MiCOM P30 and P40 ranges.
regards
Rudolf Simon
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Link copied. Please paste this link to share this article on your social media post.
Why this error is coming, How to resolve the issue

