Displaying 20 results from an estimated 1000 matches similar to: "Powercom BNT-2000AP(USB)"
2017 Apr 30
0
Powercom BNT-2000AP(USB)
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:
2017 Apr 26
0
Powercom BNT-2000AP(USB)
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
2019 Jul 16
2
Trouble getting Roline/Powercom UPS recognized
Hi all,
I’m new to NUT and have some trouble getting my new UPS to work.
Since the HCL listed Powercom UHID models as „green“ I thought buying
a Roline (German rebranded Powercom) model would be a good idea.
The OS is FreeBSD:
FreeBSD freenas-pmh.local 11.2-STABLE FreeBSD 11.2-STABLE #0 r325575+6aad246318c(HEAD): Mon Jun 24 17:25:47 UTC 2019 root at
2011 Oct 04
2
PowerCOM BNT-800AP (0d9f:0004)
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:*
2009 Sep 19
1
Powercom 600AP USB support
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
2011 Nov 13
1
Installing Powercom BNT-2000AP on CentOS 5.6
Hi Guys,
Am a Linux newbie and need some help setting up this UPS with NUT on Cent
OS 5.6. So basically I have the following packages installed with yum:
libusb-devel-0.1.12-5.1.x86_64
libusb-devel-0.1.12-5.1.i386
libusb-0.1.12-5.1.x86_64
libusb-0.1.12-5.1.i386
nut-2.2.2-1.el5.x86_64
When I run service ups start I get the following:
Starting UPS driver controller:
2011 May 17
3
Powercom issues in NUT (was: PowerCom BNT2000AT ups on nut 2.6.0 - second try)
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
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
2007 Dec 24
3
Driver for Powercom BNT/KIN/IMP/IMD series
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,
2010 Jan 08
3
USB problems on 8.0-STABLE
I am having problems with mouse, keyboard and APC UPS. When attempting to
start apcupsd I get the following error:
Jan 8 17:42:06 Ace apcupsd[1606]: apcupsd FATAL ERROR in generic-usb.c at
line 636 Cannot find UPS device -- For a link to detailed USB trouble
shooting information, please see <http://www.apcupsd.com/support.html>.
Jan 8 17:42:06 Ace apcupsd[1606]: apcupsd error shutdown
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
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
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
2013 Jun 17
2
report
This PowerCOM device (0d9f:0004) is not (or perhaps not yet) supported
by usbhid-ups. Please make sure you have an up-to-date version of NUT. If
this does not fix the problem, try running the driver with the
'-x productid=0004' option. Please report your results to the NUT user's
mailing list <nut-upsuser at lists.alioth.debian.org>.
No matching HID UPS found
Driver failed to
2013 Jun 17
1
report
device -Powercom
model: BNT-800A
17 ???? 2013, ? 14:55, Charles Lepple <clepple at gmail.com> ???????(?):
> On Jun 17, 2013, at 5:32 AM, Yuriy Yurev wrote:
>
>> This PowerCOM device (0d9f:0004) is not (or perhaps not yet) supported
>> by usbhid-ups. Please make sure you have an up-to-date version of NUT. If
>> this does not fix the problem, try running the driver
2013 May 01
1
Powercom BNT-1500AP serial config
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
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
2007 Nov 06
1
BNT-1000AP
Hi guys,
We've got a BNT-1000AP (powercom) BlackKnight UPS that works with the
KIN1500AP model in the powercom driver. Well, almost. It seems the
input frequency and the battery charge is swapped around:
# upsc blackknight at localhost
battery.charge: 46.5
driver.name: powercom
driver.parameter.manufacturer: BlackKnight
driver.parameter.modelname: BNT-1000AP
driver.parameter.port:
2014 Jul 25
3
POWERCOM HID USB controller update
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
2013 Jun 17
0
report
On Jun 17, 2013, at 5:32 AM, Yuriy Yurev wrote:
> This PowerCOM device (0d9f:0004) is not (or perhaps not yet) supported
> by usbhid-ups. Please make sure you have an up-to-date version of NUT. If
> this does not fix the problem, try running the driver with the
> '-x productid=0004' option. Please report your results to the NUT user's
> mailing list <nut-upsuser at