search for: zinto

Hi Arnaud, Hi Scott, Hi list, Here is a patch to support the Zinto D from ONLINE USV-Systeme AG. I already sent a version to Russell Kroll (2006-04-09), without no response and I cannot find support for Zinto in svn until now. I found a discussion on this list about the Xanto from ONLINE, but the Zinto seems to use different commands. The commands are quite simil...

Hi, today I have tested the Zinto 800 with blazer_ser and blazer_usb on Citrix Server 7.0. Both works fine. upsc-Output (blazer_ser): battery.charge: 94 battery.voltage: 25.70 battery.voltage.high: 26.00 battery.voltage.low: 20.80 battery.voltage.nominal: 24.0 device.mfr: device.model: ZINTO 800 device.type: ups driver.name: blaze...

...s. Thanks, -- Peter Matthias Goebl wrote: > > On Sun, Nov 26, 2006 at 12:40:44PM -0400, Peter Selinger wrote: > > Matthias, > > > > NUT drivers should always detect devices automatically if possible, > > rather than requiring the user to set a variable such as "zinto". > > > > Can you modify upsdrv_initinfo to detect the device type based on the > > model string (and/or if necessary, based on ups.mfr)? -- Peter > > That's a good idea - thanks! > I'll try and mail you again, > matthias >

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

Hello, today I'm fighting with a Online Zinto 1000 (lsusb.txt) produced by Phoenixtec/Eaton ;-) http://www.eaton.com/EatonCom/OurCompany/NewsandEvents/NewsList/CT_141334 I have tested different drivers without success (please see attachments usbhid-ups.txt, bcmxcp_usb.txt, blazer_usb.txt) The help got unfortunately time outs (explore.txt) ht...

Daniele, Thanks again for your work on both the voltronic and blzr drivers. To get the most exposure to new drivers, what we have typically done in the past is to rename the existing driver as *-old, so that users get the new driver by default when they upgrade (but the old driver is still available if there are regressions). This is how we are incorporating Michal's apcsmart updates. On

...lush: No error 16.703915 send: D 17.747941 read: No error 17.748138 blazer_status: short reply 17.748252 Status read 2 failed 18.795947 flush: No error 18.799938 send: D 19.843961 read: No error 19.844147 blazer_status: short reply 19.844255 Status read 3 failed 19.844350 Trying zinto protocol... 20.891970 flush: No error 20.895962 send: Q1 21.939989 read: No error 21.940197 blazer_status: short reply 21.940307 Status read 1 failed 22.988001 flush: No error 22.991986 send: Q1 24.036013 read: No error 24.036220 blazer_status: short reply 24.036329 Status read...

...02152 blazer_status: short reply 0.102155 Status read 1 failed 0.102159 blazer_status: short reply 0.102161 Status read 2 failed 0.102164 blazer_status: short reply 0.102167 Status read 3 failed 0.102170 Skipping megatec/old protocol... 0.102173 Skipping zinto protocol... 0.102176 No supported UPS detected /usr/lib/ups/driver/blazer_ser -DD -u root -a powermust1 Network UPS Tools - Megatec/Q1 protocol serial driver 1.56 (2.7.3) 0.000000 debug level is '2' 0.100597 Trying megatec protocol... 1.101720 blazer_status: short...

...root dialout Didn't help. I don't know why the groupname is dialout, it is the same with all rules (nut from RPM package). And yes, nut belongs to dialout group: /etc/group --- clip --- dialout:x:18:nut --- clip --- I have also tried blazer_usb with every protocol: megatec, megatec/old, zinto I did some searching and found nothing, usually "failed to claim USB device" problems were related to permission issues. -- Tapio -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/2014030...

...zer_status: short reply 4.254608 Status read 1 failed 4.255296 send: D 4.379452 read: N 4.379601 blazer_status: short reply 4.379692 Status read 2 failed 4.380447 send: D 4.504477 read: N 4.504631 blazer_status: short reply 4.504725 Status read 3 failed 4.504812 Trying zinto protocol... 4.505581 send: Q1 4.635465 read: N 4.635565 blazer_status: short reply 4.635654 Status read 1 failed 4.636344 send: Q1 4.766481 read: N 4.766580 blazer_status: short reply 4.766668 Status read 2 failed 4.767360 send: Q1 4.897519 read: N 4.897659 blazer_s...

...6 Trying megatec/old protocol... 4.246117 blazer_status: short reply 4.247034 Status read 1 failed 4.372103 blazer_status: short reply 4.372848 Status read 2 failed 4.498122 blazer_status: short reply 4.499047 Status read 3 failed 4.499709 Trying zinto protocol... 4.631115 blazer_status: short reply 4.632027 Status read 1 failed 4.763101 blazer_status: short reply 4.763842 Status read 2 failed 4.895123 blazer_status: short reply 4.895203 Status read 3 failed 4.895229 No supported UPS detected Is t...

...Status read 1 failed 0.205977 send: D 0.206016 read: D 0.206131 blazer_status: short reply 0.206171 Status read 2 failed 0.206273 send: D 0.206319 read: D 0.206357 blazer_status: short reply 0.206461 Status read 3 failed 0.206501 Trying zinto protocol... 0.206610 send: Q1 0.210744 read: error sending control message: Protocol error 0.210953 blazer_status: short reply 0.211064 Status read 1 failed 0.211107 send: Q1 0.214756 read: error sending control message: Protocol error 0.215004 blaze...

...Status read 1 failed 0.205977 send: D 0.206016 read: D 0.206131 blazer_status: short reply 0.206171 Status read 2 failed 0.206273 send: D 0.206319 read: D 0.206357 blazer_status: short reply 0.206461 Status read 3 failed 0.206501 Trying zinto protocol... 0.206610 send: Q1 0.210744 read: error sending control message: Protocol error 0.210953 blazer_status: short reply 0.211064 Status read 1 failed 0.211107 send: Q1 0.214756 read: error sending control message: Protocol error 0.215004 blaze...

...send: 'D' 8.123137 read: timeout 8.123400 blazer_status: short reply 8.123503 Status read 2 failed 8.124140 send: 'D' 9.125620 read: timeout 9.125659 blazer_status: short reply 9.125670 Status read 3 failed 9.125680 Trying zinto protocol... 9.126280 send: 'Q1' 10.127596 read: timeout 10.127641 blazer_status: short reply 10.127653 Status read 1 failed 10.128204 send: 'Q1' 11.129560 read: timeout 11.129596 blazer_status: short reply 11.129608 Status read 2 fail...

...8.355562 read: Connection timed out 8.355581 blazer_status: short reply 8.355586 Status read 2 failed 8.356632 send: D 9.357629 read: Connection timed out 9.357680 blazer_status: short reply 9.357693 Status read 3 failed 9.357705 Trying zinto protocol... 9.358612 send: Q1 10.359615 read: Connection timed out 10.359675 blazer_status: short reply 10.359689 Status read 1 failed 10.360585 send: Q1 11.361691 read: Connection timed out 11.361723 blazer_status: short reply 11.361774 Stat...

Hi Charles, I am done with few things: I made the cable - looks good, because I see some activities. I upgraded NUT to 2.7.3. but I have no success to start driver(this are the outputs) nut.cfg MODE = netserver ups.conf [infosec] driver = nutdrv_qx (or blazer_ser) port = /dev/ttyS1 desc = "XP Pro 2500 RM" output(nutdrv_qx cmd upsdrvctl -DDD start) Network UPS

...10.242586 read: Input/output error 10.245586 blazer_status: short reply 10.247586 Status read 2 failed 10.349592 send: 'D' 11.368650 read: Input/output error 11.371651 blazer_status: short reply 11.374651 Status read 3 failed 11.376651 Trying zinto protocol... 11.479657 send: 'Q1' 12.727728 read: Input/output error 12.730728 blazer_status: short reply 12.733729 Status read 1 failed 12.836734 send: 'Q1' 14.081806 read: Input/output error 14.084806 blazer_status: short reply 14.086806...

...read 1 failed 1.300475 No appropriate HID device found 1.300572 blazer_status: short reply 1.300622 Status read 2 failed 1.321620 No appropriate HID device found 1.321719 blazer_status: short reply 1.321772 Status read 3 failed 1.321827 Trying zinto protocol... 1.322081 No appropriate HID device found 1.322144 blazer_status: short reply 1.322192 Status read 1 failed 1.322417 No appropriate HID device found 1.322479 blazer_status: short reply 1.322530 Status read 2 failed 1.322747 No appro...

...> 1.290388 Status read 1 failed > 1.300475 No appropriate HID device found > 1.300572 blazer_status: short reply > 1.300622 Status read 2 failed > 1.321620 No appropriate HID device found > 1.321719 blazer_status: short reply > 1.321772 Status read 3 failed > 1.321827 Trying zinto protocol... > 1.322081 No appropriate HID device found > 1.322144 blazer_status: short reply > 1.322192 Status read 1 failed > 1.322417 No appropriate HID device found > 1.322479 blazer_status: short reply > 1.322530 Status read 2 failed > 1.322747 No appropriate HID device fou...

...Status read 1 failed 5.696313 send: D 5.696333 read: D 5.696353 blazer_status: short reply 5.696373 Status read 2 failed 5.696393 send: D 5.696413 read: D 5.696433 blazer_status: short reply 5.696453 Status read 3 failed 5.696473 Trying zinto protocol... 5.696493 send: Q1 5.873927 received 10 (85) 5.873953 read: UPS No Ack 6.051930 received 10 (85) 6.051944 read: UPS No Ack 6.229934 received 10 (85) 6.229962 read: UPS No Ack 6.407936 received 10 (85) 6.407952 read: UPS No Ac...