search for: logmax

I've acquired and installed NUT 2.4.1 on a D-Link DNS323 NAS. With exception of Load and Battery Temp readings all works well. A upsc ups at localhost command returns; battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 50 battery.date: 2001/09/25 battery.mfr.date: 2008/06/05 battery.runtime: 2122 battery.runtime.low: 120 battery.temperature: 3022999999999998800 battery.type:

Hello i tried to connect my netys 2000 pr ups to ubuntu 11.10 and i have a problem connecting it. After readin a few post i realized to dianosse the connection. I need help resolving the connextion issue So here is the response to??/lib/nut/usbhid-ups -u root -DDDDD -a netys: Network UPS Tools - Generic HID driver 0.35 (2.6.1) USB communication driver 0.31 ? ?0.000000 ? ? send_to_all: SETINFO

...Setting mode to netserver... [17:19:13] INFO: Generating /etc/nut/upsd.users... [17:19:14] INFO: Configuring user: Raul [17:19:17] INFO: Password is NOT in the Have I Been Pwned database! Nice! [17:19:20] INFO: Configuring Device named EPYC... [17:19:21] INFO: Starting the UPS drivers... HIDParse: LogMax is less than LogMin. Vendor HID report descriptor may be incorrect; interpreting LogMax -1 as 65535 in ReportID: 0x0f Network UPS Tools - Generic HID driver 0.47 (2.8.0) HIDParse: LogMax is less than LogMin. Vendor HID report descriptor may be incorrect; interpreting LogMax -1 as 255 in ReportID: 0...

Hello I have a time-comsuming program which need to simplify, I have tested the annotated program as follow: > #define function which will be call > calsta <- function(c, n=100000) + { + i <- seq(from=0, length=c) + logx <- lchoose(NT-n, CT-i) + lchoose(n, i) + logmax <- max(logx) + logmax + log(sum(exp(logx - logmax))) + } > CT=6000 #assignment to CT > NT=29535210 #assignment to NT > > vec<-c(2331,524,918,218,1100,547,289,1167,450,1723) > vec [1] 2331 524 918 218 1100 547 289 1167 450 1723 > vec<-rep(vec,1000)#replicate t...

...problem i<-0:(c-1) vec<-choose(n,i)*choose(NT-n,CT-i) #get the vector which need summation result<-log(sum(vec)) #get the log of summation # thanks to Petr, we have a solution calsta <- function(c, n) { i <- seq(from=0, length=c) logx <- lchoose(NT-n, CT-i) + lchoose(n, i) logmax <- max(logx) logmax + log(sum(exp(logx - logmax))) } # now, new problem arise, in theory, the "result" of different (c,n) pair should most probably differ, so I can order them, but > calsta(918,100000)-calsta(718,100000) [1] 0 > calsta(718,90000)-calsta(718,90000) [1] 0 >...

...lookup_usage: UPS -> 00840004 0.624002 hid_lookup_usage: PowerSummary -> 00840024 0.624002 hid_lookup_usage: RemainingCapacityLimit -> 00850029 0.624002 string_to_path: depth = 3 0.624002 Report[buf]: (2 bytes) => 11 0a 0.624002 PhyMax = 0, PhyMin = 0, LogMax = 100, LogMin = 1 0.624002 Unit = 00000000, UnitExp = 0 0.624002 Exponent = 0 0.624002 Path: UPS.PowerSummary.RemainingCapacityLimit, Type: Feature, ReportID: 0x11, Offset: 0, Size: 8, Value: 10 0.624002 send_to_all: SETINFO battery.charge.low "10" 0.62400...

...mit: 9284) Memory: 1.0M (peak: 1.9M) CPU: 43.317s CGroup: /system.slice/system-nut\x2ddriver.slice/nut-driver at apcupskelder.service ??1141 /lib/nut/usbhid-ups -a apcupskelder nov 01 01:26:40 MinipcLG2 nut-driver at apcupskelder[1068]: HIDParse: LogMax is less than LogMin. Vendor HID report descriptor may be incorrect; interpreting > nov 01 01:26:40 MinipcLG2 nut-driver at apcupskelder[1068]: HIDParse: LogMax is less than LogMin. Vendor HID report descriptor may be incorrect; interpreting > nov 01 01:26:40 MinipcLG2 nut-drive...

...cLG2 (somewhere) (Wed Oct 30 10:27:32 > 2024): > > Communications with UPS apcupskelder at localhost lost > > > Bericht aan allen van root at MinipcLG2 (somewhere) (Wed Oct 30 10:27:32 > 2024): > > Communications with UPS apcupskelder at localhost lost > > HIDParse: LogMax is less than LogMin. Vendor HID report descriptor may be > incorrect; interpreting LogMax -1 as 255 in ReportID: 0x0c > HIDParse: LogMax is less than LogMin. Vendor HID report descriptor may be > incorrect; interpreting LogMax -1 as 255 in ReportID: 0x22 > HIDParse: LogMax is less than...

...other driver! Bericht aan allen van root at MinipcLG2 (somewhere) (Wed Oct 30 10:27:32 2024): Communications with UPS apcupskelder at localhost lost Bericht aan allen van root at MinipcLG2 (somewhere) (Wed Oct 30 10:27:32 2024): Communications with UPS apcupskelder at localhost lost HIDParse: LogMax is less than LogMin. Vendor HID report descriptor may be incorrect; interpreting LogMax -1 as 255 in ReportID: 0x0c HIDParse: LogMax is less than LogMin. Vendor HID report descriptor may be incorrect; interpreting LogMax -1 as 255 in ReportID: 0x22 HIDParse: LogMax is less than LogMin. Vendor HID r...

Hi On 10/06/2014 03:04 PM, Charles Lepple wrote:> I think I see what is going on. > >???? 0.368670??? Report[buf]: (5 bytes) => 05 4e 00 48 00 >???? 0.368698??? PhyMax = 0, PhyMin = 0, LogMax = 1, LogMin = 0 >???? 0.368723??? Unit = 00000000, UnitExp = 0 >???? 0.368747??? Exponent = 0 >???? 0.368776??? Path: UPS.PowerSummary.Voltage, Type: Feature, ReportID: 0x05, Offset: 0, Size: 16, Value: 0 >???? 0.368805??? Input/OutputVoltage = 0 -> assuming correction factor = 1e+07...

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

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

...443 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 = 00000000, UnitExp = 0 > 0.571455 Exponent = 0 > 0.571457 hid_lookup_path: 00840004 -> UPS > 0.571459 hid_lookup_path: 00840024 -> PowerSummary > 0.571461 hid_lookup_path: 00840002 -> PresentStatus &gt...

....mfr and ups.model in upsc. > > And if I run upsd with high level of debug, after working OK for a while, I see these ?broken pipe? messages : > > 0.419974 Entering libusb_get_report > 0.421967 Report[get]: (4 bytes) => 60 c4 ff 3b > 0.422056 PhyMax = 0, PhyMin = 0, LogMax = 16777215, LogMin = 0 > 0.422069 Unit = 00001001, UnitExp = 0 > 0.422080 Exponent = 0 > 0.422093 hid_lookup_path: 00840004 -> UPS > 0.422107 hid_lookup_path: 00840024 -> PowerSummary > 0.422121 hid_lookup_path: 00850068 -> RunTimeToEmpty > 0.422146 Path...

I am looking at the newhid driver for this Pulsar EXtreme here but it gives odd results, for example there is no status variable :) eg debug level is '2' Checking device (0463/FFFF) (/dev/usb0//dev/ugen0) - VendorID: 0463 - ProductID: ffff - Manufacturer: unknown - Product: unknown - Serial Number: unknown - Bus: /dev/usb0 Trying to match device Device matches HID descriptor retrieved

...rocessed, but with uncorrect parameters: 55.348163 instcmd(shutdown.return, 30) 55.348205 powercom_shutdown_nuf: value = 30, command = 5E00 55.348218 hu_find_valinfo: found 24064 (value: 30) 55.348229 Unit = 00000000, UnitExp = 0 55.348239 Exponent = 0 55.348249 PhyMax = 0, PhyMin = 0, LogMax = 65535, LogMin = 0 55.348920 Report[set]: (3 bytes) => 0f 00 5e 55.348945 Set report succeeded 55.348956 instcmd: SUCCEED Value 30 is converted to 24064, and this seems the delay that is configured on the device to complete its shutdown: [...] 56.358009 Path: UPS.PowerSummary.DelayBefo...

...0.278517 hid_lookup_usage: UPS -> 00840004 > 0.278621 hid_lookup_usage: Output -> 0084001c > 0.278769 hid_lookup_usage: Voltage -> 00840030 > 0.278913 string_to_path: depth = 3 > 0.279025 Report[buf]: (3 bytes) => 2b 9e 08 > 0.279133 PhyMax = 0, PhyMin = 0, LogMax = 65535, LogMin = 0 > 0.279240 Unit = 00f0d121, UnitExp = -1 > 0.279304 Exponent = -8 > 0.279412 Path: UPS.Output.Voltage, Type: Feature, ReportID: 0x2b, > Offset: 0, Size: 16, Value: 2.206e-05 > 0.279523 Input/OutputVoltage = 2.206e-05 -> assuming correction factor &g...

...0.278517 hid_lookup_usage: UPS -> 00840004 > 0.278621 hid_lookup_usage: Output -> 0084001c > 0.278769 hid_lookup_usage: Voltage -> 00840030 > 0.278913 string_to_path: depth = 3 > 0.279025 Report[buf]: (3 bytes) => 2b 9e 08 > 0.279133 PhyMax = 0, PhyMin = 0, LogMax = 65535, LogMin = 0 > 0.279240 Unit = 00f0d121, UnitExp = -1 > 0.279304 Exponent = -8 > 0.279412 Path: UPS.Output.Voltage, Type: Feature, ReportID: 0x2b, > Offset: 0, Size: 16, Value: 2.206e-05 > 0.279523 Input/OutputVoltage = 2.206e-05 -> assuming correction factor &g...

...instcmd(shutdown.return, [NULL]) > 0.145767 powercom_shutdown_nuf: value = (null), command = 5400 > 0.145770 hu_find_valinfo: found 21504 (value: (null)) > 0.145773 Unit = 00000000, UnitExp = 0 > 0.145775 Exponent = 0 > 0.145778 PhyMax = 0, PhyMin = 0, LogMax = 65535, LogMin = 0 > 0.155952 Report[set]: (3 bytes) => 0f 00 54 > 0.155981 Set report succeeded > 0.155986 instcmd: SUCCEED > When you attempted the shutdown.return, was the UPS powered or on battery? My older Tripplite SMART2200VS won't shutdown.return unles...

...eturn, [NULL]) > 0.145767 powercom_shutdown_nuf: value = (null), command = 5400 > 0.145770 hu_find_valinfo: found 21504 (value: (null)) > 0.145773 Unit = 00000000, UnitExp = 0 > 0.145775 Exponent = 0 > 0.145778 PhyMax = 0, PhyMin = 0, LogMax = 65535, LogMin = 0 > 0.155952 Report[set]: (3 bytes) => 0f 00 54 > 0.155981 Set report succeeded > 0.155986 instcmd: SUCCEED > > > When you attempted the shutdown.return, was the UPS powered or on > battery? My older Tripplite SMART2200VS won...