Symmetra LX16000 XR Frame error E0

[avecchio]

I have a older 3P LX16000 with 1P 240v output - configured n+3 (4/5 power modules 4/4 Batteries) with an XR Frame SYAXR9B9I (9/9 Batteries) - 2 x SYMIM5 513 / 602 & AP9641 NMCv3 05 sy v2.5.0.3 aos v2.5.0.8 boot v1.5.1.1

We currently are experiencing a E0 error on our frame.

I have cold booted UPS, checked/re-seated Andersen plug and applied electrical contact grease, re-seated all modules.

Having no service manual, I did not check the fuses in the XR as was not sure on the live procedure or test points.

The NMC is currently reporting 152VDC as the Battery Bus Voltage.

Our other similar UPS in another location is showing a Bus Voltage of 139.2VDC

Is there a procedure to correctly diagnose a E0 fault

Attached is my Raw Battery data

[KarimEissa · Accepted solution]

Hello,

E0 mean cable fuse fault,The big battery cable has a blown fuse or the cable is not connected very well,

Possible conditions which would cause this error:

1. Fuses are faulty on XR Frame
2. One of the pins on the Anderson Connection is receded which causes an open connection between frames.
3. The anderson connector on the XR frame's power cord is not properly connected.
4. Problem at the VDC Bus of XR Frame and or Main Frame
5. Voltage is not being measured correctly by the MIM or one of the XR communication cards.

If you suspect that the DC cable is not connected but the customer is claiming that it is, a useful test is to disconnect all battery modules from the XR frame. If the display goes dark, it is not receiving DC power from the cable because it is not secured properly.

If the pins on power cable are good, the measured voltage readings are accurate, and the cable is fully seated, have the customer swap the batteries from the Main Frame into the XR frame and Vice Versa. If the problem persists replace XR communication card

beside MIM/RIM firmware installed are not the same, they should both had the same firmware revision, so we recommends to replace both IMs together so they should had the same latest firmware revision

Regards,

Karim

[avecchio · Accepted solution]

Ended up replacing both the intelligence modules and it fixed the issue.