search for: smart3000rm2u

...ols - UPS driver controller 2.0.5 Starting UPS: tripplite exec: /usr/local/bin/tripplite_usb -a tripplite Network UPS Tools - Tripp Lite OMNIVS and SMARTPRO driver 0.7 (2.0.5) Warning: This is an experimental driver. Some features may not function correctly. Detected a UPS: TRIPP LITE/ TRIPP LITE SMART3000RM2U libusb_get_interrupt() returned -110 instead of 8 libusb_get_interrupt() returned 0 instead of 8 libusb_get_interrupt() returned -110 instead of 8 libusb_get_interrupt() returned -19 instead of 8 libusb_get_interrupt() returned -19 instead of 8 libusb_get_interrupt() returned -19 instead of 8 libus...

...but without a way to differentiate them, I'm out of luck. Thanks. Seth System specs are as follows: OS: Ubuntu 10.04.4 nut version: 2.4.3 installed from packages (but I also tried building 2.6.4 from tarball and just using that version of tripplite_usb with same results) device: Tripp-Lite SMART3000RM2U device info: http://www.tripplite.com/en/products/model.cfm?txtModelID=3025 debug output: # /lib/nut/tripplite_usb -DD -a tl1 Network UPS Tools - Tripp Lite OMNIVS / SMARTPRO driver 0.20 (2.4.3) Warning: This is an experimental driver. Some features may not function correctly. 0.000000 debug...

Can anyone point me to information for getting the Tripplite SMART3000RM2U to work with NUT? Our newer Tripplite units seem to work with the usbhid-ups driver, but these older ones seem to need something different. So far I have had little success getting tripplite_usb to work. [root at banyan ~]# tripplite_usb -a tripplite Network UPS Tools - Tripp Lite OMNIVS / SMARTPR...

Hello, I own an older Tripp Lite SMART3000RM2U (protocol 3003). It does not work with usbhid-ups but it mostly works with the tripplite_usb driver (nut 2.7.1, the latest in the Gentoo tree), in the sense that the status (on line, on battery, etc.) is detected correctly, the machine is shut down on critical battery, and I can even get some info...

On May 24, 2014, at 5:49 PM, Stefan Bruda wrote: >> Don't worry about the battery physical properties for now - the >> problem there is that we don't have enough information from the UPS >> to do a proper calculation. With the V_interval[] settings, you can >> tweak the new state-of-charge calculation to match what you see via >> upsc when the battery is

On May 15, 2014, at 9:39 PM, Stefan Bruda wrote: > What bugs be though is that I cannot seem to be able to read the > remaining run time on battery. The battery charge is also widely > inaccurate (it drops to zero really fast and stays there). I read > somewhere that the usb.debug numbers may hold the key to this (at > least to the running time that is), but I don't know what

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

On Jun 2, 2014, at 10:25 PM, Stefan Bruda wrote: > Hello, > > At 15:42 -0400 on 2014-6-1 Charles Lepple wrote: >> >> On May 24, 2014, at 5:49 PM, Stefan Bruda wrote: >> >>>> Don't worry about the battery physical properties for now - the >>>> problem there is that we don't have enough information from the UPS >>>> to do a

On May 22, 2014, at 10:03 AM, Stefan Bruda wrote: >> >> Does battery_voltage_nominal get set correctly? Theoretically, it >> should be 48, since the 2nd and 3rd digits of ups.debug.V are 08, >> and that gets multiplied by 6. > > Yes, as it appear as 48V in the output of upsc. Good. > >> Might be useful to have an intermediate value that doesn't scale

Hello, At 09:24 -0400 on 2014-5-23 Charles Lepple wrote: > > See attached. Still doesn't have the writable V_interval values, > but I probably won't have time to test that until later. Thank you for the patch. > Don't worry about the battery physical properties for now - the > problem there is that we don't have enough information from the UPS > to do a

On May 19, 2014, at 7:12 PM, Stefan Bruda wrote: > Hello, > > First of all thank you so much for the information. No problem, glad it is useful. > [...] > Therefore as far as my UPS is concerned s_value[5] is wildly > incorrect. So it turns out that the RM15002U also does not report anything useful for s_value[5]:

Hello, At 15:42 -0400 on 2014-6-1 Charles Lepple wrote: > > On May 24, 2014, at 5:49 PM, Stefan Bruda wrote: > > >> Don't worry about the battery physical properties for now - the > >> problem there is that we don't have enough information from the UPS > >> to do a proper calculation. With the V_interval[] settings, you can > >> tweak

Hello, I am looking for good instructions on how to configure NUT to receive SNMP Trap signals and how to shutdown a server. My setup is: NUT: version 2.7.1-1ubuntu1, from package OS: Ubuntu 14.04.5 LTS UPS: Tripp Lite SMART3000RM2U The only thing I was able to understand from the documentation is to an entry in ups.conf: [tripplite-pa3] driver = snmp-ups port = tripplite-pa3.domain.com community = public mibs = ietf Then start upsd: root at dell1850:/etc/nut# upsd Network UPS Tools upsd 2....

Hello, At 22:19 -0400 on 2014-5-19 Charles Lepple wrote: > > On May 19, 2014, at 7:12 PM, Stefan Bruda wrote: > > > Therefore as far as my UPS is concerned s_value[5] is wildly > > incorrect. > > So it turns out that the RM15002U also does not report anything useful for s_value[5]: > >

Hello, First of all thank you so much for the information. At 22:43 -0400 on 2014-5-15 Charles Lepple wrote: > > On May 15, 2014, at 9:39 PM, Stefan Bruda wrote: > > > What bugs be though is that I cannot seem to be able to read the > > remaining run time on battery. The battery charge is also widely > > inaccurate (it drops to zero really fast and stays