Hi there. At the moment I'm trying to get my HP T1500 XR (Powerware 5125) UPS to work with NUT. NUT registers that the UPS is on battery/online, but I just cant get the program to shut down the computer I'm using the original cable (thus I didn't enter anything in the ups.conf file) If I remove the cable and run the daemon/program the computer will shutdown after x minutes defined in the config file (can't remember which one right now) I also put on a breakbox to see which pins goes active high/low or off when power has been removed from the UPS, and it seems like it's only 1 pin that goes off (not active low) when that happens, which means I cannot use the variables like OL = DCD etc.. I'm using FreeBSD 5.4 I'm using 2.0.2 so as far as I understand it, the BCMXCP driver should already be in that package. so bottom line.. I cannot make my computer to shutdown after x minutes defined in the config, even though the software registers the UPS is on battery. please help me out here, since I'm getting quite frustrated.. the powerware software for FreeBSD costs as much as the UPS itself, and I only need the shutdown ability. best regards Carsten Jensen
On 12/5/05, Carsten Jensen <tomse@tomse.dk> wrote:> Hi there. > At the moment I'm trying to get my HP T1500 XR (Powerware 5125) UPS to > work with NUT. > NUT registers that the UPS is on battery/online, but I just cant get the > program to shut down the computer > I'm using the original cable (thus I didn't enter anything in the > ups.conf file)Please send copies of your configuration files. -- - Charles Lepple
Hi Carsten, m?n 2005-12-05 klockan 22:59 +0100 skrev Carsten Jensen:> Hi there. > At the moment I'm trying to get my HP T1500 XR (Powerware 5125) UPS to > work with NUT. > NUT registers that the UPS is on battery/online, but I just cant get the > program to shut down the computer > I'm using the original cable (thus I didn't enter anything in the > ups.conf file) >Do you use the bcmxcp driver ?> I'm using 2.0.2 so as far as I understand it, the BCMXCP driver should > already be in that package. >Yes the bcmxcp driver is included in 2.0.2. But you should use the Testing or Development branch of the cvs. The driver have been updated to support different baud_rate and it also init the ups to run in requested mode only.> so bottom line.. I cannot make my computer to shutdown after x minutes > defined in the config, even though the software registers the UPS is on > battery.If you use the bcmxcp driver, then the value for shutdown_delay is not the time after it goes to battery. It works like this. The shutdown_delay is calculated to a maximum at the current load in the ups. If you set it to high in the config you get a warning that the time is to long to run after low_battery. So when it goes to battery it runs as long as the battery is not signaling low_batt. When it gives on_batt low_batt (OB LB) then the upsmon is signaling the system to shutdown. Then you have the time of shutdown_delay to take the system down. This is the same for all (i think) drivers. The thing is that you want it to run as long as possible on battery. The line power may return. But if the ups go to LB it need to shutdown. So give us some more info and as Charles say, the config files and we help you out. Kjell
(please keep the list CC'd... I'm no expert on Powerware devices, or the genericups driver.) On 12/9/05, Carsten Jensen <tomse@tomse.dk> wrote:> > > --------------------- > ups.conf > > [hpups] > driver = genericupsHave you tried the 'bcmxcp' driver? genericups only handles contact-closure feedback, and cannot provide detailed status information. Another thing to note: by default, NUT only notifies you when on battery (OB). The shutdown happens after the UPS signals a "low battery" condition (LB), which is usually some time after OB, when the battery has been mostly depleted. There are examples in the documentation which explain how to shut down after X minutes of "on battery" time, but there are race conditions associated with this method, and if the power comes back after the UPS has told the system to shut down, it may not be restarted properly (you should probably test this). -- - Charles Lepple