similar to: Re: [nut-commits] svn commit r430 - in branches/Testing: . docs drivers man

Hi, When running a driver with "-h" or without parameters, the upsdrv_cleanup function seems to be called (which caused the warning I mention in the ChangeLog). This doesn't seem right. Regards, On Sat, Jun 28, 2008 at 7:47 PM, Carlos Rodrigues <carlosefr-guest at alioth.debian.org> wrote: > Author: carlosefr-guest > Date: Sat Jun 28 18:47:17 2008 > New Revision:

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

Alexander Gordeev wrote: > Author: agordeev-guest > Date: Mon Aug 13 13:09:43 2007 > New Revision: 1049 > > Log: > drivers/megatec_usb.c: added credits to the banner message. Is this really needed/desirable? I think this kind of information needs to be put in the AUTHORS document. There are many more people on this list that put a lot of effort in NUT, without claiming credit

> 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

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

Hi all, Currently, the "megatec" driver only supports UPSes which have a serial (RS232) interface. However, I'm under the impression that most of the models that speak the megatec protocol, and have an USB interface, just have a standard serial-to-USB converter inside. This being the case, there should be a "/dev/ttyUSBx" device which the megatec driver could use just as

Hi all, Currently, the "megatec" driver only supports UPSes which have a serial (RS232) interface. However, I'm under the impression that most of the models that speak the megatec protocol, and have an USB interface, just have a standard serial-to-USB converter inside. This being the case, there should be a "/dev/ttyUSBx" device which the megatec driver could use just as

Does this require a new entry in scripts/hotplug/* and scripts/udev/*? -- Peter Alexander Gordeev wrote: > > Author: agordeev-guest > Date: Sat May 26 12:04:26 2007 > New Revision: 924 > > Log: > data/driver.list: added SVEN Power Smart RM 2000 to the list. > > Modified: > trunk/ChangeLog > trunk/data/driver.list > > Modified: trunk/ChangeLog >

> Author: aquette > Date: Thu Jun 21 07:43:46 2007 > New Revision: 971 > > Log: > fix communication lost status handling > > Modified: > trunk/ChangeLog > trunk/drivers/usbhid-ups.c > > Modified: trunk/ChangeLog > ============================================================================== > --- trunk/ChangeLog (original) > +++ trunk/ChangeLog

Hello Nut List! I have 2 "Lacerda 10KVA" UPS that returns strange values for Q1 and F commands: Q1 (215.0 215.0 219.0 004 60.0 2.27 39.0 00000001 F #220.0 045 240.0 60.0 At least what I know about Megatec, It seems to say that it has a 240.0 V battery with currently 2.27V. Quite strange. I contacted Lacerda to help me interpret this values and they said that 2.27 is just 1 element

Ok, so I'm trying to checkout the development branch with: svn checkout svn+ssh://carlosefr-guest@svn.debian.org/svn/nut/trunk But it keeps asking me for the password, which is weird for two reasons: 1. I submitted a public key to alioth, which I was using successfully to access the cvs repository; 2. It refuses my password. Anybody else having problems, or is it just me? --

I had some free time this weekend, and made some long overdue changes to "megatec". The thing is, these changes lead to a couple of questions that I must ask before I go on and "svn commit" them: 1) The blazer, fentonups, esupssmart, ippon, sms and mustek drivers are now completely covered and all of their functionality should now be present in megatec, and also every model

On Mon, Sep 14, 2009 at 4:49 PM, Arnaud Quette <aquette at alioth.debian.org> wrote: > Author: aquette > Date: Mon Sep 14 20:49:59 2009 > New Revision: 1986 > > Log: > draft index of manual pages > > Added: > branches/AsciiDoc/docs/man/index.txt Cool! One potential issue: /sw/bin/asciidoc --backend=xhtml11 \ --attribute localdate=`TZ=UTC date +%Y-%m-%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

Hi there, A couple years ago, I had patched the "fentonups" nut driver to allow it to work with my Unitek Alpha 500 UPS. My patch had been accepted and incorporated in the standard fentonups driver. I have had no time to stay involved in the "nut" project since (and besides this I'm not a developper...). 2 days ago I upgraded from Ubuntu Gutsy to Ubuntu Hardy and got

Hi! I don't know how I missed it before, but "bestups" seems to implement mostly the same protocol as megatec. Is anybody out there using this driver willing to try "megatec" to see if it works? AFAIK, the only difference seems to be the command that gets the UPS identification data ("I" on "megatec", "ID" on "bestups"), but

Hi! I don't know how I missed it before, but "bestups" seems to implement mostly the same protocol as megatec. Is anybody out there using this driver willing to try "megatec" to see if it works? AFAIK, the only difference seems to be the command that gets the UPS identification data ("I" on "megatec", "ID" on "bestups"), but

On Feb 2, 2008 10:16 AM, Luki <looky at poczta.fm> wrote: > Hello Carlos > > could you please help me to solve issue with Mustek 1000VA UPS under > Freebsd ? > I am not able to connect with it : > > >Network UPS Tools - UPS driver controller > >Network UPS Tools - Megatec protocol driver 1.5.4 [megatec] > >Carlos Rodrigues (c) 2003-2007 > >

Hello, I have bought Powerman Optima 500 Plus UPS. While this product might be unknown outside Russia, it is shipped with megatec software and obviously works with megatec driver in NUT. besides the following problems (I think they are caused by one reason): 1) megatac driver is able to load and detect UPS only on second or third run. On the first run it typically fails. Later if daemon is

Hi, I'm not the maintainter for the "megatec_usb" driver (in fact, I'm no longer maintainer for the base "megatec" either), so I don't really know the status for that particular UPS. I'm forwarding this to the NUT mailing-list though. Regards, -- Carlos Rodrigues On Fri, Dec 5, 2008 at 10:30 AM, Adrian Czerniak <adrian.czerniak at becomo.com> wrote: