similar to: battery.voltage Powercom Macan MRT-3000

I suppose, this approach may be apply to some other data from that UPS. I could check another values and ask powercom support for other data items to explain interpretation, if it will help. On 13.01.23 14:22, Greg Troxel wrote: > That makes sense to me. The field needs to be split into bytes. The > low byte is the integer part of voltags, and the high part is units of > 10 mV. And

That makes sense to me. The field needs to be split into bytes. The low byte is the integer part of voltags, and the high part is units of 10 mV. And this is per cell. Probably the unit is measuring the total and then dividing by 36. But volts per cell will have the same interpretation for varying cell counts, so it's a nice representation.

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

Dear all, I'm using R to perform multiple comparison testing on agriculture genotype trials. To perform the Duncan's MRT, I use the qtukey() function with the following syntax: qtukey(p = ((1 - 0.05) ^ (pos - 1)), nmeans = pos, df = ni) I experience a strange behaviour when the number of means in the trial and the number of residual degrees of freedom (ni) becomes high

Hi list here is the patch to make fentonups recognize some PowerCOM's UPS's, and to setup terminal lines for them (at least for SMK-1500a) as powercom's original upsmon do. fentonups -x powercom works correctly with SMK-1500a (it screamed ''Communications with UPS lost - check cabling' or 'Short read during UPS id sequence' without this patch). Sorry for

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

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:

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

Hi All! I have a traoble whith my ups, - megatec driver can not calculating % of charging and voltage on battery: # uname -a FreeBSD backup.*.*.* 8.1-RELEASE FreeBSD 8.1-RELEASE #0: Wed Sep 22 12:25:01 EEST 2010 ups.conf [Powercom] driver = megatec port = /dev/cuau0 #battvolts=12:24 desc = "powercom sxl-1000A" # ./nut start Network UPS Tools - UPS driver controller 2.4.1

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

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

Hi, Arjen; I am new to linux and not sure how to create the PowerCom-usb driver. So could you please compile powercom-usb file for me. I am happy to test it out with the USB PowerCom Ups. Thanks, Paul MCSE/MCSA/MCP ------------------------------ Message: 2 Date: Mon, 03 Sep 2007 11:13:32 +0200 From: Arjen de Korte <nut+users at de-korte.org> Subject: Re: [Nut-upsuser] Powercom USB UPS is

2008/10/18 Sergiy Yegorov <prapor at unixzone.org.ua>: > Dear Arnaud! Hi Sergiy and Alexey, > Please, check this patch. It adds USB-attached Powercom UPS Imperial & > Black Knight series. Originaly code is writed by Kirill Burdin > (burdin at post.ru) for Imperial UPS`es. > I`m just sysadmin without enought C programming > skills, so I adapted it to nut-2.2.2-6

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'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,

Hi ALL, Powercom Imperial IMP-525AP seems to be fully compatible with NUT. Unfortunately, I can not disable beeper. upscmd -u {NUT_USER} -p {NUT_PASSWORD} powercom beeper.toggle returns *OK*, however, ups.beeper.status=enabled Thank you, Sergey ========== Additional info: 1) $ upsc powercom battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 30 battery.date: 2010/01/01

Ok, so I previously thought I had to use usbhid-ups but when I eventually got it going this is what I got:- This Powercom device (0d9f/0002) is not supported by usbhid-ups. Please use the 'powercom' driver instead. So I switched to the powercom driver, but I have tried a whole bunch of likely suspects for the port setting, none of which have worked Tried so far:- com1 with these

Hi Have been trying to get nut and Powercom Vanguard 2000 ups communicating ? in the /lib/udev/rules.d/52-nut-usbups.rules file we have this entry #? PowerCOM VGD - Vanguard? - usbhid-ups ATTR{idVendor}=="0d9f", ATTR{idProduct}=="0004", MODE="664", GROUP="nut" ? In the /etc/ups/ups.conf [UPS] ??????? driver = usbhid-ups ??????? port =

Heya, after I bought an OptiUPS VS 575C and discovering it won't work with Linux (silly me) I sniffed the protocol, found out it's very similiar to the protocol in the powercom driver, so I ended up adding support for that UPS to that driver. The patch is against the current git HEAD and works fine for me since weeks now. The shutdown sequence also works fine (on Archlinux). This is my

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