Nut upsuser - Dec 2014 - interrupt pipe disabled [APC SMT3000RMI2U]

Hello,

I'm testing an APC SMT3000RMI2U connected to an USB port with Nut 2.7.2.
I've
got the message :

"interrupt pipe disabled (add 'pollonly' flag to 'ups.conf'
to get rid of this message)"

I've been looking for "pollonly" in the usbhid-ups man page, but
it didn't help
me.

Could someone explain me what does this means exactly ? What are these
interrupts ? What exactly may not work ?

Regards.

-- 
Frantz de Germain
D?partement Informatique UFR Sciences / DDN
Universit? d'Angers

Le Tue, 16 Dec 2014 15:36:29 +0100
Frantz de Germain <frantz at info.univ-angers.fr> ?crivait:
> Hello,
> 
> I'm testing an APC SMT3000RMI2U connected to an USB port with Nut
2.7.2. I've
> got the message :
> 
> "interrupt pipe disabled (add 'pollonly' flag to
'ups.conf' to get rid of this message)"
> 
> I've been looking for "pollonly" in the usbhid-ups man page,
but it didn't help
> me.
> 
> Could someone explain me what does this means exactly ? What are these
> interrupts ? What exactly may not work ?
> 
Bye the way I just realize that I can't retrieve the ups.load, among other
thing :-(

-- 
Frantz de Germain
D?partement Informatique UFR Sciences / DDN
Universit? d'Angers

tisdagen den 16 december 2014 15.36.29 skrev  Frantz de
Germain:
> Hello,
Hi Frantz,
> 
> I'm testing an APC SMT3000RMI2U connected to an USB port with Nut
2.7.2.
> I've got the message :
> 
> "interrupt pipe disabled (add 'pollonly' flag to
'ups.conf' to get rid of
> this message)"
> 
> I've been looking for "pollonly" in the usbhid-ups man page,
but it didn't
> help me.
> 
Only add pollonly to your ups.conf

ex:
[APC]
        driver = usbhid-ups
        port = auto
	pollonly
        vendorid = xxxx
> Could someone explain me what does this means exactly ? What are these
> interrupts ? What exactly may not work ?
> 
It depends on the implementation of the usb driver used. And it would not 
listen to the interrupt pipe. So actualy nothing works like it should.

/Kjell

On Dec 16, 2014, at 9:45 AM, Frantz de Germain <frantz at
info.univ-angers.fr> wrote:
> Bye the way I just realize that I can't retrieve the ups.load, among
other
> thing :-(
To the best of my knowledge, Microlink is not supported by any third-party tools
(including NUT), but some variables are exposed via standard USB HID.
Apparently, ups.load is not one of them.

Your UPS might support MODBUS:

   http://lists.alioth.debian.org/pipermail/nut-upsdev/2014-July/006769.html

but we need developers to help add MODBUS support to NUT.

Alternatively, you can use apcupsd:

  
http://apcupsd.cvs.sourceforge.net/viewvc/apcupsd/apcupsd/ReleaseNotes?pathrev=Release-3_14_11

and if you need connectivity with an existing NUT setup:

   http://www.networkupstools.org/docs/man/apcupsd-ups.html

-- 
Charles Lepple
clepple at gmail

On Dec 16, 2014, at 11:27 AM, Kjell Claesson <kjell.claesson at
epost.tidanet.se> wrote:
>> I've been looking for "pollonly" in the usbhid-ups man
page, but it didn't
>> help me.
>> 
> 
> Only add pollonly to your ups.conf
> 
> ex:
> [APC]
>        driver = usbhid-ups
>        port = auto
> 	pollonly
>        vendorid = xxxx
Kjell is correct that this should get basic monitoring working with usbhid-ups.
If that does not work, please send the exact log message that you receive, and
we will try to debug it.
> 
>> Could someone explain me what does this means exactly ? What are these
>> interrupts ? What exactly may not work ?
>> 
> It depends on the implementation of the usb driver used. And it would not 
> listen to the interrupt pipe. So actualy nothing works like it should.
Well, this is not entirely true - the usbhid-ups driver will still poll the UPS.
More information:

  
http://news.gmane.org/find-root.php?message_id=E4AF6D2D%2d44B0%2d4371%2d988B%2d72A1A3CE49EC%40gmail.com

-- 
Charles Lepple
clepple at gmail