search for: designcapac

...2014, at 10:03 AM, ??????? ??????? <freemgm at gmail.com> wrote: > > Any news? > > Send dubug with explore one more time > in attach > > > Unless I am mistaken, there is no new information in the latest debug > output. > > One odd thing in the HID dump is that DesignCapacity appears twice, with > very different values: > > Path: UPS.BatterySystem.Battery.*DesignCapacity*, ReportID: 0x23, Offset: > 0, Size: 32, Value: 18000 > ... > Path: UPS.PowerSummary.CapacityGranularity1, ReportID: 0x0c, Offset: 0, > Size: 8, Value: 1 > Path: UPS.PowerSumm...

Any news? Send dubug with explore one more time in attach 19.12.2014 15:39, Charles Lepple ?????: > On Dec 19, 2014, at 5:16 AM, ??????? ??????? <freemgm at gmail.com> wrote: > >> # /usr/local/libexec/nut/usbhid-ups -DD -a eaton9sx -u root -x explore -x vendorid=0x0463 2>&1 | tee /tmp/eaton9sx-explore.log > Ah, I forgot about the vendorid. The string is a regex which

...---------------------------------------------- */ > > static hid_info_t jundatech_hid2nut[] = { > > { "unmapped.ups.powersummary.capacitymode", 0, 0, > "UPS.PowerSummary.CapacityMode", NULL, "%.0f", 0, NULL }, > { "unmapped.ups.powersummary.designcapacity", 0, 0, > "UPS.PowerSummary.DesignCapacity", NULL, "%.0f", 0, NULL }, > { "unmapped.ups.powersummary.fullchargecapacity", 0, 0, > "UPS.PowerSummary.FullChargeCapacity", NULL, "%.0f", 0, NULL }, > { "unmapped.ups.powersum...

...s.belkinbatterystatus: 00000010 zzz.ups.belkinstatus.belkinpowerstatus: 0000c000 zzz.ups.powersummary.capacitygranularity1: 1 zzz.ups.powersummary.capacitygranularity2: 1 zzz.ups.powersummary.capacitymode: 2 zzz.ups.powersummary.configvoltage: 12 zzz.ups.powersummary.current: 0 zzz.ups.powersummary.designcapacity: 100 zzz.ups.powersummary.fullchargecapacity: 100 zzz.ups.powersummary.ioeminformation: Belkin zzz.ups.powersummary.iproduct: UPS zzz.ups.powersummary.rechargeable: 1 zzz.ups.powersummary.remainingcapacity: 100 zzz.ups.powersummary.voltage: 136 It seems the ups.status doesn't show OL here,...

Hi, I have an UPS with only the marking D1000 on it and it came with Junda-Tech's UpsMate. Its USB id is 3344:0025, which is apparently a microprocessor. I've could get some of the HID interactions as described on the website, but there are some outstanding. Junda-Tech does not respond to any queries. Does anybody else have the same or a similar UPS with more information? What is the

...ype: Feature, Value: 2.000000 Path: UPS.BatterySystem.Battery.BatteryID, Type: Feature, Value: 2.000000 Path: UPS.BatterySystem.Battery.Count, Type: Feature, Value: 2.000000 Path: UPS.BatterySystem.Battery.DeepDischargeProtection, Type: Feature, Value: 2.000000 Path: UPS.BatterySystem.Battery.DesignCapacity, Type: Feature, Value: 2.000000 Path: UPS.BatterySystem.Battery.PresentStatus.Present, Type: Feature, Value: 2.000000 Path: UPS.BatterySystem.Battery.PresentStatus.Present, Type: Input, Value: 2.000000 Path: UPS.BatterySystem.Battery.Test, Type: Feature, Value: 2.000000 Path: UPS.BatterySy...

...ts are percent) then battery.charge = RemainingCapacity battery.charge.low, restart = RemainingCapacityLimit battery.charge.warning = WarningCapacityLimit if CapacityMode == 0 (units are in mAh) then battery.capacity = RemainingCapacity battery.capacity.nominal = FullChargeCapacity (or DesignCapacity) Note that in each case some things are left out. I didn't see a battery.capacity.low or warning, which is probably ok because the time remaining HID objects should give a similar set of behavior? Looking at the existing drivers, it feels like most people use capacity as a percent. It make...

...th: UPS.PowerSummary.iDeviceChemistry, Type: Feature, Value: 4.000000 Path: UPS.PowerSummary.iOEMInformation, Type: Feature, Value: 3.000000 Path: UPS.PowerSummary.Rechargeable, Type: Feature, Value: 1.000000 Path: UPS.PowerSummary.CapacityMode, Type: Feature, Value: 2.000000 Path: UPS.PowerSummary.DesignCapacity, Type: Feature, Value: 100.000000 Path: UPS.PowerSummary.CapacityGranularity1, Type: Feature, Value: 5.000000 Path: UPS.PowerSummary.CapacityGranularity2, Type: Feature, Value: 10.000000 Path: UPS.PowerSummary.WarningCapacityLimit, Type: Feature, Value: 20.000000 Path: UPS.PowerSummary.Remaining...

...Offset: 0, Size: 8, Value: 1.000000 Path: UPS.BatterySystem.Battery.Count, Type: Feature, ReportID: 0x21, Offset: 0, Size: 8, Value: 1.000000 Path: UPS.BatterySystem.Battery.DeepDischargeProtection, Type: Feature, ReportID: 0x22, Offset: 0, Size: 8, Value: 1.000000 Path: UPS.BatterySystem.Battery.DesignCapacity, Type: Feature, ReportID: 0x23, Offset: 0, Size: 32, Value: 97200.000000 Path: UPS.BatterySystem.Battery.PresentStatus.Present, Type: Feature, ReportID: 0x27, Offset: 0, Size: 8, Value: 1.000000 Path: UPS.BatterySystem.Battery.PresentStatus.Present, Type: Input, ReportID: 0x27, Offset: 0, Siz...

...Conversion/Smart-UPS 3000 RM FW:666.6.D USB FW:2.4 Path: UPS.PowerSummary.iSerialNumber Path: UPS.PowerSummary.iManufacturer Path: UPS.PowerSummary.iOEMInformation Path: UPS.PowerSummary.iDeviceChemistry Path: UPS.PowerSummary.Rechargeable Path: UPS.PowerSummary.CapacityMode Path: UPS.PowerSummary.DesignCapacity Path: UPS.PowerSummary.FullChargeCapacity Path: UPS.PowerSummary.RemainingCapacity Path: UPS.PowerSummary.RemainingCapacity Path: UPS.PowerSummary.CapacityGranularity1 Path: UPS.PowerSummary.CapacityGranularity2 Path: UPS.PowerSummary.WarningCapacityLimit Path: UPS.PowerSummary.RemainingCapacity...

...th: UPS.PowerSummary.iDeviceChemistry, Type: Feature, Value: 4.000000 Path: UPS.PowerSummary.iOEMInformation, Type: Feature, Value: 3.000000 Path: UPS.PowerSummary.Rechargeable, Type: Feature, Value: 1.000000 Path: UPS.PowerSummary.CapacityMode, Type: Feature, Value: 2.000000 Path: UPS.PowerSummary.DesignCapacity, Type: Feature, Value: 100.000000 Path: UPS.PowerSummary.CapacityGranularity1, Type: Feature, Value: 5.000000 Path: UPS.PowerSummary.CapacityGranularity2, Type: Feature, Value: 10.000000 Path: UPS.PowerSummary.WarningCapacityLimit, Type: Feature, Value: 20.000000 Path: UPS.PowerSummary.Remaining...

Kelly Byrd <kbyrd at memcpy.com> writes: > Making progress on this PR. I have question about storing and checking > state in a subdriver > HID Power Devices can a "UPS.PowerSummary.CapacityMode" value. According to > the spec, the values are: > 0: maH > 1: mwH > 2: percent (%) > 3: Boolean support only (OK or failed) > > Grep'ing the source,

....ConfigVoltage Path: UPS.PowerSummary.Voltage Path: UPS.PowerSummary.iManufacturer Path: UPS.PowerSummary.CapacityMode Path: UPS.PowerSummary.RemainingCapacity Path: UPS.PowerSummary.RemainingCapacity Path: UPS.PowerSummary.RunTimeToEmpty Path: UPS.PowerSummary.RunTimeToEmpty Path: UPS.PowerSummary.DesignCapacity Path: UPS.PowerSummary.FullChargeCapacity Path: UPS.PowerSummary.WarningCapacityLimit Path: UPS.PowerSummary.CapacityGranularity2 Path: UPS.PowerSummary.RemainingCapacityLimit Path: UPS.PowerSummary.CapacityGranularity1 Path: UPS.PowerSummary.PresentStatus.Charging Path: UPS.PowerSummary.Present...

...ot;, 0, 0, "UPS.PowerSummary.ConfigVoltage", NULL, NULL, HU_FLAG_QUICK_POLL, openups_vbat_info }, */ {"battery.current", 0, 0, "UPS.PowerSummary.Current", NULL, "%.3f", HU_FLAG_QUICK_POLL, NULL}, {"battery.capacity", 0, 0, "UPS.PowerSummary.DesignCapacity", NULL, "%.0f", HU_FLAG_STATIC, NULL}, @@ -320,14 +358,6 @@ static hid_info_t openups_hid2nut[] = { {"battery.cell5.voltage", 0, 0, "UPS.PowerSummary.Battery.Cell5", NULL, NULL, HU_FLAG_QUICK_POLL, openups_vbat_info}, {"battery.cell6.voltage", 0,...

...XPLORE HID 0.1 3.323850 Path: UPS.BatterySystem.Battery.BatteryID, Type: Feature, ReportID: 0x20, Offset: 0, Size: 8, Value: 1 3.351148 Path: UPS.BatterySystem.Battery.ffff0090, Type: Feature, ReportID: 0x21, Offset: 0, Size: 8, Value: 0 3.384713 Path: UPS.BatterySystem.Battery.DesignCapacity, Type: Feature, ReportID: 0x23, Offset: 0, Size: 32, Value: 32400 3.418080 Path: UPS.BatterySystem.Battery.PresentStatus.Present, Type: Feature, ReportID: 0x27, Offset: 0, Size: 8, Value: 1 3.419506 Path: UPS.BatterySystem.Battery.PresentStatus.Present, Type: Input, ReportID: 0x27,...

....ConfigVoltage Path: UPS.PowerSummary.Voltage Path: UPS.PowerSummary.iManufacturer Path: UPS.PowerSummary.CapacityMode Path: UPS.PowerSummary.RemainingCapacity Path: UPS.PowerSummary.RemainingCapacity Path: UPS.PowerSummary.RunTimeToEmpty Path: UPS.PowerSummary.RunTimeToEmpty Path: UPS.PowerSummary.DesignCapacity Path: UPS.PowerSummary.FullChargeCapacity Path: UPS.PowerSummary.WarningCapacityLimit Path: UPS.PowerSummary.CapacityGranularity2 Path: UPS.PowerSummary.RemainingCapacityLimit Path: UPS.PowerSummary.CapacityGranularity1 Path: UPS.PowerSummary.PresentStatus.Charging Path: UPS.PowerSummary.Present...

....ConfigVoltage Path: UPS.PowerSummary.Voltage Path: UPS.PowerSummary.iManufacturer Path: UPS.PowerSummary.CapacityMode Path: UPS.PowerSummary.RemainingCapacity Path: UPS.PowerSummary.RemainingCapacity Path: UPS.PowerSummary.RunTimeToEmpty Path: UPS.PowerSummary.RunTimeToEmpty Path: UPS.PowerSummary.DesignCapacity Path: UPS.PowerSummary.FullChargeCapacity Path: UPS.PowerSummary.WarningCapacityLimit Path: UPS.PowerSummary.CapacityGranularity2 Path: UPS.PowerSummary.RemainingCapacityLimit Path: UPS.PowerSummary.CapacityGranularity1 Path: UPS.PowerSummary.PresentStatus.Charging Path: UPS.PowerSummary.Present...

...{ "PowercomDelayBeforeShutdown", 0x00020057 }, { "PowercomTest", 0x00020058 }, { "PowercomShutdownRequested", 0x00020068 }, { "PowercomInternalChargeController", 0x00020081 }, { "PowercomPrimaryBatterySupport", 0x00020082 }, { "PowercomDesignCapacity", 0x00020083 }, { "PowercomSpecificationInfo", 0x00020084 }, { "PowercomManufacturerDate", 0x00020085 }, { "PowercomSerialNumber", 0x00020086 }, { "PowercomManufacturerName", 0x00020087 }, { "\0", 0x0 } }; static usage_tables_t p...

...40, Offset: 14, Size: 1, Value: 0 0.336901 Path: UPS.PowerSummary.00000000.BatteryPresent, Type: Input, ReportID: 0x40, Offset: 15, Size: 1, Value: 0 0.337503 Path: UPS.PowerSummary.CapacityMode, Type: Feature, ReportID: 0x50, Offset: 0, Size: 8, Value: 0.02 0.338506 Path: UPS.PowerSummary.DesignCapacity, Type: Feature, ReportID: 0x51, Offset: 0, Size: 8, Value: 100 0.339508 Path: UPS.PowerSummary.RemainingCapacity, Type: Input, ReportID: 0x52, Offset: 0, Size: 8, Value: 50 0.339523 Path: UPS.PowerSummary.RemainingCapacity, Type: Feature, ReportID: 0x52, Offset: 0, Size: 8, Value: 50 0....

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