On May 25, 2016, at 3:43 PM, Larry Fahnoe wrote:
> 
>    0.016075     Initiating UPS shutdown
>    0.016117     soft_shutdown(offdelay=64): N
>    0.016137     send_cmd(msg_len=4, type='N')

The delay command ('N') was sent successfully, so the UPS is receiving commands.

>    2.117586     send_cmd(msg_len=2, type='G')
>    3.219418     libusb_get_interrupt: Connection timed out
>    3.219474     libusb_get_interrupt() returned 0 instead of 8 while sending 
> 3a 47 b8 0d 00 00 00 00 '.G......'
>    4.219593     libusb_get_interrupt: Connection timed out
>    4.219661     libusb_get_interrupt() returned 0 instead of 8 while sending 
> 3a 47 b8 0d 00 00 00 00 '.G......'

Is the unit on line power at this point? I don't think we know the command 
needed to power off the UPS when it is not running on battery (the 'G' command 
seems to be "wait for power to return"). I suspect we could emulate it with the 
watchdog, but that will require a fair amount of testing to make sure we 
understand the timer.

https://github.com/networkupstools/nut/blob/master/drivers/tripplite_usb.c#L675

As a result, the last entry in the FAQ will apply: 
http://networkupstools.org/docs/FAQ.html

-- 
Charles Lepple
clepple@gmail




_______________________________________________
Nut-upsuser mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Reply via email to