Fwd: [Nut-upsdev] Fun with TrippLite

[Peter Selinger]

Hi Charles and Jonathan,

I am going through my over 300 unread NUT messages, and I just
discovered this one from mid-December. At the time, I was trying to
clean up the tripplite subdriver of newhidups, but never got the
information I needed. I have enabled this driver now, but it is marked
"experimental". The driver is still incomplete, in the sense that
there are many unmapped device variables. "upsc" should show variables
such as these:

UPS.ffff0010.00ff0001.ffff007d
UPS.PowerSummary.PresentStatus.0084004b
UPS.Flow.ConfigVoltage

Cleaning this up requires the help of someone who actually has such a
device.

Jonathan, if you run this driver, could you use "upsc" to print out
the states of the various variables? Also observe how they change over
time as you plug/unplug the power, initiate battery tests, etc.
Perhaps you can figure out the meaning of some of the variables
starting with "UPS.*", which are the ones I haven't yet mapped. For
example, one of them might be the system load that you were looking
for.

Some of the instant commands have been implemented, and may/may not be
working. You could test the behavior of 

test.battery.start.quick
test.battery.start.deep
test.battery.stop
load.off
shutdown.return
shutdown.stop
beeper.on
beeper.off

and let me know if they do anything sensible. Note: only run these
tests if nothing important is plugged into the UPS, as it might cut
power. Also, beeper.on and beeper.off might not do anything unless
there is an "alarm condition" (such as low battery).

The most important variable to look out for is ups.status, as this is
what upsmon uses to figure out if/when to shutdown the system. You may
test that it shows OL (which the UPS is on line), OB (when it is on
battery), or LB (when the battery is low). 

Also, Jonathan, the segmentation fault bug that you encountered in
December should hopefully have been fixed by now. So you might want to
give this another try if you have not been using it the last few
months. 

Your help will be appreciated in rounding off this driver to a
distributable state! Thanks, -- Peter


Charles Lepple wrote:
> 
> Peter,
> 
> any objections to enabling the Tripp-Lite HID subdriver?
> 
> ---------- Forwarded message ----------
> From: Jonathan Freedman <jef at pleiades.ca>
> Date: Dec 15, 2005 1:20 AM
> Subject: Re: [Nut-upsdev] Fun with TrippLite
> To: Charles Lepple <clepple at gmail.com>
> 
> 
> Hey
> 
> So yeah. Instead of sleeping I decided to get this working. As you
> mentioned, there appears to be a subdriver for the tripplite in existence.
> However it was not enabled. That part was easy... I simply added a "
> &tripplite_subdriver" on line 42 and a "#include "tripplite-hid.h" on line
> 34 with the rest of the includes.
> 
> It works; and the nagios plugin works; and I am happy. The only catch is
> it doesn't seem to give the current load; but it didn't do that under
> windows either so I can live with it.
> 
> Cheers
> 
> Jonathan Freedman
> Vice President
> Pleiades Consulting
> (902) 444-4335 x400
> 
> 
> --
> - Charles Lepple
>