similar to: Tripp Lite SU5000RT3U

sorry, I thought I hit reply-all. CC'ing the list. On May 8, 2018, at 10:00 AM, Michael <fax12345 at gmail.com> wrote: > > Hi Charles, > > I'll gladly help where I can. I did reach out to their product support, and I did not have install the displaylink driver as that is for a totally different product, so ignore all that. > > The 208 V makes sense. The unit

On May 8, 2018, at 10:05 PM, Charles Lepple <clepple at gmail.com> wrote: > >> I'm new to this, so let me know what you need from me and I will try my best. This UPS does power our production servers, so shutting things down aren't an easy task, but this weekend might open up some opportunity for that if need be. If I need to test it by unplugging the main power, that I can

Hi, I ported the serial tripplite.c driver to support the non-PDC USB models. It's a bit of a mess, but this is partially due to not getting any public documentation from Tripp Lite regarding these models. What you see below is an attempt to parse the debug variables based on what we know from other models. On May 7, 2018, at 3:33 PM, Michael <fax12345 at gmail.com> wrote: > >

Charles, I followed the instructions on github, and my upsc UPSNAME command output did not change (I don't have any statuses for the ups.status line). The output is as follows: upsc Tripp-Lite Init SSL without certificate database battery.voltage.nominal: 48 device.mfr: Tripp Lite device.model: TRIPP LITE UPS device.type: ups driver.name: tripplite_usb driver.parameter.pollinterval: 2

Hi Charles, Here's a screen grab of what I ran: ubuntu at intranet:~/upsmonitor/nut$ git checkout tripplite_0005 Already on 'tripplite_0005' Your branch is up to date with 'origin/tripplite_0005'. ubuntu at intranet:~/upsmonitor/nut$ git status On branch tripplite_0005 Your branch is up to date with 'origin/tripplite_0005'. nothing to commit, working tree clean

On Wed, Oct 1, 2008 at 7:30 AM, Roman Serbski <mefystofel at gmail.com> wrote: >> Definitely seems like a permissions problem. >> >> It's been a while since I messed with USB on FreeBSD. What do the >> permissions look like on /dev/ugen*? What modifications did you make >> to /etc/devfs.rules? > > Thanks a lot Charles! I think I managed to get NUT

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 information from the UPS. This is how it all looks:

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

Hello Charles, Thank you for all of your help this far. I have made some great progress. I was hung up with all sorts of USB problems which we can chalk up to a "blonde moment" for me (or more accurately, a *bald* moment). In all my starting over and screwing around, I had forgotten to reinstall libusb-compat. Duh! I am now to a point that I think we can dig a little deeper. The

> Lots of good progress here! I tried to enable a few more commands for > your model. For instance, the "M" values seem to be min/max voltage, > so there is a "reset.input.minmax" command to use with upscmd. Also, > you can trigger a battery test with "test.battery.start". I assume the > work the same way as on Protocol 3003 :-) Hello Charles, The

I was looking at how other drivers deal with outlet collections, and I noticed some differences between newhidups in 2.0.4 (from Debian's 2.0.4-2.3) and the SVN trunk (rev 723) on an Evolution. Full diff is below, but here are the highlights: * MGE HID 0.9 vs 1.0 * outlet.#.switch seems to have moved to the commands outlet.#.load.{on,off} Then I found this in the ChangeLog: * fix

> On Jun 5, 2018, at 4:23 PM, Michael <fax12345 at gmail.com> wrote: > > Hey Charles, > > Where and how do you want me to run that query? In general, after cloning, git commands can be run in the "working copy" directory and deeper. So following the wiki instructions, it's inside the "nut" directory that was created after running "git

Hi all, So I was on the phone with their tech support, and I was able to get a copy of their protocols, see attached. >From reading it, it looks like the hex code in the debug area is key. Thanks, Mike On Wed, Jun 6, 2018 at 1:41 PM, Michael <fax12345 at gmail.com> wrote: > Hi Charles, > > Here's a screen grab of what I ran: > > ubuntu at intranet:~/upsmonitor/nut$

Here is a Compatibility Report for the Eaton Ellipse ECO 1600 UPS. Roger battery.charge: 100 battery.charge.low: 20 battery.runtime: 1575 battery.type: PbAc device.mfr: EATON device.model: Ellipse ECO 1600 device.serial: 000000000 device.type: ups driver.name: usbhid-ups driver.parameter.lowbatt: 37 driver.parameter.offdelay: 30 driver.parameter.ondelay: 40 driver.parameter.pollfreq: 30

Hi, I have successfully configured Nut to work with EATON PS 650: system detects low battery, initiates shutdown, waits for UPS to switch power off. However, when power is restored, UPS immediately powers on all power plugs independently from ups.timer.start setting. upsc reports "ups.timer.start" variable availability which is set to 0. upsrw reports "ups.delay.start"

Device Manufacturer: Eaton Device Name: 5S1500LCD ---------------------------------------------------------- upsc output: battery.charge: 100 battery.charge.low: 20 battery.runtime: 3515 battery.type: PbAc device.mfr: EATON device.model: Ellipse PRO 1500 device.serial: 0000000000 device.type: ups driver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2

Device Manufacturer: Eaton Device Name: 5S1500LCD ---------------------------------------------------------- upsc output: battery.charge: 100 battery.charge.low: 20 battery.runtime: 3515 battery.type: PbAc device.mfr: EATON device.model: Ellipse PRO 1500 device.serial: 0000000000 device.type: ups driver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2

Hello, we have a MGE Pulsar Evolution 800 connected to a Fedora Core5 Server using a serial cable. Installed and configured properly are RPM versions of nut-2.0.3-0.1.fc5 nut-client-2.0.3-0.1.fc5 nut-cgi-2.0.3-0.1.fc5 which all work (mostly) fine. The server is connected to outlet.0 and properly shuts down when it's loosing power after around 20 minutes. It also boots up whenever the ups

Hi, I've been using NUT for many years to look after the UPS on my home servers. Originally I was using a Compaq R3000 but that was replaced with an MGE Pulsar Evolution 3000 about a couple of years ago because the Compaq one was just too noisy! I'm just setting up a replacement server and would like to connect it using a serial cable as I've found that the USB connection

Hi! After some problems doing the automatic shutdown of the UPS on Debian, I have found this Debian bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=293401 Now I fixed it calling always ups-monitor from the halt script despite being halt'ed' or powered off (and relying on the POWERDOWNFLAG be set). Which is the correct aproach or best solution to workarround this bug? And now my