Nut upsdev - May 2008 - Tripplite SU1500RTXL2Ua and nut versions, battery line state fluctuates

I am trying to get a TrippLite SU1500RTXL2Ua working with nut on
Mandriva 2007.1, is there a particular version of nut needed to get this
to work?  At first I tried nut 2.0.5 (which came with 2007.1) but it
wouldn't work, and then research showed it was an older version of nut.
So nut-2.2.1-2 src rpm was pulled from Mandriva 2008.1, the binary rpm
built, and nut and nut-server installed from that binary rpm.  It mostly
works, but the UPS status is fluctuating between B and L.

With /etc/ups/ups.conf set like this:

[myserverups]
    driver = usbhid-ups
    port = auto
    desc = "TrippLite SU 1500RTXL2Ua"

and some entries in upsmon.conf and nut was started with:

service upsd start
service upsmon start

it seemed to start up ok.  upsc showed what looked like valid
data (see below).  Then I noticed in the log file that the monitor was
fluctuating between on battery and on line, so I shut down the monitor:

10:01:11 usbhid-ups[9482]: Startup successful
10:01:11 upsd[9490]: listening on 0.0.0.0 port 3493
10:01:11 upsd[9490]: Connected to UPS [myserverups]: usbhid-ups-myserverups
10:01:11 upsd[9492]: Startup successful
10:02:49 upsmon[9527]: Startup successful
10:02:49 upsd[9492]: Client upsmaster at 127.0.0.1 logged into UPS
[myserverups]
10:02:49 upsmon[9528]: UPS myserverups at localhost on battery
10:02:49 wall[9536]: wall: user ups broadcasted 1 lines (39 chars)
10:03:09 upsmon[9528]: UPS myserverups at localhost on line power
10:03:09 wall[9542]: wall: user ups broadcasted 1 lines (42 chars)
10:03:19 upsmon[9528]: UPS myserverups at localhost on battery
10:03:19 wall[9548]: wall: user ups broadcasted 1 lines (39 chars)
10:03:29 upsmon[9528]: UPS myserverups at localhost on line power
10:03:29 wall[9552]: wall: user ups broadcasted 1 lines (42 chars)
10:03:34 upsmon[9528]: UPS myserverups at localhost on battery
10:03:34 wall[9556]: wall: user ups broadcasted 1 lines (39 chars)
10:03:46 upsmon[9528]: Signal 15: exiting
10:03:46 upsmon[9527]: upsmon parent: read

Ran upsc repeatedly and it too showed that ups.status was sometimes OL,
and sometimes OB.  So, I googled, and found this thread:

http://lists.alioth.debian.org/pipermail/nut-upsdev/2007-January/001656.html

Which implied that this had all been worked out.  Perhaps not in the
release I'm using though?  Here is what upsc shows, some of the
measurements fluctuate a tiny amount, but the only one that jumps
completely is ups.status:

battery.charge: 100
battery.charge.low: 25
battery.charge.warning: 50
battery.runtime: 2072
battery.temperature: 27
battery.type: PbAc
battery.voltage: 5.3
battery.voltage.nominal: 48.0
driver.name: usbhid-ups
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.version: 2.2.1
driver.version.data: TrippLite HID 0.2 (experimental)
driver.version.internal: 0.32
input.frequency: 60.0
input.transfer.high: 138.0
input.transfer.low: 65.0
input.voltage: 123.2
input.voltage.nominal: 120
output.current: 2.30
output.frequency: 60.0
output.frequency.nominal: 60
output.voltage: 120.2
output.voltage.nominal: 120
ups.beeper.status: enabled
ups.delay.reboot: -1
ups.delay.shutdown: -1
ups.delay.start: 0
ups.load: 23
ups.mfr: Tripp Lite      
ups.model: TRIPP LITE UPS  
ups.power: 284.0
ups.power.nominal: 1500
ups.productid: 4003
ups.serial: 9516ALCPS519400548  
ups.status: OL
ups.test.result: Done and passed
ups.vendorid: 09ae

This UPS has been running on TrippLite's poweralert software, and I have
not observed it to fluctuate like this.  

Is there some other version of nut I should be using?

Thanks,


David Mathog
mathog at caltech.edu
Manager, Sequence Analysis Facility, Biology Division, Caltech