similar to: broken spec files in the trunk

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

Disclaimer: I've setup APC UPS monitoring and it works... ... but when it comes to mustek powermust 600usb (connected via com-port), I can't make it work. Got NUT installed via aptitude in ubuntu feisty and a basic setup, exactly the same as for the apc, except for the name of the ups and the corresponding section of ups.conf -- [mustek] driver = megatec port = /dev/ttyS1

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 1/23/07, Henning Brauer <hb-nut@bsws.de> wrote: > good new first: the megatec driverin 2.0.5 now works with the Online > Xanto S3000R here - well, for the very basics. > > the UPS has NO way ofidentifying itself. It also does not respond to > the power ratings query ("F"). I previously used a hacked up fentonups > driver. This means the driver cannot figure out

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

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

On Feb 11, 2008 5:30 PM, Marcio Gomes <mpg at microlink.com.br> wrote: > I change the if in [OFF] detect state to, in original way, if you send a > reset.watchdog, the UPS goes > to OFF state in clients, but it is not correct, because UPS is OL and > Shutdown are in progress, but > the power is not OFF First of all, thanks for the patch. But I have a few comments: Are you

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

> 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

Hi folks, has anyone been successful in getting a Mustek PowerMust 500 to talk to nut? All my attempts (tried "mustek" and "powermust" as drivers) have been unsuccessful so far. Thanks for any clues. Sascha -- http://yoyodyne.ath.cx

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

"mustek" is all but deprecated, so the effort should be to get powermust/megatec working. Since you have the latest development code installed, can you please run "/path/to/megatec -DDDD -a the_name_for_your_ups" (this without starting NUT normally - i.e. without upsd, upsmon, etc) and send me the output? The output should help me figure out why you are getting data stale

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

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

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

Greetings! Thanks to all the developers who have made this project so far. Searching for a Linux based Belkin UPS monitor led me straight to the Network UPS Tools. I have bought a Belkin F6C900-UNV (900VA) for use on a Slackware 10.2 server to replace an older APC model that died suddenly. So far I have successfully managed to get NUT 2.0.5 compiled and configured and found that this Belkin

Hi, a few days ago, I bought some of those Mustek UPSes that have both a serial and a USB connector. Currently only the serial port is supported by the megatec driver. This works fine so far. Now I have seen there is a megatec_usb driver, which currently only supports 2 other UPSes. How can I help to find out whether the PowerMust might actually work with the megatec_usb driver? -- Regards,