nut icon indicating copy to clipboard operation
nut copied to clipboard

"Fatal EEPROM fault!" on Eaton 5SC1500

Open Cold-Lemonade opened this issue 2 years ago • 5 comments

I have a brand new Eaton 5SC1500 and shortly after NUT server connects to it, the ups.alarm variable reads "Fatal EEPROM fault!" and the ups.status variable reads "ALARM OL CHRG". This seems to be the same issue that has been reported previously in #1444. The user there reports that the issue seemed to clear up on its own.

From context, I am running NUT v0.12.1 as an add-on to Home Assistant along with the NUT integration. My Home Assistant is: v2023.10.1, Supervisor v2023.10.0, Operating System v10.5, and Frontend v20231005.0 (all of which is current as of today 10/11/2023).

Any insight into how to resolve this alarm message? The UPS device itself is not showing any alarms on its LCD display.

Cold-Lemonade avatar Oct 11 '23 18:10 Cold-Lemonade

FYI, investigations in progress

arnaudquette-eaton avatar Oct 12 '23 08:10 arnaudquette-eaton

Thank you. In case it is useful, my 5SC1500's firmware is version 04.02.0001.

Cold-Lemonade avatar Oct 12 '23 10:10 Cold-Lemonade

Answer from my fellows working on the UPS HID Core:

Here is the description of this HID object EEPROM Configuration failure made that the configuration has been reset to default

This alarm is generally the consequence of a UPS FW upgrade, If the newer version of the UPS FW has a different EEPROM structure than the previous, this can trigger an EEPROM sanitization of the configuration.

FYI, IPP and other proprietary Eaton SW are not handling it. In all cases, this is just a warning and not an error.

I've no final decision still. Either disable or make it clear that it's a warning

arnaudquette-eaton avatar Oct 12 '23 11:10 arnaudquette-eaton

I have exactly the same error. I attached the brand new unit to a RPi and started monitoring it with NUT. It immediately showed the ALARM in ups.status and in ups.alarm it has "Fatal EEPROM fault!" I reported it to Eaton, and they sent me another unit. The new unit reports the same thing.

I ran ./usbhid-ups -a nutdev1 -DDDDD &> eaton_eprom_fault.txt and attached the results as a file eaton_eprom_fault.txt. Here is relevant parts from the file:

   5.922773     [D5] hid_lookup_usage: UPS -> 00840004
   5.922783     [D5] hid_lookup_usage: PowerSummary -> 00840024
   5.922802     [D5] hid_lookup_usage: PresentStatus -> 00840002
   5.922811     [D5] hid_lookup_usage: ConfigurationFailure -> ffff002d
   5.922818     [D4] string_to_path: depth = 4
   5.922829     [D3] Report[buf]: (5 bytes) => 03 01 00 00 00
   5.922837     [D5] PhyMax = 0, PhyMin = 0, LogMax = 255, LogMin = 0
   5.922845     [D5] Unit = 00000000, UnitExp = 0 
   5.922853     [D5] Exponent = 0
   5.922862     [D2] Path: UPS.PowerSummary.PresentStatus.ConfigurationFailure, Type: Feature, ReportID: 0x03, Offset: 0, Size: 8, Value: 1
   5.922870     [D5] hu_find_infoval: found Fatal EEPROM fault! (value: 1) 
...
   5.922773     [D5] hid_lookup_usage: UPS -> 00840004
   5.922783     [D5] hid_lookup_usage: PowerSummary -> 00840024
   5.922802     [D5] hid_lookup_usage: PresentStatus -> 00840002
   5.922811     [D5] hid_lookup_usage: ConfigurationFailure -> ffff002d
   5.922818     [D4] string_to_path: depth = 4
   5.922829     [D3] Report[buf]: (5 bytes) => 03 01 00 00 00
   5.922837     [D5] PhyMax = 0, PhyMin = 0, LogMax = 255, LogMin = 0
   5.922845     [D5] Unit = 00000000, UnitExp = 0 
   5.922853     [D5] Exponent = 0
   5.922862     [D2] Path: UPS.PowerSummary.PresentStatus.ConfigurationFailure, Type: Feature, ReportID: 0x03, Offset: 0, Size: 8, Value: 1
   5.922870     [D5] hu_find_infoval: found Fatal EEPROM fault! (value: 1) 

dacarson avatar Jan 15 '24 20:01 dacarson

Is there a way to clear this ALARM as right now it is causing issue with my UPS monitoring software.

dacarson avatar Jan 16 '24 23:01 dacarson