User Tools

Site Tools


doc:appunti:hardware:ups_apc

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
doc:appunti:hardware:ups_apc [2022/11/02 17:39] – [APC Back-UPS CS 500] niccolodoc:appunti:hardware:ups_apc [2026/09/04 14:53] (current) – [APC Back-UPS CS 500] niccolo
Line 227: Line 227:
 The two most important functions are the **#10 battery calibration** and the **#12 self-test interval**. Battery calibration must be initiated with a fully charged battery and the normal load (it should be above 10%); it will end when battery drops below about 25%. The two most important functions are the **#10 battery calibration** and the **#12 self-test interval**. Battery calibration must be initiated with a fully charged battery and the normal load (it should be above 10%); it will end when battery drops below about 25%.
  
-Unfortunately it seems that the **Back-UPS CS 500** model does not support the configuration of the **periodic self-test**chosing option #12 results always in self-test interval **//None//**. However I asked the APC support about the self-test on model CS 500: a technician answered me in a few days, saying that that model **does a self test** on **power-on** and once **every two weeks**.+Unfortunately it seems that the **Back-UPS CS 500** model does not support the configuration of the **periodic self-test**chosing option #12 results always in self-test interval **//None//**. I asked the APC support about the self-test on model CS 500: a technician answered me in a few days, saying that that model does a self test on power-on and once every two weeks, but **only if it is operated by the PowerChute sofware**, which is non-free and proprietary software and it does not run on GNU/Linux. One alternative could be to create a cronjob script which stops the **apcupsd** service, run the **apctest** utility calling option #2 **Perform self-test** and then restart the apcupsd service.
  
 ^ New battery date (MM/DD/YYYY)  | ^ New battery date (MM/DD/YYYY)  |
 | 04/10/2022  | | 04/10/2022  |
 +
 +====== APC BX2200MI =======
 +
 +Questo UPS monitorato con **apcupsd 3.14.14** di **Debian 12 Bookworm** genera continui falsi allarmi **Batteries have failed**. Sembra che sia un problema di messaggi **LOWBATT** e **REPLACEBATT** spuri generati sul bus USB. Purtroppo il software apcupsd non viene aggiornato da molto tempo e la comunità sembra che sia orientata a passare al software **[[https://packages.debian.org/search?suite=default&section=all&arch=any&searchon=names&keywords=nut|nut]]**, che ha riconosciuto il [[https://github.com/networkupstools/nut/issues/2347|problema]] e ha trovato la soluzione.
 +
 +
 +  * **[[https://www.reddit.com/r/unRAID/comments/1eq9dr3/i_keep_getting_false_alerts_on_ups_battery_can_i/|I keep getting false alerts on UPS battery, can I stop/filter them?]]**
 +  * **[[https://github.com/networkupstools/nut/issues/2347|APC Back-UPS BX1600MI spurious LOWBATT/REPLACEBATT events]]**
 +  * **[[https://github.com/networkupstools/nut/pull/2565|Address spurious LB+RB log flood on APC BXnnnnMI devices]]**
  
 ====== Voltaggio batterie ======= ====== Voltaggio batterie =======
doc/appunti/hardware/ups_apc.1667407140.txt.gz · Last modified: by niccolo