<p>Dave,</p>
<p>My NUT skills are rusty so I may need correcting, list feel free to enlighten me.</p>
<p>Last I recall there are two main triggers for shutdown, LB (low battery) from the "status" variable or a timer that begins when the "status" varible goes from OL (on line) to OB (on battery). In your case I would think the timer is the way to go. Now with that said I also recall that at least on some UPS units you can adjust the LB point. If yours is one of these you can increase the LB setting and thus give yourself more time before the battery dies.</p>
<p>Like I said it has been a while since I have been in the docs so there may be a better method but I am sure there is a solution of some type.</p>
<p>Doug</p>
<div class="gmail_quote">On Mar 25, 2013 2:34 AM, "David Vree" <<a href="mailto:david.h.vree@gmail.com">david.h.vree@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
Got one of these up and running with the tripplite_usb driver on
Ubuntu Server 12.04 x64. This particular model has product code
0x1000.<br>
<br>
Setup and installation was pretty standard. The only hiccup was I
had to create a udev rule to give the nut group access to USB
devices.<br>
<br>
If anyone has any questions let me know. Here's what I am got back
from the upsc command:<br>
<br>
<tt>battery.charge: 100</tt><br>
<tt>battery.test.status: Battery OK</tt><tt><br clear="none">
</tt><tt>battery.voltage: 14.75</tt><tt><br clear="none">
</tt><tt>battery.voltage.nominal: 36</tt><tt><br clear="none">
</tt><tt>device.mfr: Tripp Lite</tt><tt><br clear="none">
</tt><tt>device.model: UPS</tt><tt><br clear="none">
</tt><tt>device.type: ups</tt><tt><br clear="none">
</tt><tt><a href="http://driver.name" target="_blank">driver.name</a>: tripplite_usb</tt><tt><br clear="none">
</tt><tt>driver.parameter.pollinterval: 2</tt><tt><br clear="none">
</tt><tt>driver.parameter.port: /dev/usb/hiddev0</tt><tt><br clear="none">
</tt><tt>driver.version: 2.6.3</tt><tt><br clear="none">
</tt><tt>driver.version.internal: 0.20</tt><tt><br clear="none">
</tt><tt>input.voltage: 106.97</tt><tt><br clear="none">
</tt><tt>input.voltage.nominal: 120</tt><tt><br clear="none">
</tt><tt>output.voltage: 114.0</tt><tt><br clear="none">
</tt><tt>ups.debug.load_banks: 0</tt><tt><br clear="none">
</tt><tt>ups.debug.V: 31 30 36 30 58 58 0d '1060XX.'</tt><tt><br clear="none">
</tt><tt>ups.delay.shutdown: 64</tt><tt><br clear="none">
</tt><tt>ups.firmware: F1247.A</tt><tt><br clear="none">
</tt><tt>ups.firmware.aux: protocol 2001</tt><tt><br clear="none">
</tt><tt>ups.mfr: Tripp Lite</tt><tt><br clear="none">
</tt><tt>ups.model: UPS</tt><tt><br clear="none">
</tt><tt>ups.power.nominal: 750</tt><tt><br clear="none">
</tt><tt>ups.productid: 0001</tt><tt><br clear="none">
</tt><tt>ups.status: OL</tt><tt><br clear="none">
</tt><tt>ups.vendorid: 09ae</tt><br>
<br>
One question I have thought is this: What triggers the drive to
send the shutdown command?<br>
<br>
I am curious because this server draws about 600W and this model of
UPS should only last about 10min under that load and I need 3
minutes to shutdown 20 guest VMs.<br>
<br>
Thanks,<br>
Dave<br>
</div>
<br>_______________________________________________<br>
Nut-upsuser mailing list<br>
<a href="mailto:Nut-upsuser@lists.alioth.debian.org">Nut-upsuser@lists.alioth.debian.org</a><br>
<a href="http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser" target="_blank">http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser</a><br></blockquote></div>