Ask our Experts
Didn't find what you are looking for? Ask our experts!
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!
Join experts & peers to learn, share and engage about the key trends of electrical distribution around safety, availability, efficiency and connectivity, as well as power standards & regulations. From design to implementation and operation, let’s discuss how digital and software are transforming your business and your day-to-day work.
Search in
Link copied. Please paste this link to share this article on your social media post.
Posted: 2024-02-01 02:32 AM
Hi all,
I am in the process of secondary injection for a large number of MTZ2 breakers on a switchgear panel and have hit an issue that I have not seen before with the EPC.
I can communicate to an MTz2 no problem, I can rename the breaker which updates fine, but when I try to enter the Commissioning Date, entering the password, the EPC reports back that it is "Unable to write to the device". I repeatedly tried this, re-read the breaker, skipped over this Commissioning Date and the breaker goes on to be able to successfully pass the secondary injection perfectly.
But I do need to set the Commissioning Date (for alarms, etc.) I am using the latest version of EPC v2.30.0, but this is the first time I have used this version for secondary injection, perhaps there may be a bug in this version?
I'd appreciate any help as this is now preventing my progress...
Thanks in advance,
Brian
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2024-02-06 12:10 AM
Hello
That issue is not known with the V2.30
I advice you to contact your local Customer care center to share the issue and open a case to raise it to our technical team
Thanks for your understanding
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2024-02-06 12:10 AM
Hello
That issue is not known with the V2.30
I advice you to contact your local Customer care center to share the issue and open a case to raise it to our technical team
Thanks for your understanding
Link copied. Please paste this link to share this article on your social media post.
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.