Arnaud Quette wrote, On 9/11/2012 1:39 AM:
2012/9/11 Kris Jordan <[email protected] <mailto:[email protected]>> Seems to be working as far as reporting data w/o staleness. driver.version: 2.6.5-3691:3709M device.model: Back-UPS ES 725 ups.firmware: 802.n2.D ups.firmware.aux: n2 ups.productid: 0002 ups.vendorid: 051d is battery.charge reported on both units now? I'd also be interested in seeing a driver debug trace (-DDDDD, during a minute or so) and a complete upsc output, in compressed form please, to counter validate on my side.
Both units? battery.charge was always reported on this ES725 (NUT 2.6.4-2.6.5 and the new driver).
Do you normally want upsd, upsmon, and upsc ran during the 1min debug trace? Otherwise, here's the logs from the driver ran by itself for 1min.
The only difference in the upsc output is the driver version. ---I'd like to thank you guys for the Windows pid and fsd fixes, 2.6.5 has been working great. Thank you!
Logs.7z
Description: Binary data
_______________________________________________ Nut-upsuser mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
