search for: assirati

Hello, The UPS I am developing a driver to is able to report several flags for critical hardware conditions, like overheat, overload, inverter failure, output short etc. What should be the correct policy of operation when such a condition occurs? I think that the an UPS in such a condition is not reliable and therefore a system shutdown should be called. However, the developer's manual and

On Tue, 29 Sep 2020, João Luis Meloni Assirati wrote: > The UPS I am developing a driver to is able to report several flags for > critical hardware conditions, like overheat, overload, inverter failure, > output short etc. What should be the correct policy of operation when such a > condition occurs? I think that the an UPS in s...

Hello, I am developing a new NUT driver for brazilian UPS brand "Ragtech" by reverse engeneering. I have never been involved in NUT driver development, so I wish to ask some basic questions. Any help will be much appreciated! 1. Is there a mandatory C code style? I mean, any strong recommendation? If there are none, I prefer to keep mine. 2. What are the purposes of "instant

The UPS I am writing a driver to has the ability to inform that a variation in the battery's capacity has changed, and therefore a test.battery.start.deep or calibration.start has to be performed. Is there a way -- appart from syslog -- for the driver to inform the user/administrator that this maintenance action has to be performed? I would appreciate very much that my previous question if

Hello Daniel! On Tue, Sep 29, 2020 at 6:23 PM Daniel F. Dickinson <cshore at thecshore.com> wrote: > > Hello joão, > > To get more responses you should plaintext email (standard for open source development mailing lists) instead of HTML mail. I just can't believe that I was sending HTML e-mail. Thank you very very much for bringing this to my attention. I hope it is ok now.