similar to: Tripp Lite SmartPro SMX500RT1U incompatibility

engineering the UPS's responses to certain commands. I could provide any de= bug and other info needed to interpret protocol 3005. DiskStation> ./upsdrvctl -u root start Network UPS Tools - UPS driver controller 2.4.1 Network UPS Tools - Tripp Lite OMNIVS / SMARTPRO driver 0.20 (2.4.1) Warning: This is an experimental driver. Some features may not function correctly. Detected a UPS: TRIPP

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

I'm running Ubuntu 5.10, featuring a patched kernel 2.6.12. I have a Tripp Lite SmartPro SLT ups connected via USB. I have cleanly compiled and installed the new nut 2.0.3. I do have the "extras", like libusb, installed too. I need some USB advice- that is, I'm not sure what a normal baseline should look like. At boot, the modules usb_core and uhci_hcd are loaded. dmesg

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

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

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:

On March 6, 2015, at 6:17pm, Charles Leppe ,cleppe at gmail.com> wrote: 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.

<nut-upsuser at lists.alioth.debian.org> I am doing my best to avoid have to spend $280 for a network monitoring card to put into a $190 UPS just to have some good remote monitoring capabilities. Rather, I would like to monitor my many 1U Tripp Lite's on my network using a Raspberry Pi running Raspian and using NUT. However, I cannot seem to get it working. And I while the hardware

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

Hi people, I have the following dialplan, but it doesn't have the behavior that I think it should have. [default] exten => 2001,1,Answer exten => 2001,n,Dial(local/3005) exten => 2001,n,Hangup exten => 3005,1,Set(__RINGTIMER=10) exten => 3005,n,Macro(exten-vm,novm,3005) exten => 3005,n,Hangup When I execute the Originate (AMI) with the argument Channel=local/2001, It rings

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

On Thu, Jun 26, 2014 at 10:20 PM, Steve Ballantyne <steve.ballantyne at gmail.com> wrote: >> However, we don't have all of the 09AE/0001 protocols decoded in the >> tripplite_usb driver. > > I can try to help out on this front? :-) Definitely. >> > 9.783126 Unknown input voltage range: 0x02 >> > 9.783308 Unknown number of switchable

Hello Charles, Thanks for the feedback. I will try to answer some of these questions: > 09AE/0001 is essentially a USB-to-serial converter, and is not > compatible with usbhid-ups. (Theoretically, we could have a companion > driver that talks the same protocols over a real RS-232 port, but the > hardware I used to develop the tripplite_usb driver only has a USB > port.) Ah, that

Hi people, just a question: Is it possible to execute Voicemail command in the h extension? (after hangup the channel). Because if I put it before it, it works right, but if I put it there, it doesn't... The log is: -- Executing [h at cont-mine:1] NoOp("SIP/3005-096736a8", "End of cont-mine") in new stack -- Executing [h at cont-mine:2]

Good afternoon, I'm trying without much success to monitor a Tripp Lite OMNIVS1500XL using NUT. I checked the compatibility list and saw that this UPS is supported by tripplite_usb. The system is running Debian Stable, but I've downloaded NUT 2.0.3 and compiled from source since the packaged 2.0.1 doesn't include tripplite_usb. I compiled --with-user=nut. My first attempt at

Greetings NUT users, I am looking for a solution to monitor the power OUTSIDE my datacenter. (The on/blackout status of main building power). My small datacenter is covered by a UPS, an older Liebert 18Kva unit with no environmental or status monitoring outside of the LCD console and audible alarm. The Liebert UPS is backed by a 35KW diesel generator which usually kicks on within 10

I keep getting this kind of stuff in /var/log/messages Jan 18 17:45:03 bulldog tripplite_usb[9979]: libusb_get_interrupt() returned -110 instead of 8 Should I be worried about it? upsc seems to work fine... I tried building the 2.0.5 but none of the included spec files seemed to work with opensuse 10.2 and adapting their 2.0.4 spec file didn't seem to work out well either. Building from

I keep getting this kind of stuff in /var/log/messages Jan 18 17:45:03 bulldog tripplite_usb[9979]: libusb_get_interrupt() returned -110 instead of 8 Should I be worried about it? upsc seems to work fine... I tried building the 2.0.5 but none of the included spec files seemed to work with opensuse 10.2 and adapting their 2.0.4 spec file didn't seem to work out well either. Building from

Hello, I'm trying to place a call to asterisk using X-Lite. Asterisk is setup with some Grandstream phones. I can call from one grandstream extension to another. When I try to an extension with X-Lite, it comes back with Status of SIP/2.0 404 Not Found. X-Lite is not registered as asterisk extension. It is just sending a sip invite to extension@IP. Does the X-Lite need to connect to