[Nut-upsuser] Re: Re: Newpoint 200897 UPS

Peter Selinger selinger at mathstat.dal.ca
Sun Dec 31 20:51:23 CET 2006


Daniel Gimpelevich wrote:
> 
> On Sun, 31 Dec 2006 02:47:03 -0400, Peter Selinger wrote:
> 
> > You might have better luck with the unmodified
> > powercom-hid.[ch] (attached) generated by path-to-subdriver.sh, as
> > your modifications convert some of these values to strings and/or
> > other specialized datatypes that may not be appropriate for them.
> 
> driver.name: newhidups
> driver.parameter.port: auto
> driver.parameter.vendorid: 0d9f
> driver.version: 2.0.5-pre1
> unmapped.powercom1.powercom19: 128
> unmapped.powercom1.powercom20: 180
> unmapped.powercom1.powercom3.powercom10: 0
> unmapped.powercom1.powercom3.powercom11: 0
> unmapped.powercom1.powercom3.powercom12: 1
> unmapped.powercom1.powercom3.powercom13: 2
> ups.mfr: Powercom

Good. So now you should observe how this state changes in response to
power events (lose power, on battery, low battery, battery charging,
etc). If enough of the above flags change in a predictable way, we can
use this to set the ups.status register, which will be enough to drive
upsmon.

-- Peter



More information about the Nut-upsuser mailing list