similar to: [NUT]updated powercom driver for powercom BNT-500AP

Hello. It's been a while since I started this topic. I've finally tested it on Linux desktop PC. Nut version 2.6.4-2.3 Basically the behavior is the same as on raspberry pi. It reports "battery needs to be replaced" regularly and I got "on battery" message 114107.780504 Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Input, ReportID: 0x0a, Offset: 2, Size: 1,

OS name and version: pi at raspberrypi ~ $ cat /etc/*release PRETTY_NAME="Debian GNU/Linux 7.0 (wheezy)" uname -a Linux raspberrypi 3.6.11+ #393 PREEMPT Fri Mar 8 16:36:28 GMT 2013 armv6l GNU/Linux exact NUT version pi at raspberrypi ~ $ dpkg -s nut Package: nut ... Version: 2.6.4-2.3 NUT installation method: package exact device name and related information:

Thanks for the support. Here's list of when transition to battery with return to utility power within a few seconds occurred in last few days: Wednesday 1:41 11:48 11:54 12:59 13:42 14:42 18:13 18:14 Thursday 5:23 Friday 5:12 7:39 7:43 Saturday 7:34 Here's list of when messages that battery needs replacement occurred: Wednesday 20:34 Thursday 9:07 23:09 Friday 18:25 Saturday 7:32 19:47

While fundamentally working, I'm having a few issues with the driver... The default voltage quads (for every model) are way off... Showing ~95v when it should be ~117V. I've changed the 4th/final coefficient to +5.0, but haven't tested extensively (with fluctuating voltages). The input/output voltage appears to be swapped _most of the time_. When doing a battery test, or when

I took the log. Here's what happened. Broadcast Message from nut at rasp (somewhere) at 16:18 ... UPS BNT500AP at localhost battery needs to be replaced occurred when for the first time value "1" was read as "UPS.PowerSummary.PresentStatus.NeedReplacement", on this line: 6409.240690 Path: UPS.PowerSummary.PresentStatus.NeedReplacement, Type: Input, ReportID: 0x0a,

On Jun 5, 2013, at 11:49 AM, M?rti?? Pu??tis wrote: > Driver debug output attached. The debug output looks normal (many devices do not implement the interrupt pipe; hence, the timeouts). Unfortunately, we might need the log over a longer period of time, including your observations as to when various events occurred (such as transitions to battery). -- Charles Lepple clepple at gmail

On Jun 8, 2013, at 12:57 PM, M?rti?? Pu??tis wrote: > I'll take a longer driver log. This page (http://www.networkupstools.org/support.html) says that to take a driver log NUT should be stopped, so I won't be able to tell when these events occurred within a driver log. Hmm, I didn't realize it said that, but I think that's to prevent having two copies of the same driver

Hey all, Does anybody know there is a full working setup for the PowerCom BNT-1500AP. I got some stuff working with the Powercom driver and the type set to "KIN1500AP". But it seems that there is still missing usablity. I was wondering if anybody found any better configs? ---- excerpt of ups.conf [AVR1500] driver = powercom port = /dev/ttyS0 desc =

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,

[I am CC'ing Alexey from Powercom in case he has seen any of these issues with the Raspberry Pi hardware.] On Jun 10, 2013, at 1:05 PM, M?rti?? Pu??tis wrote: > I took the log. Here's what happened. > Broadcast Message from nut at rasp > (somewhere) at 16:18 ... > UPS BNT500AP at localhost battery needs to be replaced > > occurred when for the first time value

Hello all! Some days ago we received new UPS?Powercom BNT-2000AP with USB interface to replace an old staff and I've spent three 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

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,

On April 28, 2017 9:11:59 AM GMT+03:00, "????????? ?????????" <vtk-alexb at mail.ru> wrote: >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:

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

Hello. What about driver for my UPS? I have changed the powercom driver for myself, but I have made it not absolutely correctly. However, somehow this driver works. Now i have protocol spec for powercom BNT series and attach it to this email. It can be interesting to authors? -- ? ?????????, ??????? ??????? mailto:alex@reutman.ru JID: alex@reutman.ru ICQ: 5052225 -------------- next part

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

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

Hello. I have recently purchased a Powercom BNT-1000CS(Black Knight CS). I am new to NUT(and am not a programmer), but I have noticed that this model does not work with NUT. I am willing to provide details about this UPS for anyone who would like to add support for it(i dont know how to get much info though, so you'll have to tell me how). For starters, this is what happens when I do

Hello people, I use a BNT-600AP from PowerCom, and on driver loading (nut service start) the UPS goes off so I cannot use nut as service as the computer goes off with the UPS. When the computer is not using the UPS, but still connected, I see that the UPS goes off for a very short time, does battery check and goes on again. I don't know how to deal with this issue as I cannot use my UPS

Hello, Got PowerCOM BNT-1000AP, usb id 0d9f:00a6, firmware FW4.A6 nut 2.4.3 on debian stable shows only two instant commands: beeper.toggle - Toggle the UPS beeper -- not working test.battery.start.quick - Start a quick battery test -- works ok. No load and shutdown commands. Trying svn trunk version, with the same results. Debug output shows the problem: 0.035558