search for: powercoms

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

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

Hi list here is the patch to make fentonups recognize some PowerCOM's UPS's, and to setup terminal lines for them (at least for SMK-1500a) as powercom's original upsmon do. fentonups -x powercom works correctly with SMK-1500a (it screamed ''Communications with UPS lost - check cabling' or 'Short read during UPS id sequence' without this patch). Sorry for

Hey all, Finally got around to hooking up my Powercom BNT-1500AP to nut. It's the old serial interface. Connects okay and gets most information, but a couple of data are way off. Any config recommendations or upgrade recommended? I've played with config a little, but no hits yet. Details: NUT version 2.4.3 ups.conf: [ups] driver = powercom port = /dev/ttyS0

Dear Mr Claesson, prepare for quite a long letter from me. I hope you will have time to read it. I bestowed a whole morning on trying to identify the correct upstype. Here are the results: root@marto:/home/marto# /usr/local/ups/bin/powercom -DD -u root -a Inform -x type=KP625AP Network UPS Tools - PowerCom and similars protocol UPS driver $ Revision: 0.5 $ (2.0.4) debug level is '2'

Hi, Arjen; I am new to linux and not sure how to create the PowerCom-usb driver. So could you please compile powercom-usb file for me. I am happy to test it out with the USB PowerCom Ups. Thanks, Paul MCSE/MCSA/MCP ------------------------------ Message: 2 Date: Mon, 03 Sep 2007 11:13:32 +0200 From: Arjen de Korte <nut+users at de-korte.org> Subject: Re: [Nut-upsuser] Powercom USB UPS is

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

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

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

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

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

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:

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

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

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

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

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