similar to: POWERCOM HID USB controller update

Dear Sirs, We appreciate your support and cooperation. Can you please kindly add our new USB-controller with productID 0X04 to NUT compatible list. Updated USB-controller compatible with previous version which is supported by your usbhid-ups driver. Detailed information regarding new POWERCOM communication protocol you could download via link

On Sep 11, 2014, at 2:50 AM, Khokhlov Artem <khokhlov.a at pcm.ru> wrote: > Can you please kindly add our new USB-controller with productID 0X04 to NUT compatible list. Updated USB-controller compatible with previous version which is supported by your usbhid-ups driver. Confused. This commit was added in 2011:

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

Hi Charles, > Sigh, I wish the vendors 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

On Nov 12, 2014, at 3:53 AM, Maksym Bodaniuk <max.bodaniuk at gmail.com> wrote: > Hi Charles, > >> Sigh, I wish the vendors 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

[I am CC'ing Alexey from Powercom in case he has seen any of these issues with the Raspberry Pi hardware.] On Jun 10, 2013, at 1:05 PM, M?rti?? Pu??tis wrote: > I took the log. Here's what happened. > Broadcast Message from nut at rasp > (somewhere) at 16:18 ... > UPS BNT500AP at localhost battery needs to be replaced > > occurred when for the first time value

Citeren Alexander Gordeev <lasaine op lvk.cs.msu.su>: > I've received the units. Are there any special things I should test or > just the standard NUT setup? They should be detected out of the box (with the latest version from the trunk) through the 'usbhid-ups' driver. Note that I just added some additional commands to enable|disable|mute the beeper of the UPS.

I took the log. Here's what happened. Broadcast Message from nut at rasp (somewhere) at 16:18 ... UPS BNT500AP at localhost battery needs to be replaced occurred when for the first time value "1" was read as "UPS.PowerSummary.PresentStatus.NeedReplacement", on this line: 6409.240690 Path: UPS.PowerSummary.PresentStatus.NeedReplacement, Type: Input, ReportID: 0x0a,

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:

Alex and the list, Alexey Morozov (Powercom sales manager for Russia) has contacted me to propose demo units and information on the new Powercom protocol. This is preferably for a Russian team member... Anyone up? cheers, Arnaud -- Linux / Unix Expert R&D - Eaton - http://www.eaton.com/mgeops Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer -

Alex and the list, Alexey Morozov (Powercom sales manager for Russia) has contacted me to propose demo units and information on the new Powercom protocol. This is preferably for a Russian team member... Anyone up? cheers, Arnaud -- Linux / Unix Expert R&D - Eaton - http://www.eaton.com/mgeops Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer -

Hi, I know it's been a topic many times here, but I've searched the archives, googled for days, and I simply don't believe, that there is still no solution to this. I'm using a PowerCom BNT-600AP ups with usb port. I've downloaded the latest version from svn, compiled it, and tried to use it: * megatec(_usb) - no luck, it did not find the UPS (I?ve read in this list, that

On Jun 5, 2013, at 11:49 AM, M?rti?? Pu??tis wrote: > Driver debug output attached. The debug output looks normal (many devices do not implement the interrupt pipe; hence, the timeouts). Unfortunately, we might need the log over a longer period of time, including your observations as to when various events occurred (such as transitions to battery). -- Charles Lepple clepple at gmail

Alexey, I posted this before, but never got a reply. So I'm reposting this again. In the present HID PDC implementation by PowerCOM, expect problems with the non-compliant implementation of the DelayBeforeShutdown and DelayBeforeStartup pages. Third party applications will expect that these follow the HID PDC specifications if you name them like this (and break terribly in the

OS name and version: pi at raspberrypi ~ $ cat /etc/*release PRETTY_NAME="Debian GNU/Linux 7.0 (wheezy)" uname -a Linux raspberrypi 3.6.11+ #393 PREEMPT Fri Mar 8 16:36:28 GMT 2013 armv6l GNU/Linux exact NUT version pi at raspberrypi ~ $ dpkg -s nut Package: nut ... Version: 2.6.4-2.3 NUT installation method: package exact device name and related information:

On Jun 8, 2013, at 12:57 PM, M?rti?? Pu??tis wrote: > I'll take a longer driver log. This page (http://www.networkupstools.org/support.html) says that to take a driver log NUT should be stopped, so I won't be able to tell when these events occurred within a driver log. Hmm, I didn't realize it said that, but I think that's to prevent having two copies of the same driver

Thanks for the support. Here's list of when transition to battery with return to utility power within a few seconds occurred in last few days: Wednesday 1:41 11:48 11:54 12:59 13:42 14:42 18:13 18:14 Thursday 5:23 Friday 5:12 7:39 7:43 Saturday 7:34 Here's list of when messages that battery needs replacement occurred: Wednesday 20:34 Thursday 9:07 23:09 Friday 18:25 Saturday 7:32 19:47

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:*

Hello. It's been a while since I started this topic. I've finally tested it on Linux desktop PC. Nut version 2.6.4-2.3 Basically the behavior is the same as on raspberry pi. It reports "battery needs to be replaced" regularly and I got "on battery" message 114107.780504 Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Input, ReportID: 0x0a, Offset: 2, Size: 1,

Good afternoon. I try to put nut on gentoo. Has executed installation by a standard command emerge nut. All has passed successfully. I use UPS POWERCOM BNT-1500AP. It is connected to serial port 1, i.e. for my system it/dev/tts/0. In/etc/nut/ups.conf [powercom] driver = powercom port = /dev/tts/0 desc = "PowerCom BNT-1500AP on IP-PBX" modelname = "BNT-1500AP" linevoltage = 230