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" and ran "git status", I have: 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 What do you need to do next? Thanks, Mike On Tue, Jun 5, 2018 at 8:14 PM, Charles Lepple <clepple at gmail.com> wrote:> 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 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> wrote: > >> On May 25, 2018, at 5:20 PM, Michael <fax12345 at gmail.com> wrote: >> > >> > driver.version: 2.7.4-480-g14301bdb >> > >> >> I might not have provided enough information on the branch. 14301bdb >> corresponds to a commit on the master branch, rather than the >> tripplite_0005 branch that has the new code. What does "git status" say? >> >> The hex debug output is probably still useful, but I haven't looked at >> all of the files. > > > >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20180606/b8b8677b/attachment.html>
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$ 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" and ran "git status", I have: > > > 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 > > > > > What do you need to do next? > > Thanks, > Mike > > On Tue, Jun 5, 2018 at 8:14 PM, Charles Lepple <clepple at gmail.com> wrote: > >> 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 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> >> wrote: >> >>> On May 25, 2018, at 5:20 PM, Michael <fax12345 at gmail.com> wrote: >>> > >>> > driver.version: 2.7.4-480-g14301bdb >>> > >>> >>> I might not have provided enough information on the branch. 14301bdb >>> corresponds to a commit on the master branch, rather than the >>> tripplite_0005 branch that has the new code. What does "git status" say? >>> >>> The hex debug output is probably still useful, but I haven't looked at >>> all of the files. >> >> >> >> >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20180606/71dec25f/attachment-0001.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: Communication Protocol 0005.pdf Type: application/pdf Size: 49269 bytes Desc: not available URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20180606/71dec25f/attachment-0003.pdf> -------------- next part -------------- A non-text attachment was scrubbed... Name: Communication Protocol 0002.pdf Type: application/pdf Size: 50968 bytes Desc: not available URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20180606/71dec25f/attachment-0004.pdf> -------------- next part -------------- A non-text attachment was scrubbed... Name: Communication Protocol 0004.pdf Type: application/pdf Size: 46033 bytes Desc: not available URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20180606/71dec25f/attachment-0005.pdf>
On Jun 6, 2018, at 5:18 PM, Michael <fax12345 at gmail.com> wrote:> > From reading it, it looks like the hex code in the debug area is key. >Agreed - the code that I added to the tripplite_0005 branch parses those same bytes that are shown in the debug output. (All of the Tripp-Lite protocols are similar, with subtle differences in which variables they support, and whether the values are in binary or hex.) There is one more commit on that branch from this morning which uses the UPS value for battery charge instead of a NUT approximation. The key is to make sure that the 0005 protocol code is being rebuilt properly, and being used. Since you are on the tripplite_0005 branch (according to "git status"), you should be able to run "git pull" from that directory to get the battery charge update. Then, rebuild with "make". You can ether run the driver from the nut/drivers/ directory ("sudo ./tripplite_usb -DD ...", or if you are overwriting drivers from the original .deb package, you can run "sudo make install" and then start NUT as usual. The thing to look for in upsc output: driver.version.internal: 0.29 should become driver.version.internal: 0.31 (we might be missing a Makefile dependency that prevents driver.version from always updating the Git hash, but the driver.version.internal number comes from the driver file that I just updated.)