Nut upsdev - Oct 2017 - Tripplite Smart Int 1000 - wrong numbers

Hi Peter,

2012/3/14 Peter Tuh?rsky <tuharsky at misbb.sk>:
> Hi, I'd like to inform You that this UPS communicates well via the
serial
> port. I haven't tested USB, and no shutdown testing so far, however, I
hope
> it will run well.
thanks for your report.

interestingly, I've been (and am still) working on HP support recently
and have a few patches stagging on this topic.
so expect some more information soon.

FYI, USB support for this unit comes through usbhid-ups (and not bcmxcp_usb).

cheers,
Arnaud
-- 
Linux / Unix Expert R&D - Eaton - http://powerquality.eaton.com
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.free.fr/

Hi, Arnaud

One thing bothers me. I don't see parameters like
"battery.runtime.low"
here. How will the UPS notice the NUT that it is running critically low? 
Or better said, when will it do that?

With APC, there is such parameter, default set to 120 seconds. As I 
understand, when battery goes critically low (2 minutes before getting 
fully discharged), it sends "battery critical" to the NUT server, and 
the NUT sends "shutdown" command to clients.

However with the HP, either R5000 or R5500, there is no such parameter, 
and I even didn't find it in web interface settings. There is quite 
opposite setting possible (custom): how many seconds AFTER the UPS goes 
battery, should it switch off. This is quite illogical, though.

So, I'm afraid a bit doing UPS fullscale test because I don't know, 
whether servers will have enough time to shutdown before UPS switches 
itself off. I know I will face it in future, however need more info now.

Peter

D?a 20.03.2012 19:15, Arnaud Quette  wrote / nap?sal(a):
> Hi Peter,
>
> 2012/3/14 Peter Tuh?rsky<tuharsky at misbb.sk>:
>> Hi, I'd like to inform You that this UPS communicates well via the
serial
>> port. I haven't tested USB, and no shutdown testing so far,
however, I hope
>> it will run well.
>
> thanks for your report.
>
> interestingly, I've been (and am still) working on HP support recently
> and have a few patches stagging on this topic.
> so expect some more information soon.
>
> FYI, USB support for this unit comes through usbhid-ups (and not
bcmxcp_usb).
>
> cheers,
> Arnaud

Hello,

I've got Tripplite Smart Int 1000 UPS with lan4.1 serial interface. 
Quite sympathetic UPS, I must say from first glance. I have made a 
proper serial cable (btw i hate all those constructor's decisions to 
make distinct serial wiring for each and every UPS type from each and 
every manufacturer!)

I use [tripplite] driver for NUT and I can use upsc to get report from 
UPS, but some of these numbers are nonsense. For example

battery.voltage??? 13.4
(the UPS has 3x6V batteries in serial = 18V and it would never drop so 
low IMO when the UPS claims battery.charge is 99% that I also consider 
suspicious, after few minutes of charging from seriously depleted state, 
but the batteries are not new either)

input frequency seems OK at 50,2Hz, but
input.voltage (both with maximum and minimum) give 128-129V, where I 
have european grid with 230V.

Is there a problem with interpretation of these values in driver 
(version 2.7.4, internal 0.9.1), or have I UPS with faulty sensors? I 
don't deny this possibility either since I bought it second hand.

Could I diagnose it somehow and/or help improve the driver if necessary? 
E.q., send You some raw output if You tell me how?

I also miss values such as output.voltage, battery.runtime etc, but 
maybe this model simply dosen't have the numbers reported.

Sincerely
Peter