similar to: several problems with Powercom BNT-500AP

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,

[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. 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,

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

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

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

Hi, 2010/12/27 ??? <pointbre at naver.com> > First of all, thanks for your effort to NUT Project, > I'm developing remote monitoring solution for many devices based on linux > server. > In field test, we reached the power shutdown problem which may cause the > crack of linux file system. > I search the solution and find NUT project and i'm very glad that NUT >

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

Good Day Roger AA. notice that during the test, you have little or no load, since despite being in state OB DISCHRG the battery.charge is still 100. It's best to perform such tests with a dummy load such as a table lamp and an old fashioned incandescent 100 watt bulb. ==> Yes. I got it and try to ascend load as below results dinow-All-Series:~# upsc pcmups Init SSL without

Good Day Roger AA. notice that during the test, you have little or no load, since despite being in state OB DISCHRG the battery.charge is still 100. It's best to perform such tests with a dummy load such as a table lamp and an old fashioned incandescent 100 watt bulb. ==> Yes. I got it and try to ascend load as below results dinow-All-Series:~# upsc pcmups Init SSL without

Good Day Roger Price AA. Hi, Normally one would expect the UPS to disconnect it's power outlets after the default ups.delay.shutdown = 20 seconds. ==> I got it. I tried to command "upsdrvctl shutdown" on both line-mode and battery-mode ==> But ups do not disconnect its outlets power ----------------------------------------------------------------------------------- BB.

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,

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 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 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. 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 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, Last week I rescued and UPS from the trash (it's really amazing the kind of things you can find in the trash of the university research labs). No manual, no cd, no cables, just the unit. It's name is "Blizzo 500", and blizzo was just the rebranding of a spanish reseller which has been out of the scene for nearly two years now, at least according to the wayback

Hi! Is there any user of nut having this type of UPS? ( http://www.pcmups.com.tw/product/iCute.html) It works nice under windows and also is detected under Linux and installed as USB HID device. There is problem however, as the software provided by its manufacturer (http://www.pcmups.com.tw/download/Download/UPSMON_USBV091.zip) doesn't seem to comunicate with the UPS at all. It shows messages

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