similar to: Powercom driver patch

This is the patch to include SVN revision level in version number displays. There should be two enclosures; the patch itself and a new source file. common/upsversion.c. upversion.c defines a single function. upsversion(), that returns a version string for display. Some Makefile trickery ensures that this file will be recompiled whenever the project's SVN revision level has changed since it

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

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:

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,

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

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

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

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

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?

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,

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 :

On Monday, 24 August 2020 19:48:07 CEST Richard W.M. Jones wrote: > From: Mikhail Gordeev <obirvalger@altlinux.org> > It would be nicer to have few more details in the commit message and/or comments in the code, as there are things that definitely deserve explanations. Also, IMHO, it would be nice to have it split in different parts: 1) a simple patch that adds the ALT_family, in

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:

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

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

Hi I purchased an Ultra 1000VA UPS (http://www.ultraproducts.com/product_details.php?cPath=35&pPath=154&productID=154) I am trying to use nut with it (I am using gentoo linux) but can't find the proper driver. The numbers on the back suggest it might be similar to Black Knight Pro BNT-1000AP from Powercom (http://www.powercom-usa.com/ProductDetail.asp?ID=8974). So I tried the powercom

I'm trying to use NUT with PowerCom RPT-1000AP on CentOS 6/7 ups.conf: [RPT-1000] ??? driver = "usbhid-ups" ??? port = "auto" ??? vendorid = "0D9F" ??? productid = "0004" ??? product = "HID UPS Battery" ??? serial = "004-0D9F-000" ??? vendor = "POWERCOM Co.,LTD" ??? bus = "002" ??? pollfreq = 10 ??? offdelay = 120

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

On Wed, Nov 29, 2017 at 6:30 AM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Tue, Nov 28, 2017 at 2:38 PM, Joakim Tjernlund > <Joakim.Tjernlund at infinera.com> wrote: >> On Mon, 2017-11-27 at 18:18 -0500, Gene Cumm wrote: > >>> On Mon, Nov 27, 2017 at 6:07 PM, Joakim Tjernlund >>> <Joakim.Tjernlund at infinera.com> wrote: >>> > On

Hello All. I have PowerCOM ( http://pcmups.com.tw/ ) UPS management protocol specification at http://www.sovico.org/pcm.txt Current version of NUT contains any drivers include driver for Powercom, but not fully funcionality. This specification describe protocol for next series UPS: BLACK KNIGHT: All UPS AP series WARRIOR: WAR-1000AP WOW: All UPS U series IMPERIAL: All UPS KING: All UPS SMART