similar to: feature request -- talk to the router, not the UPS

That kind of scheme should be handled by scripting - not by NUT. As far as having a _perfectly good UPS with no driver_, ANY UPS can be converted into a "dumb" UPS with the addition of 2 relays. The first relay is a primary 110 (or 220v) AC coil and a set of NO contacts. When main power fails the contacts close. The second relay is a primary 12v DC coil and a variable resistor and a

Hi Ted, Thanks for the reply. I didn't realize that tapping into the serial port could be that simple. I might do that - for my application all I would need would be the first relay. I can simply set the timer in the FreeNAS GUI to wait a few minutes to see if the UPS comes back up before it does a system shut down, so I can be okay without the low battery signal. I respectfully disagree

On Jun 2, 2014, at 7:27 AM, elliot smith wrote: > For example I am using FreeNAS. Rather than supporting my unorthodox UPS > signaling scheme by installing it as a script in FreeNAS, (and me probably > messing something up in the process) this scheme could be supported > instead by NUT. Bear in mind that all of the NUT drivers have authors who are expected to be maintainers of that

I'm having a problem that I hope those with greater experience might have some ideas on. I live up in the mountains where the power is ill-conditioned. Transients which would cause a computer to reboot occur on a daily basis. Power failures are frequent and can last anywhere from five minutes to five days. I have all my computers on UPSs so the first two problems are solved. I have a

On 6/2/2014 6:28 AM, Charles Lepple wrote: > On Jun 2, 2014, at 7:27 AM, elliot smith wrote: > >> For example I am using FreeNAS. Rather than supporting my unorthodox UPS >> signaling scheme by installing it as a script in FreeNAS, (and me probably >> messing something up in the process) this scheme could be supported >> instead by NUT. > > Bear in mind that

OS: Debian Wheezy Nut: 2.6.4-2.3 Installation method: Synaptic Device: CDP B-UPR505 Traces, debugs, etc.: Not available or irrelevant Description: Where I currently live (Honduras), buying a UPS with monitoring capability means spending at least twice as much as a "plain-Jane" model - usually even more than that. Thus, since I can't afford the ones with monitoring, all I have are

Hi Billy, switching back this thread to -upsdev 2012/2/27 William R. Elliot <bill at wreassoc.com>: > I have been able to set the 'FSD' from the driver and it is picked up by > upsmon.? That gives me the functionality that I was asked to put in the > driver.? If that is against the rules then I'll make an adjustment when the > allowed method is defined.? :-) yup,

Hi, We have 2 UPS Chloride 80 NET 120 ( a black and white one ) in our datacenter. Could you please tell me if it is possible to use upsmon or other free solution with these two UPS for shuting down servers during electrical lost power before battery crash . Beet regards, Roger -------------- next part -------------- An HTML attachment was scrubbed... URL:

I think the time for me to get involved in NUT documentation has come again. Late last week I had to buy a UPS under time pressure. The Eaton unit that thus project gifted me with in 2006(?) died during a severe thunderstorm watch, so it was off to MicroCenter to get a replacement pronto. I wound up buying an APC BN700MC. It was what they had in the performance range I needed. The removable

I am using NUT 2.6.5 as part of FreeNAS 9.2.0. I am using an APC Smart-UPS 5000 RM DL4 with a AP9619 network management card. NUT properly detects when the UPS goes on battery and initiates a shutdown after the configured time. The problem I have is that I am using a 208V unit on a 240V circuit. That means the normal state for the UPS is "TRIM". NUT doesn't treat that as an on line

And now for something completely different... :-) And yes, it's off-topic to this particular forum as it's not about NUT development. <ducking> Is there anyone around here who knows his way inside the hardware of an APC Smart-UPS? The APC support division will not reveal _any_ details or service information, and the only descriptive documentation I've found on the Web is in

Regarding the follow-up, IIRC `open` walks a device list returned by libusb, checks each entry against the matcher, and tells libusb if it wants to claim the device described by a particular entry. I don't think it walks further entries after a successful match and claim? We can't use the matcher directly, because its fields can be a regex geberally (e.g. `vendor=A*` instead of `APC` or

Greetings NUT users, I am looking for a solution to monitor the power OUTSIDE my datacenter. (The on/blackout status of main building power). My small datacenter is covered by a UPS, an older Liebert 18Kva unit with no environmental or status monitoring outside of the LCD console and audible alarm. The Liebert UPS is backed by a 35KW diesel generator which usually kicks on within 10

Dear NUT developers, I am using NUT + bcmxcp + Powerware 9315. I would like to use NUT to shut down my systems if the air conditioning fails and the room get too hot. I want the same shutdown sequence as would be produced when the UPS goes on battery. The UPS has a terminal block at the front for up to six different 'building alarms'. I can connect a thermostat (35C) to the

Hi All, I have what is probably a 12 year old (or older) Compaq R3000 UPS plugged into a FreeBSD 8 system running NUT version 2.6.5 This UPS contains a total of 16 batteries in 2 banks of 8, each battery is 6 volts and the bank produces 50 volts. The UPS monitors battery voltage and the battery charger in the UPS works like this. For about 2 days it will apply a charge/float/topping

My personal experience with a number of UPSes that are monitored via USB cable is that communications errors such as the ones referenced in the issue you linked to below are a result of USB hardware incompatibilities between the USB chipset and the USB port on the motherboard.*? This is NOT specific to the NUT project as it affects both apcupsd and in fact, has been reported as an issue with

Got the: git clone git://github.com/networkupstools/nut.git To work. Had to all so do this: apt-get install autoconf apt-get install libtool Did put driver = usbhid-ups in the /etc/nut/ups.conf file like you said. Here is what I got for it all: root at odroid-u2:~/nut# ./autogen.sh Calling autoreconf... libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `.'. libtoolize: copying

Namely something like: ups.runtime - amount of seconds since powering up The reason is essentially "side effect" of this bug report: http://article.gmane.org/gmane.comp.monitoring.nut.user/7705 Where T denotes total time since ups' power up. On upses with AP9612TH it's used for dual temperature sensors (which top of apcsmart branch should gracefully support). Either way,

Hi, this does sound like a useful idea - although for the principle of least surprise and for variation in deployments, I'd rather have it as a (non-default state of a) configuration toggle that can be set via `upsmon.conf`: whether this particular client exits after processing FSD or not. The onus for the rest would be on general systems integration - e.g. ensure that init scripts `K*`ill the

On Jan 10, 2014, at 12:58 PM, Elliot Dierksen wrote: > I am using NUT 2.6.5 as part of FreeNAS 9.2.0. I am using an APC Smart-UPS > 5000 RM DL4 with a AP9619 network management card. NUT properly detects > when the UPS goes on battery and initiates a shutdown after the configured > time. The problem I have is that I am using a 208V unit on a 240V circuit. > That means the normal