[Nut-upsuser] Support for Online Yunto and Zinto
Arnaud Quette
aquette.dev at gmail.com
Mon Feb 13 18:58:04 UTC 2012
Hi Thomas,
2012/2/13 Thomas Maisl <exp-122008 at 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 -DDDDD
>> Network UPS Tools - Megatec/Q1 protocol USB driver 0.04 (2.6.3)
>> 0.000000 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.555569 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
>> 14.587338 send: Q1
>> 14.967370 read: (228.0 002.0 228.0 000 49.9 13.7 25.0 00101000
>> 14.967627 send_to_all: DATAOK
>> 14.967931 dstate_init: sock /var/run/nut/blazer_usb-YQ450 open on fd 5
>> 14.968022 send_to_all: SETINFO driver.parameter.pollinterval "2"
>> 15.970186 flush: could not claim interface 0: Device or resource busy
>> 15.974166 send: Q1
>> 16.343393 read: (228.0 002.0 228.0 000 49.9 13.7 25.0 00101000
>> 16.822141 new connection on fd 6
>> 16.822543 send_to_one: SETINFO battery.voltage "13.70"
>> 16.822622 send_to_one: SETINFO beeper.status "disabled"
>> 16.822647 send_to_one: SETINFO device.type "ups"
>> 16.822669 send_to_one: SETINFO driver.name "blazer_usb"
>> 16.822691 send_to_one: SETINFO driver.parameter.pollinterval "2"
>> 16.822714 send_to_one: SETINFO driver.parameter.port "auto"
>> 16.822737 send_to_one: SETINFO driver.parameter.productid "0002"
>> 16.822759 send_to_one: SETINFO driver.parameter.subdriver "phoenix"
>> 16.822782 send_to_one: SETINFO driver.parameter.vendorid "06da"
>> 16.822804 send_to_one: SETINFO driver.version "2.6.3"
>> 16.822826 send_to_one: SETINFO driver.version.internal "0.04"
>> 16.822848 send_to_one: SETINFO input.frequency "49.9"
>> 16.822872 send_to_one: SETINFO input.voltage "228.0"
>> 16.822895 send_to_one: SETINFO input.voltage.fault "2.0"
>> 16.822917 send_to_one: SETINFO output.voltage "228.0"
>> 16.822941 send_to_one: SETINFO ups.delay.shutdown "30"
>> 16.822964 send_to_one: SETINFO ups.delay.start "180"
>> 16.822987 send_to_one: SETINFO ups.load "0"
>> 16.823009 send_to_one: SETINFO ups.productid "0002"
>> 16.823031 send_to_one: SETINFO ups.status "OL BYPASS"
>> 16.823053 send_to_one: SETINFO ups.temperature "25.0"
>> 16.823075 send_to_one: SETINFO ups.type "offline / line interactive"
>> 16.823097 send_to_one: SETINFO ups.vendorid "06da"
>> 16.823119 send_to_one: ADDCMD beeper.toggle
>> 16.823141 send_to_one: ADDCMD load.off
>> 16.823162 send_to_one: ADDCMD load.on
>> 16.823183 send_to_one: ADDCMD shutdown.return
>> 16.823204 send_to_one: ADDCMD shutdown.stayoff
>> 16.823225 send_to_one: ADDCMD shutdown.stop
>> 16.823246 send_to_one: ADDCMD test.battery.start
>> 16.823267 send_to_one: ADDCMD test.battery.start.deep
>> 16.823296 send_to_one: ADDCMD test.battery.start.quick
>> 16.823317 send_to_one: ADDCMD test.battery.stop
>> 16.823338 send_to_one: DATAOK
>> 16.823358 send_to_one: DUMPDONE
>> 17.970353 flush: could not claim interface 0: Device or resource busy
>> 17.974263 send: Q1
>> 18.327183 read: (228.0 002.0 228.0 000 49.9 13.7 25.0 00101000
>> 19.971366 flush: could not claim interface 0: Device or resource busy
>> 19.975352 send: Q1
>> 20.343369 read: (229.0 002.0 228.0 000 49.9 13.7 25.0 00101000
>> 20.343566 send_to_all: SETINFO input.voltage "229.0"
>> 21.972355 flush: could not claim interface 0: Device or resource busy
>> 21.976359 send: Q1
>> 22.327184 read: (228.0 002.0 228.0 000 49.9 13.7 25.0 00101000
>> 22.327299 send_to_all: SETINFO input.voltage "228.0"
>> 23.973360 flush: could not claim interface 0: Device or resource busy
>> 23.977250 send: Q1
>> 24.343179 read: (228.0 002.0 228.0 000 49.9 13.7 25.0 00101000
>> 25.974238 flush: could not claim interface 0: Device or resource busy
>> 25.978338 send: Q1
>> 26.327194 read: (229.0 002.0 228.0 000 49.9 13.7 25.0 00101000
>> 26.327308 send_to_all: SETINFO input.voltage "229.0"
>> 27.974357 flush: could not claim interface 0: Device or resource busy
>> 27.978339 send: Q1
>> 28.343184 read: (228.0 002.0 228.0 000 49.9 13.7 25.0 00101000
>> 28.343296 send_to_all: SETINFO input.voltage "228.0"
>> 29.975356 flush: could not claim interface 0: Device or resource busy
>> 29.979339 send: Q1
>> 30.359372 read: (228.0 002.0 228.0 000 49.9 13.7 25.0 00101000
>> 31.976356 flush: could not claim interface 0: Device or resource busy
>> 31.980382 send: Q1
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.
if possible, I'd like to get this output both with and without "protocol=zinto"
cheers,
Arnaud
--
Linux / Unix Expert R&D - 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/
More information about the Nut-upsuser
mailing list