search for: input_voltage_scaled

Displaying 6 results from an estimated 6 matches for "input_voltage_scaled".

2014 Sep 25
2
TRIPPLITE OMNIVSINT80 Compatibility
...iate its a 240v model I dont know. This is, at least, consistent with decode_v() in the driver src: void decode_v(const unsigned char *value) { unsigned char ivn, lb; int bv = hex2d(value+2, 2); ivn = value[1]; lb = value[4]; switch(ivn) { case '0': input_voltage_nominal = input_voltage_scaled = 100; break; case '1': input_voltage_nominal = input_voltage_scaled = 120; break; case '2': input_voltage_nominal = input_voltage_scaled = 230; break; case '3': input_voltage_nominal = 208; input_voltage_scaled = 230; break;...
2014 May 19
2
Tripp Lite SMART3000RM2U (protocol 3003) running time and charge?
...== TRIPP_LITE_SMARTPRO) { - battery_charge = (unsigned)(s_value[5]); - dstate_setinfo("battery.charge", "%u", battery_charge); - } } @@ -1167,9 +1167,22 @@ hex2d(d_value+1, 2) * input_voltage_scaled / 120); bv = hex2d(d_value+3, 2) * battery_voltage_nominal / 120.0 ; - + // bv is 48V nominal rather than 12V + dstate_setinfo("battery.voltage", "%.2f", bv); + if(tl_model == TRIPP_LITE_SMARTPRO) { +...
2014 May 20
0
Tripp Lite SMART3000RM2U (protocol 3003) running time and charge?
...- battery_charge = (unsigned)(s_value[5]); > - dstate_setinfo("battery.charge", "%u", battery_charge); > - } > } > > @@ -1167,9 +1167,22 @@ > hex2d(d_value+1, 2) * input_voltage_scaled / 120); > > bv = hex2d(d_value+3, 2) * battery_voltage_nominal / 120.0 ; Does battery_voltage_nominal get set correctly? Theoretically, it should be 48, since the 2nd and 3rd digits of ups.debug.V are 08, and that gets multiplied by 6. Might be useful to have an intermediate...
2014 May 16
0
Tripp Lite SMART3000RM2U (protocol 3003) running time and charge?
On May 15, 2014, at 9:39 PM, Stefan Bruda wrote: > What bugs be though is that I cannot seem to be able to read the > remaining run time on battery. The battery charge is also widely > inaccurate (it drops to zero really fast and stays there). I read > somewhere that the usb.debug numbers may hold the key to this (at > least to the running time that is), but I don't know what
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 22
2
Tripp Lite SMART3000RM2U (protocol 3003) running time and charge?
...ge = (unsigned)(s_value[5]); > > - dstate_setinfo("battery.charge", "%u", battery_charge); > > - } > > } > > > > @@ -1167,9 +1167,22 @@ > > hex2d(d_value+1, 2) * input_voltage_scaled / 120); > > > > bv = hex2d(d_value+3, 2) * battery_voltage_nominal / 120.0 ; > > Does battery_voltage_nominal get set correctly? Theoretically, it > should be 48, since the 2nd and 3rd digits of ups.debug.V are 08, > and that gets multiplied by 6. Yes...