Nut upsuser - Feb 2014 - riello_usb: pollinterval ignored

Hello,
Some more data about my experiences with riello_ups on iDialog 800

In orderr to avoid "stale data" problems, i tried to increase 
pollinterval in ups.conf:

==== ups.conf ====pollinterval = 4
maxretry = 3

[idg800]
	driver = riello_usb
	port = auto
	desc = "idg800"
==================
It seems that pollinterval is ignored by the driver:

# upsc idg800 | grep poll
Init SSL without certificate database
driver.parameter.pollinterval: 2


Moreover, i noted some message form the driver, when run in debug mode:

  9.142152	read: FFFFFFF1 31 00 00 00 00 00 00
    9.150151	read: FFFFFFF1 03 00 00 00 00 00 00
    9.150168	in read: 48
    9.150179	Get status Ok: read byte: 48
    9.565285	send ok
    9.566165	read: FFFFFFF0 00 00 00 00 00 00 00
    9.574116	read: FFFFFFF7 02 22 20 15 32 30 30
    9.582127	read: FFFFFFF5 30 30 3E 39 03 00 00
    9.582153	in read: 12
    9.582163	Get extended Ko: command not supported
   10.490354	Communication with UPS is lost: status read failed!
   10.901292	send ok
   10.902128	read: FFFFFFF0 00 00 00 00 00 00 00
   10.910099	read: FFFFFFF7 02 22 20 52 53 32 34
   10.918083	read: FFFFFFF7 38 30 30 31 30 31 3F
   10.926089	read: FFFFFFF7 35 30 3E 38 31 3F 35

Is "Communication with UPS is lost: status read failed!" something to
be
worried about?

thanks,
rob

On Feb 28, 2014, at 3:49 AM, Roberto Resoli wrote:
> Hello,
> Some more data about my experiences with riello_ups on iDialog 800
> 
> In orderr to avoid "stale data" problems, i tried to increase
pollinterval in ups.conf:
> 
> ==== ups.conf ====> pollinterval = 4
> maxretry = 3
> 
> [idg800]
> 	driver = riello_usb
> 	port = auto
> 	desc = "idg800"
> ==================> 
> It seems that pollinterval is ignored by the driver:
> 
> # upsc idg800 | grep poll
> Init SSL without certificate database
> driver.parameter.pollinterval: 2
It does seem to be hardcoded. I CC'd the author.

Elio, do you know why this is set to 2 seconds?
> Moreover, i noted some message form the driver, when run in debug mode:
> 
> 9.142152	read: FFFFFFF1 31 00 00 00 00 00 00
>   9.150151	read: FFFFFFF1 03 00 00 00 00 00 00
>   9.150168	in read: 48
>   9.150179	Get status Ok: read byte: 48
>   9.565285	send ok
>   9.566165	read: FFFFFFF0 00 00 00 00 00 00 00
>   9.574116	read: FFFFFFF7 02 22 20 15 32 30 30
>   9.582127	read: FFFFFFF5 30 30 3E 39 03 00 00
>   9.582153	in read: 12
>   9.582163	Get extended Ko: command not supported
>  10.490354	Communication with UPS is lost: status read failed!
>  10.901292	send ok
>  10.902128	read: FFFFFFF0 00 00 00 00 00 00 00
>  10.910099	read: FFFFFFF7 02 22 20 52 53 32 34
>  10.918083	read: FFFFFFF7 38 30 30 31 30 31 3F
>  10.926089	read: FFFFFFF7 35 30 3E 38 31 3F 35
> 
> Is "Communication with UPS is lost: status read failed!"
something to be worried about?

Ideally the UPS wouldn't do that, but if it reconnects...

-- 
Charles Lepple
clepple at gmail