Nut upsdev - May 2007 - cyberpower driver

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 use the
measurements from the UPS as is (like the 'powerpanel' driver does now)
and when we need to map them in some weird way (the existing
'cyberpower'
driver), we have a single driver for all CyberPower equipment with a
serial connection (binary and text protocol). From a user (support)
perspective, this is much better than the four drivers (cyberpower,
cpsups, nitram and powerpanel) we have now for CyberPower UPSes.

This might be as simple as looking at the firmware revision, or maybe we
need something more sophisticated. In order to find that out, I would like
to see the output from 'upsc <upsname>' for both the
'cyberpower' and
'powerpanel (revision 0.20.5 or higher)' drivers. You can simply change
between the two by changing the 'driver = cyberpower' or 'driver
powerpanel' line in the relevant entry in 'ups.conf'. For the
powerpanel
driver, it would also be nice to see the debug output from the startup
when started directly from the commandline (without 'upsdrvctl').
Typically, this can be done by running

    powerpanel -u root -DDD /dev/ttySx (fill in serial port here)

After detection, about 10 seconds of debug output are sufficient (stop the
driver in debug mode by pressing <ctrl>-c. Note that you will have to stop
NUT before you can run the driver in debug mode and that you probably want
to restart NUT afterwards.

Best regards, Arjen
-- 
Eindhoven - The Netherlands
Key fingerprint - 66 4E 03 2C 9D B5 CB 9B  7A FE 7E C1 EE 88 BC 57

Arjen de Korte wrote:
> 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.
Arjen, I installed the latest version of the trunk, and I am having some trouble
with the newest powerpanel driver:

Network UPS Tools -  CyberPower text/binary protocol UPS driver 0.20.7 ()
Warning: This is an experimental driver.
Some features may not function correctly.

debug level is '4'
Trying binary protocol...
send: (2 bytes) => 0d 0d
read: timed out
send: (2 bytes) => 46 0d
read: timed out
send: (2 bytes) => 46 0d
read: timed out
send: (2 bytes) => 46 0d
read: timed out
Trying text protocol...
send: (2 bytes) => 0d 0d
read: (2 bytes) => 23 32
send: (3 bytes) => 50 34 0d
read: (46 bytes) => 23 42 43 31 32 30 30 20 20 20 20 2c 31 2e 36 30 30 2c
30 30 30 30 30 30 30 30 30 30 30 30 2c 43 59 42 45 52 20 50 4f 57 45 52 20
20 20 20
send: (3 bytes) => 50 34 0d
read: (46 bytes) => 23 42 43 31 32 30 30 20 20 20 20 2c 31 2e 36 30 30 2c
30 30 30 30 30 30 30 30 30 30 30 30 2c 43 59 42 45 52 20 50 4f 57 45 52 20
20 20 20	
send: (3 bytes) => 50 34 0d
read: (46 bytes) => 23 42 43 31 32 30 30 20 20 20 20 2c 31 2e 36 30 30 2c
30 30 30 30 30 30 30 30 30 30 30 30 2c 43 59 42 45 52 20 50 4f 57 45 52 20
20 20 20
CyberPower UPS not found on /dev/cuad0

I not sure exactly what you've changed, but I am willing to start testing...