search for: 04d8

I bought a very nice little, self contained, UPS from mini-box: http://www.mini-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

...UT working OK and the upsd running, with upsmon working OK too - all is well as long as I leave the power on, or the battery takes over but doesn?t need to shut down the system! But if I try to shut down the system using 'upsdrvctl shutdown? I get a USB error message - ?Can?t claim USB device [04d8:doo4]:? This looks like permissions but I?ve set up UDEV and the users in accordance with the instructions. Also if the battery runs down, there is no communication from the UPS via USB - the power just dies. I could use the motherboard toggle to shut down the system, but then I can?t run pre-shut...

...ght a very nice little, self contained, UPS from mini-box: > http://www.mini-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 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...

...drv_updateinfo... 0.720135 libusb_get_interrupt: Connection timed out 0.721710 Got 0 HID objects... 0.723106 Quick update... 2.469447 upsdrv_updateinfo... 2.722132 libusb_get_interrupt: Connection timed out > Could you please also provide the output of "lsusb -vvv -d 04d8:0500" > run as root? root at Scanner:~# lsusb -vvv -d 04d8:0500 Bus 003 Device 002: ID 04d8:0500 Microchip Technology, Inc. Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 (Defined at Interface level)...

...;drewzhrodague at zhrodague.net> wrote: >> >> >> Hello! I have a Dockmaster from Copeland Engineering. This is a battery saver used for a laptop docking station in a police car, which has a USB port for relaying its internal timers and state. >> >> hid-generic 0003:04D8:0500.0001: hiddev0,hidraw0: USB HID v1.10 Device [Copeland Engineering, LLC Dock Master] on usb-0000:00:10.4-3.3/input0 >> >> I'm able to configure usbhid-ups, but it doesn't seem to detect the state of the power (between ignition-on and ignition-off). I do have access to the W...

...the HID items, just the ones that are known to contain good values (for some version of the UPS firmware). > when I plug in the OpenUPS I see this : > > [ 49.049586] usb 4-5: new full-speed USB device number 3 using ohci-pci > [ 49.215825] usb 4-5: New USB device found, idVendor=04d8, idProduct=d004 > [ 49.222717] usb 4-5: New USB device strings: Mfr=1, Product=2, SerialNumber=4 > [ 49.229879] usb 4-5: Product: OPEN-UPS > [ 49.233658] usb 4-5: Manufacturer: Mini-Box.Com > [ 49.238218] usb 4-5: SerialNumber: PBSO4-LiFePO > [ 49.259143] hid-generic 0003:0...

...and gen-usbhid-subdriver but the output seems to be incorrect. Same behavior with stable 2.6.5, so I guess there is something wrong with data coming out of device. I attached the output of usbhid-ups and gen-usbhid-subdriver from the commands: drivers/usbhid-ups -DD -u root -x explore -x vendorid=04d8 -a openups >& openups-dump.txt ./gen-usbhid-subdriver.sh -n openUPS -v 04d8 -p d004 -k < ../../openups-dump.txt Thanks, Nicu -------------- next part -------------- 0.000000 debug level is '2' 0.000504 upsdrv_initups... 0.306826 Checking device (04D8/D004) (008/003) 0...

...rent: 1.192 > output.voltage: 308.16 Input and output voltage do not seem consistent with the battery voltage. What do the real values look like? > ups.mfr: Mini-Box.Com > ups.model: OPEN-UPS2 > ups.productid: d005 > ups.serial: LI-ION > ups.status: OB DISCHRG > ups.vendorid: 04d8 > > # cat /etc/nut/ups.conf > [openups] > driver = usbhid-ups > port = auto > productid = d005 > desc = "OpenUPS2" > > On Sep 8, 2014, at 7:08 PM, Charles Lepple <clep... at gmail.com> wrote: > >> On Sep 8, 2014, at 5:46 PM, John Th...

Hello! I have a Dockmaster from Copeland Engineering. This is a battery saver used for a laptop docking station in a police car, which has a USB port for relaying its internal timers and state. hid-generic 0003:04D8:0500.0001: hiddev0,hidraw0: USB HID v1.10 Device [Copeland Engineering, LLC Dock Master] on usb-0000:00:10.4-3.3/input0 I'm able to configure usbhid-ups, but it doesn't seem to detect the state of the power (between ignition-on and ignition-off). I do have access to the Windows-based c...

...uctid: d005 driver.version: 2.7.2 driver.version.data: openUPS HID 0.1 driver.version.internal: 0.38 input.current: 0.000 input.voltage: 432.74 output.current: 0.000 output.voltage: 315.08 ups.mfr: Mini-Box.Com ups.model: OPEN-UPS2 ups.productid: d005 ups.serial: LI-ION ups.status: OL ups.vendorid: 04d8 > On Nov 4, 2014, at 4:36 PM, Toomas Suurmets (Priv) <toomas at > suurmets.com> wrote: > > > Hi Charles, > > > > I tried your suggestion with OpenUPS2 (on Raspberry PI, Debian > Jessie), it works. > > Thanks for the update. We can add the ID to the drive...

...vice.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: d005 ups.serial: LI-ION ups.status: OL ups.vendorid: 04d8 Note t...

...on-PDC HID as a cheap USB-to-serial replacement), this might require a separate driver, or it might be easy to extend usbhid-ups. The "explore mode" mentioned in the link below will provide the output to guide that decision. Could you please also provide the output of "lsusb -vvv -d 04d8:0500" run as root? > > On 2/22/17 11:19 PM, Charles Lepple wrote: >> On Feb 21, 2017, at 10:21 AM, Drew from Zhrodague <drewzhrodague at zhrodague.net> wrote: >>> >>> >>> Hello! I have a Dockmaster from Copeland Engineering. This is a battery s...

...d out...basically an ATTR for every known USB UPS. Well, since mine is not a known UPS, I had to add my own entry. So I added a similar entry to all the others, but putting in my USB vendor and product IDs and setting GROUP="nut" (like all the other entries do). ATTR{idVendor}=="04d8", ATTR{idProduct}=="005c", MODE="664", GROUP="nut" But so far as I can tell, when I plug in the USB cable from the UPS...it is still not setting it to nut group permissions. I am looking at the file in /dev/usb/hid/hiddev0 (which goes away when I unplug the UPS)...

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

...e can add an entry to that table (via drivers/usbhid-ups.c, which gets parsed into the udev script) > So I added a similar entry to all the others, but putting in my USB vendor and product IDs and setting GROUP="nut" (like all the other entries do). > > ATTR{idVendor}=="04d8", ATTR{idProduct}=="005c", MODE="664", GROUP="nut" > You might need to tell udev to reload, although newer versions seem to re-read the rules files automatically. Also, I think there is a debug mode for udev that will show what is being parsed when. > But...

...# if usbraw device, ignore @@ -17,21 +20,31 @@ ATTRS{idVendor}=="03f0", ENV{UPOWER_VENDOR}="Hewlett Packard" ATTRS{idVendor}=="0463", ENV{UPOWER_VENDOR}="Eaton" ATTRS{idVendor}=="047c", ENV{UPOWER_VENDOR}="Dell" +ATTRS{idVendor}=="04d8", ENV{UPOWER_VENDOR}="Minibox" ATTRS{idVendor}=="050d", ENV{UPOWER_VENDOR}="Belkin" ATTRS{idVendor}=="051d", ENV{UPOWER_VENDOR}="APC" -ATTRS{idVendor}=="06da", ENV{UPOWER_VENDOR}="Liebert" +ATTRS{idVendor}=="0592&quot...

...rom Zhrodague <drewzhrodague at zhrodague.net> wrote: > > > Hello! I have a Dockmaster from Copeland Engineering. This is a battery saver used for a laptop docking station in a police car, which has a USB port for relaying its internal timers and state. > > hid-generic 0003:04D8:0500.0001: hiddev0,hidraw0: USB HID v1.10 Device [Copeland Engineering, LLC Dock Master] on usb-0000:00:10.4-3.3/input0 > > I'm able to configure usbhid-ups, but it doesn't seem to detect the state of the power (between ignition-on and ignition-off). I do have access to the Windows-...

Hello, Would like to see if I could get some help with this UPS on a debian set-up. Am not the best with linux and have tried what I managed to find elsewhere on the list so am just trying here. 1) Device seems supported: http://networkupstools.org/ddl/Mini-Box.com/OpenUPS2.html 2) lsusb -v -d 04d8: seems to give the right parameters including product name, max power etc from the unit 3) Followed the steps here as an initial starting point: https://gist.github.com/clungzta/2b5f737f006e1530cc59 4) Have edited the ups.conf and nut.conf files with the necessary entries but trying to start the...

...ower-hid.rules (working copy) @@ -15,6 +15,7 @@ ATTRS{idVendor}=="03f0", ENV{UPOWER_VENDOR}="Hewlett Packard" ATTRS{idVendor}=="0463", ENV{UPOWER_VENDOR}="Eaton" ATTRS{idVendor}=="047c", ENV{UPOWER_VENDOR}="Dell" +ATTRS{idVendor}=="04d8", ENV{UPOWER_VENDOR}="for getval()" ATTRS{idVendor}=="050d", ENV{UPOWER_VENDOR}="Belkin" ATTRS{idVendor}=="051d", ENV{UPOWER_VENDOR}="APC" ATTRS{idVendor}=="0592", ENV{UPOWER_VENDOR}="Powerware" @@ -47,6 +48,9 @@ # Dell...

On Feb 18, 2015, at 10:40 AM, Rob Groner <rgroner at RTD.com> wrote: > Does this revolve around hotplug and udev? Yes. (Well, technically hotplug was superseded by udev) > In other words, is the idea that the created USB device will be in the "nut" group, Yes. > and thus I'd be able to tell upsdrvctrl to start if I am user "ups"? Or do ups/nut not