similar to: fixing the cpsups driver

Hi, I'm running a Debian server (amd64) with the latest nut package (2.0.3-4). The server is connected to a Cyberpower OP750E ups. This seems to be connectable using nut with the cpsups driver. I've configured /etc/nut/ups/conf with the correct information. Here is what i get when trying to load the driver : serveurmeteo:/home/did# /sbin/upsdrvctl -v start myups Network UPS Tools -

Hello All I have a MicroDowell ups (BBox BP 1000) connected to a Gentoo box by serial cable. If I try to start the driver , I see the following : Network UPS Tools - CyberPower text protocol UPS driver .05 (2.0.5) Warning: This is an experimental driver. Some features may not function correctly. debug level is '13' ups_sync: send [\rP4\r] ups_sync: got ret 46 [#1000VA

Hello! I got my hands on a CyberPower 1500AVRT, and i'm trying to get it connected to my Gentoo machine. I've followed all the basic guides on setting up NUT and UPS' but have had no luck. My current ups.conf is: [cyberpower-gentoo] driver = cyberpower port = /dev/ttyS0 desc = Workstation Upon running /etc/init.d/upsd start or upsdrv start I get: * Starting

Hey All: I have a CyberPower OP1250 and I'm trying to mod the cpsups driver to work with it. I added the following lines to cpsups.c /* Added: Andrew Tubbiolo EXPERIMENTAL Aug 15, 2008 */ if(!strcmp(abbr, "#1250VA ")) { dstate_setinfo("ups.mfr", "%s", "CyberPower"); dstate_setinfo("ups.model",

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

I recently purchased a CyberPower CP1200AVR UPS and am trying to get NUT 2.0.3 or NUT 2.1.0 to work with the newhidups driver, but am having little success. Before I purchased I did some googling and saw people talking about problems so I'm guessing it may not be supported yet? I did find some posts about people getting it to (sort of) work with some hacks, but couldn't tell if they

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

I've just noticed that cpsups isn't listed anymore in driver.list. Any reason not have removed it from the source too? Still on the way to 2.4; any update on your confidence level to remove nitram and cyberpower too? -- Arnaud

Hi Recently i bought a MicroDoWell BP50, and with it followed a USB 2 serial converter. When i plug it into my 2.6.19 kernel, dmesg shows hiddev96: USB HID v1.10 Device [Cyber Power System CPS RS232 USB BRIDGE for UPS] on usb-0000:00:04.2-2 usbcore: registered new interface driver usbhid drivers/usb/input/hid-core.c: v2.6:USB HID core driver So, i figured i should use usbhid-ups,

> Author: nba-guest > Date: Mon Apr 24 20:45:39 2006 > New Revision: 414 > > Modified: > trunk/CHANGES > trunk/drivers/cpsups.c > Log: > Fix C++ style declarations between statements > > Modified: trunk/CHANGES Niels, What is the reason for 'fixing' this? Constructions like these are used in many locations throughout the sources (not only in the

Skipped content of type multipart/alternative-------------- next part -------------- A non-text attachment was scrubbed... Name: nut-patch.zip Type: application/zip Size: 18721 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20060706/c4c32226/nut-patch.zip

2006/11/16, Arjen de Korte <adkorte-guest@alioth.debian.org>: > Author: adkorte-guest > Date: Thu Nov 16 21:16:40 2006 > New Revision: 585 > > Modified: > trunk/ChangeLog > trunk/conf/upsd.conf.sample > trunk/server/conf.c > trunk/server/upsd.c > trunk/server/upsd.h > Log: > upsd: add MAXINIT parameter to upsd.conf to make the time upsd

Hi all! As I'm currently porting the HP PowerTrust driver from nut-1.4.3, I have a question regarding ups.delay.*. The PTs can delay the Shutdown/Restart and Kill commands by an arbitrary number of seconds, i.e. they wait for n seconds and then shutdown or kill. The delay for the restart after the shutdown can't be changed. Which of the ups.delay.* variables correspond to these values?

Hi all! As I'm currently porting the HP PowerTrust driver from nut-1.4.3, I have a question regarding ups.delay.*. The PTs can delay the Shutdown/Restart and Kill commands by an arbitrary number of seconds, i.e. they wait for n seconds and then shutdown or kill. The delay for the restart after the shutdown can't be changed. Which of the ups.delay.* variables correspond to these values?

I guess I have absorbed a bit of the agile development philosophy, or maybe I am a sucker for automatically generated status displays, but whatever the reason, we now have a Buildbot running: http://buildbot.ghz.cc/public/nut/ The idea is that anytime someone checks a new SVN revision into NUT, the buildbot master will ask the slaves to check out the changes and build NUT. Since the build

Hi, I've browsed the archives back for a few months and nothing has jumped out at me as being helpful, but since there doesn't seem to be a search facility it's certainly possible I've missed what I'm looking for. Anyway, I wonder if someone can help me. I've very recently installed nut 2.0.4-r1 on a gentoo box and am in the initial stages of configuration and testing.

I don't understand how the info_len element from the hid_info_t structure is used in usbhid-ups. It appears to me that the only use of this element is now to indicate the length of the string: > float info_len; /* if ST_FLAG_STRING: length of the string */ The above is clear, if the element is flagged as a string, the size of this string is put in this variable, so that we can use this in

Hi everybody, I've got an Unitek iZi UPS 525 with a serial interface. The supplied cable looks fairly simple: RX->RX , TX->TX and GND->GND. Using this cable and Minicom with 2400 8N1 I'm able to issue commands to the UPS using the "Megatec Protocol" http://www.networkupstools.org/protocols/megatec.html so I know the UPS is fairly "intelligent" :-) and the

Hello all, Some time ago, you all were very helpful in getting nut running on an OpenBSD system, using--for what it's worth--a CyberPower 1500AVR. So I finally got my FreeBSD system's UPS, also a CyberPower 1500AVR, within reach of its serial cable and I'm trying to get nut running here. I'm going nuts. Basically, I copied the OpenBSD configuration over to the FreeBSD system

Charles Lepple wrote: > On 8/2/06, Didrik Pinte <dpinte@itae.be> wrote: > > Le mercredi 02 ao=FBt 2006 =E0 08:08 -0400, Charles Lepple a =E9crit : > > > On 8/2/06, Didrik Pinte <dpinte@itae.be> wrote: > > > > Can you start the driver like this: "/sw/bin/newhidups -u root -DDD" > > > and paste some of the output? > > > > Here