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
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
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
