Re: [Nut-upsuser] (no subject)
Citeren ahouse-support supp...@ahouse.mine.nu: There simply is no such functionality, or the driver can not read these values because of nesovmestimoti / oschibki? Maybe a fix? Read my reply again. The *UPS* doesn't report battery charge, so the only thing NUT can do is guesstimate this based on other values it reports. And whether further use of the NUT, so that my UPS shut off my server connected to it? Read the documentation. Both the megatec and blazer_ser driver support this. Best regards, Arjen -- Please keep list traffic on the list (off-list replies will be rejected) ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] (no subject)
Citeren ahouse-support supp...@ahouse.mine.nu: # ./nut start Network UPS Tools - UPS driver controller 2.4.1 Network UPS Tools - Megatec/Q1 protocol serial driver 1.51 (2.4.1) Supported UPS detected with megatec protocol Vendor information read in 1 tries Battery runtime will not be calculated (runtimecal not set) = !!! RTFM - 'man 8 blazer'. backup# upsc power...@localhost battery.voltage: 28.80 = !!! it is a normal? what u thing about this value?? iam have 4x7AH battery in Ups This boils down to about 2.4 V / cell, which is fairly high for a PbAc battery. But please understand that a UPS is not a measuring instrument. More often than not, the reported resolution is much more than the accuracy of the measurement justifies. So unless your batteries wear out quickly, you can safely ignore this. Best regards, Arjen -- Please keep list traffic on the list (off-list replies will be rejected) ___ 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] (no subject)
I tried to run newhidups myself with the debugging messages turned on and I got the following response: debug level is '4' Checking device (/) (003/001) - VendorID: - ProductID: - Manufacturer: unknown - Product: unknown - Serial Number: unknown - Bus: 003 Trying to match device Device does not match - skipping Checking device (0463/) (002/002) - VendorID: 0463 - ProductID: - Manufacturer: unknown - Product: unknown - Serial Number: unknown - Bus: 002 Trying to match device Device matches failed to claim USB device, trying 2 more time(s)... detaching kernel driver from USB device... failed to detach kernel driver from USB device... trying again to claim USB device... failed to claim USB device, trying 1 more time(s)... detaching kernel driver from USB device... failed to detach kernel driver from USB device... trying again to claim USB device... failed to claim USB device, trying 0 more time(s)... detaching kernel driver from USB device... failed to detach kernel driver from USB device... trying again to claim USB device... Unable to get HID descriptor (error sending control message: Operation not permitted) Checking device (/) (002/001) - VendorID: - ProductID: - Manufacturer: unknown - Product: unknown - Serial Number: unknown - Bus: 002 Trying to match device Device does not match - skipping Checking device (/) (001/001) - VendorID: - ProductID: - Manufacturer: unknown - Product: unknown - Serial Number: unknown - Bus: 001 Trying to match device Device does not match - skipping No appropriate HID device found Network UPS Tools: New USB/HID UPS driver 0.28 (2.0.3) No matching USB/HID UPS found It seems like the kernel might already have a driver loaded, but I am not that familiar with the USB system. Thanks Michael Hill [EMAIL PROTECTED] -Original Message- From: Charles Lepple [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 15, 2006 5:41 PM To: Mike Hill Cc: nut-upsuser@lists.alioth.debian.org Subject: Re: [Nut-upsuser] (no subject) On 11/15/06, Mike Hill [EMAIL PROTECTED] wrote: I have installed the NUT 2.0.3 RPM for Fedora Core 4 and I have it working with an MGE Pulsar Evolution 500, but I cannot get the USB interface to work. When I plug in the USB cable I get the following message in my system log: kernel: usbhid: probe of 2-1:1.0 failed with error -5 actually, this part is normal. The device is blacklisted from the kernel usbhid driver so that it can be claimed in userspace by newhidups. Did you see any error messages from the driver or other NUT components? -- - Charles Lepple ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] (no subject)
Mike Hill wrote: I have installed the NUT 2.0.3 RPM for Fedora Core 4 and I have it working with an MGE Pulsar Evolution 500, but I cannot get the USB interface to work. When I plug in the USB cable I get the following message in my system log: kernel: usbhid: probe of 2-1:1.0 failed with error -5 Any ideas? If you want to use USB with NUT, you need to install the latest development version. The newhidups driver is very much 'work in progress' and a lot of problems from earlier versions have been fixed by now. Having said that, your UPS should be supported through the USB port then. Kind regards, Arjen ___ 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 11/15/06, Mike Hill [EMAIL PROTECTED] wrote: I have installed the NUT 2.0.3 RPM for Fedora Core 4 and I have it working with an MGE Pulsar Evolution 500, but I cannot get the USB interface to work. When I plug in the USB cable I get the following message in my system log: kernel: usbhid: probe of 2-1:1.0 failed with error -5 actually, this part is normal. The device is blacklisted from the kernel usbhid driver so that it can be claimed in userspace by newhidups. Did you see any error messages from the driver or other NUT components? -- - Charles Lepple ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
