search for: upsdebug

...buflen-1) for a timeout and buflen for success. Unfortunately, the ser_get_line_alert() and ser_get_line() functions don't have a fixed number of bytes (this is determined by the endchar). So we can no longer check if an endchar was received. Bad idea. I'd prefer to add a couple of upsdebug statements in the serial.c library instead. This would leave the interface intact, at the cost of possibly redundant upsdebug statements (if the drivers already provide these). Before bailing out with -1 on error or timeout, the ser_get_*() functions would tell why (error with errno or ment...

...happy to rework the code to use what NUT provides. > > > > > > > Even in the updated driver, I see quite a couple of fprintf() lines. > > > > Although these are in most (all?) cases encased in a 'if > > > > (nut_debug_level > 0)', we have the upsdebug* functions for that. Do > > > > yourself (and your fellow developers) a favor and use those instead. > > > > > > > Another thing related to this is the XTRACE macro. This will only use a > > > > single (1) debug level to show output. Please use a layered...

Hi, I started updating smart driver with a few things I've been missing. While going through the source: - in upsdrv_shutdown(), there're loads of printfs - they kinda look like a leftover from older debug times. Shouldn't they be changed into upsdebugx() or upslogx() ?

...probably because of 114107.780620 Path: UPS.PowerSummary.PresentStatus.BelowRemainingCapacityLimit, Type: Input, ReportID: 0x0a, Offset: 4, Size: 1, Value: 1 (on line nr. 1044544 in log) message. Full zipped log (5,8 MB) with -DDD driver debug level available at http://wikisend.com/download/396966/upsdebug.zip As before, no power failure was present at the time this happened. The UPS at the time I bought it (in June) was capable of supplying backup power for PC for more than 15 minutes. Martins Pukitis. -----Original Message----- From: Charles Lepple [mailto:clepple at gmail.com] Sent: Tuesday, J...

On Jan 27, 2008 11:07 AM, Arjen de Korte <nut+devel at de-korte.org> wrote: > > >> I also think we should not encourage people to post debug output before > >> consultation with a developer. Most of the time, providing useful debug > >> output requires more than just running the driver with an arbitrary > >> number of -D flags anyway. > > Well,

[I am CC'ing Alexey from Powercom in case he has seen any of these issues with the Raspberry Pi hardware.] On Jun 10, 2013, at 1:05 PM, M?rti?? Pu??tis wrote: > I took the log. Here's what happened. > Broadcast Message from nut at rasp > (somewhere) at 16:18 ... > UPS BNT500AP at localhost battery needs to be replaced > > occurred when for the first time value

I took the log. Here's what happened. Broadcast Message from nut at rasp (somewhere) at 16:18 ... UPS BNT500AP at localhost battery needs to be replaced occurred when for the first time value "1" was read as "UPS.PowerSummary.PresentStatus.NeedReplacement", on this line: 6409.240690 Path: UPS.PowerSummary.PresentStatus.NeedReplacement, Type: Input, ReportID: 0x0a,

...some problems to understand what is going on and what is wrong: it is quite hard to increase logging level and it is uncomfortable to work with Windows Event Log. I think that logging architecture should be improved. Linux version contains several logging function like upslogx, upslog_with_errno, upsdebugx, etc. All of them call vupslog function inside. This function can write messages into STDERR stream and send them into syslog (writing to a log file is not required because Linux has syslogd, logrotation, etc.). Windows port contains the same function. It can write messages into STDERR stream too...