similar to: TrippLite SmartPro and 2.0.3

I have a new SMART1050SLT Tripp Lite UPS that both tripplite and tripplitesu drivers hate. Both simply time out with a "can't find" message. Does anyone know about the SmartPro series?

I have a TrippLite SmartPro UP (SMART3000RM2U) that shipped with the DB9 cable# 73-0866. nut doesn't recognize the UPS using the tripplite driver. I found this page: http://www.tripplite.com/support/download/PA12/help/device.htm The link lists the SmartPro series as using the cables 73-0724 or 73-0844 and the Internet 350/525 is listed as using a cable 73-0866. I have a few 73-0844s

Well, I have good news and bad news. I have a Tripp Lite SmartPro UPS attached to a Linux server running Ubuntu 5.10, and I'm running the just-released nut 2.0.3. I had error -71 from the UPS, which Charles Lepple correctly called out as a likely cable problem (thank you, Charles.) The cable provided with the UPS by Tripp Lite was just plain bad. Not too long, mind you- defective. I

I am using NUT 2.0.2 on SuSE Linux 9.2 which is attached to a Tripplite SmartPro Net 2200 UPS. I have Nut using the included tripplite driver, and it is communicating with the UPS correctly. The battery voltage of theTripplite reported by the NUT server is 13.5VDC. If I attach the UPS to a Windows 2000 server running Tripplite's PowerAlert software, the battery voltage is being reported as

Hi Everyone, I'm new to Samba. I have setup a samba server (Redhat 9) in the internal LAN and a samba client (Win2k) in the external LAN. There is a firewall between these two LANs. My problem is I cant see my workgroup in the client Microsoft Windows Network window. I have open 139, 445 tcp ports and 137, 138 udp ports. I have open 901 port as well. Before this I have tried connect to the

I am running Debian Etch, with the nut 2.0.4 packages, and I get a segmentation fault from tripplite_usb. # /lib/nut/tripplite_usb -u root -DDDDD auto Network UPS Tools - Tripp Lite OMNIVS and SMARTPRO driver 0.6 (2.0.4) Warning: This is an experimental driver. Some features may not function correctly. debug level is '5' Checking device (09AE/0001) (002/004) - VendorID: 09ae -

Recently, Windows 2000 SP4 clients have developed a problem when using a network printer connected to a Samba print share. Some applications are OK. But take, well, notepad, for example. Selecting a local printer is normal, but there is a two minute delay (!) in selecting a network printer. Once selected, all is well. All smb operations are frozen until the selection happens. This is

The Compatibility page lists the OMNIVS1000 as supported, but the tripplite_usb driver doesn't seem to recognize my UPS. Below is the debug dump from attempting to load the driver. I am using the nut package from Debian: 2.2.1-2.1 and I was wondering if this was a known issue? maroon:/lib/nut# /lib/nut/tripplite_usb -DDDDD -a usbups Network UPS Tools - Tripp Lite OMNIVS and SMARTPRO driver

Hello, We have a Tripplite SMART1500RMXL2U and nut-2.2.0-6.el5 installed on Centos 5.3. I've been unsuccessful on getting upsmon to work. usdrvctl seems to start despite some warnings/errors: # upsdrvctl start smart1500 Network UPS Tools - UPS driver controller 2.2.0- Network UPS Tools - Tripp Lite OMNIVS and SMARTPRO driver 0.11.1 (2.2.0-) Warning: This is an experimental driver. Some

He everyone, I have a Tripplite SMART700DVa using the tripplite_usb from NUT 2.5 (rev 2217) driver running in Solaris 10x86. My driver hangs when trying to connect. Once the driver sends the watchdog command ("W\0"), it can no longer receive any signals and eventually exits. The UPS responds to other watchdog commands ("W5" for example), but there doesn't seem to be

Hello, I have a TrippLite SMART1500RMXL2U that I'm trying to get running with Nut 2.2.1. Running upsdrvctl start works, upsd works, but upsc has "issues": je-nas:~/src/nut-2.2.1# upsdrvctl start Network UPS Tools - UPS driver controller 2.2.1- Network UPS Tools - Tripp Lite OMNIVS and SMARTPRO driver 0.11 (2.2.1-) Warning: This is an experimental driver. Some features may not

Greetings to all, I recently connected a Tripp Lite SMX500RT1U unit to a Synology NAS (basically a Marvell ARM equipped box running a custom 2.6.24 Linux). I tried using the tripplite_usb driver contained in nut 2.4.1 with not much luck. It does read the model ID and VA rating properly, but fails at everything else - mains voltage (this is a 230VAC EU model), battery config, unit status etc.

Hi, I've been trying to get my new Tripplite OmniVS100 UPS (USB Connection) to work on my system. What I have is: Ubuntu 10.04 Server Nut 2.4.3 /etc/nut/ups.conf [omni] Driver = tripplite_usb Port = auto Desc = "My Server" /etc/nut/nut.conf MODE=standalone Iget the following error when using the > sudo upsdrvctl start Network

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

I'm trying to get a SMART2200CRMXL to work with nut, using a USB cable. tripplite_usb -a upsname returns: Network UPS Tools - Tripp Lite OMNIVS and SMARTPRO driver 0.11.1 (2.2.2) Warning: This is an experimental driver. Some features may not function correctly. No matching USB/HID UPS found My system info: CentOS 5.5 nut installed from repo upsd version 2.2.2 TrippLite SMART2200CRMXL

I have added preliminary support for the TrippLite protocol number 2001 into tripplite_usb.c. The attached file is supplied as a patch against today's SVN. This patch adds support for TrippLite SMART550USB and some Omni models. Tested are On Line, On Battery, Battery Good, and Battery Bad indication. Everything else seems to work, but this UPS is attached to a critical system, and I can

On Mar 6, 2015, at 12:51 PM, Eric Cobb <Eric_Cobb at 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:

Hello, I have a Tripplite SMART2200VS that isn't being shut down when the nut master asks it to. My initial test was simply upsmon -c fsd which caused the system to shut down, but the UPS remained on and providing power to its loads. Looking in the logs (daemon and syslog) it was not clear to me that NUT was telling the UPS to shut down (I was expecting to see "Shutting down the UPS

I purchased a TrippLite ECO550UPS from Amazon a few days ago thinking I was going to use it for my Windows Media Center HTPC. I've since changed my mind and decided to use Mythbuntu but it I can't get my UPS working with nut. I've tried all of the tripplite drivers and the usbhid-ups driver. The tripplite_usb and usbhid_ups output is listed below. The tripplite and tripplitesu drivers

> > > 2.117586 send_cmd(msg_len=2, type='G') > > 3.219418 libusb_get_interrupt: Connection timed out > > 3.219474 libusb_get_interrupt() returned 0 instead of 8 while > sending 3a 47 b8 0d 00 00 00 00 '.G......' > > 4.219593 libusb_get_interrupt: Connection timed out > > 4.219661 libusb_get_interrupt() returned