Re: [Nut-upsuser] Problems communicating with Tripp Lite SMART500RT1U via USB with CentOS 6.6 and NUT 2.6.5
On Mar 6, 2015, at 12:51 PM, Eric Cobb eric_c...@tripplite.com wrote: Network UPS Tools - Tripp Lite OMNIVS / SMARTPRO driver 0.20 (2.6.5) Warning: This is an experimental driver. Some features may not function correctly. Detected a UPS: Tripp Lite /TRIPP LITE SMART500RT1U Unknown input voltage range: 0x02 Unknown number of switchable load banks: 0x01 Unit ID: 65535 Unknown protocol (3005) If this is the same protocol 3005 that we saw in mid-2014 (USB ID: 09AE:0001), then support will be part of the upcoming NUT 2.7.3 release. You wouldn't happen to know anyone who would be able to publish the specs of that protocol, would you? ;-) That would help remove the experimental driver warning. -- Charles Lepple clepple@gmail ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] nutdrv_atcl_usb
Suddenly yes, I also ended with Communications with UPS lost: Query to UPS failed (on Ubuntu 14.10) and have tried everything in this thread. Mine is called EUROCASE - UPS EA200N 2000VA, 2000VA, line interactive it looks exactly as EAST UPS - Pure Sine Wave UPS with LCD Display 2000VA or even brand Vivaldi. I would say is the same hardware with different branding. Mine is shipped with windows software UPSmart2000I EAST uses UPSmart (name is very similar too). It would be nice to try EAST UPS (windows) software with my UPS, to make sure is the same HW. I didnt tried yet nutdrv_qx-fuji BR Jakub On Thu, Mar 5, 2015 at 5:08 PM, Charles Lepple clep...@gmail.com wrote: On Mar 5, 2015, at 2:34 AM, Jakub jakub.sce...@gmail.com wrote: Come on, it started to be interesting! Do you have one of these UPSes? If so, here was Dan's email about a branch to test: If you still can't get it to work with nutdrv_atcl_usb, another approach could be worth considering. Since this UPS seems to be supported by UPSmart2000I, it could use a serial-over-usb implementation of the megatec protocol. A very first early version of the nutdrv_qx driver that should support it can be found here: https://github.com/zykh/nut/tree/nutdrv_qx-fuji (USB subdriver 'fuji'; but it shouldn't be necessary to set it, as the driver is expected to automatically select it according to the iManufacturer/iProduct strings) Note that the user I first developed it for abruptly stopped replying to my mails (maybe his UPS went boom.. who knows?), so I don't really know if it works or not: quite a lot of testing may be needed. -- Charles Lepple clepple@gmail ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] nutdrv_atcl_usb
It seems like it works (partially?) with NUT/driver you mentioned. I will test it more when I return home. root@Failure:/lib/nut# ./nutdrv_qx -a test -x subdriver=fuji -u root -x productid= -x vendorid=0001 -DD Network UPS Tools - Generic Q* USB/Serial driver 0.13 (2.7.2.5) USB communication driver 0.32 0.00 debug level is '6' 0.001247 upsdrv_initups... 0.311772 Checking device (1D6B/0001) (008/001) 0.335913 - VendorID: 1d6b 0.335937 - ProductID: 0001 0.335948 - Manufacturer: Linux 3.16.0-31-generic uhci_hcd 0.335959 - Product: UHCI Host Controller 0.335968 - Serial Number: :00:1d.2 0.335978 - Bus: 008 0.335987 Trying to match device 0.336008 Device does not match - skipping 0.336099 Checking device (1D6B/0001) (007/001) 0.359946 - VendorID: 1d6b 0.359970 - ProductID: 0001 0.359981 - Manufacturer: Linux 3.16.0-31-generic uhci_hcd 0.359991 - Product: UHCI Host Controller 0.360001 - Serial Number: :00:1d.1 0.360010 - Bus: 007 0.360019 Trying to match device 0.360032 Device does not match - skipping 0.360118 Checking device (0001/) (006/002) 0.398370 - VendorID: 0001 0.398393 - ProductID: 0.398403 - Manufacturer: ATCL FOR UPS 0.398413 - Product: ATCL FOR UPS 0.398422 - Serial Number: ATCL FOR UPS 0.398431 - Bus: 006 0.398440 Trying to match device 0.398516 Device matches 0.398548 failed to claim USB device: could not claim interface 0: Device or resource busy 0.398585 detached kernel driver from USB device... 0.398627 nut_usb_set_altinterface: skipped usb_set_altinterface(udev, 0) 0.398652 send_to_all: SETINFO ups.vendorid 0001 0.398667 send_to_all: SETINFO ups.productid 0.398711 command: (8 bytes) = 80 06 04 03 51 47 53 00 0.403387 send: QGS 1.406382 read: could not claim interface 0: Device or resource busy (-110) 1.406443 qx_process_answer: short reply (input.voltage) 1.406477 command: (8 bytes) = 80 06 04 03 51 47 53 00 1.411388 send: QGS 2.413380 read: could not claim interface 0: Device or resource busy (-110) 2.413421 qx_process_answer: short reply (input.voltage) 2.413452 command: (8 bytes) = 80 06 04 03 51 47 53 00 2.419388 send: QGS 3.421378 read: could not claim interface 0: Device or resource busy (-110) 3.421417 qx_process_answer: short reply (input.voltage) 3.421442 command: (8 bytes) = 80 06 02 03 4d 00 00 00 3.427373 send: M 4.429381 read: could not claim interface 0: Device or resource busy (-110) 4.429439 qx_process_answer: short reply (ups.firmware.aux) 4.429467 command: (8 bytes) = 80 06 02 03 4d 00 00 00 4.435376 send: M 5.437377 read: could not claim interface 0: Device or resource busy (-110) 5.437461 qx_process_answer: short reply (ups.firmware.aux) 5.437524 command: (8 bytes) = 80 06 02 03 4d 00 00 00 5.443380 send: M 6.445376 read: could not claim interface 0: Device or resource busy (-110) 6.445418 qx_process_answer: short reply (ups.firmware.aux) 6.445444 command: (8 bytes) = 80 06 02 03 4d 00 00 00 6.451412 send: M 7.454378 read: could not claim interface 0: Device or resource busy (-110) 7.454441 qx_process_answer: short reply (ups.firmware.aux) 7.454469 command: (8 bytes) = 80 06 02 03 4d 00 00 00 7.459388 send: M 8.462379 read: could not claim interface 0: Device or resource busy (-110) 8.462427 qx_process_answer: short reply (ups.firmware.aux) 8.462452 command: (8 bytes) = 80 06 02 03 4d 00 00 00 8.467379 send: M 9.469379 read: could not claim interface 0: Device or resource busy (-110) 9.469420 qx_process_answer: short reply (ups.firmware.aux) 9.469446 command: (8 bytes) = 80 06 03 03 51 53 00 00 9.475378 send: QS 10.477351 read: could not claim interface 0: Device or resource busy (-110) 10.477387 qx_process_answer: short reply (input.voltage) 10.477402 command: (8 bytes) = 80 06 03 03 51 53 00 00 10.483349 send: QS 11.485378 read: could not claim interface 0: Device or resource busy (-110) 11.485419 qx_process_answer: short reply (input.voltage) 11.485447 command: (8 bytes) = 80 06 03 03 51 53 00 00 11.491377 send: QS 12.494391 read: could not claim interface 0: Device or resource busy (-110) 12.494430 qx_process_answer: short reply (input.voltage) 12.494456 command: (8 bytes) = 80 06 02 03 44 00 00 00 12.499380 send: D 13.501395 read: could not claim interface 0: Device or resource busy (-110) 13.501554 qx_process_answer: short reply (input.voltage) 13.501628 command: (8 bytes) = 80 06 02 03 44 00 00 00 13.507372 send: D 14.509379 read: could
[Nut-upsuser] Problems communicating with Tripp Lite SMART500RT1U via USB with CentOS 6.6 and NUT 2.6.5
Hello, I am trying to get a SMART500RT1U working on CentOS and just receiving the following message when attempting to start the driver: Network UPS Tools - Tripp Lite OMNIVS / SMARTPRO driver 0.20 (2.6.5) Warning: This is an experimental driver. Some features may not function correctly. Detected a UPS: Tripp Lite /TRIPP LITE SMART500RT1U Unknown input voltage range: 0x02 Unknown number of switchable load banks: 0x01 Unit ID: 65535 Unknown protocol (3005)Attached to Tripp Lite TRIPP LITE SMART500RT1U Unknown value for s[1]: 0x01 Here is the environment that it is running in: Environmental OS: Centos 6.6 Kernel: 2.6.32-504.8.1.el6.x86_64 Nut Version: nut-2.6.5-2.el6.x86_64 What would be my next step to getting this to communicate with this UPS? Whenever I run UPS after starting this driver it gives me Error: Driver not connected Eric Cobb ekc...@tripplite.com This message is for the addressee's use only. It may contain confidential information. If you receive this message in error, please delete it and notify the sender. Tripp Lite disclaims all warranties and liabilities, and assumes no responsibility for viruses which may infect an email sent to you from Tripp Lite and which damage your electronic systems or information. It is your responsibility to maintain virus detection systems to prevent damage to your electronic systems and information. ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
