<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
<head>
<meta name="Generator" content="Zarafa WebAccess v7.0.9-36358">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>RE Powercom variables</title>
<style type="text/css">
body
{
font-family: Arial, Verdana, Sans-Serif ! important;
font-size: 12px;
padding: 5px 5px 5px 5px;
margin: 0px;
border-style: none;
background-color: #ffffff;
}
p, ul, li
{
margin-top: 0px;
margin-bottom: 0px;
}
</style>
</head>
<body>
<p>Hi</p><p>We have a PCM vanguard UPS communicating on SmeServer ver 8 (Centos5.8) using the following rpms.</p><p> </p><p>nut-client-2.6.5-1geekery</p><p>nut-2.6.5-1geekery</p><p>powerman-2.3.5-2geekery</p><p> </p><p>I believe are standard 2.6.5 rpms adjusted to Centos 5 OS.</p><p> </p><p>These rpms work as shown by the upsc output</p><p>battery.charge: 100<br />battery.charge.low: 10<br />battery.charge.warning: 30<br />battery.date: 2010/12/20<br />battery.runtime: 800<br />battery.type: PbAc<br />device.mfr: POWERCOM Co.,LTD<br />device.model: HID UPS Battery<br />device.serial: 004-0D9F-000<br />device.type: ups<br />driver.name: usbhid-ups<br />driver.parameter.pollfreq: 30<br />driver.parameter.pollinterval: 2<br />driver.parameter.port: /var/lib/ups/hiddev0<br />driver.version: 2.6.5<br />driver.version.data: PowerCOM HID 0.3<br />driver.version.internal: 0.37<br />input.frequency: 49.0<br />input.voltage: 235.0<br />input.voltage.nominal: 240<br />output.frequency: 49.0<br />output.voltage: 239.0<br />output.voltage.nominal: 240<br />ups.date: 2010/12/20<br />ups.delay.shutdown: 20<br />ups.delay.start: 60<br />ups.load: 29<br />ups.mfr: POWERCOM Co.,LTD<br />ups.model: HID UPS Battery<br />ups.productid: 0004<br />ups.serial: 004-0D9F-000<br />ups.status: OL<br />ups.test.result: Done and passed<br />ups.timer.shutdown: 0<br />ups.timer.start: 740160<br />ups.vendorid: 0d9f<br /> </p><p>But we are missing some variable like battery.voltage</p><p>upsrw only returns</p><p> </p><p>[ups.delay.shutdown]<br />Interval to wait after shutdown with delay command (seconds)<br />Type: STRING<br />Value: 20<br /><br />[ups.delay.start]<br />Interval to wait before (re)starting the load (seconds)<br />Type: STRING<br />Value: 60</p><p> </p><p>Attached is the output of usbhid-ups -DDD -a UPS > PowerCOM.log 2>&1</p><p> </p><p>It shows which would indicate the data required</p><p>0.491042 Path: UPS.Battery.Temperature, Type: Feature, ReportID: 0x2d, Offset: 0, Size: 8, Value: 36</p><p>0.484061 Path: UPS.Battery.Voltage, Type: Feature, ReportID: 0x1a, Offset: 0, Size: 16, Value: 5890</p><p> </p><p>The quick update section sends back </p><p>refresh_report_buffer: expected 3 bytes, but got 2 instead</p><p>Can we adjust the buffer length? Would it cure the shortage of essential data?</p><p> </p><p>Are these issues a matter more for Powercom to sort out or can we use alternative variable name to get the information back?</p><p> </p><p>TIA and season greetings.<br /> </p><p>Regards </p><p> </p><p> Gordon</p><p> </p><p> </p>
</body>
</html>