similar to: Fwd: Auto-discard notification

Hi, Sorry for the forwarding. I sent this with the wrong "from" address and got rejected by the list. ---------- Forwarded message ---------- From: Carlos Rodrigues <cefrodrigues at mail.telepac.pt> Date: Jun 18, 2007 9:34 PM Subject: Re: Megatec - modem control lines [impact to megatec_usb] To: Arjen de Korte <nut+devel at de-korte.org> Cc: ups-dev-list <nut-upsdev at

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

On Mon, Oct 20, 2008 at 1:35 PM, Arjen de Korte <nut+devel at de-korte.org> wrote: > Citeren Carlos Rodrigues <cefrodrigues at gmail.com>: > >> BTW, the patch has a small typo in one of the comments: "applied to >> battery.volage" :) > > I'll leave that up to you to correct. Since it is only a comment, it won't > be visible to innocent users

I'm forwarding this to the list, as I'm not quite sure what's going on here. Never seen this on Linux, don't know if it is a FreeBSD thing or not. ---------- Forwarded message ---------- From: Herman J van der Merwe <herman@mercygate.com> Date: Feb 11, 2007 9:50 PM Subject: NUT on FreeBSD To: carlos.efr@mail.telepac.pt Hello Carlos Maybe you can assist me with NUT 2.0.5

> 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

On Nov 27, 2007 7:51 AM, Tom?? Smetana <tsmetana at redhat.com> wrote: > As for the removal of nut from RHEL: I don't know anything else about > the decision than you do. Red Hat has historically provided ancient NUT versions with their distributions (not Fedora though). I guess they decided that it was better to ship nothing at all. I have no idea why they did it, but if I had

Skipped content of type multipart/alternative-------------- next part -------------- A non-text attachment was scrubbed... Name: tripplite500_cmds.rtf Type: application/rtf Size: 16162 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20051205/f905e213/tripplite500_cmds.rtf

I have an MGE Pulsar Evolution 1100 connected to a Debian box, with nut-2.0.1 (the standard "sarge" packages). I have it connected through USB, and I'm using newhidups. However, about once a day the driver looses contact with the UPS and I have to restart NUT to get it to drop the "data stale" nonsense (it happens more often than this, but most times it recovers without

Hi! We have two MGE Evolution 1100 here, and I want to make use of the powershare outlets to force a particular boot sequence on the machines powered by them. However I'm not sure how to set those variables upon NUT starting, without having to change the init scripts to call "upsrw". Is there some place where I can set them, where they can be read automatically on startup? One of

Hi, Currently, "configure.in" in both testing and the trunk have libupsclient disabled by default, which means the build is broken if the user doesn't explicitly enable it when running configure. Why was it like this and can I commit the fix? -- Carlos Rodrigues

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 >

While making the necessary changes for removing the drivers obsoleted by "megatec", I noticed that the ".spec" files in "/packaging" had references to some old, nonexistant, manpages (like "powermust.8"). This means these files have been broken for a while. I don't have any rpm-based distro installed so I can't fix them myself. But if there's a

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:

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:

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

While trying to compile newhidups, I get this error... carlos@rhea:~/dev/nut/svn/trunk$ make usb make[1]: Entering directory `/home/carlos/dev/nut/svn/trunk/drivers' gcc -I../include -O -Wall -Wsign-compare -c newhidups.c In file included from newhidups.c:25: libhid.h:46: error: syntax error before "u_int16_t" libhid.h:46: warning: useless keyword or type name in empty declaration

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

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

Hi Jon, your patches are malformed because (presumably) your email client wrapped this lines. Could you please send these as a unified diff ("diff -u"), and send them in attachments, rather than as a copy-and-paste? Thanks, -- Peter Jon Gough wrote: > > Peter, > Here are the files I have worked on. I hope I have diff'd them > correctly. I have not touched the