search for: pcm_usb_protocol_2014

...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 old examples of this model have 0Xa2. Also, lets take a look inside PCM_USB_protocol_2014.pdf: "16 0x8456 Delay Before Startup R/W *5 Byte*" And old specs for BNT protocol: "16 8456 DelayBeforeStartup *** R/W *2 Byte*" So, the length for DelayBeforeStartup report changed from 2 to 5 bytes. Or there was added a new report for example: "44 0x8436 Temperature R/...

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

...; "(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 old examples of this model have 0Xa2. > > Also, lets take a look inside PCM_USB_protocol_2014.pdf: > "16 0x8456 Delay Before Startup R/W 5 Byte" > And old specs for BNT protocol: > "16 8456 DelayBeforeStartup *** R/W 2 Byte" > So, the length for DelayBeforeStartup report changed from 2 to 5 bytes. From the 2012 thread, it looks like the DelayBeforeStartup...