[Nut-upsuser] suse linux and nut

[Peter Selinger]

Marc Collin wrote:
> 
> linux64:/home/collinm/Download/trunk # /usr/local/ups/bin/upsc myups at localhost
> driver.name: newhidups
> driver.parameter.port: /dev/hiddev0
> driver.version: 2.1.0
> driver.version.data: PowerCom HID 0.1
> driver.version.internal: 0.30
> powercom.coll2.feature3: 1
> powercom.coll2.feature4: 2
> powercom.coll2.feature5: 0
> powercom.coll2.feature6: 0
> powercom.feature1: 130
> powercom.feature2: 54
> ups.mfr: PowerCom

Good, this is what I wanted to see. The next step: please experiment
to see which of the powercom.* values change in response to events
(loss of power, on battery, low battery, battery charging, battery
full, etc). The point is that we will have to guess how to compute
"ups.status" from the values. The "low battery" condition is
especially important, as it is used by upsmon.

My guesses so far: 

powercom.coll2.feature3: 1    -- don't know; perhaps a status flag
powercom.coll2.feature4: 2    -- don't know; perhaps a status flag
powercom.coll2.feature5: 0    -- don't know; perhaps a status flag
powercom.coll2.feature6: 0    -- don't know; perhaps a status flag
powercom.feature1: 130        -- perhaps a line voltage? (depends on country)
powercom.feature2: 54         -- perhaps a battery voltage or charge level?

-- Peter