search for: apas01

...help if there was some master list > of all the paths (input.voltage, battery.temperature, etc) NUT supports, > instead of having to dig through different driver files to see what's available. Is there some list? How about http://www.networkupstools.org/docs/developer-guide.chunked/apas01.html /Niels -- Niels Baggesen - @home - ?rhus - Denmark - nba at users.sourceforge.net The purpose of computing is insight, not numbers --- R W Hamming

Thanks to the great help here, I now have a UPS spitting out something resembling a report descriptor. So since I seem destined to have to create a new USB HID subdriver, I figured I'd get started on the path. I followed all of the directions on the web....I used the script to generate the usbhid subdriver, feeding it the output of the usbhid-ups driver from reading my UPS. All that worked

Not to pick on anyone in particular, but for the sake of organization, I think we might need to address the need for variables beyond the standard ones defined here: http://networkupstools.org/docs/developer-guide.chunked/apas01.html From http://networkupstools.org/docs/developer-guide.chunked/ar01s04.html#_variable_names : "PLEASE don?t make up new variables and commands just because you can. The new dstate functions give us the power to create just about anything, but that is a privilege and not a right. Imagine t...

...n; may vary dynamically with load. V dc 48 % LOAD PHASE A Output Load on Phase A, in per cent. Normally the greater of VA and Watts. For a single phase UPS, the % Load for the whole UPS is reported in this Phase A meter. % Looking at : http://www.networkupstools.org/docs/developer-guide.chunked/apas01.html I draw the conclusions that the BATTERY DCUV BAR CHART bcmxcp meter should be mapped to NUT variable battery.voltage.low Do you agree that this is correct ? I draw the conclusions that the LOAD PHASE A bcmxcp meter should be mapped to NUT variable ups.load Do you agree that this is correct...

...m out again before checking the driver in to version control. Please find attached the patches i have applied to the current master. >> >> Is there a list of all official NUT names (i haven't searched yet) ? >> > http://www.networkupstools.org/docs/developer-guide.chunked/apas01.html > Thank you. Paul. -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-drivers-fix-possible-memory-leak.patch Type: text/x-patch Size: 637 bytes Desc: not available URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20141010/9...

hem, in the hurry of sending, I've forgotten a link... 2014-02-18 22:45 GMT+01:00 Arnaud Quette <aquette.dev at gmail.com>: > > > 2014-02-16 8:31 GMT+01:00 <alf at i100.no>: > (...) > > That made me realize that it's still not referenced on the NUT Related > Projects page. > (yup Charles, yet another unshared thing...) > This last point is now

...% LOAD PHASE A > Output Load on Phase A, in per cent. Normally the greater of VA and > Watts. For a single phase UPS, the % Load for the whole UPS is > reported in this Phase A meter. % > Check:-) > > Looking at : > http://www.networkupstools.org/docs/developer-guide.chunked/apas01.html > I draw the conclusions that the BATTERY DCUV BAR CHART bcmxcp meter > should be mapped to NUT variable battery.voltage.low > Do you agree that this is correct ? > Yes this is correct. One more point to scratch from the todo list :-) > I draw the conclusions that the LOAD PHAS...

Hi On 10/03/2014 03:42 PM, Charles Lepple wrote:> On Oct 3, 2014, at 7:50 AM, paul.chavent at fnac.net wrote: > > > This is what I was referring to (from the belkin-hid log): > >???? 1.325782??? Report[buf]: (5 bytes) => 05 53 00 48 00 >???? 1.325799??? Path: UPS.PowerSummary.ConfigVoltage, Type: Feature, ReportID: 0x05, Offset: 16, Size: 16, Value: 0 >????