[Nut-upsdev] Driver for Cyberpower PR2200

Russ Romano russ at cb-1.com
Thu Apr 26 19:10:13 UTC 2007


Sounds like a plan.  I really appreciate all the support on this!

I'm a bit curious about how much of the OEM functionality I can expect
the final driver to support.  Having not gotten it working, I didn't go
through the exercise of fully configuring the clients, etc.

Using the OEM linux software (and I'm sure the windows software is the
same) it is possible to set many aspects of the UPS's behavior.  Here is
a capture of the "information" dump from the OEM linux software:

UPS model : PR2200
UPS version : 1.100
output format : 120 V
battery format :
buzzer : [on],off
cold start : on,[off]
enable status record : [on],off
shutdown system after power fails : [on],off
enable auto save function :[on],off
status record interval : 10 minute 0 seconds.
power failure causes system shutdown after : 30 seconds.
time to wait system complete shutdown : 2 minute 0 seconds
communication port : None,Auto,ttyS0,[ttyS1]
high input voltage configuration :
[138],139,140,141,142,143,144,145,146,147
low input voltage configuration : 88,89,90,91,92,93,94,95,96,[97]
percentage of battery critical capacity configuration
:[25],30,35,40,45,50,55,60
battery mode output voltage configuration : 110,[120],130

Is it safe to assume that the UPS is simply reporting what it monitors
and the software handles the rest?  Or is the "shutdown system after
power fails" a setting in the UPS itself?  In order for my machines to
come back on when power recovers, it's necessary for the UPS to have
completely powered off after all the computers shutdown, and then power
back up after the line power returns (and batteries are sufficiently
recharged).

With the over and under voltage conditions, it is possible for this UPS
to generate 120V output, while keeping it's batteries charged with the
under or over voltage line power.  Will I loose such functionality with
NUT, or is that a hardware configuration that I can set with the OEM
software and then switch to NUT?

Thanks again,
-Russ

> -----Original Message-----
> From: Kjell Claesson [mailto:kjell.claesson at epost.tidanet.se]
> Sent: Thursday, April 26, 2007 2:14 PM
> To: Russ Romano
> Cc: 'Arjen de Korte'; nut-upsdev at lists.alioth.debian.org
> Subject: RE: [Nut-upsdev] Driver for Cyberpower PR2200
> 
> 
> Hi Russ
> 
> tor 2007-04-26 klockan 11:35 -0400 skrev Russ Romano:
> > I will recapture with portmon set to hex this evening.  I was a bit
> > concerned about capturing an overwhelming amount of data, 
> so I tried
> > to break it up into pages of a particular behavior in the
> spreadsheet.
> > Is this good, or would you rather I just start capturing
> from the time
> > I run the software, and run the UPS through it's paces?
> > 
> 
> I think this is the right way. Then we don't have to search
> for it. So do as the last capture but in hex.
> 
> The start-up sequence is important that you capture from the
> beginning (start of the ups) and until it do normal polls of 
> data. In that way we can se if it needs any special setup 
> sent to the ups.
> 
> > As I noted before, I'll try to capture the log of status
> info from the
> > OEM software that matches the stream of data captured in
> portmon while
> > varying the load and cutting power off and back on.
> 
> Then you may split it on separat pages like (load change)
> when you change the load on the ups, (on battery) what 
> happens when you pull the plug, (line power back) when you 
> insert the line plug, and (discharge) when running on 
> battery. Also important is when it hit low battery state.
>  
> Regards
> Kjell
> 
> 
> 
> 




More information about the Nut-upsdev mailing list