similar to: Bug #302338 (genericups: custom configurationthrough ups.conf, not working)

I have just committed an updated version of 'drivers/genericups.c' in the Development tree. Since I have no access to a contact closure UPS at the moment (the only one I have is located two hours driving from where I'm now), can someone who has please verify that it now works? I'm fairly certain that it fixes this problem, but it would be nice to have a report that it is actually

Hello, I have a UPS connected to my server with the following: Server is Suse 10.1 Nut version is?Network UPS Tools - Generic UPS driver 1.32 (2.0.4) I installed this around 2005 and cannot remember how I installed the software. ups.conf: [sdrups] driver = genericups port = /dev/ttyS0 desc = "For Server & Backup" upstype = 9 upsd.conf: ACL all 0.0.0.0/0 ACL localhost

this is a bit off topic, but as there is a growing demand for our sponsor in North America, these can be helpful to others... 2006/3/31, Mike Patterson: > Arnaud Quette wrote on 3/31/06 3:05 AM: > > 2006/3/30, Ian Pilcher: > > >> I will certainly attempt to buy one when the time comes to replace my > >> aging Belkin model, but this is a product category in which mail

reported through launchpad: https://bugs.launchpad.net/bugs/253999 the possible regression is between nut 2.0.1 (sarge) and 2.2.1 (confirmed Jamie?) @Arjen: it may be related to some of your changes there... @Jamie: we'll need some debug output from the drivers (-DDD) Arnaud

Hello, ahgu >I have a unisys UPS, I probed the RS232 and notice that pin 2, >(receive data) is going from -6v (OL) to 12v(OB), but I don't see the >setting for the genericups. Seems nobody else is using the RD pin? >Any driver I can use? >Thanks >-Andrew Try RX as signal name (not RD). -- Best regards, Sergiy mailto:rendol@mail.zp.ua

It look to me that overwriting UPSTYPE CP signal or polarity in ups.conf have no effect. Looking at drivers/main.c source show that &upstab[upstype].line_norm is set to custom CP in initinfo() only _AFTER_ the serial signals are actually set by upsdrv_initups().

It look to me that overwriting UPSTYPE CP signal or polarity in ups.conf have no effect. Looking at drivers/main.c source show that &upstab[upstype].line_norm is set to custom CP in initinfo() only _AFTER_ the serial signals are actually set by upsdrv_initups().

On Jun 20, 2013, at 9:48 PM, Reed Hedges wrote: > UPSPORT=/dev/ttyS0 > > # type cablep kill t powerok battok cableok > robot --- RI 0 /RI --- --- > ? > > Is there an equivalent of ?---? in genericups? I think it's pretty much any value other than a valid

OK, I'll try "none" and see what happens. -----Original Message----- From: Charles Lepple [mailto:clepple at gmail.com] Sent: Thursday, June 20, 2013 10:14 PM To: Reed Hedges Cc: nut-upsuser at lists.alioth.debian.org Subject: Re: [Nut-upsuser] help creating custom genericups configuration - RNG only! On Jun 20, 2013, at 9:48 PM, Reed Hedges wrote: > UPSPORT=/dev/ttyS0 >

Hello again, I have a Sola 305 (aka Powerware 3110) here connected via a serial INT-0051 cable which I am trying to get working with nut. The driver.list file indicates that nut supports the Sola 305 when connected via the INT-0025C cable using the genericups driver with upstype set to 7 but it does not mention the INT-0051. I was able to use the "Basic CheckUPS II" utility provided

Hello, I am trying to understand how to create a custom configuration for the genericups driver. My system simply signals RI on a serial port on low battery. That's it, nothing else. This serial port is also being used for communications so the other lines are going to be changing all the time, unrelated to the UPS state. Is there a "null" upstype I can use, and then add LB=RNG?

Hi Shanan, Since I'm lagging too much on this point, I've forwarded your mail to the NUT development list, in the hope that another developer will have a bit of time to merge your patch. thanks for your contribution, Arnaud Quette -- Free Software Developer - http://arnaud.quette.free.fr/ Debian Developer - http://people.debian.org/~aquette/ Network UPS Tools (NUT) Project Leader -

Hi, I'm new to this list and I have a question concerning using the genericups driver (type 22) with the Cyberpower 485 in serial mode. When running the driver in debug mode: genericups -a myupsname_genericups22 -DDDDDD I observe the following statuses as the mains power dies, switching over to battery power, and then letting it discharge. Initially, with mains power on, status =

hi @ all, i just wonder, if it is posible to read the values for all the three phases of a mge galaxy 6000 ups? we have unfortunately one mge comet ups (one phase) to play at work, but it is important to know, how many information upsc can deliver from a galaxy. we plane to use web / snmp interface. can someone post the upsc from such ups? thanks in advance, miroslav -- SHALTEV.ORG

This code, added to drivers/genericups.h, supports the CyberPower SL series UPSes. I've tested with my 725SL - the online/on battery transition, and low battery status, and finally the shutdown signal all work as expected. *** genericups.h.orig Sun Nov 2 16:54:24 2003 --- genericups.h Mon Oct 3 13:49:00 2005 *************** *** 220,225 **** --- 220,234 ---- TIOCM_ST

I am trying to compile the latest nut version on Cygwin64 and have run into his issue Any Ideas?? gcc -DHAVE_CONFIG_H -I. -I../include -I../include -I/usr/include/neon -g -O2 -Wall -Wsign-compare -MT genericups.o -MD -MP -MF $depbase.Tpo -c -o genericups.o genericups.c &&\ mv -f $depbase.Tpo $depbase.Po In file included from genericups.c:24:0: genericups.h:147:4: error:

Hi all! I've been (very) out of the loop for a while, up to the point that I had completely missed that the mailing list has moved. Oh well. However, Kjell Claesson poked at me regarding the 3phase stuff, so I found out that I had missed the recent events. In any case, it seems that the situation is unchanged regarding 3phase support. As some of you remember I made a suggestion for a

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

Dir list! I'm using nut for many years on my home "server" without problems running on Debian 6.x nut version 2.4.3 Now I have decided to move to Debian 10. I have started from zero and install new system on a different disk. I have successfully installed new nut version 2.7.4 I've found one issue, that new version see always "low battery" state. Excerpt from syslog:

# HG changeset patch # User john.levon@sun.com # Date 1196969481 28800 # Node ID 2c28ac4db1f7542220b1472821e8631b79b6a23a # Parent 4a98d4b6e4daccd610175e3c0f8cab49b056c649 Fix ioemu compile serial.c was including another Linux-specific header. Signed-off-by: John Levon <john.levon@sun.com> diff --git a/tools/ioemu/hw/serial.c b/tools/ioemu/hw/serial.c --- a/tools/ioemu/hw/serial.c +++