[Nut-upsuser] Re Powercom Vanguard driver for nut

[Gordon Longland]

Compiled 2.6.4 with what I believe to be the right options and can now load the driver usbhid-ups for the powercom 0d9f:0004.

But just get a rolling screen of

 
 156.702195     Quick update...
 158.690980     upsdrv_updateinfo...
 158.750008     Got 1 HID objects...
 158.750030     Path: UPS.PowerSummary.RemainingCapacity, Type: Input, ReportID: 0x0e, Offset: 0, Size: 8, Value: 100
 158.750038     Full update...
 160.691067     upsdrv_updateinfo...
 160.734022     file_report_buffer: expected 0 bytes, but got 2 instead
 160.734039     HIDGetEvents: unexpected input report (ignored)
 160.734046     Got 0 HID objects...
 160.734053     Quick update...
 
with some

 94.938441     libusb_get_interrupt: Connection timed out

 
and some data

 142.943604     Quick update...
 144.690952     upsdrv_updateinfo...
 144.733790     Got 13 HID objects...
 144.733818     Path: UPS.PowerSummary.PresentStatus.Charging, Type: Input, ReportID: 0x0a, Offset: 0, Size: 1, Value: 0
 144.733837     Path: UPS.PowerSummary.PresentStatus.Discharging, Type: Input, ReportID: 0x0a, Offset: 1, Size: 1, Value: 0
 144.733853     Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Input, ReportID: 0x0a, Offset: 2, Size: 1, Value: 1
 144.733869     Path: UPS.PowerSummary.PresentStatus.BatteryPresent, Type: Input, ReportID: 0x0a, Offset: 3, Size: 1, Value: 1
 144.733883     Path: UPS.PowerSummary.PresentStatus.BelowRemainingCapacityLimit, Type: Input, ReportID: 0x0a, Offset: 4, Size: 1, Value: 0
 144.733899     Path: UPS.PowerSummary.PresentStatus.RemainingTimeLimitExpired, Type: Input, ReportID: 0x0a, Offset: 5, Size: 1, Value: 0
 144.733911     Path: UPS.PowerSummary.PresentStatus.NeedReplacement, Type: Input, ReportID: 0x0a, Offset: 6, Size: 1, Value: 0
 144.733922     Path: UPS.PowerSummary.PresentStatus.VoltageNotRegulated, Type: Input, ReportID: 0x0a, Offset: 7, Size: 1, Value: 0
 144.733933     Path: UPS.PowerSummary.PresentStatus.ShutdownRequested, Type: Input, ReportID: 0x0a, Offset: 8, Size: 1, Value: 0
 144.733944     Path: UPS.PowerSummary.PresentStatus.ShutdownImminent, Type: Input, ReportID: 0x0a, Offset: 9, Size: 1, Value: 0
 144.733956     Path: UPS.PowerSummary.PresentStatus.CommunicationLost, Type: Input, ReportID: 0x0a, Offset: 10, Size: 1, Value: 0
 144.733967     Path: UPS.PowerSummary.PresentStatus.Overload, Type: Input, ReportID: 0x0a, Offset: 11, Size: 1, Value: 0
 144.733978     Path: UPS.PowerSummary.PresentStatus.ff860080, Type: Input, ReportID: 0x0a, Offset: 15, Size: 1, Value: 0
 
But when trying to get other components to run keep getting a refusal

upsc VGD at localhost
Error: Connection failure: Connection refused
 
Is there something I am missing? Should it run under the powercom driver or the usbhid-ups?


 
Powercom returns

Network UPS Tools - PowerCom protocol UPS driver 0.13 (2.6.4)
   0.000000     debug level is '2'

Unable to open /var/lib/ups/hiddev0: No such device

  Current user id: root (0)
Serial port owner: nut (57)
Serial port group: nut (57)
     Mode of port: 0750

Things to try:

 - Use another port (with the right permissions)

 - Fix the port owner/group or permissions on this port

 - Run this driver as another user (upsdrvctl -u or 'user=...' in ups.conf).
   See upsdrvctl(8) and ups.conf(5).

   0.000610     Fatal error: unusable configuration
 
TIA

 
 
 

 
-----Original message-----
From:Charles Lepple <clepple at gmail.com>
Sent:Sun 22-07-2012 08:56
Subject:Re: [Nut-upsuser] Re Powercom Vanguard driver for nut
To:Gordon Longland <gordon at compsos.com.au>; 
CC:nut-upsuser at lists.alioth.debian.org Users <nut-upsuser at lists.alioth.debian.org>; 
[please keep the list CC'd, most likely with reply-all]

On Jul 21, 2012, at 6:46 PM, Gordon Longland wrote:

> Thank you for the reply Charles
> 
> https://bugzilla.redhat.com/show_bug.cgi?format=multiple&id=806567
> 
> The above bug reflects the issues I had with trying to compile nut on RHEL5 i686 system. Has anyone managed to get nut 2.6.3 working on RHEL5?

I don't currently use any RPM-based systems myself, but I wonder why they are calling autoreconf when using the nut-2.6.3 tarball (usually autoreconf is only needed when building from a SVN checkout). Omitting that line from the spec file should help.

-- 
Charles Lepple
clepple at gmail



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20120723/f6e415e7/attachment.html>