similar to: variable writability

Gentlemen, I have determined that on my UPS (APC Back-UPS ES 650 FW:818.w1.D USB FW:w1), the variable UPS.PowerSummary.RemainingCapacityLimit is writeable. I am setting this variable to start shutdown a little earlier. Appended is an unconditional patch for apc-hid.h. If, as indicated by the original code, there are APC UPS devices that don't allow setting of this variable, it becomes

I think having this logic buried within libhid/libusb (libusb:libusb_open(), line 179 to 206) is ultimately a mistake, albeit one that I am probably responsible for. Would it make sense to confine libhid to low-level operations, and leave the decision of trying to reopen vs. retrying to open to the high-level driver, in this case usbhid-ups? I envision that the code in usbhid-ups:reconnect_ups()

Hi Here is a very minor patch for the bcmxcp.c driver, mainly fixing the function name used in debug statement, and at the same time fix indentation. Regards Alf Hogemark From 86c7940d0ea11b5b38a7f4518095ee2428d658c7 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Alf=20H=C3=B8gemark?= <alf at i100.no> Date: Mon, 1 Jul 2013 21:11:40 +0200 Subject: [PATCH] bcmxcp: Fix method name outputted in

Best fortress support was understandably dropped, but we still use them, and someone else may want the driver I ported to nut-2.0. We also often attach the serial cable from a UPS to a network terminal server, since servers these days don't come with very many serial ports. (They call them "legacy" ports.) I submitted a patch to support these for nut-1.x, and it was rejected

Hi, the diff inline below adds a new subdriver for snmp-ups to support Huawei UPS, based on an observed walk from a UPS5000-E with a few bits filled in from the MIBs (copy at http://junkpile.org/HUAWEI_UPS_MIB/). Sample output from upsc follows the diff. cheers, Stuart diff --git a/data/driver.list.in b/data/driver.list.in index a0e82fb..fac3d5a 100644 --- a/data/driver.list.in +++

mmh.. At the moment there are 3 distinct preprocess functions that operate on 2 different types: - info_rw_t - preprocess(); - item_t - preprocess(); - item_t - preprocess_answer(). For info_rw_t: range/enum values are preprocessed just to see if that specific value is to be used or not depending on the conditions the driver meets at runtime (e.g.: low voltage devices -> low voltage ranges).

Hi and thank you for your effort. You are very close to what I want to achieve, but I was already aware of the impossibility of querying direct from a command. I wanted the following (both would be covered by your changes): 1. preprocess an item_t in the direction: NUT->DEVICE in order to be able to support queries like ups.generated.yesterday

Gentlemen, Please note that what follows pre-dates the latest changes from Arnaud (just thought someone might want to look at these before I can test the latest!). When running newhidups with -D -D -D I saw messages that looked like errors, and it took me a while to understand that they were not really errors. I therefore added two new entries in apc-hid.h, and I modified a couple of diagnistic

Hi all! I'm wondering if there's anyone doing any hacking on the snmp-ups driver at the moment. I've started looking at implementing 3phase-support, and this uncovered some rather unpleasant stuff in the snmp-ups driver that I really need to fix in order to get things sane. Those of you that's allergic to SNMP might want to stop reading now, this is rather icky ;)

Hi, I've got a apc Smart-UPS DP 8000 XL and a 940-0024c cable., and when I launch upsdrvctl, I've got the following message : Network UPS Tools - UPS driver controller 2.0.2 Network UPS Tools (version 2.0.2) - APC Smart protocol driver Driver version 1.99.7, command table version 2.0 dstate_setflags: base variable (input.transfer.high) does not exist dstate_addenum: base

Hi, I am using the NUT Software 2.7.4 (Ubuntu Repository) on Ubuntu 18.04. Configuring a UPS with the snmp-ups driver and overriding the battery.runtime.low variable leads to following warnung/error: Sep 23 11:10:08 hostname snmp-ups[27115]: dstate_setflags: base variable (battery.runtime.low) is immutable Default for battery.runtime.low is 180 seconds. My idea is to increase the value to

Hi Arnaud, Hi Scott, Hi list, Here is a patch to support the Zinto D from ONLINE USV-Systeme AG. I already sent a version to Russell Kroll (2006-04-09), without no response and I cannot find support for Zinto in svn until now. I found a discussion on this list about the Xanto from ONLINE, but the Zinto seems to use different commands. The commands are quite similar to those for Opti-UPS, so I

Hi, I recently installed a new cyberpower 1200AVR ups using the newhidups driver I built from the subversion source. I am recieving the following error on start up dstate_setflags: base variable (ups.beeper.status) does not exist dstate_setaux: base variable (ups.beeper.status) does not exist Any ideas? Thanks,

Hi, I been using samba4 from git15 version of 4.0.0, when samba4 hit stable we made it a main ADDC. Around 4.0.6 or later, I stuck on a DNS problem (which results in stop responding to clients from time to time, channging to BIND didn't help when we tried some time ago. I would like to fix those problem with reinstalling DC, but first I would like to replicate it to other DC so AD trust wont

Here are a series of my recent changes to NUT. The first few in the set are primarily little fixes and improvements. In among those are a few for .gitignore files which of course you can ignore for SVN, and there's one for a commit to a generated file which of course should not be tracked in any VCS. Then there are a couple or three to do with generating the header files used by

I am having an issue running NUT and using an TrippLite OMNI900LCD. When I run ./upsdrvctl start I get : [player@V0002-S002 bin]$./upsdrvctl start Network UPS Tools - UPS driver controller 2.1.0 Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.1.0) Detected a UPS: Tripp Lite /TRIPP LITE UPS Using subdriver: TrippLite HID 0.1 (experimental) dstate_setflags: base variable

Hi David and Charles Le 3 mars 2017 2:35 PM, "Charles Lepple" <clepple at gmail.com> a ?crit : > On Mar 3, 2017, at 8:21 AM, Charles Lepple <clepple at gmail.com> wrote: > > > > On Mar 2, 2017, at 3:38 PM, David Baker <david at baker.im> wrote: > >> > >> I?ve read the documentation, and it would appear that this can be set > by the

On Saturday 05 Apr 2014 16:28:24 Charles Lepple wrote: > On Apr 5, 2014, at 10:39 AM, Charles Lepple wrote: > > On Apr 5, 2014, at 8:52 AM, Mick <michaelkintzios at gmail.com> wrote: > >>> The upsrw command was designed for changing variables that are > >>> typically stored in non-volatile memory on the UPS. Unfortunately, > >>> your UPS

Gentlemen, I just had time to start looking at the latest version of the development tree. I have built the apc-hid part of newhidups from the development tree and I am in the process of testing it with my "Back-UPS ES 650". As of right now I have incorporated the attached changes to apc-hid.c. I have been using the corresponding changes together with some changes from Arnaud with the

Charles Lepple wrote: > On 8/2/06, Didrik Pinte <dpinte@itae.be> wrote: > > Le mercredi 02 ao=FBt 2006 =E0 08:08 -0400, Charles Lepple a =E9crit : > > > On 8/2/06, Didrik Pinte <dpinte@itae.be> wrote: > > > > Can you start the driver like this: "/sw/bin/newhidups -u root -DDD" > > > and paste some of the output? > > > > Here