[Nut-upsuser] NUT-2.0.3 - problems on setting values

[Patrick Agrain]

At 15:26 01/02/2007, Andreas Rust wrote:
>Hello,
>
>we have a MGE Pulsar Evolution 800 connected to a Fedora Core5 Server 
>using a serial cable.
>Installed and configured properly are RPM versions of
>
>nut-2.0.3-0.1.fc5
>nut-client-2.0.3-0.1.fc5
>nut-cgi-2.0.3-0.1.fc5
>
>which all work (mostly) fine.
>The server is connected to outlet.0 and properly shuts down when it's 
>loosing power after around 20 minutes. It also boots up whenever the ups 
>is getting power again.
>
>To outlet.1 there are a few components like a router, a small switch and a 
>phone connected.
>
>As to our understanding of , outlet.1.autoswitch.charge.low and 
>outlet.1.switchable it should be possible to power off these devices at a 
>given battery charge, right?
>
>However, using upsrw or upsset.cgi results in strange behaviour.
>Setting (ups|outlet.x).delay.(shutdown|start) to e.g. 120 returns some 
>random value (102, 68, etc.).

Meaby, these parameters decrease as soon as they are programmed. Reading 
them back never gives the programmed value.
ups.delay.shutdown and ups.delay.start behaves like this on our MGE UPS.

>The value reported by upsc "-1" appears odd to us as well.

Default value ? or re-programmation failed ?


>Also "ups.status: OL CHRG" looks strange, since the typical value should 
>be "OL" only, right?
>
>Issuing "upsc mgeups at localhost" results in the output:
>
>battery.charge: 100
>battery.charge.low: 25
>battery.runtime: 02025
>driver.name: mge-shut
>driver.parameter.port: /dev/ttyS0
>driver.version: 2.0.3
>driver.version.internal: 0.65
>input.frequency: 50
>input.voltage: 221
>outlet.0.desc: Main Outlet
>outlet.0.id: 0
>outlet.0.switchable: 0
>outlet.1.autoswitch.charge.low: 20
>outlet.1.delay.shutdown: -1
>outlet.1.delay.start: -1
>outlet.1.desc: PowerShare Outlet 1
>outlet.1.id: 1
>outlet.1.switch: 1
>outlet.1.switchable: 1
>outlet.2.autoswitch.charge.low: 20
>outlet.2.delay.shutdown: -1
>outlet.2.delay.start: -1
>outlet.2.desc: PowerShare Outlet 2
>outlet.2.id: 2
>outlet.2.switch: 1
>outlet.2.switchable: 1
>output.frequency: 49
>output.voltage: 222
>output.voltage.target.battery: 230
>output.voltage.target.line: 230
>ups.delay.shutdown: -1
>ups.delay.start: -1
>ups.load: 21
>ups.mfr: MGE UPS SYSTEMS
>ups.power.nominal: 800
>ups.serial: unknown
>ups.status: OL CHRG
>ups.test.result: Done and passed
>
>As said, apart from control over outlet.1 and 2 things are working as we 
>want them. Server sends me an email when it's going on battery or comes 
>back, etc. All we'd like to achieve is to shut down outlet.1 (or 2) when 
>battery charge drops down to 20%.
>
>On the previous server install we had FC4 running with a self-compiled 
>nut-2.0.4 and had the exact same troubles.
>Any ideas? Been searching the mailing list and google without much success.
>
>Also, I currently don't have physical access to the UPS and only handle it 
>remotely, so I cannot test much before the end of february. Just wonder if 
>the problem is known or has been found elsewhere.
>
>l8r
>
>Andreas Rust

Regards,
Patrick Agrain