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

On Tue, 31 Jan 2006, Arjen de Korte wrote: > > But I'd like to know what I'm testing. Could you please post a bug tracker > > URL? I'm having trouble finding #302338. > > That may be because I closed the bug (maybe a little overenthousiastic). See > > http://alioth.debian.org/tracker/index.php?func=detail&aid=302338&group_id=30602&atid=411542 >

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 =

> +22 = Gamatronic UPSs with alarm interface > + [CP=RTS] [OL=CTS] [LB=\-DCD] [SD=DTR] > + > +22 = CyberPower SL seriess > + [CP=RTS] [OL=CTS] [LB=\-CAR] [SD=DTR] > + > + This part of the patch is no good. While TIOCM_CAR is equivalent to TIOCM_CD (at least in some implementations) CAR certainly isn't handled the same as DCD by genericups. It won't be

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?

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

Hi, I'm trying to configure my ups with nut which is a locally made one. It uses a rs232 port to talk to the computer and comes with a software called "Powermanager Lite" which is provided by Richcomm and supports Windows, Linux and UNIX. According to the manual it uses the Richcomm circuitry to talk to the computer and uses a drycontact protocol. Unfortunately I couldn't

I am using nut 2.2.2 and I have a CyberPower CP550SL. According to the drivers list, I should be using genericups with upstype set to 7, but when I try that and when I run upsc I get: driver.name: genericups driver.parameter.LB: 04 driver.parameter.pollinterval: 2 driver.parameter.port: /dev/ups driver.parameter.upstype: 7 driver.version: 2.2.2 driver.version.internal: 1.34 ups.mfr: CyberPower

I am using nut 2.2.2 and I have a CyberPower CP550SL. According to the drivers list, I should be using genericups with upstype set to 7, but when I try that and when I run upsc I get: driver.name: genericups driver.parameter.LB: 04 driver.parameter.pollinterval: 2 driver.parameter.port: /dev/ups driver.parameter.upstype: 7 driver.version: 2.2.2 driver.version.internal: 1.34 ups.mfr: CyberPower

Hi, I wanted to report some success with monitoring this UPS, a "Geek Squad" brand GS-700U that I purchased earlier this year from Best Buy Canada. Information about this... thing is very scarce so here is what I know: The unit itself is probably made by Cyberpower. It has a 9-pin serial port on the UPS, as well as a serial-USB adapter thing. I cracked open the serial-USB

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

Hello folks, I have a question regarding a sweex product. Its bundled with UPSmart v 2.12. I installed nut accordingly to the user manual included in the software. A quick check of data/drivers.list revealed to me i should use the: "Sweex" "500/1000" "contact closure - shipped with UPSmart" "genericups upstype=7" driver this driver

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

To people with APC, CyberPower, Belkin and TrippLite UPS'es and using the 'usbhid-ups' driver. There are some concerns that the usbhid-ups driver is not acting as it is supposed to do. Could you run the following command (as root and with the mains plugged) and check if the UPS powers back on automatically? upsmon -c fsd I think we should *not* release nut-2.2.1 if we're not

Citeren Arnaud Quette <aquette.dev op gmail.com>: > Date: Thu, 09 Dec 2010 14:01:14 +0000 > Subject: svn commit r2726 - in branches/windows_port: common drivers include > Author: fbohe-guest > Date: Thu Dec 9 14:01:07 2010 > New Revision: 2726 > URL: http://trac.networkupstools.org/projects/nut/changeset/2726 > > Log: > More work on serial drivers. > Still

I'm looking for people that are using the 'cyberpower' driver that has been available for some years now. It seems the overhauled 'powerpanel' driver could support your UPS too. The commands and status bytes used are identical, the only difference being the way the values read for battery charge, temperature and frequency are interpreted. If we can find a way to detect when to

I'm looking for people that are using the 'cyberpower' driver that has been available for some years now. It seems the overhauled 'powerpanel' driver could support your UPS too. The commands and status bytes used are identical, the only difference being the way the values read for battery charge, temperature and frequency are interpreted. If we can find a way to detect when to

Peter, Looking through the usbhid-ups subdrivers, I came across the following function in apc-hid.c, presumably added by you about two years ago (if not, my apologies): 41 /* returns statically allocated string - must not use it again before 42 done with result! */ 43 static char *watts_to_av_conversion_fun(long value) { 44 static char buf[20]; 45 46 snprintf(buf,

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

Dear nut users, I am running nut-2.6.0 on Slackware-Linux-13.37.0 with kernel 2.6.37.6. I am trying to get the software work for a repotec UPS with model name: RPT-1003AU. The UPS communicates with the computer via USB. I know that the model is not officially supported but I want to try out whether it will work with some of the repotec drivers. Here is the result with the genericups upstype=13