Displaying 20 results from an estimated 200 matches similar to: "Driver for Powercom BNT/KIN/IMP/IMD series"
2006 Apr 21
1
Powercom BNT-1200AP
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
2006 Aug 18
0
(no subject)
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'
2010 Jul 02
0
Powercom driver patch
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
2007 Dec 29
1
Odd Values For Powercoms
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
2006 Dec 22
1
Powercom BNT-1200AP driver
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
2006 Aug 17
1
powercom upstype identify problem
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
2006 Dec 11
2
howto setup BNT-1500AP on gentoo
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
2005 Sep 15
1
SSO Samba/AD integration
OK, I'm certain that this topic has been beat to death, but I need some
assistance. I am trying to migrate to a SSO for the majority of our
workstations and servers within our organization. I am currently trying
to integrate a Gentoo Linux workstation to authenticate to the AD
server. Once I get the process nailed down, I'll be moving on to bigger
and better things...
Prior to
2006 May 17
2
NUT LynxOS port
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
2014 Nov 12
0
POWERCOM HID USB controller update
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
2017 Dec 13
0
core_udp_sendto: no mapping
On Wed, Dec 13, 2017 at 7:03 AM, Joakim Tjernlund
<Joakim.Tjernlund at infinera.com> wrote:
> On Mon, 2017-12-11 at 08:59 +0100, Joakim Tjernlund wrote:
>> On Sun, 2017-12-10 at 14:41 -0500, Gene Cumm wrote:
>> > CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is
2017 Dec 14
1
core_udp_sendto: no mapping
On Wed, 2017-12-13 at 10:34 -0500, Gene Cumm wrote:
> CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
>
>
> On Wed, Dec 13, 2017 at 7:03 AM, Joakim Tjernlund
> <Joakim.Tjernlund at infinera.com> wrote:
> > On Mon, 2017-12-11 at 08:59 +0100, Joakim
2014 Nov 12
1
POWERCOM HID USB controller update
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
2006 Jul 08
0
Powercom BNT-600AP and NUT (powercom driver)
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,
2009 Nov 05
0
[LLVMdev] Debug Information for LLVM 2.6 and TOT
Hi John,
On Thu, Nov 5, 2009 at 8:43 AM, John Criswell <criswell at uiuc.edu> wrote:
> Does the debug facilities in LLVM TOT, at present, maintain information
> better than LLVM 2.6 (i.e., if a front-end puts the debug information in,
> will the optimizations not take it out)? Does the information that the
> llvm-gcc front-end adds comparable to what llvm-gcc in LLVM 2.6 does?
2006 Aug 17
2
powercom UPS shoutdown discussion
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
2018 Mar 09
0
For Extracting gridded netcdf data into output files where each file representing the individual grid
Hi,
I have to calculate Extemes, for that I wrote a script for extracting IMD
Tmax data for one year. I need to get output files where each file
representing the individual grid with daily values.Since, my data is of
0.5*0.5 resolution, I need to get 3721(61*61=3721) output files. But, I am
only getting 3482 output files.
I think the problem is with naming the output files using paste command,
2008 Sep 05
0
Powercom IMP detection fix
Hi there.
I found out a bug in Powercom IMP/IMD series detection. Fix is obvious
(attached).
Else I own Powercom IMP-825AP and can provide a debuging support.
With best regards, Alexey
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: nut-powercom-patch
Url:
2020 Aug 24
0
[PATCH v2v] Add ALT support
From: Mikhail Gordeev <obirvalger@altlinux.org>
---
v2v/convert_linux.ml | 49 +++++++++++++++++++++++++++++++++++++++++++
v2v/convert_linux.mli | 2 +-
2 files changed, 50 insertions(+), 1 deletion(-)
diff --git a/v2v/convert_linux.ml b/v2v/convert_linux.ml
index a871d754f4..5ae83a2f66 100644
--- a/v2v/convert_linux.ml
+++ b/v2v/convert_linux.ml
@@ -52,6 +52,7 @@ let convert (g :
2014 Nov 12
2
POWERCOM HID USB controller update
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