similar to: genericups CP custom config not working

Hi! I have a MGE Pulsar ES 8+ UPS. Here is the response of some commands: - Si --> 3000 44 0 - Si 1 --> Pulsar ES8+ 0 - Ai --> 5 0 It's not recognized very well by the current (from CVS) mge-utalk driver: [root@srv01 ~]# /home/rog/src/nut/drivers/mge-utalk -i 20 -DDD -u root /dev/ttyS0 Network UPS Tools - MGE UPS SYSTEMS/U-Talk driver 0.86 (2.1.0) debug level is '3'

UPS: http://www.eaton.com/Eaton/ESeriesUPS/DXUPS/index.htm?wtredirect=www.eaton.com/DXUPS I have the same problem on two different computers. The first one is running Ubuntu 12.10 i386 , the second one is running Debian 6.0 x64. Both of them are updated. I tried using different serial cable but the result is the same. The connection to the ups using Windows 7 and Winpower is working fine on

On 18.4.2013 ?. 22:24 ?., Arnaud Quette wrote: > > 2013/4/18 Pladi Computers Ltd. <pladi at lovechnet.com > <mailto:pladi at lovechnet.com>> > > UPS: > http://www.eaton.com/Eaton/ESeriesUPS/DXUPS/index.htm?wtredirect=www.eaton.com/DXUPS > > I have the same problem on two different computers. The first one > is running Ubuntu 12.10 i386 , the

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

Hi, I own a Yunto-Q 700 (made 2000 by online usv systems) and a Yunto-Q 1200 (made 2010). They both work with blazer_ser, but didn't shutdown. I straced the proprietary driver and found the ups expected the return time given with _5_ digits instead of 4, else the command was ignored by the ups. And the Yunto don't send rating/manufacturer informations. I don't want to commit this to

Hi all ! I have communication issues between my station and my old Pulsar EX10 UPS, (U-Talk) connected by RS232, when using v2.4.1 of nut-server. I tried to come back to version 2.2.2 and then, communication start and is operational. Maybe it's linked to bug 498655, but i haven't seen any answer ? http://www.mail-archive.com/debian-bugs-dist at lists.debian.org/msg566711.html Here are

Hi, I am trying to talk to an MGE Pulsar Extreme UPS over RS232 with the mge-shut driver but I'm having some problems. It appears to init OK but I can't, say, turn the outlets off, eg.. harrow:~>upsc mge@localhost battery.charge: 78 battery.charge.low: 20 battery.runtime: 05760 driver.name: mge-shut driver.parameter.port: /dev/cuad1 driver.version: 2.0.3 driver.version.internal: 0.65

* I committed into CVS the gendb patch that I sent to the mailing list on September 12. Arnaud, I hope you approve of this patch; it is more reliable than the previous method in tracking the correct dependencies. * This, together with some other minor recent changes on the Development branch, is between the "before_PSE_3" and "after_PSE_3" tags. Arnaud: if you

Hi All, I have an mge pulsar esv 14+ rackmount UPS connected via straight through serial cable to a USB to serial adaptor (My motherboard does not have a native RS232 port). I am running Ubuntu Server 9.04 x64, and nut 2.4.1-2ubuntu4 installed via APT. I am getting the error: Poll UPS [ups1 at localhost] failed - Driver not connected My conf files: (ups.conf) [ups1] driver=mge-utalk

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

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

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 >

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 >

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, 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, I am trying to talk to an MGE Pulsar Extreme UPS over RS232 with the mge-shut driver but I'm having some problems. It appears to init OK but I can't, say, turn the outlets off, eg.. harrow:~>upsc mge@localhost battery.charge: 78 battery.charge.low: 20 battery.runtime: 05760 driver.name: mge-shut driver.parameter.port: /dev/cuad1 driver.version: 2.0.3 driver.version.internal: 0.65

Hi all. I posted this to LKML, but might get a faster reply if I go direct to you. I haven't subscribed, so please reply to me too... I began a bk export -du patch and shortly afterwards a cp -arl on the kernel source tree. The latter got stuck in ext3_lookup iget_locked find_inode_fast __wait_on_freeing_inode schedule The box is running 2.6.8.1 with SMP, HT scheduler and preempt (can

Hi. I know that for the problem that will follow many things other than ext3 are involved, like a kernel upgrade, a possible coreutils mis-behaviour and other, so I beg your pardon if I'm not in the right place ... Now the problem. I have met a trouble upgrading web/dns server running linux. Precisely, I have upgraded the kernel from 2.4.9 to 2.6.6 and the hard disk also, from 20Gb to