[Nut-upsdev] smart1050slt by tripp lite

[Charles Lepple]

On Feb 1, 2010, at 4:16 PM, chance fulton wrote:

> 117 off mains
> then  I added some more load around 350
> I let it run till it shut itself off.

Here's the status from around when the power was cut:

  116.394032     send_cmd: received 53 01 04 00 00 64 00 0d  
'S....d..' (OK)
  118.313822     send_cmd: received 53 01 04 00 00 64 00 0d  
'S....d..' (OK)
  120.361600     send_cmd: received 53 01 04 00 01 58 00 0d  
'S....X..' (OK)
  122.408599     send_cmd: received 53 01 04 00 01 4c 00 0d  
'S....L..' (OK)
  124.329167     send_cmd: received 53 01 04 00 01 40 00 0d  
'S.......' (OK)
  126.376596     send_cmd: received 53 01 04 00 01 3c 00 0d  
'S.......' (OK)
  128.296736     send_cmd: received 53 01 04 00 01 36 00 0d 'S.... 
6..' (OK)

(I removed a bunch of intermediate lines, but the driver did  
transition from "OL" to "OB" as it should.)

What's disturbing is that towards the end, the "LB" indicator is  
flickering:

1809.265763     send_cmd: received 53 01 04 00 01 1f 00 0d  
'S.......' (OK)
1811.185555     send_cmd: received 53 00 04 00 01 00 00 0d  
'S.......' (OK)
1813.233333     send_cmd: received 53 01 04 00 01 1f 00 0d  
'S.......' (OK)
1815.281109     send_cmd: received 53 01 04 00 01 1f 00 0d  
'S.......' (OK)
1817.200900     send_cmd: received 53 01 04 00 01 1f 00 0d  
'S.......' (OK)
1819.248680     send_cmd: received 53 01 04 00 01 1f 00 0d  
'S.......' (OK)
1821.296454     send_cmd: received 53 00 04 00 01 00 00 0d  
'S.......' (OK)
1823.216246     send_cmd: received 53 01 04 00 01 1e 00 0d  
'S.......' (OK)
1825.264023     send_cmd: received 53 01 04 00 01 1e 00 0d  
'S.......' (OK)
1827.183813     send_cmd: received 53 00 04 00 01 00 00 0d  
'S.......' (OK)
1829.231590     send_cmd: received 53 00 04 00 01 00 00 0d  
'S.......' (OK)

Hopefully, NUT will catch the first "LB" indicator, and shut down at  
that point.

I added a couple more things to SVN (voltage, temperature, etc.)

One thing you might want to try is pulling the power, and running the  
driver with "-k" to shut it down. There is a 64-second "offdelay", but  
you could try setting it lower, e.g. "-x offdelay=5".

-- 
Charles Lepple