Ask our Experts
Didn't find what you are looking for? Ask our experts!
Share Your Feedback – Help Us Improve Search on Community! Please take a few minutes to participate in our Search Feedback Survey. Your insights will help us deliver the results you need faster and more accurately. Click here to take the survey
Schneider, APC support forum to share knowledge about installation and configuration for Data Center and Business Power UPSs, Accessories, Software, Services.
Search in
Free
EnglishStrengthen your foundational knowledge in Data Centers for free, enroll in this path today and start your learning journey!
Link copied. Please paste this link to share this article on your social media post.
Posted: 2025-09-09 07:50 AM
Got a 100kW rated Galaxy VS that threw up an error:
The interface seemed to have locked up and required a press of the reset button the first time this happened. This came up a second time, but self-cleared after a few minutes. Is this potentially indicative of some larger issue with the NMC?
Firmware version 6.118.0.323
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: 2025-09-09 08:31 AM . Last Modified: 2025-09-09 08:32 AM
What do the NMC logs say and indicate?!? Do you see any cold starts of the NMC?!?
Verify everything related to the network cabling and infrastructure because it could also be related to the (Watch Dog) timer which can result in a self boot due to the fact it can’t communicate on the network.
In early NMC 1 firmware the watch dog would not self boot. But, remain locked up and frozen in a unknown state until it was reset / POPO.
If there are no self boots logged in the system than eject the card and clean the contacts and insert / eject five times.
Validate all pins are fine and not corroded, bent, scratched.
Follow up with using approved electrical safe canned air and flush out the internal NMC enclosure housing and reinstall the NMC.
If the problem goes away you win . . .
If the problem returns or begins to increase in frequency the next step is to format / erase the NMC to a factory default state.
If that solves the problem you win . . .
If the problem remains reflash the NMC in case the firmware has been corrupted.
If that solves the problem you win . . .
If not, the NMC 1 needs to be replaced assuming it’s still available as it’s long past EOL and supported!
If the NMC 1 is (embedded) you can complete all break fix’s in the list. If the none of the above resolve the problem you’re screwed and it’s time to replace the entire system.
Questions Ask . . . 👍
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.