On Nov 1, 2014, at 1:30 AM, jani wrote:> Hi Charles, > > I just bought a UPS that announces itself as 'ATCL FOR UPS' with VendorId of 0001. It seems to be a re-badged unit manufactured by Guangdong East Power company, and besides the little brand stamp it looks identical to: > http://eastups.com/en/productshow.aspx?CateId=473&Id=164&PCateId=447 > > It came with a windows cd containing the windows software entitled UPSmart2000I version 3.7 and while I haven't installed it the screenshots show that you can get input and output voltage and battery voltage information out of the thing. > > The problem is the nutdrv_atcl_usb driver out of nut 2.7.2 doesn't seem to function, I get the following in my logs: > Nov 1 16:28:49 microserver nutdrv_atcl_usb[2242]: Warning: excessive comm failures, limiting error reporting > Nov 1 16:28:49 microserver nutdrv_atcl_usb[2242]: Communications with UPS lost: Query to UPS failed > > Is there anything I can do to help troubleshoot the issue?Please run (as root) 'killall nutdrv_atcl_usb' and re-run the driver with the debug level set to at least 2: /path/to/nutdrv_atcl_usb -a name -DD 2>&1 | tee nutdrv_atcl_usb.log Then, please gzip and send the log as an attachment (to keep the size down, and to prevent the lines from getting mangled). Also, the output of 'lsusb -vvv -d 0001:0000' (run as root) would be useful for comparison. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20141101/8d5175f7/attachment.html>
Hi Charles, Here is the output of those. I also ran the driver a second time with debug level 4, just in case there were any extra hints in there. cheers, Jani On 1 November 2014 22:12, Charles Lepple <clepple at gmail.com> wrote:> On Nov 1, 2014, at 1:30 AM, jani wrote: > > Hi Charles, > > I just bought a UPS that announces itself as 'ATCL FOR UPS' with VendorId > of 0001. It seems to be a re-badged unit manufactured by Guangdong East > Power company, and besides the little brand stamp it looks identical to: > http://eastups.com/en/productshow.aspx?CateId=473&Id=164&PCateId=447 > > It came with a windows cd containing the windows software entitled > UPSmart2000I version 3.7 and while I haven't installed it the screenshots > show that you can get input and output voltage and battery voltage > information out of the thing. > > The problem is the nutdrv_atcl_usb driver out of nut 2.7.2 doesn't seem to > function, I get the following in my logs: > >> Nov 1 16:28:49 microserver nutdrv_atcl_usb[2242]: Warning: excessive >>> comm failures, limiting error reporting >> >> Nov 1 16:28:49 microserver nutdrv_atcl_usb[2242]: Communications with >>> UPS lost: Query to UPS failed >> >> >> Is there anything I can do to help troubleshoot the issue? > > > Please run (as root) 'killall nutdrv_atcl_usb' and re-run the driver with > the debug level set to at least 2: /path/to/nutdrv_atcl_usb -a *name* -DD > 2>&1 | tee nutdrv_atcl_usb.log > > Then, please gzip and send the log as an attachment (to keep the size > down, and to prevent the lines from getting mangled). Also, the output of > 'lsusb -vvv -d 0001:0000' (run as root) would be useful for comparison. > >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20141101/a9a800c4/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: atcl_usb_logs.tar.gz Type: application/x-gzip Size: 2169 bytes Desc: not available URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20141101/a9a800c4/attachment.bin>
On Nov 1, 2014, at 8:09 AM, jani <jani.talikka at gmail.com> wrote:> Hi Charles, > > Here is the output of those. I also ran the driver a second time with debug level 4, just in case there were any extra hints in there.Here's the culprit: 5.338858 status interrupt read: error sending control message: Operation not permitted What does 'ls -l /dev/bus/usb/005/002' say? If the UPS has been unplugged since the logs were generated, replace "005/002" with the path suffix from this set of messages: 5.499162 Checking USB device [0001:0000] (005/002) 5.510156 - VendorID : 0001 5.510202 - ProductID : 0000 5.510209 - Manufacturer : ATCL FOR UPS 5.510219 - Product : ATCL FOR UPS 5.510225 - Serial Number: ATCL FOR UPS 5.510231 - Bus : 005 5.510237 Matched expected vendor='ATCL FOR UPS'. 5.512216 USB device [0001:0000] opened Depending on your distribution and how you installed NUT, some extra steps may be necessary to fix the permissions every time the UPS is plugged in. (NUT ships with a udev rules file.) We need to fix the logging levels - the permissions message should have been logged at a higher priority.> _______________________________________________ > Nut-upsuser mailing list > Nut-upsuser at lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser-- Charles Lepple clepple at gmail -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20141101/57e360af/attachment.html>