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

2011-01-11 Thread Mick
On 11 January 2011 15:40, Kjell Claesson 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 th

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

2011-01-11 Thread Mick
On 11 January 2011 00:07, Charles Lepple wrote: > On Mon, Jan 10, 2011 at 3:28 PM, Mick wrote: >> On Monday 10 January 2011 12:19:34 you wrote: >>> Hi Mick >>> >>> 2011/1/9 Mick >> >>> > -rwxr-xr-x 1 root root 17840 Jul 25 11:45 /usr/libexec/hald-addon-hid-ups >> [snip ...] >> >>> > Could any of

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

2011-01-11 Thread Kjell Claesson
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 tr

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

2011-01-11 Thread Mick
On 11 January 2011 07:50, Arjen de Korte wrote: > Citeren Mick : > >> While nut is running, my logs fill up with: > Yes. Make your system not log messages at LOG_DEBUG. Usually you can > configure this in '/etc/syslog.conf'. On a production system, you should not > log messages with LOG_DEBUG sin

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

2011-01-11 Thread Arnaud Quette
2011/1/11 Arjen de Korte > > Citeren Mick : > > (...) > >> 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 o

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

2011-01-10 Thread Arjen de Korte
Citeren Mick : While nut is running, my logs fill up with: Jan 10 22:50:06 compaq usbhid-ups[5083]: libusb_get_report: No error Jan 10 22:50:08 compaq usbhid-ups[5083]: libusb_get_report: No error Jan 10 22:50:10 compaq usbhid-ups[5083]: libusb_get_report: No error Jan 10 22:50:12 compaq usbhid

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

2011-01-10 Thread Charles Lepple
On Mon, Jan 10, 2011 at 3:28 PM, Mick wrote: > On Monday 10 January 2011 12:19:34 you wrote: >> Hi Mick >> >> 2011/1/9 Mick > >> > -rwxr-xr-x 1 root root 17840 Jul 25 11:45 /usr/libexec/hald-addon-hid-ups > [snip ...] > >> > Could any of the above be causing the clash? >> >> indeed, /usr/libexec/

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

2011-01-10 Thread Mick
On 10 January 2011 20:28, Mick wrote: > On Monday 10 January 2011 12:19:34 you wrote: >> Hi Mick >> >> 2011/1/9 Mick > >> > -rwxr-xr-x 1 root root 17840 Jul 25 11:45 /usr/libexec/hald-addon-hid-ups > [snip ...] > >> > Could any of the above be causing the clash? >> >> indeed, /usr/libexec/hald-ad

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

2011-01-10 Thread Mick
On Monday 10 January 2011 12:19:34 you wrote: > Hi Mick > > 2011/1/9 Mick > > -rwxr-xr-x 1 root root 17840 Jul 25 11:45 /usr/libexec/hald-addon-hid-ups [snip ...] > > Could any of the above be causing the clash? > > indeed, /usr/libexec/hald-addon-hid-ups which is part of UPower (integrated >

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

2011-01-10 Thread Arnaud Quette
Hi Mick 2011/1/9 Mick > (Apologies for the long message, but there's a lot to report here.) > > After a lot of help from Kjell (thank you!) I am now testing the > 2.6.0-pre1 version with a usbhid-ups that recognises my UPS: > > # /etc/init.d/upsdrv start > * Starting UPS drivers ... > Network U

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

2011-01-09 Thread Mick
(Apologies for the long message, but there's a lot to report here.) After a lot of help from Kjell (thank you!) I am now testing the 2.6.0-pre1 version with a usbhid-ups that recognises my UPS: # /etc/init.d/upsdrv start * Starting UPS drivers ... Network UPS Tools - UPS driver controller 2.6.0-

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

2011-01-04 Thread Mick
On Tuesday 04 January 2011 20:46:26 Arjen de Korte wrote: > Citeren Mick : > > [ snip ] > > >0.171361 refresh_report_buffer: expected 4 bytes, but got 8 > >instead > > > >0.171403 Path: UPS.PowerSummary.DelayBeforeStartup, Type: > > Feature, ReportID: 0x11, Offset: 0, Size: 2

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

2011-01-04 Thread Arjen de Korte
Citeren Mick : [ snip ] 0.171361 refresh_report_buffer: expected 4 bytes, but got 8 instead 0.171403 Path: UPS.PowerSummary.DelayBeforeStartup, Type: Feature, ReportID: 0x11, Offset: 0, Size: 24, Value: 0.00 0.171446 Report descriptor retrieved (Reportlen = 412) 0.17

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

2011-01-04 Thread Arjen de Korte
Citeren Charles Lepple : Technically, HID only needs to be specified on the interface class (device class can be 0), so this descriptor is correct in that regard. If the device is auto detected by Windows and Apple, it is quite possible that this is indeed a HID PDC device. Not sure why i

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

2011-01-03 Thread Charles Lepple
On Mon, Jan 3, 2011 at 5:07 PM, Kjell Claesson wrote: > The device class is not HID, but you can try this. Technically, HID only needs to be specified on the interface class (device class can be 0), so this descriptor is correct in that regard. Not sure why it didn't match, though... -- - Char

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

2011-01-03 Thread Mick
On Monday 03 January 2011 22:07:20 you wrote: > OK > > > On Monday 03 January 2011 20:40:17 Arjen de Korte wrote: > > > Citeren Kjell Claesson : > > > > So start to send the output of: > > > > > > > > lsusb -v > > > > > > > > Cut out the part about the ups, and we have a look on it. > > > > > >

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

2011-01-03 Thread Kjell Claesson
OK > On Monday 03 January 2011 20:40:17 Arjen de Korte wrote: > > Citeren Kjell Claesson : > > > So start to send the output of: > > > > > > lsusb -v > > > > > > Cut out the part about the ups, and we have a look on it. > > > > Make that > > > > lsusb -v -d 075d:0300 > > > > to save yours

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

2011-01-03 Thread Mick
On Monday 03 January 2011 20:40:17 Arjen de Korte wrote: > Citeren Kjell Claesson : > > So start to send the output of: > > > > lsusb -v > > > > Cut out the part about the ups, and we have a look on it. > > Make that > > lsusb -v -d 075d:0300 > > to save yourself the trouble of weeding ou

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

2011-01-03 Thread Arjen de Korte
Citeren Kjell Claesson : So start to send the output of: lsusb -v Cut out the part about the ups, and we have a look on it. Make that lsusb -v -d 075d:0300 to save yourself the trouble of weeding out the interesting stuff from the other USB devices (we already know the VID:PID combin

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

2011-01-03 Thread Kjell Claesson
> Hi all, first message to the list. :-) Hi Mick, > > I've got an iBox made by iDowell: > > http://store.apple.com/uk/product/TR423ZM/A > > This seems to be similar to the smaller Microdowell UPS: > > http://idowell.eu/ > Look nice. > I cannot get it recognised by the drivers. This is what

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

2011-01-03 Thread Mick
Hi all, first message to the list. :-) I've got an iBox made by iDowell: http://store.apple.com/uk/product/TR423ZM/A This seems to be similar to the smaller Microdowell UPS: http://idowell.eu/ I cannot get it recognised by the drivers. This is what I get when I plug in the USB connector: J