search for: 051d

...indows 2008 R2 to recognise two APC Smart-UPS 3000 devices connected via USB cables. I have correctly installed libusb-win32, and run the driver wizard. In my ups.conf I have :- [Upper] driver = usbhid-ups port = auto desc = "Upper Smart-UPS 3000" vendorid = 051d serial = "JS1011030553" [Lower] driver = usbhid-ups port = auto desc = "Lower Smart-UPS 3000" vendorid = 051d serial = "JS1011030544" However, this configuration cause the driver to crash. I have further identifed that inclu...

...93 Can't connect to UPS [USV] (usbhid-ups-USV): No such file or directory . root at debian-jessie-final:~# ls -l /dev/bus/usb/001/010 crw-rw-r-- 1 root nut 189, 9 Mai 2 21:50 /dev/bus/usb/001/010 udev-rules: ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="051d", ATTR{idProduct}=="0002", MODE="0660", GROUP="nut" Lsusb: root at debian-jessie-final:~# lsusb -d 051d:0002 Bus 001 Device 010: ID 051d:0002 American Power Conversion Uninterruptible Power Supply -------------- next part -------------- An HTML attachmen...

...0.28 (2.0.3) No matching USB/HID UPS found * trying to do some debugging (as I read earlier on that list regarding a problem somewhat similar): backer:~# /lib/nut/newhidups -u root -DDDDD auto Network UPS Tools: New USB/HID UPS driver 0.28 (2.0.3) debug level is '5' Checking device (051D/0002) (001/005) - VendorID: 051d - ProductID: 0002 - Manufacturer: American Power Conversion - Product: Smart-UPS 1500 RM FW:617.3.I USB FW:1.5 - Serial Number: AS0407211609 - Bus: 001 Trying to match device Device matches HID descriptor retrieved (Reportlen = 61939) Unable to get Report descriptor...

Hi, I cant get it working. Here is my terminal output: root at debian-jessie-final:~# lsusb -d 051d:0002 Bus 001 Device 010: ID 051d:0002 American Power Conversion Uninterruptible Power Supply root at debian-jessie-final:~# ls -l /dev/bus/usb/001/010 crw-rw-r-- 1 root nut 189, 9 Mai 6 15:35 /dev/bus/usb/001/010 root at debian-jessie-final:~# sudo upsdrvctl start Network UPS Tools - UPS driver c...

...in # uname -a Linux joavma01 2.6.32.54-0.3-default #1 SMP 2012-01-27 17:38:56 +0100 x86_64 x86_64 x86_64 GNU/Linux joavma01:/usr/local/ups/bin # lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 002: ID 051d:0003 American Power Conversion UPS Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub joavma01:/usr/local/ups/bin # usb-devices T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 6 D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=1d6b ProdID=0002 Rev=...

...GNU/Linux NUT 2.4.3 self compiled dkplugbab9:/usr/local/ups/etc# /usr/local/ups/bin/usbhid-ups -a apc1500 -u nut -DD Network UPS Tools - Generic HID driver 0.34 (2.4.3) USB communication driver 0.31 0.000000 debug level is '2' 0.002738 upsdrv_initups... 0.005059 Checking device (051D/0002) (001/011) 0.005304 - VendorID: 051d 0.005351 - ProductID: 0002 0.005383 - Manufacturer: unknown 0.005420 - Product: unknown 0.005451 - Serial Number: unknown 0.005486 - Bus: 001 0.005516 Trying to match device 0.005630 Device does not match - skipping But if i use u...

...t; My system: debian etch > > Linux 2.6.18-4-686 #1 SMP Wed Feb 21 16:06:54 UTC 2007 i686 > GNU/Linux > udev version 0.105-3 > nut version 2.0.4-4 > > /lib/nut/newhidups -V > Network UPS Tools: New USB/HID UPS driver 0.28 (2.0.4) > > lsusb: > Bus 003 Device 002: ID 051d:0002 American Power Conversion > Back-UPS Pro 500/1000/1500 > > But the driver gives a error: > /lib/nut/newhidups -DDD -u root -x port=usb auto > Network UPS Tools: New USB/HID UPS driver 0.28 (2.0.4) > > debug level is '3' > Checking device (051D/0002) (003/002) &g...

...ID=raspbian ID_LIKE=debian HOME_URL="http://www.raspbian.org/" SUPPORT_URL="http://www.raspbian.org/RaspbianForums" BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs" torsten at raspberrypi:/ $ torsten at raspberrypi:/ $ lsusb Bus 001 Device 004: ID 051d:0002 American Power Conversion Uninterruptible Power Supply Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub tor...

...2-7 0 -20 http://debian.fastweb.it unstable/main Packages *** 2.2.2-6 0 -10 http://debian.fastweb.it testing/main Packages 100 /var/lib/dpkg/status 2.0.4-4 0 990 http://debian.fastweb.it etch/main Packages effem at tux:~$ lsusb [cut] Bus 001 Device 002: ID 051d:0002 American Power Conversion Back-UPS Pro 500/1000/1500 Bus 001 Device 001: ID 1d6b:0001 effem at tux:~$ ls -la /dev/bus/usb/001/ [cut] crw-rw-r-- 1 root nut 189, 1 2008-09-24 08:41 002 Config files: tux:/home/effem# cat /etc/nut/ups.conf [APC-RS800] driver = usbhid-ups port = auto tux...

So I have an entry for a USB device ( ID 051d:0002, UPS) I want to use with a given vm client. In that vm client's config file I added something like this: <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x051d'/> <product id='0x000...

Sorry, I forgot this: torsten at raspberrypi:/ $ sudo /lib/nut/usbhid-ups -a UPS -x vendorid=051d -DD Network UPS Tools - Generic HID driver 0.38 (2.7.2) USB communication driver 0.32 0.000000 debug level is '2' 0.004718 upsdrv_initups... 0.007534 Checking device (051D/0002) (001/004) 0.008910 - VendorID: 051d 0.010030 - ProductID: 0002 0.0111...

Hi list, I seem to need another pair of eyes. Here's my ups.conf: [myups] driver = usbhid-ups port = auto vendor = 051d product = 0002 serial = 4B1717P25055 And here's the output of `/lib/nut/usbhid-ups -a myups -DDD`: 0.017467 Trying to match device 0.017479 Device does not match - skipping 0.017499 Checking device (051D/0002) (001/003) 0.094770 - VendorID: 051d 0.094822 -...

...s.conf looks like this: [apcups] driver = usbhid-ups port = auto My upsd.conf looks like this: ACL all 0.0.0.0/0 ACL localhost 127.0.0.1/32 ACCEPT localhost REJECT all When I run: sudo /opt/local/bin/usbhid-ups -a apcups -DD I get what looks to be success: Checking device (051D/0002) (001/002-051d-0002-00-00) - VendorID: 051d - ProductID: 0002 - Manufacturer: American Power Conversion - Product: Back-UPS XS 1300 LCD FW:836.H7 .D USB FW:H7 - Serial Number: 8B0749R24222 - Bus: 001 Trying to match device Device matches failed to claim USB device... HID descriptor length 1079...

Whenever I try to use the newhidups driver with my new UPS I get the following message: #/lib/nut/newhidups -DDD -a SmartUps1500 Network UPS Tools: New USB/HID UPS driver 0.28 (2.0.4) debug level is '3' [...skip unrelevant device...] Checking device (051D/0002) (001/005) - VendorID: 051d - ProductID: 0002 - Manufacturer: American Power Conversion - Product: Smart-UPS 1500 FW:601.3.I USB FW:1.5 - Serial Number: AS0523120710 - Bus: 001 Trying to match device Device matches HID descriptor retrieved (Reportlen = 61939) Size read for the report descripto...

On Dec 26, 2018, at 8:59 PM, David Melik wrote: > > root at 0.darwinheim <mailto:root at 0.darwinheim>:~# lsusb -d 051d: > root at 0.darwinheim <mailto:root at 0.darwinheim>:~# If you leave off the "-d 051d:" part, do you see anything in the listing that looks like it could be the UPS? (The 051d vendor ID is for the vast majority of APC UPS models, but we have seen a few other IDs here and there...

Hello! I tried NUT 2.6.5-1 (Windows port) with my APC Back UPS ES. It seems I have configured NUT properly, nut-scanner found my UPS: [nutdev1] driver = "usbhid-ups" port = "auto" vendorid = "051D" productid = "0002" product = "Back-UPS ES 525 FW:851.t3.I USB FW:t3" serial = "8B0745R23575 " vendor = "American Power Conversion" bus = "bus-0" I see some errors: 1. UPSMON/UPSC tools are returning &q...

...t the Pro isn't detected (with usbhid-ups.) I haven't tried the NS yet but it seems to not be on the list though looks just like the Pro. >> > There are a few different angles we can approach this one from. What error message do you get from usbhid-ups, and what does "lsusb -d 051d:" show? root at 0.darwinheim:~# rc.ups start Network UPS Tools - UPS driver controller 2.7.4 Network UPS Tools - Generic HID driver 0.41 (2.7.4) USB communication driver 0.33 No matching HID UPS found Driver failed to start (exit status=1) root at 0.darwinheim:~# lsusb -d 051d: root at 0.darw...

I was testing out newhidups with an APC UPS, and I noticed that I needed '-x vendor=American.Power.*' instead of '-x vendor=APC.*' as indicated in the man page. Do other APC USB UPSes use 'APC' in the vendor string? Should we sidestep any such problems and just go with the hex vendor ID for APC examples? This was tested with a snapshot from the development branch, but the

Hi All, I get very strange UPS problem from RspberryPI mode B (both version 2 and 3). Here is our environment: OS: Raspbian 8.0, Ubuntu 16.04 and Ubuntu 14.04 Platform: RaspberryPi Mode B version 2 and version 3 NUT: tested version 2.6.3, 2.7.1 and 2.7.2 (from

...: yum install epel-release #yum update ?y i tested it also with this update but same results yum install open-vm-tools yum install putty yum install mc yum install nano yum install usbutils yum install nut yum install nut-cgi yum install nut-client yum install powerman nut-scanner ?U shows ups APC 051D:0002 so i tried: /etc/ups/ups.conf: [myups] driver = "usbhid-ups" port = /dev/usb/hiddev0 vendorid = "051D" productid = "0002" (also tried to comment vendor+product+port and set port=auto same problem) /lib/systemd/system/nut-driver.service ... ExecStart=-/sbin/upsd...