similar to: Unable to disable beeper on Powercom Imperial IMP-525AP

Hi Arnaud, I received several replies from technical support. It turned out that according to the UPS serial number it had been manufactured in 2012. So, the device should support the ability to disable the beeper. But still I can not disable the beeper using the latest version of UPSMON Plus in Windows: http://www.pcm.ru/data/download/public/soft/setup_upsmon_v2.9.rar (don't know why; the

G'day, all! It's my second trouble with NUT. Latest nut-2.6.1.tar.gz installed from source on Xenserver 5.6 SP2, UPS is Powercom WOW--500U FW3.A4 (USB). Problem with setting permissions for udev (described in /etc/udev/rules.d/52-nut-usbups.rules file): ACTION!="add|change", GOTO="nut-usbups_rules_end" don't work for me. Only when I changed ACTION to:

Hi Sergey, 2011/7/15 Sergey Talchuk <tals1975 at gmail.com> > Hi Arnaud, > > both configurations are ok :). Please find the file attached. > logic since the 2nd is automatically guessed from the first using USB Vendor and Product ID ;-) can you please send in upsc, upscmd and upsrw output. and also report the shutdown testing as described here:

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.

2008/10/18 Sergiy Yegorov <prapor at unixzone.org.ua>: > Dear Arnaud! Hi Sergiy and Alexey, > Please, check this patch. It adds USB-attached Powercom UPS Imperial & > Black Knight series. Originaly code is writed by Kirill Burdin > (burdin at post.ru) for Imperial UPS`es. > I`m just sysadmin without enought C programming > skills, so I adapted it to nut-2.2.2-6

G'day, all! I installed latest stable nut-2.6.1.tar.gz from source on Xenserver 5.6 SP2 (Linux xen-home 2.6.32.12-0.7.1.xs5.6.100.323.170596xen #1 SMP Fri Apr 8 07:25:07 EDT 2011 i686 athlon i386 GNU/Linux), my UPS is Powercom WOW--500U FW3.A4. All works almost fine but here are some troubles: when I pull the plug then upsd immediately starts (after FINALDELAY delaying) the procedure of

Hello all. Try this driver (for nut 2.2.0). See attach. - Trust, KP625AP, Egys models stay as it was - add Powercom's Black Knight Pro model support ( BNT-400/500/600/800/801/1000/1200/1500/2000AP 220-240V ) - add Powercom's King Pro model support ( KIN-425/525/625/800/1000/1200/1500/1600/2200/3000/5000AP[-RM] 100-120,200-240 V) - add Powercom's Imperial model support ( IMP-xxxAP,

Alexey Korobeinikov <alexey at fseafood.com> writes: > The UPS Powercom (productid: 0004 vendorid: 0d9f) with: > driver.version: 2.8.3.1 > driver.version.data: PowerCOM HID 0.71 > driver.version.internal: 0.64 > driver.version.usb: libusb-1.0.26 (API: 0x01000109) > > has ingnorig parametr ups.delay.start. > It turn on imediatly after power restore on input line.

Linux-2.4.28 libusb-0.1.8 nut-2.6.5 [+most recent drivers from GIT] - from tarball EATON 3S700DIN [mfr.date 09/28/14] ---------------------------------- ISSUES: I) Too many kernel logs: --- In /var/log/kernel.log usbdevfs: usb_submit_urb returned -28 In /var/log/daemon.log: usbhid-ups[744]: libusb_get_interrupt: No error usbhid-ups[744]: libusb_get_interrupt: error submitting URB: No space left

Dear Sirs, First of all I would like to thank you for support PCM product in your project. Kindly please be informed that POWERCOM launch new USB-controller with productID 0X04. Updated USB-controller compatible with previous version which supported by your usbhid-ups driver. There is added some command and changed idProduct. Vendor ID stay the same 0X0d9f without changes. Detailed information

Good Day Roger Price AA. Hi, Normally one would expect the UPS to disconnect it's power outlets after the default ups.delay.shutdown = 20 seconds. ==> I got it. I tried to command "upsdrvctl shutdown" on both line-mode and battery-mode ==> But ups do not disconnect its outlets power ----------------------------------------------------------------------------------- BB.

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

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

Hi Charles, Yes, it looks like my g++ does contain STL library which might be just my specific case... However, as a temporary solution I disabled nutclient in Makefile (please find the file attached). And nut-2.7.3 can be compiled now. Thanks, Sergey On Wed, Jul 8, 2015 at 4:13 AM, Charles Lepple <clepple at gmail.com> wrote: > On Jul 6, 2015, at 10:32 AM, Sergey Talchuk

Hi Charles, Thanks for the prompt reply! Errors occur when execute make: /bin/sh ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I../include -MT nutclient.lo -MD -MP -MF $depbase.Tpo -c -o nutclient.lo nutclient.cpp &&\ mv -f $depbase.Tpo $depbase.Plo libtool: compile: g++ -DHAVE_CONFIG_H -I. -I../include -MT nutclient.lo -MD -MP -MF .deps/nutclient.Tpo -c

Dear developers, libnutclient has been added as a C++ alternative to libupsclient in 2.7.1. As a result I can't compile nut 2.7.3 with gcc-3.3.6. There wasn't such a problem with nut-2.6.5. Is it possible to add a configuration parameter like '-without-libnutclient' to provide better compatibility with older gcc versions please (since libnutclient is an alternative to

Dear developers, libnutclient has been added as a C++ alternative to libupsclient in 2.7.1. As a result I can't compile nut 2.7.3 with gcc-3.3.6. There wasn't such a problem with nut-2.6.5. Is it possible to add a configuration parameter like '-without-libnutclient' to provide better compatibility with older gcc versions please (since libnutclient is an alternative to

Hello ! Anybody have expirience with Powercom Imperial 1500 VAC (USB interface) ? Under FreeBSD 6.2 it's shown as uhid device: uhid0: POWERCOM CO., LTD. USB to Serial, rev 1.00/0.00, addr 2, iclass 3/0 usbhid-ups doesn't recognize it, and powercom driver doesn't work with uhid device. It seems for me that FreeBSD doesn't support it, so it doesn't create serial device for