similar to: cpsups and OP1250.

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 -

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

This weekend, I've been doing some work with the cpsups driver. I'm getting to the point that it seems to be working well, and I've managed to fix some of the trouble with it. How do I go about submitting it to the trunk?

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

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

> 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

Arjen de Korte wrote: > Author: adkorte-guest > Date: Sun Jun 24 18:57:03 2007 > New Revision: 983 > > Log: > Make 'powerpanel' driver first choice for Cyber Power text and binary protocol UPS systems. > > Modified: > trunk/ChangeLog > trunk/data/driver.list > trunk/drivers/cpsups.c Is it OK to backport this into Testing, with the exception

Hi, I've installed Nut 2.0.5 on a RedHat 9 box. I have a GeekSquad 1500 UPS. (GeekSquad is a BestBuy brand) I've found out that it's actually a CyberPower 1500 AVR LCD. I'm using it with the serial cable. I'm unable to get it working with any of the drivers provided with NUT. I've tried cpsups, cyberpower and powerpanel. here's the output of the different drivers

I took the modifications from doug reynolds, ported them to 2.0.4, and tried to make it more generic such that it would work for all old devices as well as the new CP1200AVR. I don't necessarily like the implementation because I don't like global vars, but it was what I could come up with without knowing the architecture better. Hopefully this will get included into the next version

Arjen, I read the following in the upgrade notes and just wanted to see what the status was for the cyberpower driver? The note reads: - The cpsups and nitram drivers have been replaced by the powerpanel driver, and removed from the tree. The cyberpower driver may suffer the same in the future. What does this mean to me -- a cyberpower user? -- David C. Rankin, J.D.,P.E. Rankin Law

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

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

Hello, I'm a new to NUT and I'm having some setup problems. Here's my setup: Nut 2.0.2 Gentoo Linux 2.6.13-r3 CyberPower AVR900 According to the hardware compatibility guide this setup should work. Here's what I get: root@gentoo (0) [552] % upsdrvctl start Network UPS Tools - UPS driver controller 2.0.2 Network UPS Tools - CyberPower driver 1.00 (2.0.2)

This is the patch to include SVN revision level in version number displays. There should be two enclosures; the patch itself and a new source file. common/upsversion.c. upversion.c defines a single function. upsversion(), that returns a version string for display. Some Makefile trickery ensures that this file will be recompiled whenever the project's SVN revision level has changed since it

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,

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

I finally took some time to lay down a consolidated roadmap to the next major milestone (2.4), and some update on this. 1) new documentation (User and Developer Manuals) -------------------------------------------------------------------------------------- This is the biggest change for 2.4. We will use the new test.networkupstools.org website to create and maintain the content, based upon the