[Nut-upsuser] Microdowell (cpsups) driver segfault

[varain at flashmail.com]

Hello Arjen,

Wednesday, June 20, 2007, 9:59:34 AM, you wrote:

>>> As an experiment, if I compile just the driver from 2.2.0-pre1 (with the
>>> required options), can I expect it to work ? (assuming the problem was
>>> solved in this version)
>> Assuming you're coming from version 2.0.5, this will work. It won't be
>> compatible with earlier versions, since we changed the naming of the
>> driver sockets. I don't see the advantage of just compiling a driver
>> though. You'd need to setup the build environment anyway, so you might
>> just as well compile the rest of the package too.

> I was referring to the powerpanel driver here. Don't expect the cpsups
> driver to be fixed (ever). Nobody has cared for it in the past two years
> and we have a more generic driver now, that will deal with all Cyber Power
> UPSes (text and binary protocol). We will probably drop the cpsups driver
> from the tree by the time we release nut-2.2.0.

> Best regards, Arjen

The powerpanel driver starts like this:

Network UPS Tools - UPS driver controller 2.0.5
Network UPS Tools -  CyberPower text protocol UPS driver 0.12 (2.0.5)
Warning: This is an experimental driver.
Some features may not function correctly.

warning: sent "\r", expected "#2\r" but got ""
Detected CYBER POWER 1000VA on /dev/ttyS0


after this it seems to work ok, even if it the numbers reported for input voltage look a little low.
(205 to 211 in a country where nominal voltage is supposed to be 230). Maybe it's just lousy power.(I have no easy way to verify)

Just to confirm: cpsups is still broken in 2.2.0-pre1. (it still segfaults, no matter what the compilation options are)

It would be nice if someone could update the Microdowell entry in
http://www.networkupstools.org/compat/stable.html to "powerpanel" instead of "cpsups" .


Anyway, thanks for all the help.

-- 
Best regards,
 varain                            mailto:varain at flashmail.com