Re: [Nut-upsuser] Can't get iDowell to work
2011/1/11 Arjen de Korte nut+us...@de-korte.org nut%2bus...@de-korte.org Citeren Mick michaelkintz...@gmail.com: (...) 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. done (r2816) cheers, Arnaud -- Linux / Unix Expert RD - Eaton - http://powerquality.eaton.com Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.free.fr/ ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Can't get iDowell to work
On 11 January 2011 07:50, Arjen de Korte nut+us...@de-korte.org wrote:
Citeren Mick michaelkintz...@gmail.com:
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 since this is reserved for debugging messages
and can be very verbose (risking flooding the logs).
Oops! Yes, that had been left uncommented for some reason. Thanks.
Jan 10 23:15:59 compaq usbhid-ups[5945]: Got disconnected by another
driver: Device or resource busy
... and so on.
Not sure if this is how it should be - but within a few minutes I get:
# upsc iDowell
Error: Data stale
You *must* stop the usbhid-ups driver for a UPS before starting a new one.
The message Got disconnected by another driver: Device or resource busy is
a tell tale sign that you didn't. Before running 'upsdrvctl start', always
run 'upsdrvctl stop' first. A crude method would be to reboot the system, if
you can't find the running usbhid-ups processes. I usually use 'top -u upsd'
('upsd' is the name of the NUT user on my system) to find any drivers
running.
I am sure I did stop both upsd and upsdrv and then restarted them
after I added pollonly... but will check again.
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!
--
Regards,
Mick
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Can't get iDowell to work
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. Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Can't get iDowell to work
On 11 January 2011 00:07, Charles Lepple clep...@gmail.com wrote: On Mon, Jan 10, 2011 at 3:28 PM, Mick michaelkintz...@gmail.com wrote: On Monday 10 January 2011 12:19:34 you wrote: Hi Mick 2011/1/9 Mick michaelkintz...@gmail.com -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 power management), which is automatically launched when a new USB/HID UPS is plugged. since UPower is running as root, it will prevent usbhid-ups from claiming back your UPS after software disconnection. you may try to run nut as root to check if you still see the claim interface failure. I'll have to check UPower, since iirc, it wasn't previously running as root (or I'm maybe confusing with HAL...) So assuming that the new driver can now deal with my UPS, is this something that I'll have wait for to settle, as hal is deprecated and on a path to be replaced with upower? The simple answer is you can only have one of the following attached to your UPS: the HAL driver, or the normal NUT usbhid-ups driver. Right, I wasn't sure if NUT usbhid-ups was working with hal, or if it is independent of it. I've stopped hal and noticed no difference. This is what hal is polling: $ ps axf | grep -i hal 30796 pts/3S+ 0:00 \_ grep --colour=auto -i hal 30711 ?Ssl0:00 /usr/sbin/hald --use-syslog --verbose=no 30712 ?S 0:00 \_ hald-runner 30743 ?S 0:00 \_ hald-addon-input: Listening on /dev/input/event3 /dev/input/event0 /dev/input/event1 30759 ?S 0:00 \_ hald-addon-acpi: listening on acpid socket /var/run/acpid.socket 30760 ?S 0:00 \_ hald-addon-storage: polling /dev/sdb (every 2 sec) 30761 ?S 0:00 \_ hald-addon-storage: polling /dev/sdc (every 2 sec) 30762 ?S 0:00 \_ hald-addon-storage: polling /dev/sdd (every 2 sec) 30763 ?S 0:00 \_ hald-addon-storage: polling /dev/sde (every 2 sec) 30764 ?S 0:00 \_ hald-addon-storage: polling /dev/sr0 (every 2 sec) 30765 ?S 0:00 \_ hald-addon-storage: polling /dev/sr1 (every 2 sec) If /usr/libexec/hald-addon-hid-ups is launched by UPower, you may have to either disable UPower and use NUT's interface to shut down the system, or use whatever UPower is doing these days. No idea how to disable upower (or if it is even desirable to do so). It doesn't show up under running processes. -- Regards, Mick ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Can't get iDowell to work
On 11 January 2011 15:40, Kjell Claesson kjell.claes...@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 Uclients/upsclient.c UMakefile.am Udata/driver.list.in UNEWS Udrivers/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: 0001 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: 0001 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: 0001 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:
Re: [Nut-upsuser] Can't get iDowell to work
Hi Mick 2011/1/9 Mick michaelkintz...@gmail.com (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-pre1 Network UPS Tools - Generic HID driver 0.35 (2.6.0-pre1) USB communication driver 0.31 Using subdriver: iDowell HID 0.1 libusb_get_report: No error libusb_get_report: No error libusb_get_report: No error libusb_get_report: No error libusb_get_report: No error libusb_get_report: No error libusb_get_report: No error libusb_get_report: No error libusb_get_report: No error libusb_get_report: No error libusb_get_report: No error libusb_get_report: No error libusb_get_report: No error libusb_get_report: No error libusb_get_report: No error libusb_get_report: No error [ ok ] # /etc/init.d/upsd start * Starting upsd ... Network UPS Tools upsd 2.6.0-pre1 listening on 127.0.0.1 port 3493 Connected to UPS [iDowell]: usbhid-ups-iDowell allowfrom in upsd.users is no longer used [ ok ] # upsc iDowell battery.capacity: 0.03 battery.charge: 100 battery.charge.low: 15 battery.runtime: 342 --this seems to fluctuate this is calculated and reported by the device . nothing we can do about in NUT... device.mfr: iDowell device.model: iBox device.serial: 0001 device.type: ups driver.flag.pollonly: enabled 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: 0001 ups.status: OL CHRG ups.vendorid: 075d There does seem to be one problem with my system which generates reports like this before I start upsdrv: === Jan 9 19:23:20 compaq kernel: usb 3-2: USB disconnect, address 4 Jan 9 19:23:21 compaq kernel: usb 3-2: new low speed USB device using uhci_hcd and address 5 Jan 9 19:23:21 compaq kernel: usb 3-2: new low speed USB device using uhci_hcd and address 5 Jan 9 19:23:21 compaq kernel: usb 3-2: New USB device found, idVendor=075d, idProduct=0300 Jan 9 19:23:21 compaq kernel: usb 3-2: New USB device found, idVendor=075d, idProduct=0300 Jan 9 19:23:21 compaq kernel: usb 3-2: New USB device strings: Mfr=3, Product=1, SerialNumber=2 Jan 9 19:23:21 compaq kernel: usb 3-2: New USB device strings: Mfr=3, Product=1, SerialNumber=2 Jan 9 19:23:21 compaq kernel: usb 3-2: Product: iBox Jan 9 19:23:21 compaq kernel: usb 3-2: Product: iBox Jan 9 19:23:21 compaq kernel: usb 3-2: Manufacturer: iDowell Jan 9 19:23:21 compaq kernel: usb 3-2: Manufacturer: iDowell Jan 9 19:23:21 compaq kernel: usb 3-2: SerialNumber: 0001 Jan 9 19:23:21 compaq kernel: usb 3-2: SerialNumber: 0001 Jan 9 19:23:21 compaq kernel: generic-usb 0003:075D:0300.0005: hidraw1: USB HID v1.10 Device [iDowell iBox] on usb-:00:1d.1-2/input0 Jan 9 19:23:21 compaq kernel: generic-usb 0003:075D:0300.0005: hidraw1: USB HID v1.10 Device [iDowell iBox] on usb-:00:1d.1-2/input0 Jan 9 19:23:36 compaq kernel: usb 3-2: USB disconnect, address 5 Jan 9 19:23:36 compaq kernel: usb 3-2: USB disconnect, address 5 ... === (it'll keep disconnecting and reconnecting) and like this after I connect to it with upsdrv: === Jan 9 19:24:45 compaq usbhid-ups[5228]: Startup successful Jan 9 19:24:45 compaq usbhid-ups[5228]: Startup successful Jan 9 19:24:45 compaq usbhid-ups[5228]: libusb_get_report: No error Jan 9 19:24:46 compaq upsd[4933]: Connected to UPS [iDowell]: usbhid-ups-iDowell Jan 9 19:24:46 compaq upsd[4933]: Connected to UPS [iDowell]: usbhid-ups-iDowell Jan 9 19:24:47 compaq usbhid-ups[5228]: libusb_get_report: could not claim interface 0: Device or resource busy Jan 9 19:24:47 compaq usbhid-ups[5228]: Got disconnected by another driver: Device or resource busy Jan 9 19:24:49 compaq usbhid-ups[5228]: libusb_get_report: could not claim interface 0: Device or resource busy Jan 9 19:24:49 compaq usbhid-ups[5228]: Got disconnected by another driver: Device or resource busy Jan 9 19:24:51 compaq usbhid-ups[5228]: libusb_get_report: could not claim interface 0: Device or resource busy Jan 9 19:24:51 compaq usbhid-ups[5228]: Got disconnected by another driver: Device or resource busy Jan 9 19:24:53 compaq usbhid-ups[5228]: libusb_get_report: could not claim interface 0: Device or resource busy === ... and so on. At the
Re: [Nut-upsuser] Can't get iDowell to work
On 10 January 2011 20:28, Mick michaelkintz...@gmail.com wrote: On Monday 10 January 2011 12:19:34 you wrote: Hi Mick 2011/1/9 Mick michaelkintz...@gmail.com -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 power management), which is automatically launched when a new USB/HID UPS is plugged. since UPower is running as root, it will prevent usbhid-ups from claiming back your UPS after software disconnection. you may try to run nut as root to check if you still see the claim interface failure. I'll have to check UPower, since iirc, it wasn't previously running as root (or I'm maybe confusing with HAL...) So assuming that the new driver can now deal with my UPS, is this something that I'll have wait for to settle, as hal is deprecated and on a path to be replaced with upower? Some more testing tonight and after a reboot I get this. :-) # upsc iDowell battery.capacity: 0.03 battery.charge: 100 battery.charge.low: 15 battery.runtime: 650 device.mfr: iDowell device.model: iBox device.serial: 0001 device.type: ups driver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.parameter.productid: 0300 driver.parameter.vendorid: 075d 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: 0001 ups.status: OL CHRG ups.timer.start: 0 ups.vendorid: 075d 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-ups[5083]: libusb_get_report: No error regularly at 2 second intervals. Is there a way to tell it to not log such messages (or log them only once?) If I add pollonly in ups.conf I get these messages: Jan 10 23:15:57 compaq upsd[5995]: listening on 127.0.0.1 port 3493 Jan 10 23:15:57 compaq upsd[5995]: Connected to UPS [iDowell]: usbhid-ups-iDowell Jan 10 23:15:57 compaq upsd[5995]: allowfrom in upsd.users is no longer used Jan 10 23:15:57 compaq upsd[5996]: Startup successful Jan 10 23:15:57 compaq usbhid-ups[5945]: libusb_get_report: could not claim interface 0: Device or resource busy Jan 10 23:15:57 compaq usbhid-ups[5945]: Got disconnected by another driver: Device or resource busy Jan 10 23:15:59 compaq usbhid-ups[5945]: libusb_get_report: could not claim interface 0: Device or resource busy Jan 10 23:15:59 compaq usbhid-ups[5945]: Got disconnected by another driver: Device or resource busy ... and so on. Not sure if this is how it should be - but within a few minutes I get: # upsc iDowell Error: Data stale PS. What is the meaning of: battery.capacity: 0.03 ? -- Regards, Mick ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Can't get iDowell to work
Citeren Mick michaelkintz...@gmail.com:
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-ups[5083]: libusb_get_report: No error
regularly at 2 second intervals. Is there a way to tell it to not log
such messages (or log them only once?)
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 since this is reserved for
debugging messages and can be very verbose (risking flooding the logs).
If I add pollonly in ups.conf I get these messages:
Jan 10 23:15:57 compaq upsd[5995]: listening on 127.0.0.1 port 3493
Jan 10 23:15:57 compaq upsd[5995]: Connected to UPS [iDowell]:
usbhid-ups-iDowell
Jan 10 23:15:57 compaq upsd[5995]: allowfrom in upsd.users is no longer used
Jan 10 23:15:57 compaq upsd[5996]: Startup successful
Jan 10 23:15:57 compaq usbhid-ups[5945]: libusb_get_report: could not
claim interface 0: Device or resource busy
Jan 10 23:15:57 compaq usbhid-ups[5945]: Got disconnected by another
driver: Device or resource busy
Jan 10 23:15:59 compaq usbhid-ups[5945]: libusb_get_report: could not
claim interface 0: Device or resource busy
Jan 10 23:15:59 compaq usbhid-ups[5945]: Got disconnected by another
driver: Device or resource busy
... and so on.
Not sure if this is how it should be - but within a few minutes I get:
# upsc iDowell
Error: Data stale
You *must* stop the usbhid-ups driver for a UPS before starting a new
one. The message Got disconnected by another driver: Device or
resource busy is a tell tale sign that you didn't. Before running
'upsdrvctl start', always run 'upsdrvctl stop' first. A crude method
would be to reboot the system, if you can't find the running
usbhid-ups processes. I usually use 'top -u upsd' ('upsd' is the name
of the NUT user on my system) to find any drivers running.
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.
Best regards, Arjen
--
Please keep list traffic on the list (off-list replies will be rejected)
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Can't get iDowell to work
Citeren Charles Lepple clep...@gmail.com: 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 it didn't match, though... That's pretty obvious. No subdriver supports this VID:PID combination, so you'll get no match for any of them. What Kjell forgot to mention is that Mick will need to add the 'explore' flag to 'ups.conf' (see 'man 8 usbhid-ups'), so that at least we'll get some debugging output. Best regards, Arjen -- Please keep list traffic on the list (off-list replies will be rejected) ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Can't get iDowell to work
Citeren Mick michaelkintz...@gmail.com: [ 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.171461 Found HID device 0.171475 Detected a UPS: iDowell/iBox 0.171490 find_nut_info: unknown info type: load.off.delay 0.171503 find_nut_info: unknown info type: load.on.delay 0.171515 find_nut_info: unknown info type: load.off.delay 0.171542 upsdrv_initinfo... 0.171574 upsdrv_updateinfo... 0.186562 Got 10 HID objects... [snip ...] This keeps going on and on, so I attach the rest as a zipped file to keep the noise down. We probably should have warned you that we only need the first thirty seconds worth of output. Nevertheless, this device indeed speaks HID PDC, so it should be trivial to add this to the usbhid-ups driver. I don't recognize a familiar subset/pattern of commands, so I guess this warrants adding a new subdriver. Best regards, Arjen -- Please keep list traffic on the list (off-list replies will be rejected) ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Can't get iDowell to work
On Tuesday 04 January 2011 20:46:26 Arjen de Korte wrote: Citeren Mick michaelkintz...@gmail.com: [ 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.171461 Found HID device 0.171475 Detected a UPS: iDowell/iBox 0.171490 find_nut_info: unknown info type: load.off.delay 0.171503 find_nut_info: unknown info type: load.on.delay 0.171515 find_nut_info: unknown info type: load.off.delay 0.171542 upsdrv_initinfo... 0.171574 upsdrv_updateinfo... 0.186562 Got 10 HID objects... [snip ...] This keeps going on and on, so I attach the rest as a zipped file to keep the noise down. We probably should have warned you that we only need the first thirty seconds worth of output. Nevertheless, this device indeed speaks HID PDC, so it should be trivial to add this to the usbhid-ups driver. I don't recognize a familiar subset/pattern of commands, so I guess this warrants adding a new subdriver. Thank you guys! :-) Please let me know if you need anything more from me. -- Regards, Mick ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
[Nut-upsuser] Can't get iDowell to work
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:
Jan 3 19:27:26 compaq kernel: usb 3-2: new low speed USB device using
uhci_hcd and address 47
Jan 3 19:27:26 compaq kernel: usb 3-2: New USB device found, idVendor=075d,
idProduct=0300
Jan 3 19:27:26 compaq kernel: usb 3-2: New USB device strings: Mfr=3,
Product=1, SerialNumber=2
Jan 3 19:27:26 compaq kernel: usb 3-2: Product: iBox
Jan 3 19:27:26 compaq kernel: usb 3-2: Manufacturer: iDowell
Jan 3 19:27:26 compaq kernel: usb 3-2: SerialNumber: 0001
Jan 3 19:27:26 compaq kernel: generic-usb 0003:075D:0300.00CA: hidraw1: USB
HID v1.10 Device [iDowell iBox] on usb-:00:1d.1-2/input0
Jan 3 19:27:42 compaq kernel: usb 3-2: USB disconnect, address 47
The device keeps disconnecting and reconnecting with a higher numerical
address each time.
I have set up this udev rule in /etc/udev/rules.d/70-nut-usbups.rules:
# iDowell iBox USB
ATTR{idVendor}==075d, ATTR{idProduct}==0300, SYMLINK+=iDowell,
MODE=664, GROUP=nut
When I try to start the upsd I get:
# /etc/init.d/upsd restart
* Starting upsd ...
Network UPS Tools upsd 2.4.3
listening on 127.0.0.1 port 3493
Can't connect to UPS [iDowell] (usbhid-ups-iDowell): No such file or directory
allowfrom in upsd.users is no longer used [ ok ]
The driver(s) is not successful.
With usbhid-ups I get:
=
# /lib/nut/usbhid-ups - -a iDowell
Network UPS Tools - Generic HID driver 0.34 (2.4.3)
USB communication driver 0.31
0.00 send_to_all: SETINFO driver.parameter.port /dev/iDowell
0.48 send_to_all: SETINFO driver.parameter.vendorid 075d
0.81 debug level is '16'
0.000721 upsdrv_initups...
[snip ...]
0.001307 Checking device (075D/0300) (003/061)
0.035384 - VendorID: 075d
0.035399 - ProductID: 0300
0.035408 - Manufacturer: iDowell
0.035414 - Product: iBox
0.035421 - Serial Number: 0001
0.035428 - Bus: 003
0.035435 Trying to match device
0.035443 Device does not match - skipping
[snip ...]
0.071806 Trying to match device
0.071814 Device does not match - skipping
0.071823 No appropriate HID device found
0.071836 No matching HID UPS found
=
with powerpanel I get:
=
# /lib/nut/powerpanel - -a iDowell
Network UPS Tools - CyberPower text/binary protocol UPS driver 0.25 (2.4.3)
Warning: This is an experimental driver.
Some features may not function correctly.
0.00 send_to_all: SETINFO driver.parameter.port /dev/iDowell
0.64 debug level is '16'
0.011711 Trying binary protocol...
0.011745 tcgetattr(/dev/iDowell): Inappropriate ioctl for device
=
with microdowell I get:
=
# /lib/nut/microdowell - -a iDowell
Network UPS Tools - MICRODOWELL UPS driver 0.01 (2.4.3)
0.00 send_to_all: SETINFO driver.parameter.port /dev/iDowell
0.63 debug level is '16'
0.000728 tcgetattr(/dev/iDowell): Inappropriate ioctl for device
=
This is what my /etc/nut/ups.conf contains:
[iDowell]
driver = microdowell
# port = auto
port = /dev/iDowell
# manufacturer = iDowell
# vendorid = 075d
desc = iBox by iDowell
I am not sure if the problem is with the drivers I have been using or
something else, like my udev rule, access rights, etc.
# ls -la /dev/iDowell
lrwxrwxrwx 1 root root 15 Jan 3 19:38 /dev/iDowell - bus/usb/003/091
(BTW, I don't seem to have a dev/hiddev0 or similar that I thought the iBox
would be recognised as).
# ls -la /etc/nut/
total 38
drwxr-xr-x 2 root root 224 Jan 3 19:36 .
drwxr-xr-x 90 root root 6008 Jan 3 18:30 ..
-rw-r--r-- 1 root root 1413 Jan 1 14:02 nut.conf
-rw-r--r-- 1 root root 3798 Jan 3 19:35 ups.conf
-rw-r- 1 root nut 1778 Jan 1 14:37 upsd.conf
-rw-r- 1 root nut 2104 Jan 3 15:47 upsd.users
-rw-r- 1 root nut 11988 Jan 3 15:48 upsmon.conf
-rw-r--r-- 1 root root 3883 Jan 1 14:02 upssched.conf
Is there some other driver, or anything else I could use to get it going?
--
Regards,
Mick
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Can't get iDowell to work
On Monday 03 January 2011 20:40:17 Arjen de Korte wrote: Citeren Kjell Claesson kjell.claes...@epost.tidanet.se: 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 combination from the udev rule you created). Make sure to run this as root, so that we have a chance of capturing the report descriptor of this device. Best regards, Arjen Here you go guys: # lsusb -v -d 075d:0300 Bus 003 Device 011: ID 075d:0300 Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x075d idProduct 0x0300 bcdDevice0.01 iManufacturer 3 iDowell iProduct1 iBox iSerial 2 0001 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 41 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x60 (Missing must-be-set bit!) Self Powered Remote Wakeup MaxPower 10mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 0 No Subclass bInterfaceProtocol 0 None iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType33 bcdHID 1.10 bCountryCode 33 US bNumDescriptors 1 bDescriptorType34 Report wDescriptorLength 412 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 20 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0002 1x 2 bytes bInterval 20 Device Status: 0x0001 Self Powered The device gets picked up by the MSWindows default UPS management facility and from what I was told by the guy who sold it to me it is also read by the default AppleMac power manager (no idea what drivers AppleMacs use for USB connected UPS). -- Regards, Mick ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Can't get iDowell to work
OK On Monday 03 January 2011 20:40:17 Arjen de Korte wrote: Citeren Kjell Claesson kjell.claes...@epost.tidanet.se: 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 combination from the udev rule you created). Make sure to run this as root, so that we have a chance of capturing the report descriptor of this device. Best regards, Arjen Thanks Arjen :-) Here you go guys: # lsusb -v -d 075d:0300 The device class is not HID, but you can try this. Do a ups.conf like this. [iDowell] driver = usbhid-ups port = auto vendorid = 075d productid = 0300 desc = iBox by iDowell Now run it like this: /lib/nut/usbhisd-ups -DD -a iDowell -u root Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Can't get iDowell to work
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 kjell.claes...@epost.tidanet.se: 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 combination from the udev rule you created). Make sure to run this as root, so that we have a chance of capturing the report descriptor of this device. Best regards, Arjen Thanks Arjen :-) Here you go guys: # lsusb -v -d 075d:0300 The device class is not HID, but you can try this. Do a ups.conf like this. [iDowell] driver = usbhid-ups port = auto vendorid = 075d productid = 0300 desc = iBox by iDowell Now run it like this: /lib/nut/usbhisd-ups -DD -a iDowell -u root # /lib/nut/usbhid-ups -DD -a iDowell -u root Network UPS Tools - Generic HID driver 0.34 (2.4.3) USB communication driver 0.31 0.00 debug level is '2' 0.000637 upsdrv_initups... 0.001109 Checking device (046D/C069) (002/002) [snip ...] 0.038754 Checking device (075D/0300) (003/026) 0.073483 - VendorID: 075d 0.073496 - ProductID: 0300 0.073505 - Manufacturer: iDowell 0.073511 - Product: iBox 0.073518 - Serial Number: 0001 0.073526 - Bus: 003 0.073534 Trying to match device 0.073543 Device does not match - skipping [snip ...] 0.073737 No appropriate HID device found 0.073749 No matching HID UPS found Same result whether I run it with port auto or port /dev/iDowell. -- Regards, Mick ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
