similar to: Megatec - modem control lines

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

Citeren Arnaud Quette <aquette.dev at gmail.com>: > Author: keyson-guest > Date: Wed Feb 4 15:03:36 2009 > New Revision: 1765 > > Log: > - Added mocrodowell.c/h into drivers/. add man/microdowell.8. Adjusted > drivers/Makefile.am and man/makefile.am. Adjusted the code for 2.4.0 in the > microdowell.c. Besides the things already mentioned by others and the obvious

Hi ups-devel, As I looked throw www.networkupstools.org site, haven't found any pointers where to send patches, so I hope this is the right place. (Please let me know weather this is the right place.) The patch contains a minor change in the logic of the driver, our Effekta MHD 3000 UPS continuously writes status data to the serial port, so one has to send a CR character and empty the

Hello, all. Some time ago I bought myself a UPS which was advertised as USB-HID. It was a surprise to learn that while it definitely is recognized as USB device, the HID descriptor has no UPS pages at all. The only software it came with was a windows program written in visual basic. Trying to research this topic I found a reference to energizer USB ups driver and learned about variety of

Hi Henning, you should get in touch with Carlos, who his developing a generic megatec driver (available from svn: http://eu1.networkupstools.org/source.html) Arnaud -- Linux / Unix Expert - MGE UPS SYSTEMS - R&D Dpt Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://people.debian.org/~aquette/ OpenSource Developer -

I have been running a Smart-UPS RT 3000 VA using nut successfully over the 940-0095B cable for a couple of years. I have just received a second unit, but it is slightly different in 3 ways that I have found so far. 1. It's a Smart-UPS RT 3000 XL 2. The 940-0095B cable now uses an RJ45 connector at the UPS end. 3. It now requires a baud rate of 9600 instead of the 2400 used previously.

Hi Jon, your patches are malformed because (presumably) your email client wrapped this lines. Could you please send these as a unified diff ("diff -u"), and send them in attachments, rather than as a copy-and-paste? Thanks, -- Peter Jon Gough wrote: > > Peter, > Here are the files I have worked on. I hope I have diff'd them > correctly. I have not touched the

Hello Panagiotis 2015-04-01 16:28 GMT+02:00 Panagiotis Kritikakos < panagiotis.kritikakos at nikitec.gr>: > Hello all, > > OS name: FreeNAS 9.3 > NUT version: 2.7.2 > NUT installed method: Bundled with FreenNAS 9.3 > Device: EATON 5SC 1000 (http://powerquality.eaton. > com/Products-services/Backup-Power-UPS/5SC.aspx?cx=5& >

Description: Replace many usleep and some sleep calls with nanosleep. usleep is stated in its manual page as removed by POSIX. Contrary to its predecessors, nanosleep semantics is well defined. The replacement, which is mostly in drivers, is untested. Supplements http://bugs.debian.org/633791. Last-Update: Sat, 13 Aug 2011 14:04:48 +0300 Index:

Hello Arno, Thanks for the quick reply. FreeNAS is FreeBSD-based. Yes, I could test a patch. As I have mentioned, this behavior is not seen at every single reboot but after most reboots. Also, some times, the connectivity can be lost without even rebooting. That is not very often can have happened a few times. Best regards, Panagiotis On 2/4/2015 5:44 ??, Arnaud Quette wrote: > Hello

Hi there First a big thank you to all nut developers. I tried the 2.0.4 as well as the 2.0.5-pre1 versions with my CyberPower OP1000E connected to a serial to USB converter. All I got was the following: # /usr/local/ups/bin/upsdrvctl start Network UPS Tools - UPS driver controller 2.0.5-pre1 Network UPS Tools - CyberPower text protocol UPS driver .05 (2.0.5-pre1) Warning: This is an

Hi! My Liebert Power Sure PSPXT 450 with standard driver doesn't works, so I've done this modification and now it's works. # diff liebert_MY.c liebert.c 178 < ser_set_speed(upsfd, device_path, B9600); --- That is, I've only setup the port's speed. Can you update SVN code? Thanks Bye Beppe Ursino -------------- next part -------------- An HTML attachment was

will be used by Nut's powercom driver. I've failed to google anything about this UPS working with Linux. > > What does 'lsusb -d 0d9f:0002' say for this device? Bus 001 Device 002: ID 0d9f:0002 Powercom Co., Ltd The current progress is like this: With help from linux-hotplug guys (http://thread.gmane.org/gmane.linux.hotplug.devel/13551) I've managed to /dev/ttyUSB0 to

Hi there, A couple years ago, I had patched the "fentonups" nut driver to allow it to work with my Unitek Alpha 500 UPS. My patch had been accepted and incorporated in the standard fentonups driver. I have had no time to stay involved in the "nut" project since (and besides this I'm not a developper...). 2 days ago I upgraded from Ubuntu Gutsy to Ubuntu Hardy and got

Hi! I've recently come into to the possesion of a couple of Belkin Omniguard 3200 UPS's. Given the horrible apache/java based software they come with, I decided to see if I cannot get them to work with NUT. To cut a long story short, they work out to be SEC -based, and extensively modifying the nut-1.4 driver code to come up with the attached two files. I've marked them

Best fortress support was understandably dropped, but we still use them, and someone else may want the driver I ported to nut-2.0. We also often attach the serial cable from a UPS to a network terminal server, since servers these days don't come with very many serial ports. (They call them "legacy" ports.) I submitted a patch to support these for nut-1.x, and it was rejected

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

On 1/23/07, Henning Brauer <hb-nut@bsws.de> wrote: > good new first: the megatec driverin 2.0.5 now works with the Online > Xanto S3000R here - well, for the very basics. > > the UPS has NO way ofidentifying itself. It also does not respond to > the power ratings query ("F"). I previously used a hacked up fentonups > driver. This means the driver cannot figure out

G'day. I have a UPS here that is driven by the Fenton UPS driver, and which requests that I report the ID string to the NUT developers: root@anu:~# upsdrvctl start smk800 Network UPS Tools - UPS driver controller 2.0.4 Network UPS Tools - Fenton UPS driver 1.22 (2.0.4) Unknown ups - please report this ID string: #M+H SMK-800 2000 V6.2 Detected Unknown MK-800 on /dev/ttyS0 The

good new first: the megatec driverin 2.0.5 now works with the Online Xanto S3000R here - well, for the very basics. the UPS has NO way ofidentifying itself. It also does not respond to the power ratings query ("F"). I previously used a hacked up fentonups driver. This means the driver cannot figure out the battery voltage and thus no battery charge level, which is a problem in our