[Nut-upsdev] bestfortress driver establishes/loses/establishes communication and so on...

Oliver Kluge ok23 at kluge-digital.de
Wed Feb 1 23:15:17 UTC 2012


Hi,

Charles Lepple wrote:
> On Jan 31, 2012, at 8:16 PM, Oliver Kluge wrote:
>
>> When I put pollintervall=10 into the section [fortress] in ups.conf, I get the error that pollintervall is no recognized parameter
>
> Typo? Should be "pollinterval" (one "l" in "interval"), in your [fortress] section.

Thanks,

that does the trick. In German interval is spelled with two 'l'.

But correcting the typo does not correct the communication protocol. Now 
the driver runs with an interval of 10 and says so in the debug output.

But still there is a 2 seconds delay between each of the six 
communication events, and still the sixth always fails, setting data 
stale...

Thanks
Oliver






More information about the Nut-upsdev mailing list