similar to: [nut-commits] svn commit r1534 - in trunk: . drivers scripts/subdriver

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 doesn't >>> seem to do that. >> >> Well, if it doesn't do that,

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

On Jun 3, 2014, at 1:28 AM, Mick wrote: > 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

On Wednesday 04 Jun 2014 03:07:27 Charles Lepple wrote: > On Jun 3, 2014, at 1:28 AM, Mick wrote: > > 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

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 +++

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 doesn't >> seem to do that. > > Well, if it doesn't do that, how come upsc reports the changed value? It is > only after I reboot the PC

W dniu 24.08.2018 o 13:10, Charles Lepple pisze: > Sorry, I didn't mean to imply that the master branch was necessarily going to be different, just wanted to make sure you had everything set up to recompile. The real test is to see if things change after commenting out that line (such as by changing it to start with "//"): > > // { "shutdown.return", 0, 0,

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

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

Gentlemen, I have now had a chance to run some initial tests of my changes to apc-hid.c of the current development tree. Running newhipups and inspecting the -DDDD output seems to indicate that with the fix below everything seems to work as expected. However, I have not yet shut my system in order to take the UPS out of action so that I can do my various tests with a lightbulb load. I still hope

Thanks Charles, On Saturday 05 Apr 2014 12:53:06 Charles Lepple wrote: > On Apr 5, 2014, at 7:18 AM, Mick wrote: > > $ upsrw -s "ups.delay.shutdown"="30" iDowell at localhost > > Username (suzy): admin > > Password: > > OK > > This command is sending the value to the UPS (via the usbhid-ups driver). > > > $ upsc iDowell at localhost

Hi Kirill, just to notify you that your al175 driver is being removed from the NUT tree, as of 2.4.0-pre1. if you wish to see it entering the tree again, please contact the Development mailing list to talk about it. Merry Christmas and happy New Year. Arnaud -- Linux / Unix Expert R&D - Eaton - http://www.eaton.com/mgeops Network UPS Tools (NUT) Project Leader -

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

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 ;)

This is the patch to include SVN revision level in version number displays. There should be two enclosures; the patch itself and a new source file. common/upsversion.c. upversion.c defines a single function. upsversion(), that returns a version string for display. Some Makefile trickery ensures that this file will be recompiled whenever the project's SVN revision level has changed since it

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 U-Talk protocol (page 34 of http://networkupstools.org/protocols/mge/9261zwfa.pdf) but I can?t seem to figure out how to send the device the

I could not make the bestfortress driver 0.02 work for my Best Fortress LI675VA, so I have made a patch for the driver. The reason was, that all responses are preceded and terminated by CR LF, but the driver would discard everything after the first CR LF. The following patch discards everything up to the first LF. It also adds a debugging feature of displaying the accepted data (level 5 i.e. -D

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

On Wed, 4 Jun 2014, Mick wrote: >> Some of the variables (those with HU_FLAG_ABSENT) are apparently not stored >> on the UPS itself-- they are sent to the UPS when the shutdown command is >> executed. Sending the value starts the timer, in some cases, but I think >> the ups.delay.start value should be safe to send at the time when it is >> set. > > I see. So if

Hi Arnaud & Charles, You?ll have to forgive my low level of Linux Understanding here?. I downloaded the source files, modified the appropriate driver file, re-compiled it (all of this was a lot of research and learning!) When I use the new driver I get ? Network UPS Tools - UPS driver controller 2.7.2 Network UPS Tools - MGE UPS SYSTEMS/U-Talk driver 0.93 (2.7.4.1) Can't chdir to