Displaying 3 results from an estimated 3 matches for "l410".
Did you mean:
410
2018 May 07
4
Tripp Lite SU5000RT3U
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
2018 May 08
0
Tripp Lite SU5000RT3U
...;
> ups.debug.0: 00 05 58 58 58 58 0d '..XXXX.'
The first two bytes are where the version (0005) is coming from. However, the NUT code only knows about a few protocols, and neither 0003 nor 0005 are among them:
https://github.com/networkupstools/nut/blob/v2.7.4/drivers/tripplite_usb.c#L410-L433
It appears to be fairly similar to 0004, though.
> ups.debug.D: 36 43 38 37 0d 00 00 '6C87...'
https://github.com/networkupstools/nut/blob/v2.7.4/drivers/tripplite_usb.c#L1258-L1276 parses this into input.voltage and battery.voltage, but there is some weird scaling (or maybe even...
2018 May 09
0
Tripp Lite SU5000RT3U
...58 0d '..XXXX.'
>>
>> The first two bytes are where the version (0005) is coming from. However, the NUT code only knows about a few protocols, and neither 0003 nor 0005 are among them:
>>
>> https://github.com/networkupstools/nut/blob/v2.7.4/drivers/tripplite_usb.c#L410-L433
>>
>> It appears to be fairly similar to 0004, though.
>>
>>> ups.debug.D: 36 43 38 37 0d 00 00 '6C87...'
>>
>> https://github.com/networkupstools/nut/blob/v2.7.4/drivers/tripplite_usb.c#L1258-L1276 parses this into input.voltage and battery.vo...