Symmetra PX40 powers on, has no errors restarts a few seconds after self test starts.

[EMcCartney]

Our company recently purchased a PX40 and an external transfer switch with transformer from an online retailer. We currently are having 2 issues.

Issue 1:

We are missing the cable that goes between the breaker monitoring plugs and J1 on the maintenance bypass interface. I was able to install the jumper on 5/6 instead of 13/14 to bypass the external breaker monitoring.

Issue 2:

No errors during normal operation.

When running the "UPS self test, the output turns off a few seconds after start. This required manual output reset.

When running "Runtime calibration" the unit seems to run fine for most of the test. When it got to 25% battery life, it cancelled the test.

I am not sure what the issue is as there are no other errors in the logs to tell me any information.

Please let me know of anything I can test or look at to diagnose the issue.

Thank you ,

EPM

[KarimEissa · Accepted solution]

Hello,

Regarding MBP J4 is used to connected with system I/O board 0W6128 signaling ,J1 is used for PDU switchgear Q1.Q2.Q3 signaling and control ,J3 is used to connect the LEDs H2 and H3 with PDU as shown in the attachment

A jumper wire must be installed in position 13 and 14

In PX1, the RTC discharges the batteries from 100% to 25%. At the end of the calibration you will not get any information about the result of the calibration, but the displayed runtime will be updated according to the result of that calibration

The only thing that the NMC knows about the run time calibration (RTC) is when it started and when it finished. When the RTC finishes the NMC doesn't know why it finished. It doesn't know if it finished because the batteries were in fact discharged down to 25% or it was prematurely aborted because any other reason.

According to that, the NMC should never report that the calibration has failed or aborted (unless it was manually aborted).

the RTC test places the UPS into battery operation. The test will only start if the battery capacity/fuel is 100%. The test runs until the capacity/fuel reaches 25%.

• An aborted calibration test can be caused by a mains failure during the test or if the low battery shutdown voltage is reached during the test period.
• Intelligence Modules running IM firmware version 20.0 and higher will adjust the displayed runtime based on the performance of the batteries during a calibration test.
• Resets of adjusted runtime values can be performed by serially logging on to the MIM and selecting the "Reset Calibration Factor" option.

The recalibration requirements are as follows:

1) a >10% load must be applied to the UPS while on-line for several seconds prior to the discharge;
2) the capacity must be 100% prior to the discharge;
3) during the discharge the load must be stable (within 5%); and
4) the UPS must discharge to less than 35% capacity before returning to line (a complete discharge obviously meets this requirement and it's the most accurate method). If these requirements are met, the run time multiplier will adjust if it needs to (in either direction, up or down).

The NMC only shows the status of calibrations commanded by the NMC itself.
1) If you command the calibration from the NMC, then it will always say "passed" (even if a battery failed or there was a utility disturbance)
2) If you command the calibration from the Power View, then the NMC will show the status of the last calibration commanded from the NMC. If you have never commanded a calibration from the NMC, it will say "Failed"



Low Runtime observed on the PowerView display:
• If extremely low runtime (well below specification related to the connected load/batteries) is observed on the display (e.g. 1 minute) it is an indication that the runtime has been adjusted by the MIM. This indicates the IM firmware is at least revision 20.00>.
• MIM version 20.0 and later include an improved estimated runtime algorithm, which includes a runtime correcting factor
• This default value of this new parameter is 100, and it is re-calculated every time a runtime calibration is performed, or every time the batteries are discharged from 100% to 25%.
• If the batteries are new or have recently been replaced then the runtime calibration factor needs to be reset. This is done by logging into the MIM
This will restore the runtime to the maximum value based on the number of batteries and the attached load. If it is suspected that the value was erroneously adjusted then the Calibration Factor needs to be reset and a new Runtime Calibration initiated.

updating MIM/RIM firmware or replacing it with the latest firmware 20.40 or higher beside NMC updates to the latest version is recommended beside reset the runtime factor after replacing all the old batteries that reached its life time span can help to improve the runtime

you can refer to the below FAQ regarding self test run procedures and verify the batteries before running these tests 

https://www.se.com/uk/en/faqs/FA329448/

Regards,

Karim