Help
  • Explore Community
  • Get Started
  • Ask the Community
  • How-To & Best Practices
  • Contact Support
Notifications
Login / Register
Community
Community
Notifications
close
  • Forums
  • Knowledge Center
  • Events & Webinars
  • Ideas
  • Blogs
Help
Help
  • Explore Community
  • Get Started
  • Ask the Community
  • How-To & Best Practices
  • Contact Support
Login / Register
Sustainability
Sustainability

Ask Me About Webinar: Data Center Assets - Modeling, Cooling, and CFD Simulation
Join our 30-minute expert session on July 10, 2025 (9:00 AM & 5:00 PM CET), to explore Digital Twins, cooling simulations, and IT infrastructure modeling. Learn how to boost resiliency and plan power capacity effectively. Register now to secure your spot!

No sending MCL file

Protection & Control

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.

cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
  • Home
  • Schneider Electric Community
  • EcoStruxure Power & Grid
  • Protection & Control
  • No sending MCL file
Options
  • Mark Topic as New
  • Mark Topic as Read
  • Float this Topic for Current User
  • Bookmark
  • Subscribe
  • Mute
  • Printer Friendly Page
Invite a Co-worker
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
You have entered an invalid email address. Please re-enter the email address.
This co-worker has already been invited to the Exchange portal. Please invite another co-worker.
Please enter email address
Send Invite Cancel
Invitation Sent
Your invitation was sent.Thanks for sharing Exchange with your co-worker.
Send New Invite Close
Top Experts
User Count
Araceli_Monje
Lt. Commander Araceli_Monje Lt. Commander
26
HenriGRASSET
Captain HenriGRASSET Captain
15
Arun-kumar_PS
Lt. Commander Arun-kumar_PS Lt. Commander
14
View All

Invite a Colleague

Found this content useful? Share it with a Colleague!

Invite a Colleague Invite
Back to Protection & Control
Hoang_Phu
Ensign Hoang_Phu
Ensign

Posted: ‎2025-07-19 02:04 AM

0 Likes
2
56
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Link copied. Please paste this link to share this article on your social media post.

‎2025-07-19 02:04 AM

No sending MCL file

Hello guys, I can't send the MCL file. How can I send it or do I need to update the firmware of this relay?

This relay version 3.986332.0

Easergy studio version V9.3.9

ga1.jpg

Labels
  • Labels:
  • MiCOM range
Tags (1)
  • Tags:
  • english
Reply
  • All forum topics
  • Previous Topic
  • Next Topic
Replies 2
Michael_H
Lieutenant Michael_H Lieutenant
Lieutenant

Posted: ‎2025-07-22 11:32 PM

0 Likes
0
41
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Link copied. Please paste this link to share this article on your social media post.

‎2025-07-22 11:32 PM

Hello Hoang_Phu

 

The release of the MCL file must match the release of the firmware of the communication board. In Easergy Studio there are two ways to ensure that the correct releases are used:

  • To copy the IED model reference stated on the physical device when selecting the IED from the list of supported devices. Note that when updating the device firmware also the model reference stated on the device label must be updated. Double-check to use the correct firmware reference when selecting the IED.
  • To use the feature “Quick Connect” provided in Easergy Studio. Connect to the live device to read out its references for setting up the IED in the project database. This way is recommended to detect the present firmware release running in the IED.

For cases where the device firmware is updated, an existing communication configuration has to be updated as well. A facility to convert between different releases is provided by Easergy Studio.

 

Before uploading the MCL to the IED, the communication protocol must have been set up. The following parameters must be configured:

  • Config parameters / ‘IEC’ set to “With”
  • Config parameters / IEC / ‘General enable’ set to “Yes”
  • Config parameters / IEC / ‘IEC 61850 enable’ set to “Yes”
  • Config parameters / IEC / ‘IEC prot. variant’ set to “IEC 61850 ED1”

Particular note has to be taken to the protocol variant: After a cold restart the IED may initialize to support Edition 2. Then change this setting to “ED1”.

Configure the function group Config parameters / ‘GOOSE’ as applicable.

Now the device is ready to accept the MCL file.

 

Regards,

Michael

Reply
sesa164970_brid
Lieutenant JG sesa164970_brid Lieutenant JG
Lieutenant JG

Posted: ‎2025-07-29 04:47 AM . Last Modified: ‎2025-07-29 05:08 AM

0 Likes
0
11
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Link copied. Please paste this link to share this article on your social media post.

‎2025-07-29 04:47 AM

Hello Hoang_Phu,

 

Can you check please if the ICD template for P633-675 is the correct one (folder: 'C:\Users\All Users\Schneider Electric\MiCOM S1 Studio\DataModels\IED Configurator\Templates\P63x', file: 'PX633-675-257ED1.icd', size: 423411 bytes, dated 2023-11-30). If you have different file, with Data Model Manager tool (part of Easergy Studio) you may download the latest versions.

 

Then you may check if your device respond to ping. The default IP address for the bottom port EthC is 192.168.1.4, for the upper one EthA/B (if such port exists in your device) it is 192.168.0.4. These addresses are valid even for the device without IEC61850 configuration.

IP address presented in PC function group: [111.004] 'PC IP address' is not valid for ports on the Ethernet board, it is valid for the CPU board, it is not useful any more since few years ago this physical interface has been removed (although all circuits are still there).

It is also worth to trigger cold restart - if there is some problem with Ethernet board initialisation, this would help. Please be aware that cold restart removes all existing settings from the device so it should be configured again.

 

If response for PING is received and there is correct ICD template present on your PC, the only explanation would be Ethernet board failure. In such case please send this device to your service department.

 

Kind Regards,

Boguslaw

Reply
Preview Exit Preview

never-displayed

You must be signed in to add attachments

never-displayed

 
To The Top!

Forums

  • APC UPS Data Center Backup Solutions
  • EcoStruxure IT
  • EcoStruxure Geo SCADA Expert
  • Metering & Power Quality
  • Schneider Electric Wiser

Knowledge Center

Events & webinars

Ideas

Blogs

Get Started

  • Ask the Community
  • Community Guidelines
  • Community User Guide
  • How-To & Best Practice
  • Experts Leaderboard
  • Contact Support
Brand-Logo
Subscribing is a smart move!
You can subscribe to this board after you log in or create your free account.
Forum-Icon

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.

Register today for FREE

Register Now

Already have an account? Login

Terms & Conditions Privacy Notice Change your Cookie Settings © 2025 Schneider Electric

This is a heading

With achievable small steps, users progress and continually feel satisfaction in task accomplishment.

Usetiful Onboarding Checklist remembers the progress of every user, allowing them to take bite-sized journeys and continue where they left.

of