search for: d005

...ini-box.com/OpenUPS2 thinking it would be handled by NUT. I think I misread or misinterpreted the HCL http://www.networkupstools.org/stable-hcl.html The OpenUPS UPS is listed as supported under usbhid-ups, and I had assumed that OpenUPS2 would be as well. Bzzzzt. I get a unknown device ID for d005 Is adding (or hacking) support for this device into the HID driver something simple which can be done without a recompile? -- Do things because you should, not just because you can. John Thurston 907-465-8591 John.Thurston at alaska.gov Enterprise Technology Services Department of Admini...

Hi, Debug output of driver is attached, started with OpenUPS2 input feed online @ 12V and going offline at 15th second of debug run. Second attached file is debug output of unsuccessful UPS shutdown captured with command: /lib/nut/usbhid-ups -a openups -x productid=d005 -u root -DDD *-k* 2>&1 |tee openups-d005-shut.log I believe input voltage on my earlier upsc run was around 16V, just in case, i'll dump another copy here @ approx 12,2V input # upsc openups Init SSL without certificate database battery.capacity: 100 battery.charge: 100 battery.char...

...ID to the driver, but I noticed a few inconsistencies (indicated below). > OpenUPS2 Configuartion variables modification would be very welcome.... I'm assuming these are exposed via USB HID? If so, we need a debug log. Start the driver like so: /path/to/usbhid-ups -a openups -x productid=d005 -u root -DDD 2>&1 |tee openups-d005.log Please gzip the log before attaching it, and send to either this list, or nut-upsdev@ > # upsc openups > Init SSL without certificate database > battery.capacity: 100 > battery.charge: 98 > battery.charge.low: 5 > battery.charge.war...

...; http://www.networkupstools.org/stable-hcl.html Correct, we only knew about the original openUPS (USB ID 04d8:d004) at the time that was written. > The OpenUPS UPS is listed as supported under usbhid-ups, and I had assumed that OpenUPS2 would be as well. Bzzzzt. I get a unknown device ID for d005 > > Is adding (or hacking) support for this device into the HID driver something simple which can be done without a recompile? As a first test, start upsd (let us know if you need more details, but this depends on how your OS/distribution packages things up) and then run the usbhid-ups driv...

...6tables-save v1.4.20 on Tue May 13 00:35:06 2014 *mangle :PREROUTING ACCEPT [0:0] :INPUT ACCEPT [0:0] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [0:0] :POSTROUTING ACCEPT [0:0] -A PREROUTING -d 2001:470:f9b0:a005::/64 -i eth1 -j DNPT--src-pfx 2001:470:f9b0:a005::/64 --dst-pfx fdde:3033:88c2:d005::/64 -A POSTROUTING -s fdde:3033:88c2:d005::/64 -j SNPT--src-pfx fdde:3033:88c2:d005::/64 --dst-pfx 2001:470:f9b0:a005::/64 COMMIT Expected Results: # Generated by ip6tables-save v1.4.20 on Wed May 14 01:36:03 2014 *mangle :PREROUTING ACCEPT [0:0] :INPUT ACCEPT [0:0] :FORWARD ACCEP...

...me estimate seems high, but you might need to plot that over time to see what the scale factor should be for that. NUT usually reports it in seconds. > Second attached file is debug output of unsuccessful UPS shutdown captured with command: > > /lib/nut/usbhid-ups -a openups -x productid=d005 -u root -DDD -k 2>&1 |tee openups-d005-shut.log Not sure what to tell you - there is no shutdown command listed in the HID descriptor. I CC'd the author of the driver - maybe the manufacturer can provide more information? Same thing with the configuration variables. There are a few non...

...battery.type: battery.voltage: 10.13 device.mfr: Mini-Box.Com device.model: OPEN-UPS2 device.serial: LI-ION device.type: ups driver.flag.maxreport: enabled driver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.parameter.productid: d005 driver.parameter.synchronous: no driver.parameter.vendorid: 04d8 driver.version: 2.7.4 driver.version.data: openUPS HID 0.4 driver.version.internal: 0.41 input.current: 0.000 input.voltage: 12.08 output.current: 0.000 output.voltage: 12.04 ups.mfr: Mini-Box.Com ups.model: OPEN-UPS2 ups.productid: d...

Hello, I have an openups2 ups. It works very well with nut, except two things: 1) It keeps sending a 'libusb_get_string: invalid argument' message to the log; 2) It does not report any command. Following http://nut-upsdev.alioth.debian.narkive.com/bmJyFFkO/libusb-get-string-invalid-argument, I was able to fix the error message using the attached patch. I do not know how ot fix the

...ATTRS{idVendor}=="047c", ATTRS{idProduct}=="ffff", ENV{UPOWER_BATTERY_TYPE}="ups" +# Minibox +ATTRS{idVendor}=="04d8", ATTRS{idProduct}=="d004", ENV{UPOWER_BATTERY_TYPE}="ups" +ATTRS{idVendor}=="04d8", ATTRS{idProduct}=="d005", ENV{UPOWER_BATTERY_TYPE}="ups" + # Belkin ATTRS{idVendor}=="050d", ATTRS{idProduct}=="0375", ENV{UPOWER_BATTERY_TYPE}="ups" ATTRS{idVendor}=="050d", ATTRS{idProduct}=="0551", ENV{UPOWER_BATTERY_TYPE}="ups" @@ -49,15 +66...

...a1.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04) [ 1.726434] ata2.00: ATAPI: TSSTcorp DVD+/-RW TS-L633C, DW60, max UDMA/100 [ 1.726600] ata2.00: applying bridge limits [ 1.748299] ata2.00: configured for UDMA/100 [ 1.753800] ata1.00: ATA-8: ST9320423AS, D005SDM1, max UDMA/133 [ 1.754025] ata1.00: 625142448 sectors, multi 16: LBA48 NCQ (depth 31/32) [ 1.756868] ata1.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04) [ 1.757527] ata1.00: configured for UDMA/133 [ 1.757968] scsi 0:0:0:0: Direct-Access ATA...