![powerchute business edition login default powerchute business edition login default](https://img.youtube.com/vi/GLjvcB7IRCk/hqdefault.jpg)
- POWERCHUTE BUSINESS EDITION LOGIN DEFAULT DRIVER
- POWERCHUTE BUSINESS EDITION LOGIN DEFAULT SOFTWARE
- POWERCHUTE BUSINESS EDITION LOGIN DEFAULT PC
- POWERCHUTE BUSINESS EDITION LOGIN DEFAULT WINDOWS 8
I may try to use NUT and this driver from a generic linux machine to see if I can get it working properly when I have more control over the NUT setup (FreeNAS doesn't give you free access to the config files and over-writes them if you set anything directly in the files). This appears to be a limitation of the usbhid-ups driver, and not specifically an issue with FreeNAS.
![powerchute business edition login default powerchute business edition login default](https://windows-cdn.softpedia.com/screenshots/APC-PowerChute-Business-Edition_9.png)
With NUT (using usbhid-ups driver), it sits with a message of "Waiting on AC", and ignores power-on delays and just turns everything on at once when AC is restored. With Powerchute, it sits with a message of "Outlet Group 2 on by USB in: 120s" and works correctly when AC is restored. Once AC power is restored, the 120s counts down to 0 and the outlet group turns on, and after their programmed delay the other outlet groups turn on as well. Only, this time, instead of sitting in sleep with "Waiting for AC" on the UPS front panel display and the LEDs sequencing, it sits there with "Outlet Group 2 on by USB in: 120s", but nothing happens.
POWERCHUTE BUSINESS EDITION LOGIN DEFAULT PC
it continues running for 60 seconds, then the PC initiated a shutdown and after the programmed delay, the UPS shut off as well.
![powerchute business edition login default powerchute business edition login default](https://assets.rappler.com/612F469A6EA84F6BAE882D2B94A4B421/img/3E9FF6D1EC2C460691992B60D9EB83A0/salcedo-park-20140910_3E9FF6D1EC2C460691992B60D9EB83A0.jpg)
POWERCHUTE BUSINESS EDITION LOGIN DEFAULT SOFTWARE
I have their software set to shutdown the computer (and UPS) 1 minute after power failure. From their software, i can see the power-on delays that I programmed at the front panel.
POWERCHUTE BUSINESS EDITION LOGIN DEFAULT WINDOWS 8
Ok - I connected the UPS to a windows 8 machine running Powerchute Business Edition agent/server/console level programs. Has anyone else encountered this type of issue? I think it may have something to do with the actual command that is being issued by the driver to shut the UPS down. This leads to servers booting before the NFS mounts are available, etc. When I reconnect the power, the UPS turns back on immediately (as expected, since the battery wasn't drained), but instead of going through the 10 minute sequence of powering on the outlet groups, all 3 groups just come on immediately. The FreeNAS gives the UPS the shutdown command on its way down, and the UPS powers everything off, and sits in what looks like a deep sleep mode. The key is have the system commit to the power down once initiated and slaves have been notified there is no turning back. FreeNAS didn't give the other servers time to shutdown - but I'm sure I can find the parameter governing this timing. All of the servers shut down (slaves and freenas master), although I wasn't happy with the sequence. Group 3 - comes on 8 minutes later powering other servers - after FreeNAS has had time to boot and NFS mounts are available.įor testing purposes, I have freenas set to initiate a powerdown when "UPS goes on battery" instead of low battery to avoid running things down just to test the procedure.Īfter setting everything up, I simulated a power failure by pulling the plug on the UPS. Group 2 - comes on 2 minutes later powering the FreeNAS server Group 1 - comes on immediately for networking gear Everything seems to be working great - I can query details from the master or slaves, and everyone gets konsole notifications of communication errors (forced when I change UPS config in GUI).Ī little background info - I have 3 outlet groups set up to do a sequenced power up. There are several machines communicating with the freenas in slave mode. The ups is configured using the "APC ups 2 Smart-UPS USB USB (usbhid-ups)" driver in master mode. I'm running FreeNAS-9.3-STABLE-201511040813 with a USB connection to an APC SmartUPS 3000.