search for: 0d9f

Hello. I've been trying to got it work but haven't luck. I'm using NUT 2.6.0-1 under Windows XP with libusb driver installed (USB\VID_0D9F&PID_0004&REV_0001). I had tryed all options with such config: *PWCOM] driver = usbhid-ups port = auto vendorid = 0d9f desc = "Powercom BNT-800AP" type=BNT* * *Here is output from CMD:* c:\Program Files (x86)\NUT\bin>usbhid-ups.exe -DDDDD...

...t; pc communication. I have trouble using it under nut. My system is Arch > Linux (updated). I tried usbhid-ups and powercom. I was hoping that you > would like to help me solve this problem. Thank you very much for your > attention. > > lsusb output: > > Bus 004 Device 008: ID 0d9f:0001 Powercom Co., Ltd > Device Descriptor: > bLength 18 > bDescriptorType 1 > bcdUSB 1.00 > bDeviceClass 0 (Defined at Interface level) > bDeviceSubClass 0 > bDeviceProtocol 0 > bMaxPacketSize0 8...

..... The "best" results I received with usbhid-ups driver: # /usr/local/libexec/nut/usbhid-ups -a BNT2000 -DDD Network UPS Tools - Generic HID driver 0.38 (2.7.2) USB communication driver 0.32 ???0.000000 debug level is '3' ???0.000557 upsdrv_initups... ???0.000744 Checking device (0D9F/0004) (/dev/usb//dev/ugen0.3) ???0.031233 - VendorID: 0d9f ???0.031240 - ProductID: 0004 ???0.031245 - Manufacturer: unknown ???0.031248 - Product: unknown ???0.031252 - Serial Number: unknown ???0.031256 - Bus: /dev/usb ???0.031260 Trying to match device ???0.031268 Device matches ???0.080235 Unab...

...on 15 Player. But my Raspberry Pi 3b + (with raspbian last version) doesn’t work with the same UPS, and with same NUT configuration. Raspberry sees the UPS, but the driver does not cling. Here is the response of Raspberry 3b + to some commands. pi at raspberrypi:~ $ lsusb Bus 001 Device 004: ID 0d9f:0004 Powercom Co., Ltd Bus 001 Device 005: ID 0424:7800 Standard Microsystems Corp. Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub Bus 001 Device 002: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub pi at...

...161 - ProductID: 0002 0.410194 - Manufacturer: unknown 0.410226 - Product: unknown 0.410258 - Serial Number: unknown 0.410290 - Bus: 001 0.410322 - Device release number: 0310 0.410354 Trying to match device 0.410390 Device does not match - skipping 0.430089 Checking device (0D9F/0002) (004/002) 0.438445 - VendorID: 0d9f 0.439423 - ProductID: 0002 0.440289 - Manufacturer: POWERCOM CO., LTD. 0.441156 - Product: USB to Serial 0.442018 - Serial Number: unknown 0.442872 - Bus: 004 0.443725 - Device release number: 0000 0.444579 Trying to match device...

...al] on usb-0000:00:1a.1-1 [root at tcm-file itsupport]# /sbin/lsusb Bus 004 Device 001: ID 0000:0000 Bus 006 Device 001: ID 0000:0000 Bus 001 Device 001: ID 0000:0000 Bus 007 Device 001: ID 0000:0000 Bus 005 Device 001: ID 0000:0000 Bus 003 Device 001: ID 0000:0000 Bus 002 Device 004: ID 0d9f:0002 Powercom Co., Ltd Bus 002 Device 001: ID 0000:0000 **** NUT-2.2.0 detected the PowerCom UPS but failure to establish a connection with it**** [root at tcm-file itsupport]# /sbin/usbhid-ups -a myups -u root -x vendorid=0d9f -x explore -D Network UPS Tools: 0.28 USB communication drive...

...al] on usb-0000:00:1a.1-1 [root at tcm-file itsupport]# /sbin/lsusb Bus 004 Device 001: ID 0000:0000 Bus 006 Device 001: ID 0000:0000 Bus 001 Device 001: ID 0000:0000 Bus 007 Device 001: ID 0000:0000 Bus 005 Device 001: ID 0000:0000 Bus 003 Device 001: ID 0000:0000 Bus 002 Device 004: ID 0d9f:0002 Powercom Co., Ltd Bus 002 Device 001: ID 0000:0000 **** NUT-2.2.0 detected the PowerCom UPS but failure to establish a connection with it**** [root at tcm-file itsupport]# /sbin/usbhid-ups -a myups -u root -x vendorid=0d9f -x explore -D Network UPS Tools: 0.28 USB communication drive...

Hi Have been trying to get nut and Powercom Vanguard 2000 ups communicating ? in the /lib/udev/rules.d/52-nut-usbups.rules file we have this entry #? PowerCOM VGD - Vanguard? - usbhid-ups ATTR{idVendor}=="0d9f", ATTR{idProduct}=="0004", MODE="664", GROUP="nut" ? In the /etc/ups/ups.conf [UPS] ??????? driver = usbhid-ups ??????? port = /var/lib/ups/hiddev0 ??????? productid = 0004 When running the command upsdrvctl -u nut -DDDDD start ? It returns Network UPS Tools...

...rID: 1d6b ?? 0.015938??? - ProductID: 0002 ?? 0.015941??? - Manufacturer: unknown ?? 0.015944??? - Product: unknown ?? 0.015946??? - Serial Number: unknown ?? 0.015949??? - Bus: 006 ?? 0.015951??? Trying to match device ?? 0.015953??? Device does not match - skipping ?? 0.015957??? Checking device (0D9F/00A3) (005/007) ?? 0.017893??? - VendorID: 0d9f ?? 0.017902??? - ProductID: 00a3 ?? 0.017906??? - Manufacturer: unknown ?? 0.017908??? - Product: unknown ?? 0.017910??? - Serial Number: unknown ?? 0.017912??? - Bus: 005 ?? 0.017914??? Trying to match device ?? 0.017939??? Device matches ?? 0.019894...

...rID: 1d6b ?? 0.015938??? - ProductID: 0002 ?? 0.015941??? - Manufacturer: unknown ?? 0.015944??? - Product: unknown ?? 0.015946??? - Serial Number: unknown ?? 0.015949??? - Bus: 006 ?? 0.015951??? Trying to match device ?? 0.015953??? Device does not match - skipping ?? 0.015957??? Checking device (0D9F/00A3) (005/007) ?? 0.017893??? - VendorID: 0d9f ?? 0.017902??? - ProductID: 00a3 ?? 0.017906??? - Manufacturer: unknown ?? 0.017908??? - Product: unknown ?? 0.017910??? - Serial Number: unknown ?? 0.017912??? - Bus: 005 ?? 0.017914??? Trying to match device ?? 0.017939??? Device matches ?? 0.019894...

...m able to run this ups with nut just see Dean thread on: http://www.tigerdirect.com/applications/searchtools/item-details.asp?EdpNo=770423&Tab=11&NoMapp=0 i use suse 10.1, i installed nut the ups is connected directely to my computer with an usb cable lsusb return Bus 001 Device 004: ID 0d9f:0001 Powercom Co., Ltd with lsmod, i can see usbhid 43296 0 /etc/ups/ups.conf i tried powercom and newhidups driver = newhidups port = /dev/hiddev0 desc = "Local UPS" /etc/ups/upsd.conf ACL all 0.0.0.0/0 ACL localhost 127.0.0.1/32 ACCEPT localhost REJECT all /etc/ups/upsmon.conf...

...endors wouldn't change operation without changing identifiers. > > Do you have any recommendations on how the driver should decide whether it is an old 0x0004 or new 0x0004 device? No-no, there is no an old 0x0004 or new 0x0004 device, I guess that we have to handle general case for all 0d9f:0x0004 devices. From PCM_USB_LIST_device2014.pdf attached by Alexey Morozov: "(VGD, VRT, RPT, .. and new UPS etc.) - 0X04.". According to this doc we can expect that all new PowerCOM devices will be shipped with ID 0X0d9f:0X04. For example, my Imperial IMD-825AP LCD has 0x0004, but an...

...MODE=netserver user=nut # Ultra ULT33046 2000 VA 1200 W Backup UPS with AVR (B000GC98H8) # From stickers: # Label: ULTRA # Model: RCD-UPS2000D # Serial Number: 40206430906 # # lsusb -vd 0d9f:0002|sed -ne '/^\w/p;/\bi/p' # Bus 002 Device 002: ID 0d9f:0002 Powercom Co., Ltd # Device Descriptor: # idVendor 0x0d9f Powercom Co., Ltd # idProduct 0x0002 # iManufacturer 1 POWERCOM CO., LTD. # iProduc...

On Nov 11, 2014, at 3:30 PM, Maksym Bodaniuk <max.bodaniuk at gmail.com> wrote: > Dear Charles and Artem, > > I've recently bought a new PowerCom Imperial IMD825-AP LCD which identifies itself as 0x0d9f:0x0004. > At first glance it seems that usbhid-ups driver works fine. But when I tried to shutdown UPS via DelayBeforeShutdown it started double beeping every couple seconds for indefinite time (the same problem described by Vincenzo Colonnella here: http://lists.alioth.debian.org/pipermail/nut-...

...nnect, address 3 Jul 7 23:25:30 eric-desktop kernel: [ 3049.073041] usb 2-1: new low speed USB device using uhci_hcd and address 4 Jul 7 23:25:30 eric-desktop kernel: [ 3049.257903] usb 2-1: configuration #1 chosen from 1 choice Jul 7 23:25:31 eric-desktop kernel: [ 3049.671558] generic-usb 0003:0D9F:0004.0005: hiddev96,hidraw1: USB HID v1.00 Device [POWERCOM Co.,LTD HID UPS Battery] on usb-0000:00:1d.0-1/input0 Here's my etc/nut/ups.conf file: Code: # /etc/nut/ups.conf [Ultra] driver = powercom port = port=/dev/hidraw1 linevoltage = 120 manufacturer = Ultra modelna...

...t change operation without changing identifiers. >> >> Do you have any recommendations on how the driver should decide whether it is an old 0x0004 or new 0x0004 device? > > No-no, there is no an old 0x0004 or new 0x0004 device, I guess that we have to handle general case for all 0d9f:0x0004 devices. You're right, I jumped to the wrong conclusion on that one. There was another thread about this, where it seems there are other mismatches between the report descriptor sizes, and what the UPS expects: http://article.gmane.org/gmane.comp.monitoring.nut.user/7662 > From PC...

...tery Mode dinow-All-Series:/etc/nut$ upsc pcmups Init SSL without certificate database battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 30 battery.date: 2010/12/20 battery.runtime: 784 battery.type: PbAc device.mfr: POWERCOM Co.,LTD device.model: HID UPS Battery device.serial: 004-0D9F-000 device.type: ups driver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.version: 2.7.1 driver.version.data: PowerCOM HID 0.4 driver.version.internal: 0.38 input.frequency: 0.0 input.voltage: 0.0 input.voltage.nominal: 120 output...

...results I received with usbhid-ups driver: ># /usr/local/libexec/nut/usbhid-ups -a BNT2000 -DDD >Network UPS Tools - Generic HID driver 0.38 (2.7.2) >USB communication driver 0.32 >???0.000000 debug level is '3' >???0.000557 upsdrv_initups... >???0.000744 Checking device (0D9F/0004) (/dev/usb//dev/ugen0.3) >???0.031233 - VendorID: 0d9f >???0.031240 - ProductID: 0004 >???0.031245 - Manufacturer: unknown >???0.031248 - Product: unknown >???0.031252 - Serial Number: unknown >???0.031256 - Bus: /dev/usb >???0.031260 Trying to match device >???0.031268...

...like they are using USB HID to emulate a serial > port. (A true USB HID Power Device Class report descriptor is > generally several hundred bytes long, versus the 37 shown here). > > Is it possible that you just need to load the usbserial kernel > module, and bind it to the UPS' 0d9f:0002 ID? Then the /dev/ttyUSB* > port can be passed to the "powercom" driver. (This is suggested by > http://networkupstools.org/stable-hcl.html?manufacturer=Powercom&connection=USB > ) OK, thanks! I read up about the stuff in the last paragraph, and it's not clear to m...

...;>>>>>>>>>><<<<<<<<<<<<<<<< Pheno-Mint upsmon # /sbin/upsdrvctl start Network UPS Tools - UPS driver controller 2.6.1 Network UPS Tools - Generic HID driver 0.35 (2.6.1) USB communication driver 0.31 This PowerCOM device (0d9f:0004) is not (or perhaps not yet) supported by usbhid-ups. Please make sure you have an up-to-date version of NUT. If this does not fix the problem, try running the driver with the '-x productid=0004' option. Please report your results to the NUT user's mailing list <nut-upsuser at l...