similar to: Little help with NUT on a Energizer UPS

Wondering if anyone could give me a little assistance here. I'm trying to setup monitoring of the UPS so the system can shutdown nicely. I have an Energizer ER-HM450 UPS. When I plug it in the system finds it as: kernel: input: USB HID v1.00 Gamepad [Ver 1.0 USB To RS232 Interface (V1.0) BaudRate 2400bps] on usb-0000:00:03.1-1 Looking at the FAQ makes me think I should have a section in the

Hello, all. Some time ago I bought myself a UPS which was advertised as USB-HID. It was a surprise to learn that while it definitely is recognized as USB device, the HID descriptor has no UPS pages at all. The only software it came with was a windows program written in visual basic. Trying to research this topic I found a reference to energizer USB ups driver and learned about variety of

04252006 0906 GMT-6 Apparently sometime in the last two weeks my Internet Explorer stopped working. My son said one day a message popped up and said Updates Available from Ubuntu so he did the update and he thought Wine was one of them. Anyway, I have to have IE for a IE only site. What can I do to figure out why it is not now starting? Wade

I got dovecot to start but then I had to reboot and now Im receiving errors: Apr 27 19:48:18 wadesmart dovecot: auth(default): You'll need to add at least one userdb Im still following the steps from http://wiki.dovecot.org/BasicConfiguration wade

Hi ALL, Powercom Imperial IMP-525AP seems to be fully compatible with NUT. Unfortunately, I can not disable beeper. upscmd -u {NUT_USER} -p {NUT_PASSWORD} powercom beeper.toggle returns *OK*, however, ups.beeper.status=enabled Thank you, Sergey ========== Additional info: 1) $ upsc powercom battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 30 battery.date: 2010/01/01

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

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

My UPS Powercom WOW-1000U does greatly work with NUT, but not auto-cofigurable... This UPS is not usb-hid ups, and works well with this settings in NUT: [powercom] desc = "powercom" driver = powercom port = "/dev/serial/by-id/usb-POWERCOM_CO.__LTD._USB_to_Serial-if00-port0" type = IMP lsusb -v fragment attached. Unlike other UPSes, gnome-power-manager does

Hello I have UPS Powercom Black Knight Pro 1200 (BNT-1200AP) I try to use nut, but powercom driver not understand my model Ok, i try to use type KIN1500AP and it's work But powercom driver can't set UPS's shutdown delay time Also i have powercom's original program (upsmon), and this program can do it What can i do for help to add this function to nut's powercom driver? For

Dino, Alexey, there are a number of users suffering issues with your Powercom devices. Could you (Dino, and Keven if possible) please have a look at the below one, from Angela, and check for a fix? I've scheduled to release 2.6.1 next week, and having that fixed is part of the list. 2011/5/16 Angela Williams <angierfw at gmail.com> > Hi All > > On Friday 13 May 2011 at

Hello Does anybody know if it's possible to monitor a Powercom EBk 500 (RS232)? the trick is that I am using a raspberry pi, it does not have RS232 so I connected a keyspan RS232 to USB adapter, but so far I can?t make this work. Thanks for your time to read this. -Edgar -------------- next part -------------- An HTML attachment was scrubbed... URL:

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

Hello all! Some days ago we received new UPS?Powercom BNT-2000AP with USB interface to replace an old staff and I've spent four last days trying to connect it with NUT. I have a FreeBSD 8.4 box with NUT 2.7.2. # dmesg|grep -i powercom ugen0.3: <POWERCOM Co.,LTD> at usbus0 uhid0: <POWERCOM Co.,LTD HID UPS Battery, class 0/0, rev 1.10/0.01, addr 3> on usbus0 uhid0: <POWERCOM

Hi, I have a little problem with PowerCom BNT600AP after running driver I see: root@rask> powercom -D /dev/ttyS1 Network UPS Tools - PowerCom and similars protocol UPS driver $ Revision: 0.5 $ (2.0.2) debug level is '1' Values of arguments: manufacturer : 'PowerCom' model name : 'Unknown' serial number : 'Unknown' line

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

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

Hi, colleagues! Something strange happens with a server. I am attempting to connect management interface of UPS with server via USB. In console I see a lot of errors: Mar? 7 13:42:04 xxx kernel: ugen2.2: <POWERCOM Co.,LTD HID UPS Battery> at usbus2 Mar? 7 13:42:05 xxx kernel: uhid0 on uhub6 Mar? 7 13:42:05 xxx kernel: uhid0: <POWERCOM Co.,LTD HID UPS Battery, class 0/0, rev 1.10/0.02,

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