Re: [Nut-upsuser] APC SmartUPS 3000VA LCD not connecting
On 02/07/2012 10:58 AM, Zach La Celle wrote: On 02/07/2012 10:41 AM, Arnaud Quette wrote: that's what I was suspecting. I've never seen that one before, though! a driver debug output, Ie: $ /lib/nut/usbhid-ups -D -a rack1ups please, compress the result or sent in a reference to the file. I would also be interested in a 2nd run, calling export USB_DEBUG=3, before starting usbhid-ups. we should get some visibility from libusb. cheers, Arnaud I've put up two files: one without USB_DEBUG=3, and one with USB_DEBUG=3. Without: http://db.tt/55mUqzJA With: http://db.tt/Rcf2Phv6 I hope this helps! -Zach ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser I'm back in the office, and can collect more information for you if it will help. Is there anything else you need? -Zach ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] APC SmartUPS 3000VA LCD not connecting
2012/2/13 Zach La Celle lace...@roboticresearch.com: On 02/07/2012 10:58 AM, Zach La Celle wrote: On 02/07/2012 10:41 AM, Arnaud Quette wrote: that's what I was suspecting. I've never seen that one before, though! a driver debug output, Ie: $ /lib/nut/usbhid-ups -D -a rack1ups please, compress the result or sent in a reference to the file. I would also be interested in a 2nd run, calling export USB_DEBUG=3, before starting usbhid-ups. we should get some visibility from libusb. cheers, Arnaud I've put up two files: one without USB_DEBUG=3, and one with USB_DEBUG=3. Without: http://db.tt/55mUqzJA With: http://db.tt/Rcf2Phv6 I hope this helps! -Zach ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser I'm back in the office, and can collect more information for you if it will help. Is there anything else you need? quite frankly, I still have no clue on what could be happening. have you tried on another USB port? is there anything else cabled on the same USB bus? would you be able to test this device on another system, with different OS? 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/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Support for Online Yunto and Zinto
2012/2/4 Mario Giammarco mgiamma...@gmail.com: 2012/2/2 Arnaud Quette aquette@gmail.com: 2012/2/1 Mario Giammarco mgiamma...@gmail.com: Here we go! This one for 06da:0601: ... ok, so that one seems almost good. can you please send also upsc / upscmd / upsrw output? upsc: upsc mieionline Error: Driver not connected upsd: upsd 2.6.1 listening on 127.0.0.1 port 3493 listening on ::1 port 3493 Can't connect to UPS [mieionline] (blazer_usb-mieionline): No such file or directory you've probably stopped the driver. so start both upsd and the driver to get data. ... 0.478318 Ratings read in 1 tries 0.480405 send: I 0.622185 read: I this command seems not supported by your unit. not sure if there is a more suitable subdriver, but you may want to test with other available ones (check the manpage or blazer_usb -h for a list) I have tried other subdrivers and it seems to me that they give more error than ippon. Is I command so important? it's not that the I command is important, but more than it's showing us that you're on the wrong protocol. as per your previous debug output with the 06DA/0601, you should set protocol=zinto in your ups.conf entry. then start upsd and the driver in debug mode, and send back the driver output and an upsc output too. for the 2nd, as per its USB IDs (06DA/0002), the driver should be bcmxcp_usb. can you please try it in debug more and also send back the output? 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/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Support for Online Yunto and Zinto
schrieb Arnaud Quette, Am 13.02.2012 18:28: for the 2nd, as per its USB IDs (06DA/0002), the driver should be bcmxcp_usb. can you please try it in debug more and also send back the output? A few minutes ago I managed to connect to a Yunto YQ450 using USB connection. [YQ450] driver = blazer_usb subdriver = phoenix vendorid = 06da productid = 0002 port = auto desc = Yunto YQ450 via USB I'm not shure if everything (all available parameters/values) is ok. Debug output: /lib/nut/blazer_usb -a YQ450 -D Network UPS Tools - Megatec/Q1 protocol USB driver 0.04 (2.6.3) 0.00 debug level is '5' 0.078276 Checking device (1D6B/0001) (004/001) [..] 0.078745 Checking device (06DA/0002) (002/003) 0.098362 - VendorID: 06da 0.098474 - ProductID: 0002 0.098566 - Manufacturer: ONLINE 0.098617 - Product: YUNTO 0.098657 - Serial Number: unknown 0.098698 - Bus: 002 0.098737 Trying to match device 0.098903 Device matches 0.099009 failed to claim USB device: could not claim interface 0: Device or resource busy 0.137797 detached kernel driver from USB device... 0.142334 send_to_all: SETINFO ups.vendorid 06da 0.142391 send_to_all: SETINFO ups.productid 0002 0.142420 send_to_all: SETINFO device.type ups 0.142442 send_to_all: SETINFO driver.version 2.6.3 0.142462 send_to_all: SETINFO driver.version.internal 0.04 0.142483 send_to_all: SETINFO driver.name blazer_usb 0.142502 Trying megatec protocol... 1.145357 flush: could not claim interface 0: Device or resource busy 1.149216 send: Q1 1.527180 read: (228.0 002.0 228.0 000 49.9 13.7 25.0 00101000 1.527358 send_to_all: SETINFO input.voltage 228.0 1.527431 send_to_all: SETINFO input.voltage.fault 2.0 1.527502 send_to_all: SETINFO output.voltage 228.0 1.527552 send_to_all: SETINFO ups.load 0 1.527583 send_to_all: SETINFO input.frequency 49.9 1.527610 send_to_all: SETINFO battery.voltage 13.70 1.527634 send_to_all: SETINFO ups.temperature 25.0 1.527660 send_to_all: SETINFO beeper.status disabled 1.527682 send_to_all: SETINFO ups.type offline / line interactive 1.527711 send_to_all: SETINFO ups.status OL BYPASS 1.527729 Status read in 1 tries 1.527746 Supported UPS detected with megatec protocol 2.530350 flush: could not claim interface 0: Device or resource busy 2.534335 send: F 3.537357 read: could not claim interface 0: Device or resource busy 3.537475 blazer_rating: short reply 3.537572 Rating read 1 failed 4.540354 flush: could not claim interface 0: Device or resource busy 4.544349 send: F 5.546183 read: could not claim interface 0: Device or resource busy 5.546266 blazer_rating: short reply 5.546309 Rating read 2 failed 6.549183 flush: could not claim interface 0: Device or resource busy 6.553248 send: F 7.555355 read: could not claim interface 0: Device or resource busy 7.555471 blazer_rating: short reply 7.69 Rating read 3 failed 7.555614 Rating information unavailable 8.557177 flush: could not claim interface 0: Device or resource busy 8.561245 send: I 9.563177 read: could not claim interface 0: Device or resource busy 9.563262 blazer_vendor: short reply 9.563307 Vendor information read 1 failed 10.566164 flush: could not claim interface 0: Device or resource busy 10.570338 send: I 11.572352 read: could not claim interface 0: Device or resource busy 11.572477 blazer_vendor: short reply 11.572572 Vendor information read 2 failed 12.574358 flush: could not claim interface 0: Device or resource busy 12.578335 send: I 13.581180 read: could not claim interface 0: Device or resource busy 13.581267 blazer_vendor: short reply 13.581314 Vendor information read 3 failed 13.581354 Vendor information unavailable 13.581395 Battery runtime will not be calculated (runtimecal not set) 13.581445 send_to_all: SETINFO ups.delay.start 180 13.581468 send_to_all: SETINFO ups.delay.shutdown 30 13.581488 send_to_all: ADDCMD beeper.toggle 13.581507 send_to_all: ADDCMD load.off 13.581525 send_to_all: ADDCMD load.on 13.581543 send_to_all: ADDCMD shutdown.return 13.581562 send_to_all: ADDCMD shutdown.stayoff 13.581581 send_to_all: ADDCMD shutdown.stop 13.581599 send_to_all: ADDCMD test.battery.start 13.581618 send_to_all: ADDCMD test.battery.start.deep 13.581637 send_to_all: ADDCMD test.battery.start.quick 13.581657 send_to_all: ADDCMD test.battery.stop 14.583159 flush: could not claim interface 0: Device or resource busy
Re: [Nut-upsuser] Support for Online Yunto and Zinto
Hi Thomas, 2012/2/13 Thomas Maisl exp-122...@maisl.com: schrieb Arnaud Quette, Am 13.02.2012 18:28: for the 2nd, as per its USB IDs (06DA/0002), the driver should be bcmxcp_usb. can you please try it in debug more and also send back the output? A few minutes ago I managed to connect to a Yunto YQ450 using USB connection. thanks a lot for your feedback. could you please also send in an lsusb -v -d06dA:0002 output, using root. [YQ450] driver = blazer_usb subdriver = phoenix vendorid = 06da productid = 0002 port = auto desc = Yunto YQ450 via USB can you also try adding protocol=zinto here, to see if it makes things better? have you also tried other subdrivers (cypress, ippon, krauler) before succeeding with phoenix? Theoretically, I'm not shure if everything (all available parameters/values) is ok. Debug output: /lib/nut/blazer_usb -a YQ450 -D Network UPS Tools - Megatec/Q1 protocol USB driver 0.04 (2.6.3) 0.00 debug level is '5' 0.078276 Checking device (1D6B/0001) (004/001) [..] 0.078745 Checking device (06DA/0002) (002/003) 0.098362 - VendorID: 06da 0.098474 - ProductID: 0002 0.098566 - Manufacturer: ONLINE 0.098617 - Product: YUNTO 0.098657 - Serial Number: unknown 0.098698 - Bus: 002 0.098737 Trying to match device 0.098903 Device matches 0.099009 failed to claim USB device: could not claim interface 0: Device or resource busy 0.137797 detached kernel driver from USB device... 0.142334 send_to_all: SETINFO ups.vendorid 06da 0.142391 send_to_all: SETINFO ups.productid 0002 0.142420 send_to_all: SETINFO device.type ups 0.142442 send_to_all: SETINFO driver.version 2.6.3 0.142462 send_to_all: SETINFO driver.version.internal 0.04 0.142483 send_to_all: SETINFO driver.name blazer_usb 0.142502 Trying megatec protocol... 1.145357 flush: could not claim interface 0: Device or resource busy 1.149216 send: Q1 1.527180 read: (228.0 002.0 228.0 000 49.9 13.7 25.0 00101000 1.527358 send_to_all: SETINFO input.voltage 228.0 1.527431 send_to_all: SETINFO input.voltage.fault 2.0 1.527502 send_to_all: SETINFO output.voltage 228.0 1.527552 send_to_all: SETINFO ups.load 0 1.527583 send_to_all: SETINFO input.frequency 49.9 1.527610 send_to_all: SETINFO battery.voltage 13.70 1.527634 send_to_all: SETINFO ups.temperature 25.0 1.527660 send_to_all: SETINFO beeper.status disabled 1.527682 send_to_all: SETINFO ups.type offline / line interactive 1.527711 send_to_all: SETINFO ups.status OL BYPASS 1.527729 Status read in 1 tries 1.527746 Supported UPS detected with megatec protocol 2.530350 flush: could not claim interface 0: Device or resource busy 2.534335 send: F 3.537357 read: could not claim interface 0: Device or resource busy 3.537475 blazer_rating: short reply 3.537572 Rating read 1 failed 4.540354 flush: could not claim interface 0: Device or resource busy 4.544349 send: F 5.546183 read: could not claim interface 0: Device or resource busy 5.546266 blazer_rating: short reply 5.546309 Rating read 2 failed 6.549183 flush: could not claim interface 0: Device or resource busy 6.553248 send: F 7.555355 read: could not claim interface 0: Device or resource busy 7.555471 blazer_rating: short reply 7.69 Rating read 3 failed 7.555614 Rating information unavailable 8.557177 flush: could not claim interface 0: Device or resource busy 8.561245 send: I 9.563177 read: could not claim interface 0: Device or resource busy 9.563262 blazer_vendor: short reply 9.563307 Vendor information read 1 failed 10.566164 flush: could not claim interface 0: Device or resource busy 10.570338 send: I 11.572352 read: could not claim interface 0: Device or resource busy 11.572477 blazer_vendor: short reply 11.572572 Vendor information read 2 failed 12.574358 flush: could not claim interface 0: Device or resource busy 12.578335 send: I 13.581180 read: could not claim interface 0: Device or resource busy 13.581267 blazer_vendor: short reply 13.581314 Vendor information read 3 failed 13.581354 Vendor information unavailable 13.581395 Battery runtime will not be calculated (runtimecal not set) 13.581445 send_to_all: SETINFO ups.delay.start 180 13.581468 send_to_all: SETINFO ups.delay.shutdown 30 13.581488 send_to_all: ADDCMD beeper.toggle 13.581507 send_to_all: ADDCMD load.off 13.581525 send_to_all: ADDCMD load.on 13.581543 send_to_all: ADDCMD shutdown.return 13.581562 send_to_all: ADDCMD shutdown.stayoff
