Re: [Nut-upsuser] Tripp-Lite OMNI750ISO

2013-03-25 Thread Douglas Parsons
Dave, My NUT skills are rusty so I may need correcting, list feel free to enlighten me. 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

Re: [Nut-upsuser] Tripp-Lite OMNI750ISO

2013-03-25 Thread David Vree
On 03/25/2013 03:08 AM, Douglas Parsons wrote: Dave, My NUT skills are rusty so I may need correcting, list feel free to enlighten me. 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

Re: [Nut-upsuser] Tripp-Lite OMNI750ISO

2013-03-25 Thread Charles Lepple
On Mar 25, 2013, at 2:34 AM, David Vree wrote: 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. I haven't run across a product code on these units before (just the USB VID, PID, and a Tripp-Lite

Re: [Nut-upsuser] Tripp-Lite OMNI750ISO

2013-03-25 Thread Charles Lepple
On Mar 25, 2013, at 9:20 AM, David Vree wrote: [ups.delay.shutdown] Interval to wait after shutdown with delay command (seconds) Type: STRING Value: 64 There is nothing apparently settable about its LB point via the driver. BTW -- What do you think ups.delay.shutdown means?

Re: [Nut-upsuser] Tripp-Lite OMNI750ISO

2013-03-25 Thread David Vree
On 03/25/2013 09:26 AM, Charles Lepple wrote: On Mar 25, 2013, at 2:34 AM, David Vree wrote: 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. Did you install via the official .debs, or source? The

Re: [Nut-upsuser] Tripp-Lite OMNI750ISO

2013-03-25 Thread David Vree
On 03/25/2013 09:36 AM, Charles Lepple wrote: On Mar 25, 2013, at 9:20 AM, David Vree wrote: [ups.delay.shutdown] Interval to wait after shutdown with delay command (seconds) Type: STRING Value: 64 There is nothing apparently settable about its LB point via the driver. BTW -- What do you