Displaying 20 results from an estimated 4000 matches similar to: "svn commit r2041 - trunk/drivers"
2008 Apr 06
1
[nut-commits] svn commit r1417 - in trunk: . drivers
> - drivers/dstate-hal.[ch]: added sleep here, to limit the polling rate
> (previously, the driver would completely ignore the poll interval and
> would run upsdrv_updateinfo() without any delay in between)
>
> The changes to dstate-hal.[ch] should probably be backported to Testing
> ASAP, since ignoring the poll_interval is not a good idea (you'll be
> basically polling
2015 Mar 26
2
New snmp-ups subdriver for Huawei
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
+++
2008 Feb 20
3
Important regression in usbhid-ups (r1113)
while finishing some work on the HAL integration (I'm now mapping DBus
method with NUT commands, to allow at least the final UPS poweroff), I
was horrified to realize (and so late) the changes in
usbhid-ups->upsdrv_shutdown().
We've lost a lot there, but making a generic code, instead of keeping
the subdrivers delegation.
For example, the shutdown.return command (which is or should be
2012 Nov 20
2
[PATCH][RFC] OpenUPS driver
Hi all,
I attached a driver for MiniBox openUPS device (
http://www.mini-box.com/OpenUPS) and a dump of the hid usages.
I had the possibility to make a few adjustments to the device firmware for
HID usages, and although I haven't managed to produce a good structure
many issues from previous firmware were at least fixed and new information
added.
ATM the driver only shows pertaining
2008 Mar 21
1
[nut-commits] svn commit r1376 - in trunk: . server
Hi Arjen,
there is a small glitch with r1376:
upsd.c: In function ?mainloop":
upsd.c:857: warning: too few argument for the format
2008/3/18, Arjen de Korte <adkorte-guest at alioth.debian.org>:
> Author: adkorte-guest
> Date: Tue Mar 18 19:59:15 2008
> New Revision: 1376
> ...
> + if (ret == 0) {
> + upsdebugx(2, "%s: no data
2013 Jul 01
1
bcmxcp: Patch for cosmetic code changes
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
2007 Aug 11
1
apc-hid.c: watts_to_av_conversion
Peter,
Looking through the usbhid-ups subdrivers, I came across the following
function in apc-hid.c, presumably added by you about two years ago (if
not, my apologies):
41 /* returns statically allocated string - must not use it again before
42 done with result! */
43 static char *watts_to_av_conversion_fun(long value) {
44 static char buf[20];
45
46 snprintf(buf,
2005 Jul 12
0
Smart-UPS DP missing variable
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
2013 Jul 03
1
bcmxcp: Patch for using command map if present to control commands added by dstate_addcmd
Hi
Inspired by the changes by Prachi Gandhi to use the command map from the
UPS in the bcmxcp driver, I think the map should be used, if available,
to control
all commands the driver adds using "dstate_addcmd".
The following patch is an attempt at doing so. The patch is against the
bcmxcp branch.
Since my UPS also supports :
#define PW_UPS_ON (unsigned char)0x89 /* UPS on
2018 Feb 04
0
[PATCH 3/3] OpenUPS: fix current calculations
Monitoring the input and output currents reported through upsc for an
OpenUPS device suggests that it is an energy creation device - the
power out is greater than the power into the system once the battery
is fully charged.
Analysis and measurement reveals several issues:
1. "UPS.PowerStatus.Output.Current" is scaled for NUTs "output.current"
value, which should be the
2006 Dec 30
3
Newpoint 200897 UPS
I got sick & tired of constant power outages with no warning, so when I
saw various UPSes at the store, I decided to get one, and the one I got
was a model 200897 from Newpoint (a.k.a. Power Sentry). A couple of days
later the power went out and I decided to use the opportunity to hook up
the UPS. I added up the wattages of the equipment I would be connecting,
and found that the only way I
2008 Mar 11
0
[nut-commits] svn commit r1372 - in trunk: . data docs drivers
> Author: adkorte-guest
> Date: Mon Mar 10 10:08:08 2008
> New Revision: 1372
>
> Log:
> - allow subdrivers to override the 'shutdown.(return|stayoff)' commands
> that are 'composed' in the driver
> - add new 'load.(on|off).delay' commands to allow the above (will
> implicitly define 'load.(on|off)' command with a delay value of
2007 Aug 13
1
instcmd "beeper.off "
While working on the mge-hid subdriver, I wanted to add the
'beeper.mute' command. Unfortunately, the description I intended to use
was used already by the 'beeper.off' instcmd:
CMDDESC beeper.off "Temporarily mute the UPS beeper"
Now of course we could add another instcmd 'beeper.reallyoff', but
instead I would prefer to bite the buller and do the following:
2008 Mar 27
1
[nut-commits] svn commit r1207 - in trunk: . include
Hi Charles,
while finishing the Testing release, I faced an autoreconf issue on
Testing, linked to the below change (to its non application on Testing
in fact):
include/Makefile.am:9: shell unset LANG && svnversion -n $(top_srcdir:
non-POSIX variable name
include/Makefile.am:9: (probably a GNU make extension)
include/Makefile.am:10: shell if test "$(SVNREV: non-POSIX variable name
2010 Aug 28
0
[nut-commits] svn commit r2504 - in branches/AsciiDoc/docs: . website
FYI, I've fixed the below error in the log, directly on the server.
The "pre-revprop-change" hook is not in place, so "svn propedit / propset"
do not work.
2010/8/28 Arnaud Quette
> Author: aquette
> Date: Sat Aug 28 00:23:05 2010
> New Revision: 2504
> URL: http://trac.networkupstools.org/projects/nut/changeset/2504
>
> Log:
> Fix page titles for
2007 Aug 23
1
[nut-commits] svn commit r1073 - in trunk: . drivers
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()
2010 Oct 18
0
[Bug 662435] [NEW] megatec_usb driver stopped working after upgrade from 8.04 to 10.04
2010/10/18 Michael Eitelwein
> Hi Arnaud
>
Hi Michael,
> Yes, did test it without success.
>
can you please post the first 20 seconds running blazer_usb in debug mode,
ie:
$ sudo /lib/nut/blazer_usb -DDD -a cyberpower
aside from fixing the megatec situation, ensuring that you'll be able to run
the replacement is also to be considered ;-)
now, for the megatec issue, we need
2007 Oct 03
2
[nut-commits] svn commit r1136 - in trunk: . drivers
> Author: agordeev-guest
> Date: Wed Oct 3 00:09:21 2007
> New Revision: 1136
>
> Log:
> - drivers/megatec_usb.c: added ability to do subdriver-specific
> initialization, and moved some shared code to agiler init function
> since krauler doesn't need it.
[...]
I'm not very thrilled about this patch:
1) Down at the subdriver level, one shouldn't use
2007 Feb 08
3
Re: [nut-commits] svn commit r801 - in branches/megatec-usb: . drivers
Hi Alexander,
thanks for your good work on the megatec_usb driver. I have made a few
more (cosmetic) changes.
Is the driver now working stably for your device? In particular, do
the instant commands (and particularly "upsdrvctl -k") work properly?
In this case, we could hopefully mark the device as "supported" and
merge the driver to the main branch.
There is still the
2011 Feb 07
4
[PATCH/RFC v2 0/3] Updates to ACP smart driver
This is 2nd version of the earlier patch featuring a few new features
and fixes to the apcsmart driver, following the remarks in:
http://www.mail-archive.com/nut-upsdev at lists.alioth.debian.org/msg02294.html
Major changes from v1:
- handle battery.charge and battery.runtime checks at main.c level
- handle "immutable but writable" conflict gracefully at driver level
-