similar to: How to find out the output of "upsc" for each UPS model supported by NUT ?

On Jul 7, 2013, at 6:09 AM, Alf H?gemark wrote: > Do other NUT users miss knowing exactly how the upsc output will look for a UPS model ? > Does anyone have opinions on where we could record such information ? Should it be one page per model, or one page per driver with a section for each model ? It would be nice to collect this information somehow. At the moment, we only really have upsc

On 07/07/2013 10:03 PM, Charles Lepple wrote: > On Jul 7, 2013, at 6:09 AM, Alf H?gemark wrote: > >> Do other NUT users miss knowing exactly how the upsc output will look for a UPS model ? >> Does anyone have opinions on where we could record such information ? Should it be one page per model, or one page per driver with a section for each model ? > It would be nice to collect

On Sep 19, 2013, at 2:19 PM, Alf H?gemark wrote: > Just to let you know, I am looking at various wiki software, and aim to set up a wiki where we all can document the output from our different UPSes with different drivers, I think it will help people who are looking to buy UPS and want to use it with NUT. > I hope to have the wiki up during October, but cannot promise anything. Just

On Feb 15, 2014, at 12:54 PM, Arnaud Quette wrote: > 2014-02-13 6:55 GMT+01:00 Alf H?gemark <alf at i100.no>: >> Hi > > Hi Alf, > >> On >> http://nutwiki.kanonbra.com/wiki/Category:Eaton_Powerware_5110 > > cool thing! > But duplicating the NUT Device Dumps Library [1]. > The DDL can also serve both users and developers purposes, by providing

Hi On http://nutwiki.kanonbra.com/wiki/Category:Eaton_Powerware_5110 you can see what is reported. The unreleased part refers to v2.7.1, which is now released. Alf Greg Vickers <daehenoc at iinet.net.au>: >Hi all, > >I've hooked up an Eaton Powerware 5110 to Ubuntu 13.10 server, and >configured nut appropriately. The cgi scripts are working fine, but on

2014-02-13 6:55 GMT+01:00 Alf H?gemark <alf at i100.no>: > Hi > Hi Alf, > On > http://nutwiki.kanonbra.com/wiki/Category:Eaton_Powerware_5110 cool thing! But duplicating the NUT Device Dumps Library [1]. The DDL can also serve both users and developers purposes, by providing these dumps as .dev files (usable with dummy-ups). I'm looking for someone to help me completing

On 08/07/2013 02:02 PM, Bendtsen, Jon wrote: > On 07/08/2013, at 13.40, Jan Phillip Greimann <jg at softjury.de> wrote: > >> Hi there, >> >> OS: (L)ubuntu 12.04 precise LTS >> Nut: 2.6.3-1ubuntu1.1 >> Installation Method: Package (apt-get install nut) >> Hardware: HP R1500 G3 INT > > FYI: > I have a different UPS, a HP R3000 XR and I monitor

Hi I had to close pull request 33, due to misspelling of commit messages. Charles helped me to fix it, and I have made a new pull request. The new pull request is : https://github.com/networkupstools/nut/pull/35 Regards Alf

The driver will poll the UPS for what variables it supports when it starts, and then go into a polling loop. Look for a section defining the meter map, and you should see the result, as well as the raw data. You can get the comm spec for XCP from the nut site if you want to delve deeper. I'd give more specifics, but am out of town and only working from memory at the moment . . . - Tim On

On Feb 12, 2014, at 7:50 PM, Tim Dawson wrote: > Run the driver with -DDDDD and see what variables it picks up. I have noted that with the Prestige 9 in bcmxcp, some variables are not consistent within models, and had to do some gentle remapping to get things to work correctly. Tim, is this the issue you mentioned on 2014-02-02 with blocks 0x9 and 0x13? I'll reply to that email. > On

> On February 14, 2014 11:22:22 PM CST, Greg Vickers <daehenoc at iinet.net.au> wrote: >> I ran the new driver (see below) and with -DDDD it throws out tons of >> never ending information, what am I looking for? :) > On Feb 15, 2014, at 2:57 AM, Tim Dawson wrote: > The driver will poll the UPS for what variables it supports when it starts, and then go into a polling

Hi I have the following UPS : ups.mfr: Eaton ups.model: POWERWARE UPS 500i ups.power.nominal: 500 It is using the bcmxcp_usb driver. I started the driver with debug options, and noticed the following for the meter map : 0.475625 0027 0000 51 output.frequency 0.475634 0028 0004 51 input.frequency 0.475641 0033 0008 51 battery.voltage

On 13/02/14 12:16, Charles Lepple wrote: > On Feb 12, 2014, at 7:50 PM, Tim Dawson wrote: > >> Run the driver with -DDDDD and see what variables it picks up. I have noted that with the Prestige 9 in bcmxcp, some variables are not consistent within models, and had to do some gentle remapping to get things to work correctly. I ran the new driver (see below) and with -DDDD it throws out

[attachments trimmed] Begin forwarded message: > From: eric kreuwels > Subject: UPSC based Windows Client > Date: October 13, 2013 4:43:31 PM EDT > To: nut-upsdev at lists.alioth.debian.org > > > Dear developers > > Last month I wrote WinUPSC, a Windows task tray UPS monitor. WinUPSC re-uses the UPSC logic to poll the UPS. > This initial version was tested

On 08/08/2013, at 18.58, Alf H?gemark <alf at i100.no> wrote: > On 08/07/2013 02:02 PM, Bendtsen, Jon wrote: >> On 07/08/2013, at 13.40, Jan Phillip Greimann <jg at softjury.de> wrote: >> >>> Hi there, >>> >>> OS: (L)ubuntu 12.04 precise LTS >>> Nut: 2.6.3-1ubuntu1.1 >>> Installation Method: Package (apt-get install nut)

Hi One idea I&#39;ve had for some time, but unfortunately not had time to implement, is to add a general SNMP agent, which will work with all UPSes supported by nut. The idea is to have the SNMP agent use the "nut API" to fetch values from the UPS. So the SNMP agent will be similar to the "upsc" utility. Whenever the SNMP agent is queried for information, it will use the

[Please remember to copy the list.] On Oct 15, 2013, at 8:45 AM, eric kreuwels wrote: > Hi Charles > > Thanks for your answer. Good questions/suggestions. I copied both the WinUPSC and the installer project on my GDRIVE and shared it with you: > https://docs.google.com/file/d/0B0mSjYYj84-6ZGM4MWZfMnFxbUU/edit?usp=sharing > > Archiving WinUPSC in the NUT GitHub would be my

On Oct 15, 2013, at 3:40 PM, Eric Cobb wrote: > My name is Eric Cobb and I am a Product Specialist with Tripp Lite. We have tested your latest NUT distributions against our HID USB compatible UPS systems and would like to know what is needed and/or who is needed to contact in order to updated the listing of compatible Tripp Lite UPS systems in your HCL list? Hi Eric, From end users of NUT,

Hello, My name is Eric Cobb and I am a Product Specialist with Tripp Lite. We have tested your latest NUT distributions against our HID USB compatible UPS systems and would like to know what is needed and/or who is needed to contact in order to updated the listing of compatible Tripp Lite UPS systems in your HCL list? Best Regards, Eric K. Cobb Product Management Specialist [Tripp Lite] 1111

Gabor: note, these HCL reports go to the nut-upsdev list. Begin forwarded message: > From: Gabor Tjong A Hung > Subject: Re: Network UPS Tools - Compatibility List > Date: September 3, 2013 2:18:31 PM EDT > > Sorry, > I just noticed the "If your device isn?t listed" part: > > [HCL] Forza FX-1500LCD supported by blazer_usb > > > [root at freenas] ~#