search for: tripplite_0005

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 After I ran "make...

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

...ays some level of risk with testing new code on an UPS, but if things didn't shut down before, you should be okay. You can try building this week, but I'd still wait until the weekend to test the new driver. > If you have a chance to build the master branch to test, you can also try the tripplite_0005 branch. I need to dig out the OMNIVS1000 for regression testing, and of course I don't have a SU5000 to test with, but it should work based on the debug information you provided.

...rectory and deeper. So following the wiki instructions, it's inside the "nut" directory that was created after running "git clone". It will probably say something like this: $ git status On branch master Your branch is up to date with 'github/master'. To test the tripplite_0005 branch, run "git checkout tripplite_0005" and run "make". > > Thanks, > Mike > > On Fri, May 25, 2018 at 5:01 PM, Charles Lepple <clepple at gmail.com <mailto:clepple at gmail.com>> wrote: > On May 25, 2018, at 5:20 PM, Michael <fax12345 at gm...

...ith testing new code on an UPS, but > if things didn't shut down before, you should be okay. You can try building > this week, but I'd still wait until the weekend to test the new driver. > > > If you have a chance to build the master branch to test, you can also try > the tripplite_0005 branch. I need to dig out the OMNIVS1000 for regression > testing, and of course I don't have a SU5000 to test with, but it should > work based on the debug information you provided. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://alioth-lists.de...

Hi, I am trying to configure my Tripp Lite SU5000RT3U on Ubuntu 18.04 as I am not able to completely get all the data from the UPS. After installing all required packages from the Ubuntu repos (had to run sudo apt-get install dkms, I had to install the displaylink drivers from displaylink.org by doing sudo ./displaylink-driver-4.2.29.run, and I created a sim link by doing the following: sudo ln