<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; " class=""><h1 class=""></h1>Apologies for resurrecting an old thread and likely poor formatting - I wasn't subscribed to the list at the time and have copied it out of the archives (<a href="http://lists.alioth.debian.org/pipermail/nut-upsuser/2010-July/006104.html">http://lists.alioth.debian.org/pipermail/nut-upsuser/2010-July/006104.html</a>).<div><br></div><div>I've been unable to locate any further progress on this UPS (Liebert 10af:0001) - a thread from 2009 (<a href="http://lists.alioth.debian.org/pipermail/nut-upsdev/2009-November/004252.html">http://lists.alioth.debian.org/pipermail/nut-upsdev/2009-November/004252.html</a>) seemed to work for a Liebert PSA 650 model from then, but this 2010 thread seems to have unearthed an incompatible model - I've just purchased two Liebert PSA 1500 which exhibit exactly the same issues as below. I've put some output inline.</div><div><br></div><div>I've checked out trunk and there seems to be no progress there. I'm happy to help debugging the driver, is there still some way we can progress this?</div><div><br></div><div>All I get from upsc is:</div><div><br></div><div><div>battery.charge.low: 38</div><div>battery.charge.warning: 38</div><div>battery.type: PbAc</div><div>device.mfr: Emerson Network Power</div><div>device.model: LiebertPSA</div><div>device.serial: </div><div>device.type: ups</div><div>driver.name: usbhid-ups</div><div>driver.parameter.pollfreq: 30</div><div>driver.parameter.pollinterval: 2</div><div>driver.parameter.port: auto</div><div>driver.version: 2.6.2-3254</div><div>driver.version.data: Belkin HID 0.12</div><div>driver.version.internal: 0.35</div><div>ups.mfr: Emerson Network Power</div><div>ups.model: LiebertPSA</div><div>ups.productid: 0001</div><div>ups.serial: </div><div>ups.status: OB</div><div>ups.vendorid: 10af</div></div><div><br></div><div><br></div><div>Many thanks, Tim.</div><div><br><blockquote type="cite"><i class="">Tue Jul 13 19:54:03 UTC 2010</i><div class=""></div>
<pre class="">Citeren Michelle Wright <<a href="http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser" class="">michelle.wright op gmail.com</a>>:
><i class=""> $ sudo /lib/nut/usbhid-ups -DDD -a maxfun
</i>><i class=""> Network UPS Tools - Generic HID driver 0.34 (2.4.3)
</i>><i class=""> USB communication driver 0.31
</i>
[...]
><i class=""> 0.341940 Report[get]: (3 bytes) => 1d 8b 00
</i>><i class=""> 0.341960 Path: UPS.PowerSummary.Voltage, Type: Feature, ReportID:
</i>><i class=""> 0x1d, Offset: 0, Size: 16, Value: 0.000001
</i>
The UPS is reporting a battery voltage of 1 uV here, most likely
because Liebert got the exponent of this value wrong. I assume they
meant something like 13.9 V, since 00 8B (hex) equals 139 (decimal).
We can fix this though, but this will require a dedicated sub driver.
</pre></blockquote>I get:</div><div><div>0.413899<span class="Apple-tab-span" style="white-space:pre"> </span>Report[get]: (3 bytes) => 1d 08 01</div><div>0.413920<span class="Apple-tab-span" style="white-space:pre"> </span>Path: UPS.PowerSummary.Voltage, Type: Feature, ReportID: 0x1d, Offset: 0, Size: 16, Value: 0.000003</div><div><br></div><blockquote type="cite"><pre class="">
><i class=""> 0.345939 Report[get]: (3 bytes) => 1f 0c 00
</i>><i class=""> 0.345956 Path: UPS.PowerSummary.ConfigVoltage, Type: Feature,
</i>><i class=""> ReportID: 0x1f, Offset: 0, Size: 16, Value: 0.000000
</i>
Same here. The nominal battery voltage is probably 12 V, but what is
reported is 0.12 uV, since 00 0C (hex) equals 12 (decimal). Can be
fixed too.<font class="Apple-style-span" color="#000000" face="Helvetica"><span class="Apple-style-span" style="white-space: normal;">
</span></font></pre></blockquote><div>0.417897<span class="Apple-tab-span" style="white-space:pre"> </span>Report[get]: (3 bytes) => 1f 18 00</div><div>0.417916<span class="Apple-tab-span" style="white-space:pre"> </span>Path: UPS.PowerSummary.ConfigVoltage, Type: Feature, ReportID: 0x1f, Offset: 0, Size: 16, Value: 0.000000</div><div><br></div><blockquote type="cite"><pre class="">
><i class=""> 0.350081 Report[buf]: (2 bytes) => 07 0d
</i>><i class=""> 0.350095 Path: UPS.PowerSummary.PresentStatus.ACPresent, Type:
</i>><i class=""> Feature, ReportID: 0x07, Offset: 2, Size: 1, Value: 0.000000
</i>><i class=""> 0.350106 Report[buf]: (2 bytes) => 07 0d
</i>><i class=""> 0.350120 Path: UPS.PowerSummary.PresentStatus.ACPresent, Type:
</i>><i class=""> Input, ReportID: 0x07, Offset: 2, Size: 1, Value: 0.000000
</i>
Although I didn't expect otherwise, the UPS is reporting that AC is
not present (that's why you see NUT reporting OB instead of OL). Try
if these value change to '1.000000' if you unplug the mains. </pre></blockquote><div>I tried this - unfortunately no they do not. I get this with power disconnected:</div><div><div> 0.422018<span class="Apple-tab-span" style="white-space:pre"> </span>Report[buf]: (2 bytes) => 07 0d</div><div> 0.422034<span class="Apple-tab-span" style="white-space:pre"> </span>Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Feature, ReportID: 0x07, Offset: 2, Size: 1, Value: 0.000000</div><div> 0.422046<span class="Apple-tab-span" style="white-space:pre"> </span>Report[buf]: (2 bytes) => 07 0d</div><div> 0.422061<span class="Apple-tab-span" style="white-space:pre"> </span>Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Input, ReportID: 0x07, Offset: 2, Size: 1, Value: 0.000000</div><div><br></div></div><div>With the upsd and upsmon running, I get a console message that I'm on battery which stays that way regardless of whether the AC is connected or not.</div><blockquote type="cite"><pre class="">In that
case Liebert seems to report the status reversed from what is
specified in the HID PDC specifications (which doesn't surprise me at
all, given the broken battery voltage reporting).
><i class=""> 0.350131 Report[buf]: (2 bytes) => 07 0d
</i>><i class=""> 0.350145 Path: UPS.PowerSummary.PresentStatus.BatteryPresent, Type:
</i>><i class=""> Feature, ReportID: 0x07, Offset: 3, Size: 1, Value: 0.000000
</i>><i class=""> 0.350156 Report[buf]: (2 bytes) => 07 0d
</i>><i class=""> 0.350170 Path: UPS.PowerSummary.PresentStatus.BatteryPresent, Type:
</i>><i class=""> Input, ReportID: 0x07, Offset: 3, Size: 1, Value: 0.000000
</i>
I assume the UPS contains a battery and that this value is reversed as well.<font class="Apple-style-span" color="#000000" face="Helvetica"><span class="Apple-style-span" style="white-space: normal;">
</span></font></pre></blockquote><div> 0.422073<span class="Apple-tab-span" style="white-space:pre"> </span>Report[buf]: (2 bytes) => 07 0d</div><div> 0.422088<span class="Apple-tab-span" style="white-space:pre"> </span>Path: UPS.PowerSummary.PresentStatus.BatteryPresent, Type: Feature, ReportID: 0x07, Offset: 3, Size: 1, Value: 0.000000</div><div> 0.422101<span class="Apple-tab-span" style="white-space:pre"> </span>Report[buf]: (2 bytes) => 07 0d</div><div> 0.422116<span class="Apple-tab-span" style="white-space:pre"> </span>Path: UPS.PowerSummary.PresentStatus.BatteryPresent, Type: Input, ReportID: 0x07, Offset: 3, Size: 1, Value: 0.000000</div><div><br></div><div>My UPS contains a battery, yes :)</div><blockquote type="cite"><pre class="">
><i class=""> 0.353937 Report[get]: (3 bytes) => 2b 63 09
</i>><i class=""> 0.353954 Path: UPS.Output.Voltage, Type: Feature, ReportID: 0x2b,
</i>><i class=""> Offset: 0, Size: 16, Value: 0.000024
</i>
Most likely the same problem as for the battery voltage. It looks more
like the output voltage should be 240.3 V, instead of 24.03 uV.
</pre></blockquote><div><br></div><div> 0.425897<span class="Apple-tab-span" style="white-space:pre"> </span>Report[get]: (3 bytes) => 2b 60 09</div><div> 0.425916<span class="Apple-tab-span" style="white-space:pre"> </span>Path: UPS.Output.Voltage, Type: Feature, ReportID: 0x2b, Offset: 0, Size: 16, Value: 0.000024</div><div><br></div><blockquote type="cite"><pre class="">
><i class=""> 0.361937 Report[get]: (3 bytes) => 20 68 09
</i>><i class=""> 0.361954 Path: UPS.Input.Voltage, Type: Feature, ReportID: 0x20,
</i>><i class=""> Offset: 0, Size: 16, Value: 0.000024
</i>
Same here. Input voltage is probably 240.8 V instead of 24.08 uV.<font class="Apple-style-span" color="#000000" face="Helvetica"><span class="Apple-style-span" style="white-space: normal;">
</span></font></pre></blockquote><div> 0.433903<span class="Apple-tab-span" style="white-space:pre"> </span>Report[get]: (3 bytes) => 20 68 09</div><div> 0.433925<span class="Apple-tab-span" style="white-space:pre"> </span>Path: UPS.Input.Voltage, Type: Feature, ReportID: 0x20, Offset: 0, Size: 16, Value: 0.000024</div><div><br></div><blockquote type="cite"><pre class="">
><i class=""> 0.365937 Report[get]: (3 bytes) => 38 f5 01
</i>><i class=""> 0.365955 Path: UPS.Input.Frequency, Type: Feature, ReportID: 0x38,
</i>><i class=""> Offset: 0, Size: 16, Value: 501.000000
</i>
Something similar here too. The input frequency is probably 50.1 Hz,
instead of 501 Hz.<font class="Apple-style-span" color="#000000" face="Helvetica"><span class="Apple-style-span" style="white-space: normal;">
</span></font></pre></blockquote><div> 0.437896<span class="Apple-tab-span" style="white-space:pre"> </span>Report[get]: (3 bytes) => 38 f3 01</div><div> 0.437916<span class="Apple-tab-span" style="white-space:pre"> </span>Path: UPS.Input.Frequency, Type: Feature, ReportID: 0x38, Offset: 0, Size: 16, Value: 499.000000</div><div><br></div><blockquote type="cite"><pre class="">
><i class=""> 0.630102 upsdrv_updateinfo...
</i>><i class=""> 0.881839 libusb_get_interrupt: Connection timed out
</i>><i class=""> 0.881854 Got 0 HID objects...
</i>><i class=""> 0.881863 Quick update...
</i>
NUT attempts to read from the interrupt pipeline here, but at this
time there are no messages queued. This is normal, nothing to worry
about.
The good news is that we can probably support this UPS (sort of),
provided you're willing to help us finding and fixing all it's quirks.
It will require checking out the development version from SVN and
frequent compiling from sources. You'd also need to be able to take
the UPS out of service from time to time for testing a new version of
the driver. Let us know if you are interested in helping getting this
device supported.
</pre></blockquote><div>No problem, happy to do this.</div><blockquote type="cite"></blockquote><br><blockquote type="cite"><pre class="">
Best regards, Arjen
--
Please keep list traffic on the list
</pre></blockquote></div></body></html>