Re: [Nut-upsuser] Support for Online Yunto and Zinto
Hi Mario, first, please keep the traffic on the list. 2012/2/28 Mario Giammarco mgiamma...@gmail.com: Here it is: [mieionline] driver = blazer_usb protocol = zinto port = auto desc = yunto q700 # subdriver = zinto vendorid = 06da productid = 0601 But please note that I have done: man blazer_usb and I see no protocol option. I am using the ubuntu 11.10 version 2.6.1-2ubuntu2 everything is fine in your ups.conf, and with your setup. I've even tested it with the same setup (ubuntu and nut 2.6.1-2ubuntu2): $ sudo upsdrvctl start blazer Network UPS Tools - UPS driver controller 2.6.2 Network UPS Tools - Megatec/Q1 protocol USB driver 0.03 (2.6.2) Duplicate driver instance detected! Terminating other driver! Supported UPS detected with zinto protocol Vendor information unavailable Battery runtime will not be calculated (runtimecal not set) so it's either an old version that was still running, or another obscure error. can you please try again, ensuring that you're using the right binaries? 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/ 2012/2/28 Arnaud Quette aquette@gmail.com: 2012/2/27 Mario Giammarco mgiamma...@gmail.com: I am not able to do the test When I put protocol=zinto I get: Fatal error: 'protocol' is not a valid variable name for this driver. I have also tried subdriver=zinto without luck could you please send back your ups.conf. cheers, Arno ___ 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/27 Mario Giammarco mgiamma...@gmail.com: I am not able to do the test When I put protocol=zinto I get: Fatal error: 'protocol' is not a valid variable name for this driver. I have also tried subdriver=zinto without luck could you please send back your ups.conf. cheers, Arno ___ 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/27 Thomas Maisl exp-122...@maisl.com: Hello, schrieb Arnaud Quette, Am 16.02.2012 18:48: Can you please counter check, and report back upsc/upsrw/upscmd upsc: # upsc YQ450 battery.voltage: 13.40 beeper.status: disabled device.type: ups driver.name: blazer_usb driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.parameter.productid: 0002 driver.parameter.protocol: zinto driver.parameter.subdriver: cypress driver.parameter.vendorid: 06da driver.version: 2.6.3 driver.version.internal: 0.04 input.frequency: 50.0 input.voltage: 232.0 input.voltage.fault: 1.0 this seems not normal! output.voltage: 232.0 ups.delay.shutdown: 30 ups.delay.start: 180 ups.load: 0 ups.productid: 0002 ups.status: OL BYPASS ups.temperature: 25.0 ups.type: offline / line interactive ups.vendorid: 06da # upsrw -u xxx -p xxx -s ups.delay.start YQ450 Enter new value for ups.delay.start: 90 Unexpected response from upsd: ERR ACCESS-DENIED # upsrw -u xxx -p xxx -s ups.delay.shutdown YQ450 Enter new value for ups.delay.shutdown: 90 Unexpected response from upsd: ERR ACCESS-DENIED # upscmd -u xxx -p xxx YQ450 shutdown.return 1 Unexpected response from upsd: ERR ACCESS-DENIED the user and password used for upsrw and upscmd are the ones defined in upsd.users. here, upsd is telling us that you've used wrong ones (generally system ones, such as root...). output, along with the shutdown test: http://www.networkupstools.org/docs/user-manual.chunked/ar01s06.html#Shutdown_design while doing shutdown # upslog -s yq450 -i 2 -l - Network UPS Tools upslog 2.6.3 logging status of yq450 to - (2s intervals) 20120227 091805 NA 0.0 0 [OB] 25.0 0.0 20120227 091807 NA 0.0 0 [OB] 25.0 0.0 20120227 091809 NA 0.0 0 [OB] 25.0 0.0 20120227 091811 NA 0.0 0 [OB] 25.0 0.0 20120227 091957 NA NA NA [FSD WAIT] NA 0.0 20120227 091959 NA 0.0 0 [FSD OB] 25.0 0.0 20120227 092001 NA 0.0 0 [FSD OB LB] 25.0 0.0 20120227 092003 NA 0.0 0 [FSD OB LB] 25.0 0.0 so, no battery voltage is displayed battery.voltage is not part of the default upslog string: %TIME @Y@m@d @H@M@S% %VAR battery.charge% %VAR input.voltage% %VAR ups.load% [%VAR ups.status%] %VAR ups.temperature% %VAR input.frequency% the above shows that OB+LB has triggered FSD. so upsmon.conf-SHUTDOWNCMD has been executed. parallel /lib/nut/blazer_usb -a YQ450 -D 23.832061 read: (000.0 001.0 230.0 000 00.0 12.5 25.0 10001000 25.472224 send: Q1 25.816057 read: (000.0 001.0 230.0 000 00.0 12.5 25.0 11001000 25.816249 send_to_all: SETINFO ups.status OB LB 27.473243 send: Q1 27.832053 read: (000.0 001.0 230.0 000 00.0 12.5 25.0 11001000 29.476227 send: Q1 29.848055 read: (000.0 001.0 230.0 000 00.0 12.5 25.0 11001000 31.478227 send: Q1 31.832056 read: (000.0 001.0 230.0 000 00.0 12.5 25.0 11001000 32.070549 send_to_one: PONG Temperature is always 25.0°C When cutting off power to the UPS, power to the outlets isn't switched off despite the low battery warning (at least 15 minutes after cutting power) Do I have a faulty UPS?2 it depends on what you mean with cutting off power to the UPS... if you refer to upscmd -u xxx -p xxx YQ450 shutdown.return, it has failed. if you mean following the above FSD, it's indeed not normal. I would need the driver output when going FSD (or using upscmd... shutdown.return) remember to not power your PC with the UPS while testing this! note that you may also contact the manufacturer support to get some help on their possible variation of the protocol. cheers, Arno ___ 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
Hello, schrieb Arnaud Quette, Am 16.02.2012 18:48: Can you please counter check, and report back upsc/upsrw/upscmd upsc: # upsc YQ450 battery.voltage: 13.40 beeper.status: disabled device.type: ups driver.name: blazer_usb driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.parameter.productid: 0002 driver.parameter.protocol: zinto driver.parameter.subdriver: cypress driver.parameter.vendorid: 06da driver.version: 2.6.3 driver.version.internal: 0.04 input.frequency: 50.0 input.voltage: 232.0 input.voltage.fault: 1.0 output.voltage: 232.0 ups.delay.shutdown: 30 ups.delay.start: 180 ups.load: 0 ups.productid: 0002 ups.status: OL BYPASS ups.temperature: 25.0 ups.type: offline / line interactive ups.vendorid: 06da # upsrw -u xxx -p xxx -s ups.delay.start YQ450 Enter new value for ups.delay.start: 90 Unexpected response from upsd: ERR ACCESS-DENIED # upsrw -u xxx -p xxx -s ups.delay.shutdown YQ450 Enter new value for ups.delay.shutdown: 90 Unexpected response from upsd: ERR ACCESS-DENIED # upscmd -u xxx -p xxx YQ450 shutdown.return 1 Unexpected response from upsd: ERR ACCESS-DENIED output, along with the shutdown test: http://www.networkupstools.org/docs/user-manual.chunked/ar01s06.html#Shutdown_design while doing shutdown # upslog -s yq450 -i 2 -l - Network UPS Tools upslog 2.6.3 logging status of yq450 to - (2s intervals) 20120227 091805 NA 0.0 0 [OB] 25.0 0.0 20120227 091807 NA 0.0 0 [OB] 25.0 0.0 20120227 091809 NA 0.0 0 [OB] 25.0 0.0 20120227 091811 NA 0.0 0 [OB] 25.0 0.0 20120227 091957 NA NA NA [FSD WAIT] NA 0.0 20120227 091959 NA 0.0 0 [FSD OB] 25.0 0.0 20120227 092001 NA 0.0 0 [FSD OB LB] 25.0 0.0 20120227 092003 NA 0.0 0 [FSD OB LB] 25.0 0.0 so, no battery voltage is displayed parallel /lib/nut/blazer_usb -a YQ450 -D 23.832061 read: (000.0 001.0 230.0 000 00.0 12.5 25.0 10001000 25.472224 send: Q1 25.816057 read: (000.0 001.0 230.0 000 00.0 12.5 25.0 11001000 25.816249 send_to_all: SETINFO ups.status OB LB 27.473243 send: Q1 27.832053 read: (000.0 001.0 230.0 000 00.0 12.5 25.0 11001000 29.476227 send: Q1 29.848055 read: (000.0 001.0 230.0 000 00.0 12.5 25.0 11001000 31.478227 send: Q1 31.832056 read: (000.0 001.0 230.0 000 00.0 12.5 25.0 11001000 32.070549 send_to_one: PONG Temperature is always 25.0°C When cutting off power to the UPS, power to the outlets isn't switched off despite the low battery warning (at least 15 minutes after cutting power) Do I have a faulty UPS?2 Thomas ___ 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
I am not able to do the test When I put protocol=zinto I get: Fatal error: 'protocol' is not a valid variable name for this driver. I have also tried subdriver=zinto without luck 2012/2/21 Arnaud Quette aquette@gmail.com: 2012/2/16 Mario Giammarco mgiamma...@gmail.com: Tomorrow I will do the test! Marco, Thomas, before I switched to something else, I'd like to complete this case. have you been able to do some testing on your side? 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/16 Mario Giammarco mgiamma...@gmail.com: Tomorrow I will do the test! Marco, Thomas, before I switched to something else, I'd like to complete this case. have you been able to do some testing on your side? 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
Halo Thomas und Mario ;-) 2012/2/14 Thomas Maisl exp-122...@maisl.com: attached information was retrieved while UPS was operating _offline_ (doing a runtime test) thanks a lot for your test results. 1. lsusb -v -d06dA:0002 2-6. blazer_usb using subdriver cypress|phoenix|ippon|krauler with and w/o protocol zinto IMO cypress with zinto produced the best result, ippon and krauler didn't work indeed cypress with zinto is the best fit, though your unit doesn't answer to anything else than the basic 'Q1' phoenix also provides the same support. [YQ450] driver = blazer_usb subdriver = cypress protocol = zinto vendorid = 06da productid = 0002 port = auto desc = Yunto YQ450 via USB I've just committed a patch to the trunk (r3447) which links 06da:0002 to the cypress subdriver, and added the following HCL entry: Onlineups 2 Yunto YQ450 blazer_usb This means that you now (using the latest trunk) just need to specify: [YQ450] driver = blazer_usb protocol = zinto port = auto desc = Yunto YQ450 via USB Moreover, specifying zinto is not that useful, since only Q1 is supported. So you can omit it. Can you please counter check, and report back upsc/upsrw/upscmd output, along with the shutdown test: http://www.networkupstools.org/docs/user-manual.chunked/ar01s06.html#Shutdown_design the remaining point is still with the other unit (06da:0601) from Mario... @Mario: as per your previous feedback, your unit reports 'Q1', 'F', but not 'I'. so could you please do the same tests I asked Thomas, with protocol=zinto? this should use 'FW?' and provide vendor info. cheers, Arnaud ___ 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
Tomorrow I will do the test! 2012/2/16 Arnaud Quette aquette@gmail.com: Halo Thomas und Mario ;-) 2012/2/14 Thomas Maisl exp-122...@maisl.com: attached information was retrieved while UPS was operating _offline_ (doing a runtime test) thanks a lot for your test results. 1. lsusb -v -d06dA:0002 2-6. blazer_usb using subdriver cypress|phoenix|ippon|krauler with and w/o protocol zinto IMO cypress with zinto produced the best result, ippon and krauler didn't work indeed cypress with zinto is the best fit, though your unit doesn't answer to anything else than the basic 'Q1' phoenix also provides the same support. [YQ450] driver = blazer_usb subdriver = cypress protocol = zinto vendorid = 06da productid = 0002 port = auto desc = Yunto YQ450 via USB I've just committed a patch to the trunk (r3447) which links 06da:0002 to the cypress subdriver, and added the following HCL entry: Online ups 2 Yunto YQ450 blazer_usb This means that you now (using the latest trunk) just need to specify: [YQ450] driver = blazer_usb protocol = zinto port = auto desc = Yunto YQ450 via USB Moreover, specifying zinto is not that useful, since only Q1 is supported. So you can omit it. Can you please counter check, and report back upsc/upsrw/upscmd output, along with the shutdown test: http://www.networkupstools.org/docs/user-manual.chunked/ar01s06.html#Shutdown_design the remaining point is still with the other unit (06da:0601) from Mario... @Mario: as per your previous feedback, your unit reports 'Q1', 'F', but not 'I'. so could you please do the same tests I asked Thomas, with protocol=zinto? this should use 'FW?' and provide vendor info. cheers, Arnaud ___ 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
attached information was retrieved while UPS was operating _offline_ (doing a runtime test) 1. lsusb -v -d06dA:0002 2-6. blazer_usb using subdriver cypress|phoenix|ippon|krauler with and w/o protocol zinto IMO cypress with zinto produced the best result, ippon and krauler didn't work [YQ450] driver = blazer_usb subdriver = cypress protocol = zinto vendorid = 06da productid = 0002 port = auto desc = Yunto YQ450 via USB schrieb Arnaud Quette, Am 13.02.2012 19:58: 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. seems to be identical with Marios UPS [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? no, not before. I did try bcmxcp_usb w/o success, did some reading and realised that there had been some support in the megatec-driver which blazer is the successor. In blazer_usbs' manpage phoenix is a subdriver option - and lsusb pointed to Phoenixtec. So I gave this subdriver a shot. 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) [..] [..] Q1 is answering, which is the basic for this protocol. but not to F and I. but the numerous flush: could not claim interface 0: Device or resource busy msg lead me to think that there is probably another instance of the driver running. could you please confirm (using ps for example)? and if it's the case, stop all driver instances, start only 1 in debug mode (as you did above) and send again a debug output. no, no other instance was running. Behaviour is reproducible (see attachment). While testing I did detach and reattach the USB-cable. The connection to the UPS was established again. :) HTH, Thomas Online-Yunto_YQ450.txt.gz Description: GNU Zip compressed data ___ 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
Re: [Nut-upsuser] Support for Online Yunto and Zinto
What can I do next? Thanks, Mario ___ 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/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 ... 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? Thanks again, Mario ___ 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
Bus 002 Device 004: ID 06da:0002 Phoenixtec Power Co., Ltd UPS Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x06da Phoenixtec Power Co., Ltd idProduct 0x0002 UPS bcdDevice0.02 iManufacturer 1 ONLINE iProduct2 YUNTO iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 34 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 3 bmAttributes 0x80 (Bus Powered) MaxPower 100mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 0 No Subclass bInterfaceProtocol 0 None iInterface 4 Sample HID HID Device Descriptor: bLength 9 bDescriptorType33 bcdHID 1.00 bCountryCode0 Not supported bNumDescriptors 1 bDescriptorType34 Report wDescriptorLength 31 Report Descriptor: (length is 31) Item(Global): Usage Page, data= [ 0x01 ] 1 Generic Desktop Controls Item(Local ): Usage, data= [ 0x05 ] 5 Gamepad Item(Main ): Collection, data= [ 0x01 ] 1 Application Item(Local ): Usage, data= [ 0x06 ] 6 Keyboard Item(Local ): Usage Minimum, data= [ 0x01 ] 1 Pointer Item(Local ): Usage Maximum, data= [ 0xf0 ] 240 (null) Item(Global): Logical Minimum, data= [ 0x00 ] 0 Item(Global): Logical Maximum, data= [ 0x01 ] 1 Item(Global): Report Size, data= [ 0x08 ] 8 Item(Global): Report Count, data= [ 0x08 ] 8 Item(Main ): Input, data= [ 0x02 ] 2 Data Variable Absolute No_Wrap Linear Preferred_State No_Null_Position Non_Volatile Bitfield Item(Local ): Usage, data= [ 0x07 ] 7 Keypad Item(Global): Report Size, data= [ 0x08 ] 8 Item(Global): Report Count, data= [ 0x10 ] 16 Item(Main ): Output, data= [ 0x02 ] 2 Data Variable Absolute No_Wrap Linear Preferred_State No_Null_Position Non_Volatile Bitfield Item(Main ): End Collection, data=none 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 32 Device Status: 0x (Bus Powered) 2012/2/2 Arnaud Quette aquette@gmail.com: 2012/2/1 Mario Giammarco mgiamma...@gmail.com: And for 06da:0002: ... this one has a problem. could you please send back the following output (as root): $ lsusb -v -d 06da:0002 it may turn out to be a HID device more than a megatec / Q1. as for the other unit, you may also try other subdrivers... 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/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? ... 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) 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/1 Mario Giammarco mgiamma...@gmail.com: And for 06da:0002: ... this one has a problem. could you please send back the following output (as root): $ lsusb -v -d 06da:0002 it may turn out to be a HID device more than a megatec / Q1. as for the other unit, you may also try other subdrivers... 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/1/31 Arnaud Quette aquette@gmail.com: so you should also use sudo, Ie: $ sudo /path/to/blazer_usb -D -a upsname Unfortunately I am already root. I have enabled the root account I am tired to to always use sudo. Even as root the problem persists. ___ 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
I have searched and killed all processes that I think can use usb, so I do not know what is happening 2012/2/1 Mario Giammarco mgiamma...@gmail.com: 2012/1/31 Arnaud Quette aquette@gmail.com: so you should also use sudo, Ie: $ sudo /path/to/blazer_usb -D -a upsname Unfortunately I am already root. I have enabled the root account I am tired to to always use sudo. Even as root the problem persists. ___ 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
Arnaud Quette aquette.dev at gmail.com writes: so you should also use sudo, Ie: $ sudo /path/to/blazer_usb -D -a upsname Unfortunately I am already root, I have enabled the root account. I have also tried to kill processes that may lock usb but with no luck. What can I do? Thanks, Mario ___ 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
Here we go! This one for 06da:0601: 0.00 send_to_all: SETINFO driver.parameter.port auto 0.000117 send_to_all: SETINFO driver.parameter.subdriver ippon 0.000179 send_to_all: SETINFO driver.parameter.vendorid 06da 0.000230 send_to_all: SETINFO driver.parameter.productid 0601 0.000315 debug level is '5' 0.002600 Checking device (1D6B/0003) (009/001) 0.002832 - VendorID: 1d6b 0.002879 - ProductID: 0003 0.002916 - Manufacturer: Linux 3.0.0-16-generic xhci_hcd 0.002955 - Product: xHCI Host Controller 0.002992 - Serial Number: :03:00.0 0.003028 - Bus: 009 0.003063 Trying to match device 0.003118 Device does not match - skipping 0.003165 Checking device (1D6B/0002) (008/001) 0.003245 - VendorID: 1d6b 0.003285 - ProductID: 0002 0.003321 - Manufacturer: Linux 3.0.0-16-generic xhci_hcd 0.003417 - Product: xHCI Host Controller 0.003453 - Serial Number: :03:00.0 0.003489 - Bus: 008 0.003524 Trying to match device 0.003562 Device does not match - skipping 0.003604 Checking device (1D6B/0001) (007/001) 0.003677 - VendorID: 1d6b 0.003716 - ProductID: 0001 0.003751 - Manufacturer: Linux 3.0.0-16-generic ohci_hcd 0.003787 - Product: OHCI Host Controller 0.003823 - Serial Number: :00:16.0 0.003859 - Bus: 007 0.003894 Trying to match device 0.003932 Device does not match - skipping 0.003974 Checking device (1D6B/0001) (006/001) 0.004045 - VendorID: 1d6b 0.004083 - ProductID: 0001 0.004118 - Manufacturer: Linux 3.0.0-16-generic ohci_hcd 0.004154 - Product: OHCI Host Controller 0.004190 - Serial Number: :00:14.5 0.004226 - Bus: 006 0.004260 Trying to match device 0.004299 Device does not match - skipping 0.004340 Checking device (1D6B/0001) (005/001) 0.004410 - VendorID: 1d6b 0.004454 - ProductID: 0001 0.004489 - Manufacturer: Linux 3.0.0-16-generic ohci_hcd 0.004526 - Product: OHCI Host Controller 0.004562 - Serial Number: :00:13.0 0.004834 - Bus: 005 0.004872 Trying to match device 0.004911 Device does not match - skipping 0.004954 Checking device (1D6B/0001) (004/001) 0.005027 - VendorID: 1d6b 0.005065 - ProductID: 0001 0.005101 - Manufacturer: Linux 3.0.0-16-generic ohci_hcd 0.005138 - Product: OHCI Host Controller 0.005174 - Serial Number: :00:12.0 0.005211 - Bus: 004 0.005248 Trying to match device 0.005288 Device does not match - skipping 0.005329 Checking device (1D6B/0002) (003/001) 0.005449 - VendorID: 1d6b 0.005524 - ProductID: 0002 0.005560 - Manufacturer: Linux 3.0.0-16-generic ehci_hcd 0.005597 - Product: EHCI Host Controller 0.005634 - Serial Number: :00:16.2 0.005670 - Bus: 003 0.005705 Trying to match device 0.005744 Device does not match - skipping 0.005787 Checking device (058F/6387) (002/006) 0.008028 - VendorID: 058f 0.008069 - ProductID: 6387 0.008080 - Manufacturer: Generic 0.008092 - Product: Mass Storage 0.008103 - Serial Number: FFB279FA 0.010059 - Bus: 002 0.010090 Trying to match device 0.010168 Device does not match - skipping 0.010201 Checking device (046D/C50E) (002/005) 0.017189 - VendorID: 046d 0.017231 - ProductID: c50e 0.017241 - Manufacturer: Logitech 0.017252 - Product: USB Receiver 0.017262 - Serial Number: unknown 0.017272 - Bus: 002 0.017282 Trying to match device 0.017304 Device does not match - skipping 0.017330 Checking device (06DA/0002) (002/004) 0.020214 - VendorID: 06da 0.020359 - ProductID: 0002 0.020370 - Manufacturer: ONLINE 0.020382 - Product: YUNTO 0.020392 - Serial Number: unknown 0.020402 - Bus: 002 0.020412 Trying to match device 0.020496 Device does not match - skipping 0.020528 Checking device (06DA/0601) (002/003) 0.032763 - VendorID: 06da 0.032814 - ProductID: 0601 0.032825 - Manufacturer: ONLINE 0.032835 - Product: ZINTO 0.032848 - Serial Number: unknown 0.032858 - Bus: 002 0.032868 Trying to match device 0.032939 Device matches 0.033027 failed to claim USB device: could not claim interface 0: Device or resource busy 0.033429 detached kernel driver from USB device... 0.035076 send_to_all: SETINFO ups.vendorid 06da 0.035123 send_to_all: SETINFO ups.productid 0601 0.035153 send_to_all: SETINFO device.type ups 0.035182 send_to_all: SETINFO driver.version 2.6.1 0.035198 send_to_all: SETINFO driver.version.internal 0.03 0.035213 send_to_all: SETINFO driver.name
Re: [Nut-upsuser] Support for Online Yunto and Zinto
And for 06da:0002: 0.00 send_to_all: SETINFO driver.parameter.port auto 0.000198 send_to_all: SETINFO driver.parameter.subdriver ippon 0.000248 send_to_all: SETINFO driver.parameter.vendorid 06da 0.000332 send_to_all: SETINFO driver.parameter.productid 0002 0.000415 debug level is '5' 0.002832 Checking device (1D6B/0003) (009/001) 0.003011 - VendorID: 1d6b 0.003058 - ProductID: 0003 0.003096 - Manufacturer: Linux 3.0.0-16-generic xhci_hcd 0.003134 - Product: xHCI Host Controller 0.003170 - Serial Number: :03:00.0 0.003245 - Bus: 009 0.003322 Trying to match device 0.003373 Device does not match - skipping 0.003419 Checking device (1D6B/0002) (008/001) 0.003495 - VendorID: 1d6b 0.003536 - ProductID: 0002 0.003571 - Manufacturer: Linux 3.0.0-16-generic xhci_hcd 0.003608 - Product: xHCI Host Controller 0.003681 - Serial Number: :03:00.0 0.003718 - Bus: 008 0.003753 Trying to match device 0.003798 Device does not match - skipping 0.003847 Checking device (1D6B/0001) (007/001) 0.003919 - VendorID: 1d6b 0.003967 - ProductID: 0001 0.004014 - Manufacturer: Linux 3.0.0-16-generic ohci_hcd 0.004050 - Product: OHCI Host Controller 0.004085 - Serial Number: :00:16.0 0.004128 - Bus: 007 0.004171 Trying to match device 0.004209 Device does not match - skipping 0.004348 Checking device (1D6B/0001) (006/001) 0.004424 - VendorID: 1d6b 0.004469 - ProductID: 0001 0.004504 - Manufacturer: Linux 3.0.0-16-generic ohci_hcd 0.004550 - Product: OHCI Host Controller 0.004593 - Serial Number: :00:14.5 0.004629 - Bus: 006 0.004671 Trying to match device 0.004719 Device does not match - skipping 0.004761 Checking device (1D6B/0001) (005/001) 0.004831 - VendorID: 1d6b 0.004872 - ProductID: 0001 0.004907 - Manufacturer: Linux 3.0.0-16-generic ohci_hcd 0.004950 - Product: OHCI Host Controller 0.004996 - Serial Number: :00:13.0 0.005032 - Bus: 005 0.005067 Trying to match device 0.005107 Device does not match - skipping 0.005149 Checking device (1D6B/0001) (004/001) 0.005245 - VendorID: 1d6b 0.005292 - ProductID: 0001 0.005328 - Manufacturer: Linux 3.0.0-16-generic ohci_hcd 0.005364 - Product: OHCI Host Controller 0.005404 - Serial Number: :00:12.0 0.005446 - Bus: 004 0.005482 Trying to match device 0.005520 Device does not match - skipping 0.005560 Checking device (1D6B/0002) (003/001) 0.005633 - VendorID: 1d6b 0.005672 - ProductID: 0002 0.005709 - Manufacturer: Linux 3.0.0-16-generic ehci_hcd 0.005755 - Product: EHCI Host Controller 0.005790 - Serial Number: :00:16.2 0.005825 - Bus: 003 0.005870 Trying to match device 0.005908 Device does not match - skipping 0.005949 Checking device (058F/6387) (002/006) 0.008146 - VendorID: 058f 0.008226 - ProductID: 6387 0.008266 - Manufacturer: Generic 0.008310 - Product: Mass Storage 0.008350 - Serial Number: FFB279FA 0.008386 - Bus: 002 0.008421 Trying to match device 0.008510 Device does not match - skipping 0.008562 Checking device (046D/C50E) (002/005) 0.015983 - VendorID: 046d 0.016030 - ProductID: c50e 0.016041 - Manufacturer: Logitech 0.016052 - Product: USB Receiver 0.016062 - Serial Number: unknown 0.016072 - Bus: 002 0.016081 Trying to match device 0.016103 Device does not match - skipping 0.016130 Checking device (06DA/0002) (002/004) 0.019975 - VendorID: 06da 0.020496 - ProductID: 0002 0.020540 - Manufacturer: ONLINE 0.020578 - Product: YUNTO 0.020622 - Serial Number: unknown 0.020659 - Bus: 002 0.020695 Trying to match device 0.020829 Device matches 0.020908 failed to claim USB device: could not claim interface 0: Device or resource busy 0.141642 detached kernel driver from USB device... 0.143605 send_to_all: SETINFO ups.vendorid 06da 0.143653 send_to_all: SETINFO ups.productid 0002 0.143686 send_to_all: SETINFO device.type ups 0.143718 send_to_all: SETINFO driver.version 2.6.1 0.143734 send_to_all: SETINFO driver.version.internal 0.03 0.143748 send_to_all: SETINFO driver.name blazer_usb 0.143761 Trying megatec protocol... 0.144436 send: Q1 1.145382 read: Connection timed out 1.145429 blazer_status: short reply 1.145442 Status read 1 failed 1.146106 send: Q1 2.147258 read: Connection timed out 2.147308 blazer_status: short reply 2.147320 Status read 2 failed 2.147972 send: Q1
Re: [Nut-upsuser] Support for Online Yunto and Zinto
2012/1/31 Charles Lepple clep...@gmail.com: On Jan 30, 2012, at 3:15 PM, Mario wrote: I have a Yunto e a Zanto ups connected with usb with id 06da:0002 and 06da:0601. I have seen that people had some success using megatec driver. But now megatec is replaced by blazer-usb and I am not able to use my upses under nut. Can you help me? Some additional information would be useful: http://www.networkupstools.org/support.html#_request_help seconded. we need more info to be able to help you! side comment: the only USB ID related to 0x06da that is known by blazer_usb is 0x06da:0x0003 this means that you must provide vendorid and productid params to the driver, either by using -x or by mentioning these in ups.conf: [mydev] driver = blazer_usb port = auto vendorid = 06da productid = 0601 subdriver = ippon will probably be needed too. Then send us back the debug output of the driver, ie (as root): $ /path/to/blazer_usb -D -a upsname Let it run for a minute or so, then stop it using Ctrl+C. 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
Arnaud Quette aquette.dev at gmail.com writes: ppon will probably be needed too. Then send us back the debug output of the driver, ie (as root): $ /path/to/blazer_usb -D -a upsname Let it run for a minute or so, then stop it using Ctrl+C. Sorry for missing informations: I have ubuntu oneiric and so nut 2.6.1 installed from standard repository. I give the command above and here is the output but unfortunately it seems to me that there is an error: /lib/nut/blazer_usb -D -a mieionline Network UPS Tools - Megatec/Q1 protocol USB driver 0.03 (2.6.1) 0.00 send_to_all: SETINFO driver.parameter.port auto 0.000126 send_to_all: SETINFO driver.parameter.subdriver ippon 0.000179 send_to_all: SETINFO driver.parameter.vendorid 06da 0.000238 send_to_all: SETINFO driver.parameter.productid 0601 0.000315 debug level is '5' 0.002986 Checking device (1D6B/0003) (009/001) 0.003127 - VendorID: 1d6b 0.003171 - ProductID: 0003 0.003292 - Manufacturer: unknown 0.003330 - Product: unknown 0.003367 - Serial Number: unknown 0.003403 - Bus: 009 0.003440 Trying to match device 0.003528 Device does not match - skipping 0.003577 Checking device (1D6B/0002) (008/001) 0.003643 - VendorID: 1d6b 0.003682 - ProductID: 0002 0.003719 - Manufacturer: unknown 0.003791 - Product: unknown 0.003831 - Serial Number: unknown 0.003867 - Bus: 008 0.003903 Trying to match device 0.003943 Device does not match - skipping 0.004023 Checking device (1D6B/0001) (007/001) 0.004085 - VendorID: 1d6b 0.004125 - ProductID: 0001 0.004193 - Manufacturer: unknown 0.004232 - Product: unknown 0.004268 - Serial Number: unknown 0.004304 - Bus: 007 0.004340 Trying to match device 0.004416 Device does not match - skipping 0.004459 Checking device (1D6B/0001) (006/001) 0.004519 - VendorID: 1d6b 0.004563 - ProductID: 0001 0.004607 - Manufacturer: unknown 0.004643 - Product: unknown 0.004679 - Serial Number: unknown 0.004716 - Bus: 006 0.004754 Trying to match device 0.004793 Device does not match - skipping 0.004834 Checking device (1D6B/0001) (005/001) 0.004898 - VendorID: 1d6b 0.004938 - ProductID: 0001 0.004975 - Manufacturer: unknown 0.005018 - Product: unknown 0.005058 - Serial Number: unknown 0.005094 - Bus: 005 0.005130 Trying to match device 0.005177 Device does not match - skipping 0.005220 Checking device (1D6B/0001) (004/001) 0.005279 - VendorID: 1d6b 0.005372 - ProductID: 0001 0.005388 - Manufacturer: unknown 0.005399 - Product: unknown 0.005409 - Serial Number: unknown 0.005419 - Bus: 004 0.005429 Trying to match device 0.005511 Device does not match - skipping 0.005525 Checking device (1D6B/0002) (003/001) 0.005542 - VendorID: 1d6b 0.005556 - ProductID: 0002 0.005566 - Manufacturer: unknown 0.005576 - Product: unknown 0.005586 - Serial Number: unknown 0.005596 - Bus: 003 0.005605 Trying to match device 0.005616 Device does not match - skipping 0.005627 Checking device (058F/6387) (002/007) 0.005645 - VendorID: 058f 0.005656 - ProductID: 6387 0.005666 - Manufacturer: unknown 0.005676 - Product: unknown 0.005685 - Serial Number: unknown 0.005695 - Bus: 002 0.005705 Trying to match device 0.005726 Device does not match - skipping 0.005739 Checking device (046D/C50E) (002/006) 0.005756 - VendorID: 046d 0.005767 - ProductID: c50e 0.005777 - Manufacturer: unknown 0.005790 - Product: unknown 0.005801 - Serial Number: unknown 0.005814 - Bus: 002 0.005824 Trying to match device 0.005835 Device does not match - skipping 0.005846 Checking device (06DA/0002) (002/004) 0.008788 - VendorID: 06da 0.008835 - ProductID: 0002 0.008846 - Manufacturer: ONLINE 0.008858 - Product: YUNTO 0.008868 - Serial Number: unknown 0.008879 - Bus: 002 0.00 Trying to match device 0.008973 Device does not match - skipping 0.009003 Checking device (06DA/0601) (002/003) 0.009084 - VendorID: 06da 0.009097 - ProductID: 0601 0.009107 - Manufacturer: unknown 0.009118 - Product: unknown 0.009128 - Serial Number: unknown 0.009138 - Bus: 002 0.009148 Trying to match device 0.009186 Device matches 0.009210 failed to claim USB device: could not claim interface 0: Operation not permitted 0.009228 failed to detach kernel driver from USB device: could not detach kernel driver from interface 0: Operation not permitted 0.009244 failed to claim USB
[Nut-upsuser] Support for Online Yunto and Zinto
Hello, I have a Yunto e a Zanto ups connected with usb with id 06da:0002 and 06da:0601. I have seen that people had some success using megatec driver. But now megatec is replaced by blazer-usb and I am not able to use my upses under nut. Can you help me? Thanks! Mario ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
