similar to: [PATCH] Add OptiUPS VS 575C support to PowerCom

Hi! (first of all, FAQ tells me I should mention "queequeg" :P) I recently bought the UPS mentioned in the subject, assuming it'd work with Linux somehow, and the protocol will soon be something common -- turns out I was wrong. Website of the UPS: http://www.opti-ups.com/ -> USA -> Click on the big banner when it turns up (turns out I can't like to it directly, probably

* Charles Lepple <clepple at gmail.com> [2013-08-27 19:53:38 -0400]: > On Aug 26, 2013, at 3:10 PM, Florian Bruhin wrote: > > Also, what does the red color mean in the compability table? Anything > > that's not supported, or is it just "you have to solder your own cable > > but then you should be okay"? > > Technically, one star is "protocol

* Florian Bruhin <me at the-compiler.org> [2013-09-17 15:35:01 +0200]: > Heya, > > I recently bought an Opti-UPS[1] ValueSeries 575C and now I'm trying > to write a NUT driver for it. > [...] I started reading through all drivers using the same baudrate, and the powercom protocol and driver looked really familiar! I then got it to work by doing some minimal changes to

Hi Arnaud, Hi Scott, Hi list, Here is a patch to support the Zinto D from ONLINE USV-Systeme AG. I already sent a version to Russell Kroll (2006-04-09), without no response and I cannot find support for Zinto in svn until now. I found a discussion on this list about the Xanto from ONLINE, but the Zinto seems to use different commands. The commands are quite similar to those for Opti-UPS, so I

On Aug 26, 2013, at 3:10 PM, Florian Bruhin wrote: > queequeg Subtlety is key :-) > It came with some "Sentinel" software for Windows. Hmm, not sure if this is similar to software we have seen before. > Also, what does the red color mean in the compability table? Anything > that's not supported, or is it just "you have to solder your own cable > but then you

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

Hello, Some time ago i bought 2 OPTI UPS devices, but was really sad to see the page about the OPTI protocol on the nut page. But i don't wanted to give up :) So i sniffed the serial communication using the windows application/driver and found out that these PS (PowerSeries) devices are different than the ES series mentioned on the Nut page. They use some kind of ASCII protocol, with the

Hi Matthias, thanks for writing, but please reply to the nut-upsdev mailing list, not to me personally. There are lots of good people on the list whose input you wouldn't want to miss. Thanks, -- Peter Matthias Goebl wrote: > > On Sun, Nov 26, 2006 at 12:40:44PM -0400, Peter Selinger wrote: > > Matthias, > > > > NUT drivers should always detect devices

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

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

It seems the `libmodbus` library or headers were not found, or something similar - so the driver against it was not built. Did you install `libmodbus-dev` before the build? What does `config.log` in the build root say (and.or the summary shown after you run the `configure` script)? On Sat, Sep 16, 2023 at 7:46?PM FatGear <fatgear1 at free.fr> wrote: > Hi, > > I don't know what

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

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

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 *Simon, i got a similar setup here (also a powercom-oem-product, but in my case labeled by a swiss "manufacturer") with the same problems, using powercom's upsmon works fine, while nut completely refuses to cooperate. after trying almost everything i somehow hopeless surfed on the official nut-page, when i saw that there are powercom-products which don't need the

Hey all, I've tried some very base configs with the powercom 2200, but I can't seem to get it to work. Has anyone dealt with these UPSes before, or know if they use the standard powercom drivers? I'd be more than happy to allow access to my test system so someone more knowledgeable can take a look (and am also willing to pay something for the solution of said problem.) -Dan

Hi! I've tried the Fenton Driver for my UPS. The Powercom driver doesn't work. Here is the results: Network UPS Tools - UPS driver controller 2.0.0 Network UPS Tools - Fenton UPS driver 1.21 (2.0.0) Unknown ups - please report this ID string: #PCM SMK-1000 2001 V9.0 Detected Unknown MK-1000 on /dev/ttyS0 Have you any ideas to make it compartible with NUT. Thanks! With

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