similar to: No subject

Tokarev replyed when Alexey Sidorov wrote the "enhanced" features of the powercom driver, and supposing is the same Michael Tokarev of the upsd, why didn't he completed the powercom driver? I see that from time to time, someone asks on the list to improve or add features to the driver (a few years ago "Dan Mahoney, System Admin" offered a network for development), but

Tokarev replyed when Alexey Sidorov wrote the "enhanced" features of the powercom driver, and supposing is the same Michael Tokarev of the upsd, why didn't he completed the powercom driver? I see that from time to time, someone asks on the list to improve or add features to the driver (a few years ago "Dan Mahoney, System Admin" offered a network for development), but

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

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

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,

Hello all, Last week I rescued and UPS from the trash (it's really amazing the kind of things you can find in the trash of the university research labs). No manual, no cd, no cables, just the unit. It's name is "Blizzo 500", and blizzo was just the rebranding of a spanish reseller which has been out of the scene for nearly two years now, at least according to the wayback

Hey all, I found a pinout of powercom's Kingpro UPSes in their manual. http://www.powercom-ups.com/manuals/kingpro.pdf Page 11. Unfortunately, this doesn't give PROTOCOL details. Does anyone have a "first step" at how to decode that? (for example, how to gauge line speed, how to "snoop" the serial port under windows? (for which the only software exists right

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, To to build an RPM from the nut 2.0.3 source I've corrected the old nut.spec.in file. Please find a copy of the slightly updated spec file attached. The changes are documented at the bottom of the spec file. Regards, Will -------------- next part -------------- # don't know how different I can do this %define majorver 2.0 %define version 2.0.3 %define relver 1 %define nutuser

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

Might be of interest for some of you, especially: o HTB - detailed look into new QoS shaper - Martin Devera o Linux Packet Classification Performance - Jamal Hadi Salim o Status of IPv6 Implementations - Peter Bieringer o High Availability using Keepalived - Alexandre Cassen o Application Layer Fingerprinting - Hendrik Scholz

I've got a Powercom Imperial UPS, with an internal USB<=>serial converter. It implements the same protocol as other powercom devices implements, but only when talking over serial port (there's no such port on the device). Someone wrote a draft version of usbserial driver for it, and the UPS works with this kernel-level driver and with powercom driver from nut (using /dev/ttyUSBx

Guys, For what it's worth, after months of trying to troubleshoot issues with them, and after paying them around $2500 for setup and a down payment (it's unclear what of that will be refunded, if any) BroadVox -- http://www.broadvox.net/ -- decided to terminate our contract without any valid reason, and the only explanation they could cite was "it's because of the software

Hi, I'd like to organize my Asterisk to properly handle incoming SIP/IAX/H323 callerids so they can be called back if needed. I have three incoming contexts for sip, iax and h323 calls. To each incoming call I'd like to prepend certain number that will be catched with pattern matching on output calls. For instance for iax I have: [from-iax] exten => s,1,NoOp(IAX call from outside

On 4/5/16 4:04 AM, Michael S. Tsirkin wrote: > On Mon, Apr 04, 2016 at 02:14:19PM -0400, Jeff Mahoney wrote: >> This fixes the following warning: >> drivers/virtio/virtio_ring.c:1032:5: warning: ?queue? may be used >> uninitialized in this function >> >> The conditions that govern when queue is set aren't apparent to gcc. >> >> Setting queue = NULL

On 4/5/16 4:04 AM, Michael S. Tsirkin wrote: > On Mon, Apr 04, 2016 at 02:14:19PM -0400, Jeff Mahoney wrote: >> This fixes the following warning: >> drivers/virtio/virtio_ring.c:1032:5: warning: ?queue? may be used >> uninitialized in this function >> >> The conditions that govern when queue is set aren't apparent to gcc. >> >> Setting queue = NULL

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'

As far as I can remember I only opened sip and tftp ports for the phone. For some reason (didn't look into it too much) the call stays with sip and doesn't use RTP. The problem you describe (the call doesn't even ring on the other side) is something I had and was solved by upgrading the firmware. Checkpoint's tracker explicitly said what connection attempts were blocked and why.

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