Displaying 3 results from an estimated 3 matches for "s_value_2".
Did you mean:
s_value
2014 Jul 01
1
The dreaded Tripp Lite SMART500RT1U and NUT
...ften, but it would be good to do
that at least once to verify the LB flag. On yours, I think that would
look like "S: 00 ..."
The "01 04" seems to be the state before a self-test on yours as well
as on the ASCII version of the SMARTPRO protocol. See comments around
"switch(s_value_2) {" in the source code.
> UNPLUGD a while
> ups.debug.D: 00 00 00 7d 0d 00 00 '.......' <---- 4th segment = 125
Looks like the first pairs of digits are the input voltage, and "00
7d" = 125V out.
> ups.debug.L: 06 00 00 07 58 58 0d '....XX.' <----...
2014 Jul 01
0
The dreaded Tripp Lite SMART500RT1U and NUT
On Tue, Jul 1, 2014 at 9:17 AM, Steve Ballantyne
<steve.ballantyne at gmail.com> wrote:
> How would I go about providing you this stuff? Can you point me to
> something that would help trace out the USB data?
I thought I would try to make sense of the ups.debug data. All I have
really figured out is that the fourth hex segment for S is a 00 for
plugged in and a 01 for on-battery.
2014 Jul 01
2
The dreaded Tripp Lite SMART500RT1U and NUT
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