similar to: Bestfortress driver, network serial patch for nut-2.0

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

Arnaud Quette wrote: > Anyhow, I would more see this as a merge of all these drivers, with > some autodetection or flag/param to switch the mfr/model and maybe > capabilities... Whatever the driver name is, a good thing would be the > name of the protocol or something generic enough, though powermust is > fine. Ok, I made some minor changes to powermust, to make it less

Carlos Rodrigues wrote: > Author: carlosefr-guest > Date: Sat Dec 29 20:17:01 2007 > New Revision: 1204 > > Log: > - drivers/megatec.c: detect OB status while OFF. You've changed a bit more than this line suggests. [...] > @@ -565,10 +575,16 @@ > dstate_setinfo("input.voltage.fault", "%.1f", query.fvolt); >

The tripplite driver was developed on a machine with a reliable serial connection, and inherited the assumption that the serial line connection would not drop, reorder, or fail character read and writes. This patch adds significantly improved failure mode handling and also does basic checks of data validity. There's also a few minor cleanups/beautification. I've tested this code on my

I have added preliminary support for the TrippLite protocol number 2001 into tripplite_usb.c. The attached file is supplied as a patch against today's SVN. This patch adds support for TrippLite SMART550USB and some Omni models. Tested are On Line, On Battery, Battery Good, and Battery Bad indication. Everything else seems to work, but this UPS is attached to a critical system, and I can

Citeren Arnaud Quette <aquette.dev at gmail.com>: > Author: keyson-guest > Date: Wed Feb 4 15:03:36 2009 > New Revision: 1765 > > Log: > - Added mocrodowell.c/h into drivers/. add man/microdowell.8. Adjusted > drivers/Makefile.am and man/makefile.am. Adjusted the code for 2.4.0 in the > microdowell.c. Besides the things already mentioned by others and the obvious

Hi Henning, you should get in touch with Carlos, who his developing a generic megatec driver (available from svn: http://eu1.networkupstools.org/source.html) Arnaud -- Linux / Unix Expert - MGE UPS SYSTEMS - R&D Dpt Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://people.debian.org/~aquette/ OpenSource Developer -

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

Hey All: I have a CyberPower OP1250 and I'm trying to mod the cpsups driver to work with it. I added the following lines to cpsups.c /* Added: Andrew Tubbiolo EXPERIMENTAL Aug 15, 2008 */ if(!strcmp(abbr, "#1250VA ")) { dstate_setinfo("ups.mfr", "%s", "CyberPower"); dstate_setinfo("ups.model",

Description: Replace many usleep and some sleep calls with nanosleep. usleep is stated in its manual page as removed by POSIX. Contrary to its predecessors, nanosleep semantics is well defined. The replacement, which is mostly in drivers, is untested. Supplements http://bugs.debian.org/633791. Last-Update: Sat, 13 Aug 2011 14:04:48 +0300 Index:

Hi! I've recently come into to the possesion of a couple of Belkin Omniguard 3200 UPS's. Given the horrible apache/java based software they come with, I decided to see if I cannot get them to work with NUT. To cut a long story short, they work out to be SEC -based, and extensively modifying the nut-1.4 driver code to come up with the attached two files. I've marked them

Hi there First a big thank you to all nut developers. I tried the 2.0.4 as well as the 2.0.5-pre1 versions with my CyberPower OP1000E connected to a serial to USB converter. All I got was the following: # /usr/local/ups/bin/upsdrvctl start Network UPS Tools - UPS driver controller 2.0.5-pre1 Network UPS Tools - CyberPower text protocol UPS driver .05 (2.0.5-pre1) Warning: This is an

sent two 0 byte packets to the driver, then it sent 'URB_FUNCTION_SYNC_REST_PIPE_AND_CLEAR_STALL' down the pipe which seems to come back up as well, and then the UPS turned off. I'll play around later with what happens in that regard, although it may be a bit tricky to figure out when the battery is low without having it plugged in ;-) Also, about nut-usbups.rules.in... The

sent two 0 byte packets to the driver, then it sent 'URB_FUNCTION_SYNC_REST_PIPE_AND_CLEAR_STALL' down the pipe which seems to come back up as well, and then the UPS turned off. I'll play around later with what happens in that regard, although it may be a bit tricky to figure out when the battery is low without having it plugged in ;-) Also, about nut-usbups.rules.in... The

sent two 0 byte packets to the driver, then it sent 'URB_FUNCTION_SYNC_REST_PIPE_AND_CLEAR_STALL' down the pipe which seems to come back up as well, and then the UPS turned off. I'll play around later with what happens in that regard, although it may be a bit tricky to figure out when the battery is low without having it plugged in ;-) Also, about nut-usbups.rules.in... The

Dear list anyone know wich is the limit of maxload into asterisk.conf ? Also the meaning is related to RAM ? or CPU ? Regards Andrea

Hi all I'm trying to limit the maximum concurrent calls on my Asterisk to try and mitigate another problem I posted about earlier. I've edited /etc/asterisk/asterisk.conf And uncommented this line, and put a value of 60 in there: maxcalls = 60 in an effort to limit my Asterisk to 60 simultaneous calls. I did a core reload in the CLI after doing that.

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

G'day y'all, Here's a tiny patch set for drivers/apcsmart.c and drivers/apcsmart.h. Adds APC SmartUPS 1250 ("8QD" case) + 940-0024C recognition to apcsmart. (Unpatched apcsmart.c v1.99.8 misidentifies the SmartUPS 1250 as a "dumb" UPS.) For NUT 2.0.5+. NUT 2.0.5: Patches apply successfully. Builds successfully. Works as expected under Ubuntu 7.04. NUT 2.2:

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