[Nut-upsdev] Driver for Cyberpower PR2200

Russ Romano russ at cb-1.com
Fri Apr 27 04:14:33 UTC 2007

I recaptured data this evening with portmon set to hex.  There are three
pages on the new spreadsheet, each is labeled to describe the scenario
captured, and the UPS's status log (with 1 second update interval) is
included on the same page of the spreadsheet.

The 3rd page is the scenario where the UPS is allowed to drain all the
way down and shut down.  In this mode I had to log the portmon data to a
file (rather than copy and paste the data out) and this changes the
format somewhat making it harder to read.  Since power panel shuts down
the windows machine collecting the data, I can't be sure just how much
data may be lost at the end of the scenario transcript.

The updated spreadsheet can be found here:


> -----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