search for: batterypresent

I have a new-ish APC Back-UPS XS 1500G connected via USB. It's giving me a "ups.alarm: No battery installed!" error. I also installed and configured apcupsd to give that a try and it's giving me the same error. I suspect this is a driver problem because while NUT claims the battery isn't plugged in, it's giving me battery runtime/charge info. Both can't be valid

...following two are returned with long notification from Back-UPS ES 650 */ + { "ups.status", 0, 1, "UPS.PowerSummary.PresentStatus.RemainingTimeLimitExpired", NULL, + "%.0f", HU_FLAG_OK, NULL }, + { "ups.status", 0, 1, "UPS.PowerSummary.PresentStatus.BatteryPresent", NULL, + "%.0f", HU_FLAG_OK, NULL }, /* Input page */ { "input.voltage", 0, 0, "UPS.Input.Voltage", NULL, "%.1f", HU_FLAG_OK, NULL }, diff -u nut-2.0.2.orig/drivers/newhidups.c nut-2.0.2/drivers/newhidups.c --- nut-2.0.2.orig/drivers/newhidup...

...o be the source of the "no battery" alarm: > 0.571436 hid_lookup_path: 00840004 -> UPS > 0.571438 hid_lookup_path: 00840024 -> PowerSummary > 0.571440 hid_lookup_path: 00840002 -> PresentStatus > 0.571443 hid_lookup_path: 008500d1 -> BatteryPresent > 0.571446 Path: UPS.PowerSummary.PresentStatus.BatteryPresent, Type: Input, ReportID: 0x16, Offset: 3, Size: 1, Value: 0 > 0.571449 Report[buf]: (5 bytes) => 16 04 00 00 00 > 0.571451 PhyMax = 0, PhyMin = 0, LogMax = 1, LogMin = 0 > 0.571453 Unit = 00...

...that newhidups doesn't know what > to do with the variables, although the current change doesn't affect > status evaluation in any way either. Rather than using a NULL item mapping I am now using the hex_conversion mapping to accept the two items: UPS.PowerSummary.PresentStatus.BatteryPresent and UPS.PowerSummary.PresentStatus.RemainingTimeLimitExpired that are however still ignored, as it happened with the 2.0.2 changes. If the experts think it would be worthwhile to actually make the two items available (although they are not particularly useful), please let me know how they migh...

...y.PresentStatus.Charging Path: UPS.PowerSummary.PresentStatus.Charging Path: UPS.PowerSummary.PresentStatus.Discharging Path: UPS.PowerSummary.PresentStatus.Discharging Path: UPS.PowerSummary.PresentStatus.ACPresent Path: UPS.PowerSummary.PresentStatus.ACPresent Path: UPS.PowerSummary.PresentStatus.BatteryPresent Path: UPS.PowerSummary.PresentStatus.BatteryPresent Path: UPS.PowerSummary.PresentStatus.BelowRemainingCapacityLimit Path: UPS.PowerSummary.PresentStatus.BelowRemainingCapacityLimit Path: UPS.PowerSummary.PresentStatus.ShutdownImminent Path: UPS.PowerSummary.PresentStatus.ShutdownImminent Path: UPS...

...y.PresentStatus.Charging Path: UPS.PowerSummary.PresentStatus.Charging Path: UPS.PowerSummary.PresentStatus.Discharging Path: UPS.PowerSummary.PresentStatus.Discharging Path: UPS.PowerSummary.PresentStatus.ACPresent Path: UPS.PowerSummary.PresentStatus.ACPresent Path: UPS.PowerSummary.PresentStatus.BatteryPresent Path: UPS.PowerSummary.PresentStatus.BatteryPresent Path: UPS.PowerSummary.PresentStatus.BelowRemainingCapacityLimit Path: UPS.PowerSummary.PresentStatus.BelowRemainingCapacityLimit Path: UPS.PowerSummary.PresentStatus.ShutdownImminent Path: UPS.PowerSummary.PresentStatus.ShutdownImminent Path: UPS...

Hello, I'm using the stable amd64 port of Debian Linux. I installed (the latest) nut-2.0.1-4 and nut-usb packages for utilizing an APC Smart-UPS 1500 USB. I tried "apcupsd" first but "nut" makes an even more sophisticated impression on me and has more security options. I had problems with the newhidups driver. It didn't find a device with matching VendorID. And

...the status reversed from what is > specified in the HID PDC specifications (which doesn't surprise me at > all, given the broken battery voltage reporting). > > > 0.350131 Report[buf]: (2 bytes) => 07 0d > > 0.350145 Path: UPS.PowerSummary.PresentStatus.BatteryPresent, Type: > > Feature, ReportID: 0x07, Offset: 3, Size: 1, Value: 0.000000 > > 0.350156 Report[buf]: (2 bytes) => 07 0d > > 0.350170 Path: UPS.PowerSummary.PresentStatus.BatteryPresent, Type: > > Input, ReportID: 0x07, Offset: 3, Size: 1, Value: 0.000000 > &g...

...0.130595 Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Input, ReportID: 0x0a, Offset: 2, Size: 1, Value: 1 0.130600 Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Feature, ReportID: 0x0a, Offset: 2, Size: 1, Value: 1 0.130605 Path: UPS.PowerSummary.PresentStatus.BatteryPresent, Type: Input, ReportID: 0x0a, Offset: 3, Size: 1, Value: 1 0.130610 Path: UPS.PowerSummary.PresentStatus.BatteryPresent, Type: Feature, ReportID: 0x0a, Offset: 3, Size: 1, Value: 1 0.130615 Path: UPS.PowerSummary.PresentStatus.BelowRemainingCapacityLimit, Type: Input, ReportID: 0x...

...= 0, PhyMin = 0, LogMax = 1, LogMin = 0 >???? 0.428240??? Unit = 00000000, UnitExp = 0 >???? 0.428264??? Exponent = 0 >???? 0.428290??? hid_lookup_path: 00840004 -> UPS >???? 0.428316??? hid_lookup_path: 00840024 -> PowerSummary >???? 0.428344??? hid_lookup_path: 008500d1 -> BatteryPresent >???? 0.428373??? Path: UPS.PowerSummary.BatteryPresent, Type: Input, ReportID: 0x0c, Offset: 4, Size: 1, Value: 0 > Yes the presence of the battery isn't reported as i expected. > >>>> (4) would it be useful to add missing items to the driver's hid to nu lookup tab...

...Value: 0.000000 0.577816 Report[buf]: (2 bytes) => 07 0d 0.577828 Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Input, ReportID: 0x07, Offset: 2, Size: 1, Value: 0.000000 0.577837 Report[buf]: (2 bytes) => 07 0d 0.577849 Path: UPS.PowerSummary.PresentStatus.BatteryPresent, Type: Feature, ReportID: 0x07, Offset: 3, Size: 1, Value: 0.000000 0.577858 Report[buf]: (2 bytes) => 07 0d 0.577870 Path: UPS.PowerSummary.PresentStatus.BatteryPresent, Type: Input, ReportID: 0x07, Offset: 3, Size: 1, Value: 0.000000 0.577879 Report[buf]: (2 bytes) => 0...

...Value: 0.000000 0.577816 Report[buf]: (2 bytes) => 07 0d 0.577828 Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Input, ReportID: 0x07, Offset: 2, Size: 1, Value: 0.000000 0.577837 Report[buf]: (2 bytes) => 07 0d 0.577849 Path: UPS.PowerSummary.PresentStatus.BatteryPresent, Type: Feature, ReportID: 0x07, Offset: 3, Size: 1, Value: 0.000000 0.577858 Report[buf]: (2 bytes) => 07 0d 0.577870 Path: UPS.PowerSummary.PresentStatus.BatteryPresent, Type: Input, ReportID: 0x07, Offset: 3, Size: 1, Value: 0.000000 0.577879 Report[buf]: (2 bytes) => 0...

Peter Selinger wrote: > Hm. I need more information, as NUT seems to garble the values even > before I can see them. I am not so worried about the date and > temperatures (although, strangely, the battery replacement date > appears to be Sept 25, 2001, which makes no sense). But the voltage is > definitely important. > > [...] > Thanks Peter - I'll send the new

...0.055360 Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Input, ReportID: 0x16, Offset: 2, Size: 1, Value: 1 > 0.055752 Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Feature, ReportID: 0x16, Offset: 2, Size: 1, Value: 1 > 0.056148 Path: UPS.PowerSummary.PresentStatus.BatteryPresent, Type: Input, ReportID: 0x16, Offset: 3, Size: 1, Value: 1 > 0.056541 Path: UPS.PowerSummary.PresentStatus.BatteryPresent, Type: Feature, ReportID: 0x16, Offset: 3, Size: 1, Value: 1 > 0.056957 Path: UPS.PowerSummary.PresentStatus.BelowRemainingCapacityLimit, Type: Input, ReportID:...

...x0c, Offset: 1, Size: 1, Value: 0 0.009195 Path: UPS.PowerSummary.ACPresent, Type: Feature, ReportID: 0x0c, Offset: 2, Size: 1, Value: 1 0.009226 Path: UPS.PowerSummary.BelowRemainingCapacityLimit, Type: Feature, ReportID: 0x0c, Offset: 3, Size: 1, Value: 0 0.009250 Path: UPS.PowerSummary.BatteryPresent, Type: Feature, ReportID: 0x0c, Offset: 4, Size: 1, Value: 1 0.009274 Path: UPS.PowerSummary.Undefined, Type: Feature, ReportID: 0x0c, Offset: 5, Size: 3, Value: 0 0.009298 Path: UPS.PowerSummary.Charging, Type: Input, ReportID: 0x0c, Offset: 0, Size: 1, Value: 1 0.009334 Path: UPS.Powe...

Hi On 10/03/2014 03:42 PM, Charles Lepple wrote:> On Oct 3, 2014, at 7:50 AM, paul.chavent at fnac.net wrote: > > > This is what I was referring to (from the belkin-hid log): > >???? 1.325782??? Report[buf]: (5 bytes) => 05 53 00 48 00 >???? 1.325799??? Path: UPS.PowerSummary.ConfigVoltage, Type: Feature, ReportID: 0x05, Offset: 16, Size: 16, Value: 0 >????

...60 Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Input, ReportID: 0x16, Offset: 2, Size: 1, Value: 1 >> 0.055752 Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Feature, ReportID: 0x16, Offset: 2, Size: 1, Value: 1 >> 0.056148 Path: UPS.PowerSummary.PresentStatus.BatteryPresent, Type: Input, ReportID: 0x16, Offset: 3, Size: 1, Value: 1 >> 0.056541 Path: UPS.PowerSummary.PresentStatus.BatteryPresent, Type: Feature, ReportID: 0x16, Offset: 3, Size: 1, Value: 1 >> 0.056957 Path: UPS.PowerSummary.PresentStatus.BelowRemainingCapacityLimit, Type: Input, Repo...

...scharging, Type: Feature, > Value: > > 0.000000 > > Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Input, Value: > > 1.000000 > > Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Feature, Value: > > 1.000000 > > Path: UPS.PowerSummary.PresentStatus.BatteryPresent, Type: Input, > Value: > > 1.000000 > > Path: UPS.PowerSummary.PresentStatus.BatteryPresent, Type: Feature, > > Value: 1.000000 > > Path: UPS.PowerSummary.PresentStatus.BelowRemainingCapacityLimit, > Type: > > Input, Value: 0.000000 > > Path: UPS.PowerSumma...

Hello I recently switched from apcupsd to NUT2.2.2 without any troubles. I tried to figure out how I can configure the self-test intervall. The command upsrw lists only the variables battery.charge.low battery.runtime.low ups.delay.shutdown ups.delay.start The command usbhid-ups -D and the listing under http://obsvermes.org/cgi-bin/nut/upsstats.cgi?host=apcsmart at localhost&treemode

On Jan 8, 2015, at 11:43 PM, Graham Menhennitt <graham at menhennitt.com.au> wrote: > Hello Nutters, > > I'm running nut 2.7.2 on FreeBSD 10-stable (via the FreeBSD port) with an APC Back-UPS CS 350 connected via USB. I get persistent (every few minutes) messages logged "battery is low" but I don't understand why. I don't think it's for the reason