[Nut-upsuser] Can't get iDowell to work

Mick michaelkintzios at gmail.com
Tue Jan 11 20:56:27 UTC 2011


On 11 January 2011 15:40, Kjell Claesson
<kjell.claesson at epost.tidanet.se> wrote:
> Hi,
>> >> PS. What is the meaning of:  battery.capacity: 0.03 ?
>> >
>> > This is a mapping problem. The UPS is reporting 100% battery capacity is
>> > available and I mistakenly mapped this to the battery capacity (Ah)
>> > value. I will remove this later on.
>>
>> Kewl!
>
> This is already done in the trunk by Arnaud. So 'emerge nut-svn' and it would
> be fixed.

 * subversion update start -->
 *      repository: svn://svn.debian.org/nut/trunk
U    clients/upsclient.c
U    Makefile.am
U    data/driver.list.in
U    NEWS
U    drivers/idowell-hid.c
Updated to revision 2819.


This is the latest and greatest:

# upsc iDowell
battery.charge: 100
battery.charge.low: 15
battery.runtime: 650
device.mfr: iDowell
device.model: iBox
device.serial: 00000001
device.type: ups
driver.name: usbhid-ups
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.version: 2.6.0-pre1
driver.version.data: iDowell HID 0.1
driver.version.internal: 0.35
ups.delay.shutdown: 20
ups.delay.start: 30
ups.mfr: iDowell
ups.model: iBox
ups.productid: 0300
ups.serial: 00000001
ups.status: OL CHRG
ups.timer.shutdown: 60
ups.vendorid: 075d


and this is the debug version:

   0.039254     Checking device (075D/0300) (003/039)
   0.073922     - VendorID: 075d
   0.073943     - ProductID: 0300
   0.073951     - Manufacturer: iDowell
   0.073958     - Product: iBox
   0.073965     - Serial Number: 00000001
   0.073972     - Bus: 003
   0.073978     Trying to match device
   0.073992     Device matches
   0.074024     failed to claim USB device: could not claim interface
0: Device or resource busy
   0.074057     detached kernel driver from USB device...
   0.081942     HID descriptor length 412
   0.136924     Report Descriptor size = 412
   0.137148     Using subdriver: iDowell HID 0.1
   0.141917     libusb_get_report: could not claim interface 0: Device
or resource busy
   0.141943     Can't retrieve Report 0b: Device or resource busy
   0.141956     Path: UPS.PowerConverter.PowerConverterID, Type:
Feature, ReportID: 0x0b, Offset: 0, Size: 8
   0.146917     libusb_get_report: could not claim interface 0: Device
or resource busy
   0.146935     Can't retrieve Report 0b: Device or resource busy
   0.146954     Path: UPS.PowerConverter.Output.OutputID, Type:
Feature, ReportID: 0x0b, Offset: 8, Size: 8
   0.151915     libusb_get_report: could not claim interface 0: Device
or resource busy
   0.151930     Can't retrieve Report 0e: Device or resource busy
   0.151943     Path: UPS.PowerConverter.Output.Voltage, Type:
Feature, ReportID: 0x0e, Offset: 0, Size: 8
   0.156916     libusb_get_report: could not claim interface 0: Device
or resource busy
   0.156935     Can't retrieve Report 13: Device or resource busy
   0.156949     Path: UPS.PowerConverter.Output.LowVoltageTransfer,
Type: Feature, ReportID: 0x13, Offset: 0, Size: 8
   0.161915     libusb_get_report: could not claim interface 0: Device
or resource busy
   0.161929     Can't retrieve Report 13: Device or resource busy
   0.161942     Path: UPS.PowerConverter.Output.HighVoltageTransfer,
Type: Feature, ReportID: 0x13, Offset: 8, Size: 16
   0.166915     libusb_get_report: could not claim interface 0: Device
or resource busy
   0.166931     Can't retrieve Report 0b: Device or resource busy
   0.166945     Path: UPS.Flow.[4].FlowID, Type: Feature, ReportID:
0x0b, Offset: 16, Size: 8
   0.171914     libusb_get_report: could not claim interface 0: Device
or resource busy
   0.171928     Can't retrieve Report 12: Device or resource busy
   0.171941     Path: UPS.Flow.[4].ConfigVoltage, Type: Feature,
ReportID: 0x12, Offset: 0, Size: 8
   0.176920     libusb_get_report: could not claim interface 0: Device
or resource busy
   0.176953     Can't retrieve Report 0d: Device or resource busy
   0.176975     Path: UPS.Flow.[4].ConfigFrequency, Type: Feature,
ReportID: 0x0d, Offset: 0, Size: 8
   0.181918     libusb_get_report: could not claim interface 0: Device
or resource busy
   0.181940     Can't retrieve Report 0d: Device or resource busy
   0.181954     Path: UPS.Flow.[4].ConfigApparentPower, Type: Feature,
ReportID: 0x0d, Offset: 8, Size: 16
   0.186915     libusb_get_report: could not claim interface 0: Device
or resource busy
   0.186933     Can't retrieve Report 0b: Device or resource busy
   0.186946     Path: UPS.PowerSummary.PowerSummaryID, Type: Feature,
ReportID: 0x0b, Offset: 24, Size: 8
   0.191913     libusb_get_report: could not claim interface 0: Device
or resource busy
   0.191927     Can't retrieve Report 0b: Device or resource busy
   0.191939     Path: UPS.PowerSummary.FlowID, Type: Feature,
ReportID: 0x0b, Offset: 32, Size: 8
   0.196924     Path: UPS.PowerSummary.CapacityMode, Type: Feature,
ReportID: 0x0c, Offset: 0, Size: 8, Value: 2
   0.196952     Path: UPS.PowerSummary.RemainingCapacityLimit, Type:
Feature, ReportID: 0x0c, Offset: 8, Size: 8, Value: 15
   0.196969     Path: UPS.PowerSummary.CapacityGranularity1, Type:
Feature, ReportID: 0x0c, Offset: 16, Size: 8, Value: 25
   0.201912     libusb_get_report: could not claim interface 0: Device
or resource busy
   0.201927     Can't retrieve Report 10: Device or resource busy
   0.201940     Path: UPS.PowerSummary.iDeviceChemistry, Type:
Feature, ReportID: 0x10, Offset: 0, Size: 8
   0.206913     libusb_get_report: could not claim interface 0: Device
or resource busy
   0.206928     Can't retrieve Report 10: Device or resource busy
   0.206940     Path: UPS.PowerSummary.iManufacturer, Type: Feature,
ReportID: 0x10, Offset: 8, Size: 8
   0.211912     libusb_get_report: could not claim interface 0: Device
or resource busy
   0.211926     Can't retrieve Report 10: Device or resource busy
   0.211938     Path: UPS.PowerSummary.iProduct, Type: Feature,
ReportID: 0x10, Offset: 16, Size: 8
   0.216917     libusb_get_report: could not claim interface 0: Device
or resource busy
   0.216950     Can't retrieve Report 10: Device or resource busy
   0.216970     Path: UPS.PowerSummary.iSerialNumber, Type: Feature,
ReportID: 0x10, Offset: 24, Size: 8
   0.221915     libusb_get_report: could not claim interface 0: Device
or resource busy
   0.221936     Can't retrieve Report 0e: Device or resource busy
   0.221950     Path: UPS.PowerSummary.PercentLoad, Type: Feature,
ReportID: 0x0e, Offset: 8, Size: 8
   0.221968     Path: UPS.PowerSummary.DesignCapacity, Type: Feature,
ReportID: 0x0c, Offset: 24, Size: 8, Value: 100
   0.221983     Path: UPS.PowerSummary.FullChargeCapacity, Type:
Feature, ReportID: 0x0c, Offset: 32, Size: 8, Value: 100
   0.226922     Path: UPS.PowerSummary.RemainingCapacity, Type:
Feature, ReportID: 0x16, Offset: 0, Size: 8, Value: 100
   0.226943     Path: UPS.PowerSummary.RemainingCapacity, Type: Input,
ReportID: 0x16, Offset: 0, Size: 8, Value: 100
   0.226958     Path: UPS.PowerSummary.RunTimeToEmpty, Type: Feature,
ReportID: 0x16, Offset: 8, Size: 16, Value: 650
   0.226972     Path: UPS.PowerSummary.RunTimeToEmpty, Type: Input,
ReportID: 0x16, Offset: 8, Size: 16, Value: 650
   0.231911     libusb_get_report: could not claim interface 0: Device
or resource busy
   0.231927     Can't retrieve Report 01: Device or resource busy
   0.231940     Path:
UPS.PowerSummary.PresentStatus.CommunicationLost, Type: Input,
ReportID: 0x01, Offset: 0, Size: 1
   0.236912     libusb_get_report: could not claim interface 0: Device
or resource busy
   0.236928     Can't retrieve Report 01: Device or resource busy
   0.236941     Path:
UPS.PowerSummary.PresentStatus.CommunicationLost, Type: Feature,
ReportID: 0x01, Offset: 0, Size: 1
   0.241910     libusb_get_report: could not claim interface 0: Device
or resource busy
   0.241924     Can't retrieve Report 01: Device or resource busy
   0.241936     Path: UPS.PowerSummary.PresentStatus.Undefined, Type:
Input, ReportID: 0x01, Offset: 1, Size: 7
   0.246911     libusb_get_report: could not claim interface 0: Device
or resource busy
   0.246927     Can't retrieve Report 01: Device or resource busy
   0.246940     Path: UPS.PowerSummary.PresentStatus.Undefined, Type:
Feature, ReportID: 0x01, Offset: 1, Size: 7
   0.251931     Path: UPS.PowerSummary.PresentStatus.ACPresent, Type:
Input, ReportID: 0x02, Offset: 0, Size: 1, Value: 1
   0.251964     Path: UPS.PowerSummary.PresentStatus.Charging, Type:
Input, ReportID: 0x02, Offset: 1, Size: 1, Value: 1
   0.251991     Path: UPS.PowerSummary.PresentStatus.Discharging,
Type: Input, ReportID: 0x02, Offset: 2, Size: 1, Value: 0
   0.252017     Path:
UPS.PowerSummary.PresentStatus.BelowRemainingCapacityLimit, Type:
Input, ReportID: 0x02, Offset: 3, Size: 1, Value: 0
   0.252043     Path: UPS.PowerSummary.PresentStatus.NeedReplacement,
Type: Input, ReportID: 0x02, Offset: 4, Size: 1, Value: 0
   0.252068     Path: UPS.PowerSummary.PresentStatus.Good, Type:
Input, ReportID: 0x02, Offset: 5, Size: 1, Value: 1
   0.252093     Path: UPS.PowerSummary.PresentStatus.ShutdownImminent,
Type: Input, ReportID: 0x02, Offset: 6, Size: 1, Value: 0
   0.252119     Path: UPS.PowerSummary.PresentStatus.Overload, Type:
Input, ReportID: 0x02, Offset: 7, Size: 1, Value: 0
   0.252143     Path: UPS.PowerSummary.PresentStatus.InternalFailure,
Type: Input, ReportID: 0x02, Offset: 8, Size: 1, Value: 0
   0.252168     Path: UPS.PowerSummary.PresentStatus.Undefined, Type:
Input, ReportID: 0x02, Offset: 9, Size: 7, Value: 0
   0.252192     Path: UPS.PowerSummary.PresentStatus.ACPresent, Type:
Feature, ReportID: 0x02, Offset: 0, Size: 1, Value: 1
   0.252216     Path: UPS.PowerSummary.PresentStatus.Charging, Type:
Feature, ReportID: 0x02, Offset: 1, Size: 1, Value: 1
   0.252241     Path: UPS.PowerSummary.PresentStatus.Discharging,
Type: Feature, ReportID: 0x02, Offset: 2, Size: 1, Value: 0
   0.252265     Path:
UPS.PowerSummary.PresentStatus.BelowRemainingCapacityLimit, Type:
Feature, ReportID: 0x02, Offset: 3, Size: 1, Value: 0
   0.252289     Path: UPS.PowerSummary.PresentStatus.NeedReplacement,
Type: Feature, ReportID: 0x02, Offset: 4, Size: 1, Value: 0
   0.252321     Path: UPS.PowerSummary.PresentStatus.Good, Type:
Feature, ReportID: 0x02, Offset: 5, Size: 1, Value: 1
   0.252347     Path: UPS.PowerSummary.PresentStatus.ShutdownImminent,
Type: Feature, ReportID: 0x02, Offset: 6, Size: 1, Value: 0
   0.252373     Path: UPS.PowerSummary.PresentStatus.Overload, Type:
Feature, ReportID: 0x02, Offset: 7, Size: 1, Value: 0
   0.252398     Path: UPS.PowerSummary.PresentStatus.InternalFailure,
Type: Feature, ReportID: 0x02, Offset: 8, Size: 1, Value: 0
   0.252423     Path: UPS.PowerSummary.PresentStatus.Undefined, Type:
Feature, ReportID: 0x02, Offset: 9, Size: 7, Value: 0
   0.256917     libusb_get_report: could not claim interface 0: Device
or resource busy
   0.256944     Can't retrieve Report 0f: Device or resource busy
   0.256962     Path: UPS.PowerSummary.DelayBeforeShutdown, Type:
Feature, ReportID: 0x0f, Offset: 0, Size: 24
   0.261913     libusb_get_report: could not claim interface 0: Device
or resource busy
   0.261942     Can't retrieve Report 11: Device or resource busy
   0.261961     Path: UPS.PowerSummary.DelayBeforeStartup, Type:
Feature, ReportID: 0x11, Offset: 0, Size: 24
   0.262004     Report descriptor retrieved (Reportlen = 412)
   0.262018     Found HID device
   0.262032     Detected a UPS: iDowell/iBox
   0.262067     Path: UPS.PowerSummary.PresentStatus.ACPresent, Type:
Feature, ReportID: 0x02, Offset: 0, Size: 1, Value: 1
   0.262100     Path:
UPS.PowerSummary.PresentStatus.BelowRemainingCapacityLimit, Type:
Feature, ReportID: 0x02, Offset: 3, Size: 1, Value: 0
   0.262130     Path: UPS.PowerSummary.PresentStatus.Charging, Type:
Feature, ReportID: 0x02, Offset: 1, Size: 1, Value: 1
   0.266913     libusb_get_report: could not claim interface 0: Device
or resource busy
   0.266936     Can't retrieve Report 01: Device or resource busy
   0.266947     Got disconnected by another driver: Device or resource busy
   0.266956     Can't initialize data from HID UPS

Quite a few "Can't retrieve Report 01: Device or resource busy" in
there - are these because of upower or whatever else is antagonising
usbhiod-ups?

Thanks again guys for all your help.
-- 
Regards,
Mick



More information about the Nut-upsuser mailing list