similar to: Ubuntu 10.04 Ultra 700VA UPS Setup Nut

Howdy, I've been trying for a while now to get this running. Can anybody please tell me what the proper configuration is for this unit ??? This is what I've got/tried so far: # cat ups.conf # Start with # # # upsdrvctl -u nut -D start MEGATEC MODE=netserver user=nut # Ultra ULT33046 2000 VA 1200 W

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

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

All, I'm using the Powercom driver from 2.2 (not the one recently mailed to thelist). Since it's a KIN2200AP, I'm using the driver settings right from the manpage. All the values look "sane" when I'm on-line, but note some of the odd values (<-- Here) when on battery: Also, does anyone know if this UPS supports logging of the "boost" or

Hi All I'm trying to get my Ultra UPS connected. It connects using a standard USB cable I have --with-drivers=hidups in the configure command and I have lsusb showing Bus 001 Device 002: ID 0d9f:0001 Powercom Co., Ltd Bus 001 Device 001: ID 0000:0000 I have /dev/usb/hiddev0 now matter what I try I keep getting upsdrvctl start Network UPS Tools - UPS driver controller 2.0.3 Can't

I've read through the archives http://lists.alioth.debian.org/pipermail/nut-upsuser/2006-August/001550.htmland http://lists.alioth.debian.org/pipermail/nut-upsuser/2006-August/001558.html. Going through the readme, http://eu1.networkupstools.org/doc/2.2.0/INSTALL.html, I made it to step 8 before the problems started. Originally I had used the usb program supplied with the ups from powercom,

hi i bought a ultra ULT31502 ups someone seem 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

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

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

please subscribe to the nut user mailing list ( http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser) and post the output of "/path/to/usbhid-ups -DDDDD -a <your_ups_name_in_ups.conf>" 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, fellow NUT gurus; I am having a big issue with our new Powercom Imperial Digital UPS. The UPS is come with a serial over USB port and plug into the usb port on the computer. I am having problem to setup our fedora 7 linux machine talks to the ups. The kernel 2.6.22.1 seems to be able to detect the ups is plug into one of its usb port. But it just couldn't establish a connection with

Hi, fellow NUT gurus; I am having a big issue with our new Powercom Imperial Digital UPS. The UPS is come with a serial over USB port and plug into the usb port on the computer. I am having problem to setup our fedora 7 linux machine talks to the ups. The kernel 2.6.22.1 seems to be able to detect the ups is plug into one of its usb port. But it just couldn't establish a connection with

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

On Mon, 15 May 2017, Dinow Hsieh wrote: > ==> I have tried this command "upsdrvctl shutdown" as below results (However the UPS still sustain the power) > > ??? Network UPS Tools - UPS driver controller 2.7.1 > ??? Network UPS Tools - Generic HID driver 0.38 (2.7.1) > ??? USB communication driver 0.32 > ??? Using subdriver : PowerCOM HID 0.4 > ??? Initiating UPS

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

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

In a separate discussion, on 6/26/17 4:04 AM, Arnaud Quette wrote: > Hi > > If you're sure it's a HID device, add an entry in drivers/powercom-hid.c > { USB_DEVICE(POWERCOM_VENDORID, 0x0002), NULL }, > > Then autogen.sh + configure... > Please also report back so that I can update the code > > Cheers > Arno Thanks! I don't *know* whether or not

I was able to make NUT and my Powercom SPIDER UPS (USB port) work under the Raspberry Pi Desktop (Debian). Everything works in VMware Workstation 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