Re: [Nut-upsuser] Mustek PowerMust 848
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 [EMAIL PROTECTED] wrote: Hi, are you going to support Mustek PowerMust 848? I'm not able to run it with lastest SVN: #./megatec_usb -a mustek -D Network UPS Tools 2.3.0-1595 - Megatec protocol driver 1.5.18 [megatec_usb] Carlos Rodrigues (c) 2003-2008 Serial-over-USB transport layer for Megatec protocol driver [megatec_usb] Andrey Lelikov (c) 2006, Alexander Gordeev (c) 2006-2007, Jon Gough (c) 2007 debug level is '5' Checking device (0665/5161) (003/004) - VendorID: 0665 - ProductID: 5161 - Manufacturer: Cypress Semiconductor - Product: USB to Serial - Serial Number: unknown - Bus: 003 Trying to match device Device matches DTR=1, RTS=0 send_to_all: SETINFO driver.version.internal 1.5.18 Starting UPS detection process... Asking for UPS information [I]... I = FAILED [short read] I detail: (1 bytes) = 49 Asking for UPS status [Q1]... 00]_data_phoenix: got so far [Q1 get_data_phoenix: (8 bytes) = 51 31 0d 2e 30 0d 30 30 Q1 = FAILED [short read] Q1 detail: (2 bytes) = 51 31 Asking for UPS status [Q1]... 00]_data_phoenix: got so far [Q1 get_data_phoenix: (8 bytes) = 51 31 0d 2e 30 0d 30 30 Q1 = FAILED [short read] Q1 detail: (2 bytes) = 51 31 Asking for UPS status [Q1]... 00]_data_phoenix: got so far [Q1 get_data_phoenix: (8 bytes) = 51 31 0d 2e 30 0d 30 30 Q1 = FAILED [short read] Q1 detail: (2 bytes) = 51 31 Asking for UPS status [Q1]... 00]_data_phoenix: got so far [Q1 get_data_phoenix: (8 bytes) = 51 31 0d 2e 30 0d 30 30 Q1 = FAILED [short read] Q1 detail: (2 bytes) = 51 31 Asking for UPS status [Q1]... 00]_data_phoenix: got so far [Q1 get_data_phoenix: (8 bytes) = 51 31 0d 2e 30 0d 30 30 Q1 = FAILED [short read] Q1 detail: (2 bytes) = 51 31 5 out of 5 detection attempts failed (minimum failures: 2). Megatec protocol UPS not detected. -- Regards, Adrian Czerniak ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Some issues with UPS Forza SL-1001
On Thu, Sep 4, 2008 at 6:31 AM, Néstor Peña [EMAIL PROTECTED] wrote: Nut states battery is at 87,5% but Winpower says 100%. In fact, with nut, the battery doesn't charge above 95%. Using megatec_ups -DD gave me this voltage ranges: 13,7V-9,7V, and the maximum battery voltage I ever seen is 13,5V. Is WinPower using relaxed values? Is the UPS needing a battery recalibrate? I just unpacked and connect it... Winpower is shipped by most vendors on their megatec procotol UPSes. Just like you can use the battvolts parameter in ups.conf to tweak the voltage ranges, so did the vendor to their default Winpower configuration. Regards, -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] megatec process die
On Tue, Jul 1, 2008 at 10:04 AM, Ercan Istek [EMAIL PROTECTED] wrote: Jul 1 11:56:46 ginning upsd[10590]: Can't connect to UPS [tuncmatik] (megatec-tuncmatik): Connection refused Jul 1 11:56:46 ginning upsd[10590]: Data for UPS [tuncmatik] is stale - check driver Jul 1 11:56:46 ginning kernel: megatec[21553]: segfault at 100 ip 00d32216 sp bffb05f0 error 4 in libgcc_s-4.3.0-20080428.so.1[d2b000+d000] What is the problem ? Can you try the latest version of the driver (from SVN)? This should be fixed. -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] megatec driver floods syslog with UPS lost/re-established messages
On Thu, Jul 3, 2008 at 10:57 PM, Anton Martchukov [EMAIL PROTECTED] wrote: 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 being stoped and started again it's more likely to fail after restart too, but on the second restart it will mostly work ok. When it fails to start it outputs this to syslog: Jul 2 22:58:53 alcor upsd[5353]: Can't connect to UPS [powerman] (megatec-powerman): No such file or directory 2) When it starts properly it works nice, e.g. output UPS parameters, deteact low baterry etc. besides the fact that it floods syslog with the following message each polling cycle of the driver Jul 3 23:07:16 alcor megatec[7070]: Communications with UPS re-established Jul 3 23:07:24 alcor megatec[7070]: Communications with UPS lost: No status from UPS. Jul 3 23:07:31 alcor megatec[7070]: Communications with UPS re-established Jul 3 23:07:39 alcor megatec[7070]: Communications with UPS lost: No status from UPS. Jul 3 23:07:46 alcor megatec[7070]: Communications with UPS re-established Jul 3 23:07:54 alcor megatec[7070]: Communications with UPS lost: No status from UPS. Jul 3 23:08:01 alcor megatec[7070]: Communications with UPS re-established Jul 3 23:08:07 alcor megatec[7070]: Communications with UPS lost: No status from UPS. Jul 3 23:08:14 alcor megatec[7070]: Communications with UPS re-established Jul 3 23:08:29 alcor megatec[7070]: Communications with UPS lost: No status from UPS. I have tried different settings of polling cycle for the dirver and believe that it does not affect the presence of this message at all. Any help/directions will be highly appreciated. I know a bit of C and willing to try to solve this problem. Which version of NUT are you using? -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] megatec process die
On Tue, Jul 1, 2008 at 10:04 AM, Ercan Istek [EMAIL PROTECTED] wrote: Jul 1 11:56:46 ginning upsd[10590]: Can't connect to UPS [tuncmatik] (megatec-tuncmatik): Connection refused Jul 1 11:56:46 ginning upsd[10590]: Data for UPS [tuncmatik] is stale - check driver Jul 1 11:56:46 ginning kernel: megatec[21553]: segfault at 100 ip 00d32216 sp bffb05f0 error 4 in libgcc_s-4.3.0-20080428.so.1[d2b000+d000] What is the problem ? What version of NUT, distribution, etc...? -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] megatec process die
On Tue, Jul 1, 2008 at 2:22 PM, Ercan Istek [EMAIL PROTECTED] wrote: Hello Carlos, nut-client-2.2.2-1.fc9.i386 nut-2.2.2-1.fc9.i386 I am using Fedora 9 Linux ginning 2.6.25.4-30.fc9.i686 #1 SMP Wed May 21 18:12:35 EDT 2008 i686 i686 i386 GNU/Linux Is the problem reproducible? How to reproduce it? Does it happen when the driver starts? PS: please keep the list CC:ed, thanks. -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] megatec process die
On Tue, Jul 1, 2008 at 2:47 PM, Ercan Istek [EMAIL PROTECTED] wrote: Hello Carlos, it occur 7-8 hour after i start nut. megatec binary dies. Without more information (a stack trace or something), it's kind of difficult to find the problem. It can be a megatec issue, or an issue with the driver host. PS: Please keep the list CC:ed. -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] megatec process die
Like I said, this may be a problem with megatec, or it may not, so please CC: the NUT mailing-list when you reply. Please run the driver with -DDD at least. Does it terminate in the same place everytime? Rebuilding the driver with debugging symbols on and run it through valgrind would be useful too. On Tue, Jul 1, 2008 at 4:13 PM, Ercan Istek [EMAIL PROTECTED] wrote: Hello Carlos, Asking for UPS status [Q1]... Q1 = OK [(214.5 214.5 220.1 030 49.9 2.22 41.5 ] Calculated battery charge: 100.0% Asking for UPS status [Q1]... Q1 = OK [(214.5 214.5 220.1 030 49.9 2.22 41.5 ] Calculated battery charge: 100.0% *** stack smashing detected ***: megatec terminated === Backtrace: = /lib/libc.so.6(__fortify_fail+0x48)[0x9b6ce8] /lib/libc.so.6(__fortify_fail+0x0)[0x9b6ca0] megatec[0x804a71a] megatec[0x804d250] [0x871abe8] === Memory map: 0011-00111000 r-xp 0011 00:00 0 [vdso] 00111000-0011b000 r-xp 08:01 15467217 /lib/libnss_files-2.8.so 0011b000-0011c000 r--p a000 08:01 15467217 /lib/libnss_files-2.8.so 0011c000-0011d000 rw-p b000 08:01 15467217 /lib/libnss_files-2.8.so 008a-008bc000 r-xp 08:01 15826946 /lib/ld-2.8.so 008bc000-008bd000 r--p 0001c000 08:01 15826946 /lib/ld-2.8.so 008bd000-008be000 rw-p 0001d000 08:01 15826946 /lib/ld-2.8.so 008c-00a23000 r-xp 08:01 15826953 /lib/libc-2.8.so 00a23000-00a25000 r--p 00163000 08:01 15826953 /lib/libc-2.8.so 00a25000-00a26000 rw-p 00165000 08:01 15826953 /lib/libc-2.8.so 00a26000-00a29000 rw-p 00a26000 00:00 0 00d2b000-00d38000 r-xp 08:01 15826975 /lib/libgcc_s-4.3.0-20080428.so.1 00d38000-00d39000 rw-p c000 08:01 15826975 /lib/libgcc_s-4.3.0-20080428.so.1 08048000-08054000 r-xp 08:01 17236226 /sbin/megatec 08054000-08055000 rw-p c000 08:01 17236226 /sbin/megatec 08719000-0873a000 rw-p 08719000 00:00 0 [heap] b7fbc000-b7fbe000 rw-p b7fbc000 00:00 0 b7fd1000-b7fd2000 rw-p b7fd1000 00:00 0 bf8bc000-bf8d1000 rw-p bffeb000 00:00 0 [stack] Aborted [EMAIL PROTECTED] ~]# [EMAIL PROTECTED] ~]# Broadcast message from nut (Tue Jul 1 18:07:45 2008): Communications with UPS [EMAIL PROTECTED] lost Tuesday, July 1, 2008, 4:58:39 PM, you wrote: On Tue, Jul 1, 2008 at 2:47 PM, Ercan Istek [EMAIL PROTECTED] wrote: Hello Carlos, it occur 7-8 hour after i start nut. megatec binary dies. Without more information (a stack trace or something), it's kind of difficult to find the problem. It can be a megatec issue, or an issue with the driver host. PS: Please keep the list CC:ed. -- Best regards, Ercanmailto:[EMAIL PROTECTED] -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Megatec and Belkin F6H550-UPS
On Sat, Jun 28, 2008 at 7:18 PM, Jayson Anderson [EMAIL PROTECTED] wrote: Will the Q1 return parsing be changed in future versions to help interpret output like mine w/special chars and such ? For your case it is already changed in the latest development version. -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Megatec and Belkin F6H550-UPS
2008/6/27 Jayson Anderson [EMAIL PROTECTED]: Greetings Arnaud, I wrote you some time ago about whether NUT would support the Belkin F6H550-UPS device in the future. [snip] I managed to get the device sort-of working, but i'm getting the unsupported combination of battery voltage... error when attempting to bring upsdrvctl online. That's not really an error, but a warning. The way to get rid of it is by using the battvolts option in upsd.conf. Just check the manpage for more details (man 8 megatec). To get the values required, just let the UPS charge completely. Then, run megatec -DDD -a yourups somefile.txt, unplug the UPS from mains and let it discharge until it shuts itself down (it must be powering something, but probably not your computer...). Then, from the file, you can obtain the battery voltage when the UPS was fully charged (from the first line in the file) and the battery voltage when the UPS was fully discharged (from the last line in the file). Finally, send those values to me, so that I can add them to that model's entry in the compatibility list. -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Megatec battery level
On Fri, Jun 13, 2008 at 6:50 AM, Ercan Istek [EMAIL PROTECTED] wrote: What is problem with my UPS i can not see Battery charge level ? Just use the battvolts parameter in ups.conf. Check the megatec manpage for more information. -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Dynamix UPS-650VA
On Thu, May 8, 2008 at 4:20 AM, Peter McKenna [EMAIL PROTECTED] wrote: That's correct. I used to be able to toggle it in Nut 2.0 and the response from upsc would show off/on, but if you unplugged it it would still beep. I assumed there where other less critical beep alerts being turned off. Then it never actually worked, it only appeared to work. The driver was probably assuming the beeper was on at startup and just changing its internal state when you issued the toggle command without actually getting that state from the UPS. Can you check the logs (/var/log/messages or similar, depending on the distribution you're using) to see if there's any message there indicating the beeper.toggle command didn't succeed? -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Dynamix UPS-650VA
On Mon, May 5, 2008 at 4:05 AM, Peter McKenna [EMAIL PROTECTED] wrote: Thanks for your reply Carlos. The ignoreoff suggestion didn't work. The driver appeared to not connect. Hmmm, my bad. I only added the ignoreoff option _after_ 2.2.1. The Temp reading has never worked returning 0.0. That means the UPS doesn't have a temperature sensor. The beeper did work in 2.0. I could toggle it with an instant command, but now doesn't work with the same command. upsc just shows it as disabled. The beeper has always worked when the ups is unplugged. Define doesn't work. The beeper can still be heard after you try to disable it, or the driver still shows the beeper as disabled? In many models the beeper status flag is bogus (this is mentioned in the manpage btw) and never changes (it is always enabled or disabled). I'm not sure if in 2.0 the driver exposed the beeper status or not... PS: Please keep the list CC:ed when replying. Thanks. -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Dynamix UPS-650VA
On Mon, May 5, 2008 at 10:24 AM, Jean Delvare [EMAIL PROTECTED] wrote: On Mon, 5 May 2008 09:49:12 +0100, Carlos Rodrigues wrote: On Mon, May 5, 2008 at 4:05 AM, Peter McKenna [EMAIL PROTECTED] wrote: The Temp reading has never worked returning 0.0. That means the UPS doesn't have a temperature sensor. Wouldn't it be better if the driver didn't expose the temperature value at all in this case? The version currently in the subversion repository does that since yesterday afternoon. :) Although it is of limited usefulness for the general population, because most models that don't have a temperature sensor return a fixed value (mine always returns 25.0) making it impossible to tell if it is bogus or not... -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Dynamix UPS-650VA
On Mon, May 5, 2008 at 10:47 AM, Jean Delvare [EMAIL PROTECTED] wrote: Yes I know, mine always returns 29.2... Too bad that the manufacturers don't make it clearer when a thermal sensor is present and when it's not. And it would be easy to do. The protocol specifies that an non-existent value should be expressed as a non-numeric field (eg. @@.@). The only thing we can do, I suppose, is look at the UPS device name string and have a blacklist in the driver for devices which are known to not have a thermal sensor. The benefit might not be worth the maintenance cost though. Yeah, the benefit isn't worth it, especially since the subset of models that provide bogus values seems to map almost completely to the subset of models that provide absolutely no device string whatsoever... -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Liebert ITON 600 VA
On Wed, Apr 23, 2008 at 11:56 AM, Guenther Boelter [EMAIL PROTECTED] wrote: It has an serial interface and it's the only ups i could found here with an interface. May be this link could be helpful http://www.emersonnetworkpower-partner.com/Liebert-ITON-600-VA-50Hz-MY/default.aspx By the looks of it, it may be supported by the megatec driver. -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Network UPS Tools version 2.2.2-pre2 released
On Fri, Apr 18, 2008 at 11:00 AM, Roger Price [EMAIL PROTECTED] wrote: I removed the current rpm's (2.2.0) with rpm -e and tried to install the 2.2.2-pre2 rpm (a big thankyou to Arjen de Korte and Arnaud Quette). glacon2 # rpm -Uvh nut-2.2.2-pre2.i586.rpm error: Failed dependencies: libgd.so.2 is needed by nut-2.2.2-pre2.i586 libneon.so.26 is needed by nut-2.2.2-pre2.i586 libnetsnmp.so.15 is needed by nut-2.2.2-pre2.i586 These three libraries are present: glacon2 # locate libgd.so.2 /usr/lib64/libgd.so.2 /usr/lib64/libgd.so.2.0.0 glacon2 # locate libneon.so.26 /usr/lib64/libneon.so.26 /usr/lib64/libneon.so.26.0.4 glacon2 # locate libnetsnmp.so.15 /usr/lib64/libnetsnmp.so.15 /usr/lib64/libnetsnmp.so.15.1.0 The libraries are present, yes, but they are 64bit and you are trying to install a 32bit rpm. You can either install the 32bit versions of those libraries, or try rebuilding the rpm to obtain a 64bit one. -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] [Bug 215389] [NEW] No battery charge percentage on belkin usb avr
On Fri, Apr 11, 2008 at 8:02 PM, Arnaud Quette [EMAIL PROTECTED] wrote: 2008/4/10, David Erosa [EMAIL PROTECTED]: After updating to last nut package (2.2.1-2.1ubuntu6), the megatec_usb driver seems to be working, except for the charge percentage: [...] F = FAILED [short read] F detail: (0 bytes) = Cannot calculate charge percentage for this UPS. - [...] So I tried the svn version (as today, revision 143) and the result is: F = OK [#230.0 002 12.00 50.0] 12.0V battery, interval [9.7V, 13.7V]. - Done setting up the UPS. The first snippet shows that the driver couldn't get the ratings from the UPS, and without those values there's no way to calculate the charge percentage. There have been some improvements in reliability while talking to the UPS, so maybe that's why the newer version works. You can always use the battvolts option though, like Arnaud said. And it looks like you need to use it because the calculated percentage doesn't look correct (assuming the UPS is fully charged). The thing is, for a given nominal battery voltage, different models from different vendors behave differently, and there is no way to tell them apart to ajust the calculation. -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] [Bug 209001] [NEW] Nut no longer functions with belkin usb avr
On Fri, Apr 4, 2008 at 8:46 PM, Alexander I. Gordeev [EMAIL PROTECTED] wrote: thanks for these info, and good luck for your degree. I just saw that Carlos has taken over, so there is no problem. Arnaud Thanks! And good luck to Carlos... Errrm... taken over what? I'll backport megatec.c, and I can try and backport megatec_usb also, but I don't have the hardware to test it. -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] problem with output voltage on a mustek ups
On Fri, Mar 7, 2008 at 11:15 AM, Pedro Mendes Jorge [EMAIL PROTECTED] wrote: This output voltage is too low! I think power spikes may be better than using this voltage. Is this indicated by the UPS, or did you measure this voltage externally? Arjen has mentioned this before, but the values returned by UPSes are generally not calibrated. It is returned by the UPS. But again, I sometimes have an output voltage of ~225V when it is not trimming. I could try and measure the real one, but following Arjen's advice I won't waste my time, nor someone else's time (yours). I used to have a Mustek UPS (600VA). The voltage readings it reported were off by 12~15V. When on line power it reported too much voltage, and when on battery it reported too low a voltage. This comparing to the values read with a voltimeter. Don't sweat it. Cheap hardware has downsides... -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Unitek UPS 1250xD - megatec_usb driver
On Feb 17, 2008 7:56 PM, Alexander I. Gordeev [EMAIL PROTECTED] wrote: The best solution would probably to ignore the first couple of failures in the 'megatec.c' driver, before declaring data stale. Generally speaking, one should be careful to declare data stale and only do so after a couple of attempts to read the status (typically three in a row) have failed. I like the idea of solving this in megatec.c. Both serial and usb interfaces could easily fail. If the driver fails to get any data in the current polling cycle, it declares the data as stale until the next cycle. It tried to read the data, it got nothing, ergo the current data is stale. I don't agree the driver should systematically retry reading the status within a polling cycle. However, if communication failures are a systematic problem over USB, the USB layer should deal with it appropriately. -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Unitek UPS 1250xD - megatec_usb driver
On Feb 17, 2008 9:16 PM, Alexander I. Gordeev [EMAIL PROTECTED] wrote: Still I concern about the added latency. I can retry after timeout but it means that ser_send_pace will not return for seconds. I'd rather add a variable in megatec.c to make user decide the number of retries before driver declares data stale (0 by default). Ok, I guess it's no big deal to wait for a couple of polling cycles before declaring the data as stale. However, we should choose the number of cycles, not the user. If we can't get the status for a few cycles, either the UPS as a broken cable or something needs fixing in the driver. -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] problem with Mustek UPS - Freebsd
On Feb 2, 2008 10:16 AM, Luki [EMAIL PROTECTED] 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 Megatec protocol UPS not detected. Driver failed to start (exit status=1) Maybe the tty device has the wrong permissions? -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] problem with Mustek UPS - Freebsd
On Feb 2, 2008 8:20 PM, Luki [EMAIL PROTECTED] wrote: I have checked that, I have set 777 to cuaa0 - serial port (COM1) I have run /usr/local/ups/bin/megatec -DDD -a, results are as follows : [EMAIL PROTECTED] ~]# /usr/local/ups/bin/megatec -DDD -a server Network UPS Tools - Megatec protocol driver 1.5.4 [megatec] Carlos Rodrigues (c) 2003-2007 debug level is '3' Starting UPS detection process... Attempting to detect the UPS... Sending Q1 command... Wrong answer to Q1 command. Attempting to detect the UPS... Sending Q1 command... Wrong answer to Q1 command. Attempting to detect the UPS... Sending Q1 command... Wrong answer to Q1 command. Attempting to detect the UPS... Sending Q1 command... Wrong answer to Q1 command. Attempting to detect the UPS... Sending Q1 command... Wrong answer to Q1 command. 5 out of 5 detection attempts failed (minimum failures: 2). Megatec protocol UPS not detected. I am sorry for bothering you, but do you have idea how to solve it ? That's strange... Maybe you have a bad cable, or that model doesn't use the megatec procotol. What's the name of the software that Mustek ships with that UPS? Have you been able to use the UPS with any software other that NUT (on FreeBSD or any other operating system)? PS: please keep the list CC:ed so that others may have the opportunity to give their 2 cents. -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Belkin F6H375 not seen by nut 2.2.1
On Jan 14, 2008 10:32 PM, Joseph Borg [EMAIL PROTECTED] wrote: I added some printf statements to megatec.c and verified that the return value is '-110' but I can't seem to figure out why this is happening. I added printf statements to ser_get_line in serial.c but none seem to be printing (as an aside I'd like to understand why they're not :-)). The ser_* functions in serial.c are reimplemented in megatec_usb.c to keep the megatec driver transport agnostic. -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Need help with Unitek Alpha 1200sx.
On Jan 2, 2008 8:19 PM, Joseph Borg [EMAIL PROTECTED] wrote: No luck unfortunately :-( --- [myups] driver = megatec_usb port = auto bus=001 vendorid = 0f03 productid = 0001 subdriver = agiler desc = Unitek Alpha 1200sx --- [EMAIL PROTECTED] www]# /sbin/upsdrvctl -DD start Network UPS Tools - UPS driver controller 2.2.0- Starting UPS: myups exec: /sbin/megatec_usb -a myups Network UPS Tools 2.2.0- - Megatec protocol driver 1.5.4 [megatec_usb] Carlos Rodrigues (c) 2003-2007 Serial-over-USB transport layer for Megatec protocol driver [megatec_usb] No supported devices found. Please check your device availability with 'lsusb' and make sure you have an up-to-date version of NUT. If this does not help, try running the driver with at least 'vendorid' and 'subdriver' options specified. Please refer to the man page for details about these options (man 8 megatec_usb). Please report your results to the NUT user's mailing list nut-upsuser@lists.alioth.debian.org. - I've also tried changing the subdriver with no luck. The other options I specified I *think* are ok from the lsusb output. The strange thing is that this fails really fast...it's as though it's not even trying to detect the ups I'm afraid I can't be of much more help. I'll let the megatec_usb developers step in. -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Plexus UPS 1000V - megatec_usb
On Dec 28, 2007 1:52 PM, [EMAIL PROTECTED] wrote: But shutdown is still not implemented (at least in the krauler subdriver)! And I'can't help to support shutdown because my own UPS doesn't do it well. No shutdown whatsoever? -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] [Nut-upsdev] Plexus UPS 1000V - megatec_usb
On Dec 28, 2007 3:28 PM, Arjen de Korte [EMAIL PROTECTED] wrote: Therefor, I propose to relax the interpretation of the status bits in the 'megatec' driver, to allow the interpretation of 'OL' and 'OB', even if we already think/know the output is switched off. No problem by me, but should I keep the OFF status together with OB/OL, like OB OFF? -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Plexus UPS 1000V - megatec_usb
On Dec 28, 2007 6:59 PM, Jason Pearce [EMAIL PROTECTED] wrote: I have recompiled with the patched megatec.c and have added ignoreoff to my ups.conf However, I now receive this error : /usr/local/ups/bin/megatec_usb -a plexus Network UPS Tools 2.2.1 - Megatec protocol driver 1.5.9 [megatec_usb] Carlos Rodrigues (c) 2003-2007 Serial-over-USB transport layer for Megatec protocol driver [megatec_usb] Andrey Lelikov (c) 2006, Alexander Gordeev (c) 2006-2007, Jon Gough (c) 2007 Fatal error: 'ignoreoff' is not a valid flag for this driver. Look in the man page or call this driver with -h for a list of valid variable names and flags. Did you replace only the megatec binary? megatec_usb is also rebuilt when megatec.c changes and should also be replaced if you are copying manually. -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Strange battery power shortage on an Unitek iZi UPS 525
On Dec 22, 2007 2:34 PM, Ciprian Marius Vizitiu [EMAIL PROTECTED] wrote: 3. Somehow the newer version of nut fails to correctly read/interpret the values from the UPS and decides to shut down earlier. Unless you specify a lowbatt value in you ups.conf, the shutdown will happen when the UPS raises the low battery flag. How this flag is handled by megatec/powermust hasn't changed between 2.0.3 and 2.2.0. 4. ... any other ideas? Either you new system draws enough extra power, or your UPS wasn't fully charged when you did that second test, or your battery is going bad, or a combination thereof. It doesn't look like something related to NUT. -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Mustek Powermust 800 under Ubuntu
On Dec 15, 2007 6:47 PM, Igal [EMAIL PROTECTED] wrote: Hello, I'm trying to setup my UPS using the megatec driver, but for now without success. from what I understood, the UPS should be connected to serial port (despite being an USB UPS), so I did i. What do you mean despite being an USB UPS? That model should work when using its serial port connection. Can you provide more info? (The configuration you are using, for example.) -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Mustek Powermust 800 under Ubuntu
On Dec 15, 2007 8:29 PM, Igal [EMAIL PROTECTED] wrote: I mean, it IS connected to computer's serial port. I'm using Ubuntu 7.10 and the kernel version is 2.6.22-14-generic. /etc/default/nut : # start upsd START_UPSD=yes # start upsmon START_UPSMON=yes /etc/nut/ups.conf : [mustek] driver=megatec port=/dev/ttyS0 Hmm, that should be enough. Maybe the that's not the correct tty? Or perhaps you could try the latest development version of NUT. If not only because the latest version of megatec produces a bit more output when invoked with -DDD. -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] NUT auto-discovery [Was: Re: Nut problems with Centos and Belkin UPS]
On Nov 27, 2007 12:56 PM, Carlos Rodrigues [EMAIL PROTECTED] wrote: 1. most medium/large datacenters have a small number of large UPSes with generator backups, so NUT is rather pointless; 2. the datacenter has a big UPS and no generator backup, and people find their 60 minute runtime enough and don't bother to configure a large number of machines with NUT, especially since their distribution of choice would force them to compile from source; 3. they just don't know about the existence of NUT, and continue to use the suck-ass software from the UPS vendor, which normally eats half their systems memory with its java-based daemon. Sorry about the change in the subject, I was goink to ask how hard would it be to implement some kind of auto-discovery/centralized configuration for slave upsmon's but after thinking a bit I though it would be too much work for questionable gain and changed my mind. -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] NUT auto-discovery [Was: Re: Nut problems with Centos and Belkin UPS]
On Nov 27, 2007 3:59 PM, Arjen de Korte [EMAIL PROTECTED] wrote: When you have only one UPS in your network, this might work. Otherwise, one UPS going offline might cause all clients to shutdown. This is probably not very desireable. What I had in mind was more of a centrally managed configuration, than no configuration. For example, extending ACLs to include the name(s) of the UPS powering the specified system (or subnet), plus a repository of default configurations for upsmon. The clients would only specify the address of the server, nothing more, and then all future configuration changes could be done on the server, without client intervention. Clients would have the possibility of modifying their own configuration, but that would be the exception, not the norm. Like I said, I kind of changed my mind about this because (although this would have benefits for large installations), the work required would possibly be overkill, but anyway... -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Mustek Powermust 600VA
On Nov 20, 2007 9:43 PM, Krzysztof Sasiak [EMAIL PROTECTED] wrote: I'm having a hard time configuring a Mustek Powermust 600VA ups to work via USB with nut. I read somewhere that nut works OK via the rs232 cable, but unfortunately I don't have a COM port in my computer. The kernel detects the ups as an Xbox pad :) and loads the xpad module. I tried running /lib/nut/megatec with different /dev/ttySx but it displays megatec protocol UPS was not detected. That UPS may be supported by megatec_usb (or may not yet be). Anyway, you can get an USB-to-serial adapter (one supported by the kernel) and connect the serial port on the UPS to an USB port on your machine. Then you can use the regular megatec driver with something like /dev/ttyUSB0. I never done it myself, but it should work. -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] (no subject)
On 10/3/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I have in my possession a PowerWalker VI 1400, the big brother to the NUT-supported VI 1000. It seems to work fairly well with the megatec-driver, however there is one bigger problem and that is the incorrect detection of battery.charge. This causes the UPS send the OB LB flag at - according to NUT - 43% of battery.charge, however the real charge at this point is closer to ~25%. A powerloss is inevitable when there is - again, according to NUT - 17% left in the battery.charge. I haven't tried the dev-tree but since megatec.c in the dev-tree is identical to the megatec.c in nut-2.2.1-pre1 I assume the problem is still around. From NUT 2.2.0 onwards, the megatec driver supports an option named battvolts in ups.conf, in which one specified the battery.voltage reported by the UPS when discharged (just before it turns itself off, not when it triggers a low battery event), and the voltage when the UPS is full. For example... battvolts = 20:26.2 ...would mean battery.voltage: 20 when almost completely discharged and battery.voltage: 26.2 when fully charged. The value you are obtaining for battery.charge is just a best effort value based on data obtained from other models. If that value is incorrect, the only way to set it straight is to use the battvolts option. -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Masterguard A-19 3000
On 9/27/07, Stefan Teubel [EMAIL PROTECTED] wrote: I am trying to get this UPS talking with NUT (2.2.0) under Fedora 7/CentOS5. I have searched the mailing list and found some infos: http://lists.alioth.debian.org/pipermail/nut-upsdev/2007-February/001799.html but I'm not really sure how that helps me. USB would be cool but I don't really need that, it just has to work. I have also found a document that shows the pinout of the com port (page 8) there: http://www.watfordcontrol.co.th/products/UPS/series_ae1/Catalog_A-19_A_E_engl(1999).pdf My question is, do I have to swap the TXD and RXD pins to get it working? I have tried to add the USB device address into the ups.conf and run the driver config tool thing. After a while it says: tcgetattr(/proc/bus/usb/004/002): Inappropriate ioctl for device After that I have tried the serial port, with a 1:1 cable, which didn't worked as well. What driver are you using? You can try the masterguard driver, or megatec. -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] How can I setup Ubuntu 7.04 feisty + Udev + Nut + Unitek Ups (megatec) + Usb ????
On 9/21/07, Sébastien CRAMATTE [EMAIL PROTECTED] wrote: I've got an Unitek UPS (650ipE) that use megatec driver ... I'm running Ubuntu 7.04 with a 2.6.20 kernel and nut 2.0.5-1 package Ubuntu by default use Udev and hid, usbhid, evdev kernel modules are loaded automatically The UPS is detected on system level but upsdrvctl can't access to the device ... The megatec driver only supports UPSes connected through the serial port, not USB. If you have a serial port available and your UPS also has this kind of connection, it should work though. For USB, the megatec_usb driver available in NUT 2.2.0 may support your UPS. -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] driver for my ups
On 9/13/07, Alexander Fradiani [EMAIL PROTECTED] wrote: If it also has serial port, it should be supported by megatec. If it is USB only, you may try megatec_usb to see if it works. thanks for the answer, just two more questions i´ve been searching for the megatec_usb driver, but can't find it yet. where should i get it. The megatec_usb driver was introduced in NUT 2.2.0 (the current stable release). using the megatec, i get the following: tcgetattr(/dev/bus/usb/002/012): Inappropriate ioctl for device is that because of the driver, or am i trying to connect to the wrong port (the only way i know to identify the port is using the lsusb command). megatec can only drive UPSes connected through the serial port, not USB (unless your UPS has a true USB-to-serial converter, which I very much doubt it, and gets assigned a /dev/ttyUSBx device by the kernel). The Winpower software speaks the megatec protocol, so megatec_usb is your best shot. If it doesn't work, maybe its maintainers can help modifying it in order to work. -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] driver for my ups
On 9/13/07, Alexander Fradiani [EMAIL PROTECTED] wrote: Hello everyone. I have a Forza Power Technologies UPS, model sl-501. the software i've been used to manage it is Winpower v.2.2.0.1. It works on windows but not linux. There is a version for this app for linux, but once installed, it doesn't detect the ups (the connection is via usb). My question is if there is a driver useful for this hardware. I've bee reading that maybe testing those from genericups could work, but i don't know very well how to configure the different files yet. Before getting stuck trying to find a functional configuration, i really would appreciate any help or orientation on this. If it also has serial port, it should be supported by megatec. If it is USB only, you may try megatec_usb to see if it works. -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Upsonic CXR1000, megatec and NUT
On 7/11/07, Andrew Janke [EMAIL PROTECTED] wrote: None of these extra features work that I can tell. But what it can get from it is all I need. Are you talking about the extra information, or saying that the driver can't shutdown the UPS and so on? -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Upsonic CXR1000, megatec and NUT
On 7/9/07, Arnaud QUETTE [EMAIL PROTECTED] wrote: My UPS is a: Upsonic CXR1000 (made in Oz, probably rebranded monitoring) Driver: Megatec Works perfectly! [snip] I'll add your model to the supported ones once Carlos has validated everything is fine. I can do that. From the output shown, I can see that the driver doesn't calculate the battery charge percentage for your UPS. This seems to be related to the fact that the nominal values (aka: UPS ratings) are also missing, which makes this an unfixable issue on the driver's side. You can, however, pass the battvolts parameter to the driver (in ups.conf) and the calculation will be done based on those values. For example battvolts = 20:27 means battery.voltage is 27V when the UPS is full, and 20V when the UPS is empty. You can also check the manpage. -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] energizerups and bestups - megatec?
On 7/7/07, Dâniel Fraga [EMAIL PROTECTED] wrote: On Fri, 6 Jul 2007 19:33:07 +0100 Carlos Rodrigues [EMAIL PROTECTED] wrote: And there's energizerups... How feasible is it to have megatec_usb obsolete this driver? Hi Carlos, could you help me with a megatec_usb problem? If I use one of thesse options (krauler or agiler) it returns the following: sudo ../bin/megatec_usb -u root -a tsshara -DD [snip] Actually, I'm not of much help in megatec_usb issues, since I'm not the author of that driver. But the people in the know should be reading this. BTW (for the authors of megatec_usb), the banner for megatec_usb only shows my name (from the core/serial layer), when it should also show the authors/maintainers of the USB layer. -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
[Nut-upsuser] energizerups and bestups - megatec?
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 that's not mandatory in megatec (and I'm willing to implement the other command, provided there's someone out there to test it). And there's energizerups... How feasible is it to have megatec_usb obsolete this driver? -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Belkin USB UPSes
On 5/17/07, Eric S. Raymond [EMAIL PROTECTED] wrote: I just bought a pair of Belkin USB UPSes -- F6C1200-UNV and F6C550-AVR -- and installed the latest version of nut under Ubuntu 7.04. I'm using the F6C1200-UNV. If these UPSes have a serial port, they are probably supported by the megatec driver. Over USB, maybe they are supported by the megatec_usb driver that's in the trunk, or the driver can be made to work with them. -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Belkin USB UPSes
On 5/17/07, Eric S. Raymond [EMAIL PROTECTED] wrote: The Ubuntu package of nut-2.0.4 that I've installed has a megatec driver (written by you, I notice) but no megatec_usb. I take it this means I'll need to build with SVN trunk? Yes, that driver is quite new and hasn't made it into a stable release yet. I'm not the megatec_usb maintainer though, so I can't be of much help there, but I'm CC:ing the dev list, the right people should be reading that at least. -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] hardened kernel and nut access to ttyS
On 5/8/07, Vieri [EMAIL PROTECTED] wrote: However, I just built a hardened kernel on a new gentoo machine and have no experience with it. NUT (upsdrv) is failing because it says it doesn't have permission to access ttyS0 even though nut is within the appropriate group. I can add user = root in ups.conf but I'd rather not. Does someone have experience with hardened kernels? Define hardened. Are we talking about something like SELinux or AppArmor here? -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Re: Sweex UPS 500VA and NUT problem
Arjan DJ wrote: I have only one problem: when I'm really using the UPS (upsc shows OB) my PC just turns off after a couple of minutes (ungracefully!). The UPS just turns off and so does the PC. The serial cable/etc is all OK. This seems like a problem with the UPS itself. To know for sure, just stop NUT (make sure the driver isn't running, etc) and disconnect the UPS from the wall. If the UPS still dies off after a few minutes, then there's something wrong with the UPS and it isn't anything the driver is doing. It's best to try this with the UPS powering something else other than your computer, like a light bulb. However, a light bulb might end up not causing this behavior (I had a Mustek powermust that had this problem, it would die off when powering the computer and disconnected from the wall, but otherwise worked fine when connected to a light bulb). -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
[Nut-upsuser] Re: Mustek PowerMust 2000VA via USB
On 2/27/07, Markus Layr [EMAIL PROTECTED] wrote: do you now if there is a possibility to get an connection betwenn nut an the Mustek PowerMust 2000VA via USB? I tried if with newhidups but I always got No matching HID UPS found. In the latest development version of NUT there's a new driver called megatec_usb that may support your UPS. If it doesn't, support may be added if you care to help with some information. I'm sending this reply to the NUT user's mailing-list also, you may want to subscribe to it. -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
[Nut-upsuser] Re: NUT on FreeBSD
fileserver# /usr/local/etc/nut/bin/upsdrvctl start Network UPS Tools - UPS driver controller 2.0.5 Network UPS Tools - Megatec protocol driver 1.5 (2.0.5) Carlos Rodrigues (c) 2003-2006 Can't uu_lock cuad1: creat error: Permission denied Driver failed to start (exit status=1) Have you tried starting the driver without using upsdrvctl? Like this: megatec -a QP1000 -DDD -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] sweex 1000VA LB OB issue
On 1/28/07, Udo van den Heuvel [EMAIL PROTECTED] wrote: Did you try the Powermust driver? It works OK with my Sweex 800VA UPSses. In recent versions it's megatec. PS: why isn't reply-to set for NUT's lists? I keep forgetting and replying only to the original poster instead of the list. -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] NUT on VMWare ESX?...
On 1/18/07, Steve Loughran [EMAIL PROTECTED] wrote: Hi Having used NUT for many years (Irix/Linux/Solaris/win32), but only used VMWare ESX v3 for about 4 weeks, what scripted command are you telling NUT to run to tell ESX to shutdown/suspend the VMs before it really powers itself down? (Not sure calling shutdown would be such a good idea :) I've never used ESX, but on GSX and now the new VMware Server, what happens to the VMs when VMware stops is defined per-VM, in their settings panel. The VM can be powered off (default), suspended or gracefully shutdown. -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
[Nut-upsuser] Re: [Nut-upsdev] megatec driver and usb-to-serial converters
On 11/2/06, Peter Selinger [EMAIL PROTECTED] wrote: All the serial over USB devices that I have seen have used a manufacturer-specific hack. So connecting to a USB device should not usually be as simple as connecting to /dev/something. I was under that impression too, but I saw a discussion about UMTS/3G cards under Linux where it was mentioned that they most of them used a regular serial-to-usb converter, which just wasn't recognized by the kernel and required those two parameters to usbserial, so I thought hey, maybe this works for USB UPSes too! -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Re: [Nut-upsdev] megatec driver and usb-to-serial converters
On 11/2/06, Doug Reynolds [EMAIL PROTECTED] wrote: I not sure if this helps, but Windows XP automatically supports serial to USB cables without installing any additional drivers.. There is probably some kind of spec... good luck finding it though. AFAIK, both Windows and Linux have a similar level of support for these devices, in both cases there are a set of them which have their IDs already listed, there are others that aren't recognized because their IDs are not yet listed, and there are others yet which really need special drivers/hardware specific hacks. -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Re: Kebo UPS-600A and Kebo UPS-1200M setup
Try running megatec -DDD -a yourups and send me the output. Showing 0% for the load is very strange. Unless you mean charge, in which case it means the driver doesn't know how to calculate it for your model (I can fix that, by looking at the output of the above mentioned command). On 9/24/06, Sergiy Kazakov [EMAIL PROTECTED] wrote: 2. Kebo UPS-1200M Driver: fentonups Config extras: none Note: Looks like twin brother of Microlab UPS-1200M :) Driver ask me to report ID string: Unknown ups - please report this ID string: #KEBOUPS-1200M VER3.1C Sorry, but i don't know where I should send this one If you are using a recent enough version of nut, try using the megatec driver instead of fentonups. Thanks. Looks like it works, but I've got strange readings from driver: 20060924 233643 0.0 226.0 0.0 [OFF] 0.0 50.0 According that logline, my UPS is in shutdown state (upsc shows the same), but UPS works fine. With using 'fentonups' it's works good: 20060924 233653 100.0 226.0 000 [OL] NA 50.0 and it manage all events correctly (OL/OB/LB state, SD command). Except, maybe, LOAD value: in both cases it shows 0% insted of 30% - probable consumption of connected server. But this is not important for my case. I can't check other modes (response on OB==OL, LB state) because it works hard right now. P.S. I'm using NUT from FreeBSD ports collection (recent update is 2006-09-22) and its ver. 2.0.4. Comm vith UPS via RS-232. -- Best regards, Sergiymailto:[EMAIL PROTECTED] -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Kebo UPS-600A and Kebo UPS-1200M setup
On 9/24/06, Sergiy Kazakov [EMAIL PROTECTED] wrote: 2. Kebo UPS-1200M Driver: fentonups Config extras: none Note: Looks like twin brother of Microlab UPS-1200M :) Driver ask me to report ID string: Unknown ups - please report this ID string: #KEBOUPS-1200M VER3.1C Sorry, but i don't know where I should send this one If you are using a recent enough version of nut, try using the megatec driver instead of fentonups. -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] BlueWalker Powerwalker VI Line-Interactive UPS
Try using the serial connection and then the powermust or megatec drivers. On 9/20/06, Michael Helmling [EMAIL PROTECTED] wrote: Hi, I have a small home-use UPS for my home server from powerwalker (http://powerwalker.com/de/index.php?option=com_contenttask=blogcategoryid=63Itemid=106 sorry I only found a german version). It has a USB and a serial connector. lsusb lists it as 06da:0003 Phoenixtec Power Co., Ltd, in /proc/bus/usb/devices it sais Manufacturer=OMRON and Product=USB UPS. The devices isn't listed at the nut homepage, so I started to try the usb drivers. With bcmxcp_usb I get some response: # /etc/init.d/upsdrv start * Starting UPS drivers ... Network UPS Tools - UPS driver controller 2.0.3 Network UPS Tools - BCMXCP UPS driver 0.10 (2.0.3) Can't open POWERWARE USB device, retrying ... Can't open POWERWARE USB device, retrying ... So it seems to be recognized as Powerware device. Permissions shouldn't be the problem, as I updated them and also # upsdrvctl -u root start gives me the same result. I also tried the bestups serial driver, but without luck (do I need some special kernel options for the serial device? Never used that one before). Using nut-2.0.4-r1, the latest in Gentoo portage. I you know any help, I'd appreciate that. However this is only a home-size not-at-all critical thing, so I could live with a 'we've got more serious business to do.' ;) Regards, Michael ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] PowerMust 500
On 8/5/06, Sascha Wildner [EMAIL PROTECTED] wrote: I did what you said. But all I got was: yoyodyne# megatec -a powermust500 -DDD Network UPS Tools - Megatec protocol driver 1.4 (2.0.4) Carlos Rodrigues (c) 2003-2006 [...] My ups.conf: [powermust500] driver = megatec port = /dev/cuaa0 Would trying out the development version make a difference (don't have svn at hand at the moment)? No need to. If you are indeed using the correct serial port, then the UPS doesn't talk the megatec protocol. Maybe it is supported by some other driver, maybe genericups. -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] PowerMust 500
On 8/4/06, Sascha Wildner [EMAIL PROTECTED] wrote: 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. What's the software that comes bundled with it? Is it Commander Pro or WinPower? Are you trying to use it via the serial port or USB? (Only the serial port is supported.) -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] protocol for Surge MAX
That page mentions safenet. You can try the safenet driver to see if it works. On 7/7/06, Brian Read [EMAIL PROTECTED] wrote: I am sorry if this is an FAQ, but there doesn't seem to be searchable archives, and the supported manufacturer's list doesn't include surge master. Google was also not much help. I have just put a Linux box and the customer has a surge max UPS. Anyone any ideas what protocol it uses? There is a Green serial cable. The manufacturers web site is here: http://www.surgemax.net/list_cat.php?category=2 But it isn't much use... -- Cheers Brian Reliable, secure and affordable Office servers using Open Source software http://www.abandonmicrosoft.co.uk ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Negative values for ups.delay.shutdown and ups.delay.start
On 6/28/06, Bruno Wolff III [EMAIL PROTECTED] wrote: I was testing my new MGE Nova 1100 and I am seeing negative numbers for ups.delay.start and ups.delay.shutdown which seems odd, but also seems to be expected according to examples I have found for MGE Systems. Can someone explain or point me to an explanation of what those numbers mean? The short descriptions don't appear to be compatible with negative numbers. I guess it means default. The correct way would be to initialize them to the actual defaults, but maybe they differ from model to model and there's no way to ask the UPS for them. -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
[Nut-upsuser] Setting MGE powershare attributes
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 the UPSes is connected to a SUSE box, and the other to a Debian box. -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Config for powercom 2200
If it doesn't work with megatec, it won't work with fentonups. On 6/8/06, gypsy [EMAIL PROTECTED] wrote: Dan Mahoney, System Admin wrote: Hey all, I've tried some very base configs with the powercom 2200, but I can't seem to get it to work. Has anyone dealt with these UPSes before, or know if they use the standard powercom drivers? I'd be more than happy to allow access to my test system so someone more knowledgeable can take a look (and am also willing to pay something for the solution of said problem.) -Dan Mahoney Need more info. I have a SmartLink that uses PowerCom monitoring software and (so far at least), there is no Nut serial driver that works for it. Try fentonups. What software was supplied with the UPS? Does it work? What message(s) do you get when you run 'upsdrvctl start'? Does the powercom or fentonups driver load in spite of the error(s)? If so, what happens when you run upsd? If that works, what happens when you run upslog? What I'm going to do is to try all the serial drivers again. When I did this the first time, a few actually loaded in spite of error messages. I did not try to run upsd on any of these. 'upsdrvctl stop' failed to kill the serial driver for some. But it may just be that there is a name string expected that is not in the driver, so an error message is generated. In that case, the protocol might still work. I simply have not had time to fsck with it because trying different serial drivers is time consuming and tedious. There oughtta be a better way... Another user suggested Nut 2.1 version using the megatec driver, but my SmartLink does not speak any protocol that megatec knows. -- gypsy ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
[Nut-upsuser] Re: NUT mustek UPS driver (fwd)
Ok. Now I need to know what voltage the UPS reports when it is at 100% capacity, and also the voltate reported when it goes into low battery. On 5/30/06, Alexander Kostadinov [EMAIL PROTECTED] wrote: Hallo again. Below I give you the information you told me to give. I just want ot mantion that 2,31V should be the voltage of the battery cells. One friend told me that it should be 1,2V so every battery should be 12V and the the 3 batteries in the unit should be 36V. (The UPS has 3 batteries of 12V - explained in the documentation). The mustek driver works fine but gives wrong battery capacity percents because it also expects battery but not cell voltage. On Fri, 26 May 2006, Carlos Rodrigues wrote: 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 - -a the_name_for_your_ups (this without starting NUT normally - i.e. without upsd, upsmon, etc) and send me the output? Here is the web page: http://www.mustek.de/eng_/html/produkte/ups1000online.htm I paste here the output from the command: debug level is '4' Starting UPS detection process... Attempting to detect the UPS... Sending F command... F command successful. Sending Q1 command... Q1 command successful. Attempting to detect the UPS... Sending F command... F command successful. Sending Q1 command... Q1 command successful. Attempting to detect the UPS... Sending F command... F command successful. Sending Q1 command... Q1 command successful. Attempting to detect the UPS... Sending F command... F command successful. Sending Q1 command... Q1 command successful. Attempting to detect the UPS... Sending F command... F command successful. Sending Q1 command... Q1 command successful. 0 out of 5 detection attempts failed (minimum failures: 2). Asking for UPS information (I command)... UPS doesn't return any information about itself. Megatec protocol UPS detected. Asking for UPS power ratings (F command)... UPS power ratings: 220.0 005 036.0 50.0 Asking for UPS status (Q1 command)... UPS status: 226.5 227.9 221.0 031 50.0 2.31 25.0 0001 This UPS has an unsupported combination of battery voltage/number of batteries. The battery.charge value will be bogus. Done setting up the UPS. Asking for UPS status (Q1 command)... UPS doesn't return any information about its status. dstate_init: sock /var/state/ups/D3_main open on fd 5 Asking for UPS status (Q1 command)... UPS doesn't return any information about its status. Asking for UPS status (Q1 command)... UPS doesn't return any information about its status. Asking for UPS status (Q1 command)... The output should help me figure out why you are getting data stale (may be a timing issue). Also, can you point me to the mustek product page for that UPS? On 5/26/06, Alexander Kostadinov [EMAIL PROTECTED] wrote: Hallo again. I just wrote you and just found the Megatec protocol page. 2.31 must be the cell power but I think here it is too high (should be 1). And how could I know the nominal,min and max power? Just to say I tried the latest 2.1 code and the megatec driver, but it also reports stale data... -- Carlos Rodrigues -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] VMARK ups
Like the last time, I need to know the voltage at the low battery transition. On 4/26/06, lonely wolf [EMAIL PROTECTED] wrote: Hi again I have just found another UPS which I guess that could be supported by the megatec driver. It is described at http://www.vmarkpower.com/diyhp/7558/enus/p-AAAV+EAAhAAAcGXAAW/Uninterruptible_Power_Supply.html megatec -DDD with almost no load : http://wdl.lug.ro/vmark/megatec.debug megatec -DDD at 40% load, 100% charged: http://wdl.lug.ro/vmark/megatec.debug2 Report obtained with the software supplied by the manufacturer, at 40% load, 100% charged: http://wdl.lug.ro/vmark/vmark.status Do you think that nut can be updated to support this fine Chinese product ? Regards manuel -- Manuel Wolfshant linux registered user #131416 IT managerNoBug Consulting Romania http://www.brainbench.com/transcript.jsp?pid=40317 ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Ablerex MARS
It was a silly bug, I've fixed it, should work now. On 4/22/06, lonely wolf [EMAIL PROTECTED] wrote: On 04/22/2006 07:41 PM, Carlos Rodrigues wrote: Right now megatec just calculates a linear approximation. It doesn't give accurate values, but it is enough to have a fuzzy idea of the charge left (like saying it's almost noon instead of it's 12:45), and I'm not seeing how to plot a more accurate charge that fits all the models that megatec is supposed to support (especially given I'm no electrical engineer). Now, I've introduced these values to megatec, and I've commited it to SVN. Can you (not Charles) check if they are acceptable now? Still no go: [EMAIL PROTECTED] ~]# megatec -a ablerex Network UPS Tools - Megatec protocol driver 1.4 (2.1.0) Carlos Rodrigues (c) 2003-2006 Megatec protocol UPS detected [Ablerex MS3000RT MS02035C]. This UPS has an unsupported combination of battery voltage/number of batteries. The battery.charge value will be bogus. I have uploaded a new dump of megatec -DDD -a ablerex to http://wdl.lug.ro/ablerex -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Ablerex MARS
On 4/22/06, Peter Selinger [EMAIL PROTECTED] wrote: However, seeing a maximum voltage of 3V on a unit that is nominally 96V seems wrong, even if that is 8 batteries of 12V each. Could there be a conversion error? Perhaps 2.3V should be 23V? It looks strange to me too, but that's actually what the UPS is reporting (judging by the logs). -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] PowerPal (fentonups) readings off
You should try using powermust (or megatec in the development branch) instead of fentonups. On 4/22/06, Criggie [EMAIL PROTECTED] wrote: Hi all - I have recently installed Nut at work, and its running marvellously. Two of my UPSs are cheap powerpal serial units which work with the fentonups driver. The powerpal 660 VA reports a battery of -138.6% and the powerpal 425 reports a battery level of 70.6% Who should I talk with to try and fix these readings? -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Square One QP1010
powermust should support that UPS. Maybe it is connected to a serial port other than the first one? Have you tried /dev/ttyS1? On 4/6/06, Neil Wilson [EMAIL PROTECTED] wrote: Below is my config file. [EMAIL PROTECTED]:/usr/local/ups# cat etc/ups.conf [SquareOne] driver = powermust port = /dev/ttyS0 desc = Square One QP1010 I've tried using the following, and none of them seem to give me anything. powercom,gamatronic,blazer,fentonups and a few others so far. I'm beggining to wonder if I have a faulty UPS, unfortunately, I've never seen the UPS, and I can't guarentee that it's connected properly, as I wasn't the one who connected it because we maintain the server remotely. -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Re: F6H500ukUNV working with fentonups driver
The UPS didn't turn off, but did you try to wait a while? powermust turns off the UPS immediately, but I'm not sure about fentonups now. Some drivers wait a minute before turning the UPS off. On 4/3/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I tested it by pulling the supply to the ups. It got the 'on and then the 'low battery' upsmon then shutdown my system. The ups however remained on. the ups shutoff (hardware ups shutdown) seems not to be working. Carlos might have more ideas on the cause... This might not be a bug - it could be that I reconnected the supply to soon. I say this because I now remember that after testing the shutdown worked the ups remained on so after some time I reconnected the supply and when the ups came back online I turned my pc on. Early on during the boot process the ups clicked and the pc lost power. I checked the ups straight away and it was powered and seemed ok. When my pc lost power I'm sure the ups made a 'switching' sound. -- Patrick ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
[Nut-upsuser] Re: F6H500ukUNV working with fentonups driver
On 4/3/06, Arnaud Quette [EMAIL PROTECTED] wrote: The Belkin is connected using the serial cable but this is through a usb/serial convertor. so the port is /dev/ttyUSB0 The fentonups driver identifies the Belkin as 'BELKIN PowerPure aster' (Not a mis-type it is 'aster') probably a fentonups bug (I've previously seen that kind of truncation...) The identification string has fields with a fixed number of characters (space filled), maybe fentonups is just splitting them wrong. Anyway - I just wanted to let you know and also thankyou for you work on nut. as there are chances that the fentonups will also be replaced by the megatec driver, can you give a try to it with the NUT 2.1 in subversion: http://eu1.networkupstools.org/source.html @Carlos: can you check to update the compat list, and further testing with Patrick? Patrick, can you try the powermust driver? Maybe it calculates the battery charge better (if it doesn't, you can send me the output of upsc when the UPS is fully charged, and when it hits low battery). -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
[Nut-upsuser] Re: POWER WALKER LINE-INTERACTIVE VI1000
Megatec v1.4 already has manufacturer and model autodetection. The
output showing unknown means the UPS doesn't provide any information
whatsoever. The only way around this is by adding mfr = Manufacturer
and model = Model manually to ups.conf.
On 3/29/06, Arnaud Quette [EMAIL PROTECTED] wrote:
thanks for the feedback Mathias.
Note that the megatec unknown ups.{mfr,model} is under resolution by
Carlos, so he might ask your for further testing...
--
Carlos Rodrigues
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
[Nut-upsuser] Re: POWER WALKER LINE-INTERACTIVE VI1000
Hmmm, there's a problem with this output... the present battery voltage is 26.6 when the nominal value is just 12V. It probably has two separate battery packs... The battery.charge value is therefore bogus (the calculation changes according to battery.voltage.nominal, perhaps I should change this). Could you try the masterguard driver and send me the output of upsc? Megatec is supposed to assimilate masterguard too, so the help would be appreciated. 2006/3/29, Mathias Mayrhofer [EMAIL PROTECTED]: output megatec: (new) === battery.charge: 100.0 battery.voltage: 26.6 battery.voltage.nominal: 12.0 driver.name: megatec driver.parameter.port: /dev/ttyS0 driver.version: 2.1.0 driver.version.internal: 1.4 input.frequency: 49.9 input.voltage: 226.7 input.voltage.fault: 226.7 input.voltage.maximum: 227.2 input.voltage.minimum: 225.8 output.voltage: 226.7 output.voltage.nominal: 230.0 ups.delay.shutdown: 2 ups.delay.start: 3 ups.load: 16.0 ups.mfr: unknown ups.model: unknown ups.serial: unknown ups.status: OL ups.temperature: 25.0 -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
[Nut-upsuser] Re: POWER WALKER LINE-INTERACTIVE VI1000
From that I see you're better off using megatec than masterguard. I'll try to fix the battery charge bug tonight. I'll notify you when it has been commited to the SVN repository. On 3/29/06, Mathias Mayrhofer [EMAIL PROTECTED] wrote: I'm sure, it has two batteries! output as follows: startup: == Network UPS Tools - UPS driver controller 2.1.0 Network UPS Tools - MASTERGUARD UPS driver 0.23 (2.1.0) Found Q1 WH says WH with length 2 New WH String found. Please report to maintainer : Success Found Q1 WH says WH with length 2 New WH String found. Please report to maintainer : Success MASTERGUARD UPS found update info Q1 Buffer is : 225.8 225.8 225.8 016 49.9 26.0 25.0 1001 value=225.8 value=225.8 value=225.8 value=016 value=49.9 value=26.0 value=25.0 value=1001 Status is OL upsc: battery.voltage: 26.0 driver.name: masterguard driver.parameter.port: /dev/ttyS0 driver.version: 2.1.0 driver.version.internal: 0.23 input.frequency: 49.9 input.voltage: 225.8 output.voltage: 225.8 ups.load: 016 ups.mfr: MASTERGUARD ups.model: unknown ups.status: OL ups.temperature: 25.0 -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
[Nut-upsuser] Re: PowerWalker UPS - Re-branded Mustek ?
Go for powermust. The mustek driver right now only has a subset of powermust's functionality. As for the output of upslog showing an additional NA for powermust... that's a bug... it should be input.frequency and not output.frequency. :) On 3/27/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hello ! first off, thank you all for making this piece of software. from what i have seen so far this seems to be a really mature and advanced tool for all sorts of UPS models ! I`d like to tell that I own a UPS which isn`t listed on the compatibility list, but seems to be compatible. It is a PowerWalker - see this at http://powerwalker.com/de/index.php?option=com_contenttask=blogcategoryid=63Itemid=106 It was damn cheap and I bought it just for testing, if such cheap UPS would fit to low end needs. From what I can tell for now, i`m quite satisfied - I have a little homeserver running with this for over a year now and it works fine. (From time to time I do a test and plug the cable and all works continues running). The thing that ever annoyed me with this UPS is the big fat java-based control software. Even the agent running on the server is big fat java-crap. A year ago I came across this project and didn`t find my model on the list. I lost interest because of this but now a year later I thought: hey, let`s look again - but still not being listed. On the PowerWalker website, I read that the person behind that company was related to Mustek before - so I thought, that there is a chance that the PowerWalker is a rebranded Mustek. I downloaded the source and grepped it for mustek and saw: hey, there is a driver - so I gave it a try and it really seems that my UPS is a re-branded Mustek. with the mustek driver - upsc gives: battery.charge: 97.5 battery.voltage: 13.6 driver.name: mustek driver.version: 2.0.3 driver.version.internal: 0.2 input.frequency: 50.1 input.voltage: 228.5 output.voltage: 228.5 ups.load: 014 ups.mfr: Mustek ups.model: PowerMust ups.status: OL upslog gives: 20060326 165042 95.0 228.5 013 [OL] NA 50.1 With the powermust driver (tested the next day) i get: battery.charge: 100.0 battery.voltage: 13.7 battery.voltage.nominal: 12.0 driver.name: powermust driver.version: 2.0.3 driver.version.internal: 1.1 input.voltage: 230.7 input.voltage.fault: 230.7 input.voltage.maximum: 231.1 input.voltage.minimum: 230.7 output.frequency: 50.1 output.voltage: 230.7 output.voltage.target.battery: 220.0 ups.delay.shutdown: 2 ups.delay.start: 3 ups.load: 13.0 ups.mfr: Mustek ups.model: PowerMust ups.serial: unknown ups.status: OL upslog gives: 20060327 194453 100.0 230.7 13.0 [OL] NA NA I didn`t have time to do in-depth test, but I think this UPS will probably work fine with this software. Does somebody own a PowerWalker and can acknowledge this? What additional tests should I do to make sure compatibility is sufficient ? For example, i`m unsure what driver should I use - I thought sure - take powermust - but why does upslog show less information than with mustek driver (it shows two fields NA) ? Anyway - i`m happy that I seem to have native linux support for my UPS now. regards roland k. systems engineer ps: Furthermore, there seems some inconsistency between driver.list and website: # Network UPS Tools driver.list # # This file is used to build the compat.html on the web server. Any line # with exactly 4 arguments will be turned into an entry on there. # Naturally, it is read by parseconf, so the usual escaping tricks are # allowed if you need to insert something unusual. Is compat.html really built from this file or is this just outdated information ? For example, I don`t find information about the fact, that Mustek UPS is known to NUT. (BTW: can NUT do autodetection? this should help others who donŽt have such luck or which are not happy to do experiments) pps: sorry for crossposting - but i thought this was probably of interest for both users and developers - and since traffic isn`t very high.. __ XXL-Speicher, PC-Virenschutz, Spartarife mehr: Nur im WEB.DE Club! Jetzt gratis testen! http://freemail.web.de/home/landingpad/?mc=021130 -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
