search for: shutdown_design

I'm running NUT 2.6.3 on Debian wheezy [ with a 3.3.0 i686 kernel ] I've installed NUT via Debian APT [ package nut version 2.6.3-1 ] I have a REDi Blazer 600VA (BLAZER600c) UPS and I want to detect power failures. I have tried the following drivers: * gamatronic: Can't talk to UPS on port /dev/ttyS1! * bestups: Unable to detect a Best/SOLA or Phoenix protocol UPS * blazer_ser: No

...he file attached. > logic since the 2nd is automatically guessed from the first using USB Vendor and Product ID ;-) can you please send in upsc, upscmd and upsrw output. and also report the shutdown testing as described here: http://www.networkupstools.org/docs/user-manual.chunked/ar01s06.html#Shutdown_design I'll then add this model to the HCL. cheers, Arnaud > thanks, > Sergey > > P.S. Have nice weekend > > > On Wed, Jul 13, 2011 at 6:20 PM, Arnaud Quette <aquette.dev at gmail.com>wrote: > >> >> 2011/7/13 Sergey Talchuk <tals1975 at gmail.com> &g...

Hi, are this UPS supported by any other driver than "richcomm_usb". The device works with richcomm_usb, but only signals online, offline etc. Not voltage, batterylevels etc. Bus 006 Device 009: ID 0925:1234 Lakeview Research Bus 006 Device 009: ID 0925:1234 Lakeview Research Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10

?Hello everybody, I've just noticed that POWERDOWNFLAG defaults to /etc/killpower in upsmon.conf. I believe that such files belong to the /run sub-tree. Not only because it's not a config. file; mainly because many embedded systems actually have most of the FS read-only and have only the /tmp, /var and /run writable... Is there any particular reason to keep the file in /etc? Thanks,

> Subject: [Nut-upsuser] CyberPower DX600E won't switch up after power > is back > Message-ID: <3c530815d1ea602efdfec0d67eb1e0b1 at secretfatty.net> > Content-Type: text/plain; charset=UTF-8; format=flowed > > Hello > I have an issue with an CyberPower DX600E, > it doesn't switch up when the power is back; after it has been > unloaded; > is it because

Hi Charles, thank you for your answer. This was indeed the core of the problem. I have amended the configuration files. It means now the communication works as required. Alas I now have another problem. Just for the record here is the configuration after the changes. The configuration is as follows. #nut.conf MODE=standalone #ups.conf [eaton] driver = usbhid-ups port = auto