[Nut-upsdev] tripplite smart2000rmxl2u product id 3014

[Charles Lepple]

On Mon, Oct 20, 2008 at 11:20 AM, Ken Teh <teh at anl.gov> wrote:
> Charles Lepple wrote:
>>
>> On Fri, Oct 17, 2008 at 11:55 AM, Ken Teh <teh at anl.gov> wrote:
>>>
>>> I have it sort of working.  I was able to run the usbhid-ups driver with
>>> the productid as you suggested but I have to run everything as root.  Here's
>>> a quick summary of results:
[...]
>>> Today was the smoke test day.  I took the UPS off line power, partially
>>> drained the battery with a electric heater, and monitored the battery charge
>>> with upsc.  It kept dropping down to 1 and stayed there like forever.
>>>  upsmon never went through executing the low battery notify event or the
>>> shutdown.  I noticed that the UPS LEDs indicated adequate power (it was
>>> still green) so this leads me to the next questions:
>>
>> What fraction of the UPS power capacity was the heater wattage?

Still interested in the answer to this one.

I don't think you mentioned how you were cutting line power, but Arjen
has pointed out that it is better to leave the ground connected (e.g.
use a power strip switch or circuit breaker to remove power during
testing). That could affect the accuracy of the charge meter.

Another thing is that you may need to fully drain the battery once to
calibrate the charge meter. The manual for the UPS may cover this
procedure.

[...]
> You
> mentioned debug logs during the discharge cycle.  Could you be more
> specific?  upsd logs?  upsmon logs?

I am referring to the log output from starting the usbhid-ups driver
with "-DDD" on the command line. This is basically the raw data from
the UPS. You can use something like "/lib/nut/usbhid-ups -DDD -a
name-of-ups | tee /tmp/tripplite.log", then cut power, and press
Ctrl-C after you have tried draining the battery for a while. If upsd
is running, you should also be able to retrieve status with upsc.

I assume you meant that you saw battery.charge go to 1 in the upsc
output. We probably will see that in the driver log output, so you
could just check that once to be sure the problem still exists.

>  Is there a specific piece of code I
> should try hacking?  tripplite_usb?  Or, something higher up?

The "tripplite_usb" driver predates your UPS. It is basically the old
Tripp Lite serial protocol wrapped in USB packets, as opposed to the
standardized HID Power Device Class (PDC) protocol that Tripp Lite,
APC and MGE use now.

Things specific to the Tripp Lite PDC UPSes are in tripplite-hid.c,
and there are some more generic parts in usbhid-ups.c, libhid.c/h and
libusb.c/h.

I am not yet sure what needs to be changed, though.

-- 
- Charles Lepple