[Nut-upsuser] Powercom INF-800 support

[Larry Fahnoe]

On Sat, May 28, 2016 at 11:05 AM, abi <abi at abinet.ru> wrote:

> However I was unable to shutdown.return it. Maybe protocol is not fully
> compatible?
>
>    0.145757    Initiating UPS shutdown
>    0.145760    upsdrv_shutdown...
>    0.145763    instcmd(shutdown.return, [NULL])
>    0.145767    powercom_shutdown_nuf: value = (null), command = 5400
>    0.145770    hu_find_valinfo: found 21504 (value: (null))
>    0.145773    Unit = 00000000, UnitExp = 0
>    0.145775    Exponent = 0
>    0.145778    PhyMax = 0, PhyMin = 0, LogMax = 65535, LogMin = 0
>    0.155952    Report[set]: (3 bytes) => 0f 00 54
>    0.155981    Set report succeeded
>    0.155986    instcmd: SUCCEED
>

When you attempted the shutdown.return, was the UPS powered or on battery?
My older Tripplite SMART2200VS won't shutdown.return unless it is running
off of batteries.  When I did try shutdown.return with the UPS powered, the
tripplite_usb driver showed a similar pattern of "libusb_get_interrupt:
Connection timed out" messages.


> Every 2 sec driver outputs the following:
>   10.254942    upsdrv_updateinfo...
>   10.507035    libusb_get_interrupt: Connection timed out
>   10.507054    Got 0 HID objects...
>   10.507060    Quick update...
>   10.507657    refresh_report_buffer: expected 3 bytes, but got 2 instead
>   10.507671    Path: UPS.PowerSummary.DelayBeforeShutdown, Type: Feature,
> ReportID: 0x0f, Offset: 0, Size: 16, Value: 0


--Larry

-- 
Larry Fahnoe, Fahnoe Technology Consulting, fahnoe at FahnoeTech.com
           Minneapolis, Minnesota       www.FahnoeTech.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20160528/7982a943/attachment-0001.html>