<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">On Nov 1, 2014, at 1:30 AM, jani wrote:<br><div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr">Hi Charles,<div><br></div><div>I just bought a UPS that announces itself as <span style="white-space: pre-wrap;">'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: </span></div><div><a href="http://eastups.com/en/productshow.aspx?CateId=473&Id=164&PCateId=447">http://eastups.com/en/productshow.aspx?CateId=473&Id=164&PCateId=447</a></div><div><br></div><div>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.</div><div><br></div><div>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:</div><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; position: static; z-index: auto;"><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; position: static; z-index: auto;">Nov 1 16:28:49 microserver nutdrv_atcl_usb[2242]: Warning: excessive comm failures, limiting error reporting</blockquote><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; position: static; z-index: auto;">Nov 1 16:28:49 microserver nutdrv_atcl_usb[2242]: Communications with UPS lost: Query to UPS failed</blockquote><div><br></div></blockquote><div>Is there anything I can do to help troubleshoot the issue?</div></div></blockquote><br></div><div>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 <i>name</i> -DD 2>&1 | tee nutdrv_atcl_usb.log</div><div><br></div><div>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.</div><br></body></html>