search for: alert_handl

...*cmd, char *result, int resultsize) ?{ ????????int ret; -???????char ch, buf[256]; +???????unsigned char ch; +???????char buf[256]; ? ????????/* Check for the Inverter status alarm if pending : ???????? * "\r\n{Inverter: ? ? On}\r\n=>" @@ -190,10 +191,12 @@ ????????????????POLL_ALERT, alert_handler, 0, 20); ? ????????ser_send(upsfd, cmd); +???????sleep(UPSDELAY); ? ????????/* delete command echo up to \012 but no further */ ????????for (ch = '\0'; ch != '\012'; ser_get_char(upsfd, &ch, 0, 10)); ? +???????sleep(UPSDELAY); ????????/* get command response?*/ ????????ret = s...

This is 2nd version of the earlier patch featuring a few new features and fixes to the apcsmart driver, following the remarks in: http://www.mail-archive.com/nut-upsdev at lists.alioth.debian.org/msg02294.html Major changes from v1: - handle battery.charge and battery.runtime checks at main.c level - handle "immutable but writable" conflict gracefully at driver level -

This patch introduces a handful of new options, I mentioned earlier in: http://www.mail-archive.com/nut-upsdev at lists.alioth.debian.org/msg02088.html See the large commit message in the follow-up for the details and rationale. I realize it's a bit larger diff - so if it's required I can split it into few smaller ones. Michal Soltys (1): APC smart driver update and new features.

...of my head, but if you want to manually start the driver with a few -D flags and log the resulting output, we can see whether or not your UPS is sending the notifications the way that the driver is expecting them. apcsmart quick power cuts @ 20 & 30 usbhid-ups @ 30 & 40 The APC unit logs alert_handler: OB. usbhid-ups isn't so obvious, so I'm not sure. At least the apcsmart driver is reacting immediately, but upsmon reports nothing unless I cut power long enough. upsmond has noticed quick power cut, but I think that's because It happened at the same time as the normal check int...

On Dec 4, 2013, at 3:52 PM, Kris Jordan wrote: > Roger Price wrote, On 12/4/2013 12:35 PM: >> I would like nut to become more loquacious, and to log a much more complete report of its activity. At present nut reports that its components have started operation but does not automatically log their activity when UPS's switch between OB and OL. I believe that this under-reporting of

Inital tests with two apc units (2005 and pre-2000) seem to go well. See commit message for details. I'll add more detailed rationale after getting some sleep :) Michal Soltys (1): apcsmart: switch processing to ICANON + minor fixes drivers/apcsmart.c | 270 +++++++++++++++++++++++++++++++++++----------------- drivers/apcsmart.h | 127 ++++++++++++++++--------- 2 files changed, 267

Sorry for a bit longer delay than I anticipated, I was stuffed with the work. This is the next iteration of the patch adding some functionality to apcsmart driver, and relying on 'ignorelb' recently added. Follow up from previous thread: http://www.mail-archive.com/nut-upsdev at lists.alioth.debian.org/msg02331.html Main differences is that V3 is split into many small patches, so the