[Nut-upsuser] Powercom INF-800 support

[abi]

On 28.05.2016 19:46, Larry Fahnoe wrote:
> On Sat, May 28, 2016 at 11:05 AM, abi <abi at abinet.ru 
> <mailto: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.

UPS was powered. Actually, inverter of this particular UPS is broken 
(but undetected by it's logic), so I was unable to test it fully. I need 
UPS free of so called power race condition, however,

10.507657    refresh_report_buffer: expected 3 bytes, but got 2 instead
and
ups.timer.start: 740160

looks suspicious. As you suggest to test it on batt, I'm unsure what to 
do now - get it replaced or exchange to IMPERIAL series.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20160528/6246499c/attachment.html>