similar to: Joining forces with the Network UPS Tools

Hi fellows, I'm really pleased to announce that a first stage of NUT and HAL [1] integration has been reached: NUT drivers (in fact, only newhidups, tripplite_usb and bcmxcp_usb for the moment) can feed HAL data. It's a "quick and dirty" hack, as a proof of concept, and there is still lots of things to be done, both on NUT and HAL sides. But it's a good base, and very

Dear NUT users and developers, Like the other years, before taking a small rest, here are some news related to NUT. * First, you should have seen the 2.0.5-pre1 release announcement. I don't think 2.0.5 is very far, but I realized that I've made an archive including the .svn directory (bad, bad me. I should know that release are made against exported svn, not checked out!) * Next,

Dear NUT users and developers, Like the other years, before taking a small rest, here are some news related to NUT. * First, you should have seen the 2.0.5-pre1 release announcement. I don't think 2.0.5 is very far, but I realized that I've made an archive including the .svn directory (bad, bad me. I should know that release are made against exported svn, not checked out!) * Next,

I've recently been working a bit on adding PDU (http://en.wikipedia.org/wiki/Power_distribution_unit) support in NUT. Some of you might have seen the Powerman thread, which also deals with adding more PDUs support: http://powerman.sourceforge.net/supported.html The result is that we now have support for 2 Eaton | Powerware ePDUs (Managed and Monitored iirc, check http://www.epdu.com). I plan

On Feb 11, 2008 5:30 PM, Marcio Gomes <mpg at microlink.com.br> wrote: > I change the if in [OFF] detect state to, in original way, if you send a > reset.watchdog, the UPS goes > to OFF state in clients, but it is not correct, because UPS is OL and > Shutdown are in progress, but > the power is not OFF First of all, thanks for the patch. But I have a few comments: Are you

Hi fellows, As the NUT-NG draft will take me more time than I currently have (I found myself too optimistic since I got a baby ;-), below is the beginning of an answer to the "Common Power Management with UPS support" problem... First, NUT is pure userspace code, for portability issue, and will remain. USB is through libusb, snmp through net-snmp and serial through standard read/write.

2009/1/22 Spiros Ioannou <sivann at gmail.com> > Cher Arnaud, > Hi Spiros, > I send you a demo that reads info from an Emerson Liebert > GXT2-10000T230 through the RS-232 port. This uses the "ESP-II (ESP 2) > Protocol". > Current supported data includes: measurements (voltage, temperature, > etc) , ID strings (serial number, etc), status flags (inverter on,

THE GOOD: NUT is able to communicate with my Powerware 5115A over USB using the bcmxcp_usb driver: ambient.temperature: 38 battery.charge: 99 battery.runtime: 9000 battery.voltage: 27.07 driver.name: bcmxcp_usb driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.version: 2.2.1 driver.version.internal: 0.13 input.frequency: 50.34 input.voltage: 235 output.current: 0.0

I have an FC5 system with a powerware 5110 usb ups. The system seems to find the UPS ------------------------------ [root@b1 src]# lsusb Bus 004 Device 001: ID 0000:0000 Bus 003 Device 002: ID 0592:0002 Powerware Corp. Bus 003 Device 001: ID 0000:0000 Bus 002 Device 001: ID 0000:0000 Bus 005 Device 001: ID 0000:0000 Bus 001 Device 001: ID 0000:0000 ------------------------------- [root@b1

Hello, I have bought Powerman Optima 500 Plus UPS. While this product might be unknown outside Russia, it is shipped with megatec software and obviously works with megatec driver in NUT. besides the following problems (I think they are caused by one reason): 1) megatac driver is able to load and detect UPS only on second or third run. On the first run it typically fails. Later if daemon is

fellows, You can now commit to the trunk everything that is scheduled for 2.4 For my part, the november month will be mostly dedicated to the following: - commit the USB "improved maintenance" code. I'm about to finish that one, which allows to extract USB info and generate the various USB related files (hotplug, udev and hal). so the end of that bothering era ^_^ - complete &

Hi Alexander, > I've UPS named PowerMan RealSmart 1000, it is not listed in > compatibility list. I found that it works with "fentonups" driver and > have ups.model "Unknown S163-1000". Ithink "1000" is from capacity - > I've seen in Internet someone have RealSmart 800 identified "S163-800". > Also PowerMan have

On Sun, Nov 16, 2008 at 11:08 AM, Arnaud Quette <aquette.dev at gmail.com> wrote: >>> The remainder, until the -pre stage, will be: >>> - the Powerman support (through the powerman driver) for more PDUs >>> - the possible RRD integration into upslog >> >> It would be nice to have native RRD support in upslog, but we may also >> want to point

Hi, I have the Eaton 5E850iUSBDIN UPS connected via USB to a Raspberry Pi 3B+. It seems that everything but the ondelay parameter works so far. when I test the setup with this command: upsmon -c fsd The NUT server makes the NUT clients shut down properly and the Raspberry Pi running the NUT server shuts down correctly too. The problem is that after UPS shuts down, it immediatelly brings the

Hi, I get a trouble using nut with PowerMan Back Pro N 1400 Plus ~# /lib/nut/megatec -DDDDD -a pman Network UPS Tools - Megatec protocol driver 1.6 (2.4.1) send_to_all: SETINFO driver.parameter.port "/dev/ttyS0" debug level is '5' DTR=1, RTS=0 Starting UPS detection process... Asking for UPS information [I]... I => OK [# PCSTAR-PRO V1.02-2411] I VALUES => [

2008/12/19 Arjen de Korte <adkorte-guest at alioth.debian.org>: > Author: adkorte-guest > Date: Fri Dec 19 09:34:11 2008 > New Revision: 1656 > > Log: > Some more header file changes > > Removed: > trunk/drivers/powerman-pdu.h the same can be applied to many driver's headers since this goes back to pre autoconf/automake full support. so I created quite a

Built for years every version using: ./configure --with-usb Configuration summary: ====================== build serial drivers: yes build USB drivers: yes build SNMP drivers: yes build neon based XML driver: yes build Powerman PDU client driver: no build IPMI driver: no enable SSL development code: yes enable libwrap (tcp-wrappers) support: yes build CGI programs: no enable HAL support: no

Rainer, Arjen I was wandering around the code, and found that few things are missing around the IVT code: - no manpage, - no entry in driver.list - no device{mfr,model,type} in the code. I was about to submit a patch to address the above (ready to commit), but wanted first to get an update on the status. looking at the last thread, it's a bit unclear... I'm also interested an upsc

Hi All I'm trying to get my Ultra UPS connected. It connects using a standard USB cable I have --with-drivers=hidups in the configure command and I have lsusb showing Bus 001 Device 002: ID 0d9f:0001 Powercom Co., Ltd Bus 001 Device 001: ID 0000:0000 I have /dev/usb/hiddev0 now matter what I try I keep getting upsdrvctl start Network UPS Tools - UPS driver controller 2.0.3 Can't

Hi, thanks for previous help. I have some question about Lustre RPC and the sequence of events that occur during large concurrent write() involving many processes and large data size per process. I understand there is a mechanism of flow control by credits, but I''m a little unclear on how it works in general after reading the "networking & io protocol" white paper. Is