search for: l1099

Displaying 3 results from an estimated 3 matches for "l1099".

Did you mean: 1099
2014 May 16
0
Tripp Lite SMART3000RM2U (protocol 3003) running time and charge?
...ey to this (at > least to the running time that is), but I don't know what to do with > them (and I can no longer find that piece of information...). Here's where the battery.charge variable is calculated: https://github.com/networkupstools/nut/blob/master/drivers/tripplite_usb.c#L1099 battery_charge = (unsigned)(s_value[5]); (In that file, the 3003 protocol is denoted by "tl_model == TRIPP_LITE_SMARTPRO".) Due to the command prefix characters in the protocol, the ups.debug.S hex values are actually indexed from 1 as follows: 1 2 3 4 5 6 7 up...
2014 May 16
2
Tripp Lite SMART3000RM2U (protocol 3003) running time and charge?
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:
2014 May 19
2
Tripp Lite SMART3000RM2U (protocol 3003) running time and charge?
...he running time that is), but I don't know what to do with > > them (and I can no longer find that piece of information...). > > Here's where the battery.charge variable is calculated: > > https://github.com/networkupstools/nut/blob/master/drivers/tripplite_usb.c#L1099 > > battery_charge = (unsigned)(s_value[5]); > > (In that file, the 3003 protocol is denoted by "tl_model == TRIPP_LITE_SMARTPRO".) > > Due to the command prefix characters in the protocol, the > ups.debug.S hex values are actually indexed from 1 as follow...