similar to: Odd Values For Powercoms

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

Hello, I'm new there. I bought an UPS Powercom BNT-600AP. It's compatible in NUT with driver powercom and protocol type KIN1500AP. But I have a simple problem: the 'upsc' shows wrong values in battery.charge (maybe in other rows also /ups.load, voltages?/) - if battery is 100% charged it shows only 92.6% or 93.0%. I thing I have wrong values in driver parameters: batteryPercentage,

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

Hi! Normally nut was just worked and worked for me! Not this time though! Distro is Gentoo withe latest nut-2.6.0 emerged today. Linux kernel version is 2.6.36 UPS is PowerCom BNT2000AT "Driver" is powercom ups.conf looks like this! Okay so APC1 is not and APC! [APC1] driver = powercom type = BNT port = /dev/ttyS1 numOfBytesFromUPS = 16

Hi! Normally nut was just worked and worked for me! Not this time though! Distro is Gentoo withe latest nut-2.6.0 emerged today. Linux kernel version is 2.6.36 UPS is PowerCom BNT2000AT "Driver" is powercom ups.conf looks like this! Okay so APC1 is not and APC! [APC1] driver = powercom type = BNT port = /dev/ttyS1 numOfBytesFromUPS = 16

Hello everybody! I'm trying to use nut-2.4.1 with brand new UPS Powercom Imperial IMD-825AP USB. I've faced a problem that the driver powercom despite specifying type=IMP automatically re-detects the UPS as "KIN" and then interprets raw data incorrectly. The same problem was reported by other Powercom users on the official support forum ( http://forum.pcm.ru ). I suppose the

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,

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'

Dear R readers: I have written a short lme.R function, which adds normalized coefficients and White heteroskedasticity-adjusted statistics to the standard output. Otherwise, it behaves like lm. This is of course trivial for experts, but for me and other amateur users perhaps helpful. y= rnorm(15); x= rnorm(15); z= rnorm(15); m= lme( y ~ x + z); print(summary(m)); produces something

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, This patch includes port of NUT to LynxOS 4.0. The patch is against yesterday's svn tree. Here is a brief description of changes: drivers/powercom.c: Rename shutdown() to shutdown2(). shutdown() is already defined in LynxOS system header files. Please feel free to rename it more appropriately. (I didn't do it due to lack of imagination :-) ) include/proto.h: Added

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Has anyone used nut with a XPCC UPS, in particular one of the XVRT units? Their supplied monitoring tool "works", but I'd really prefer to use nut if possible. I've systematically gone through each of the drivers in /lib/nut and none seem to talk with the unit properly. I'll be talking with a XPCC support person tomorrow, though

I just bought an Ultra UPS system for my linux server, and I need help getting it set up. It's an Ultra 700VA UPS. NUT INFORMATION: Package (apt-get install nut) NUT VERSION: Latest Driver: I don't have one? Here's the device information from my syslog: Code: Jul 7 23:25:27 eric-desktop kernel: [ 3045.609066] usb 2-1: USB disconnect, address 3 Jul 7 23:25:30 eric-desktop

Mr Claesson, with my current configuration, the ups.status when the UPS is disconnected from the mains is "OB". There is no more "OB BOOST". Now my upsd.users is: [root] password = password allowfrom = localhost upsmon master actions = SET instcmds = ALL and upsmon.conf is: RUN_AS_USER root MONITOR Inform@localhost 1 root password master MINSUPPLIES 1 SHUTDOWNCMD

Thank you for your response. The point is that I have configured my system to shut down at the event "upsc Inform@localhost ups.status"!="OL", not at "LB". So there will be no /etc/killpower file created. At an ups.status != "OL" event, the following script named "notifyme" is run: echo `date` >> /root/upsLog echo " No power, shutting

Hello, Some time ago i bought 2 OPTI UPS devices, but was really sad to see the page about the OPTI protocol on the nut page. But i don't wanted to give up :) So i sniffed the serial communication using the windows application/driver and found out that these PS (PowerSeries) devices are different than the ES series mentioned on the Nut page. They use some kind of ASCII protocol, with the