search for: 912571

Displaying 4 results from an estimated 4 matches for "912571".

Did you mean: 12571
2018 May 07
4
Tripp Lite SU5000RT3U
...7 0d 00 00 '6C87...' ups.debug.L: 31 31 35 41 30 31 0d '115A01.' ups.debug.load_banks: 8 ups.debug.M: 30 30 37 31 0d 00 00 '0071...' ups.debug.P: 30 35 30 30 0d 00 00 '0500...' ups.debug.S: 31 34 30 30 30 30 0d '140000.' ups.debug.T: 39 31 32 35 37 31 0d '912571.' ups.debug.V: 33 30 38 38 0d 00 00 '3088...' ups.delay.shutdown: 64 ups.firmware: F1114.A ups.firmware.aux: protocol 0005 ups.id: 65535 ups.mfr: Tripp Lite ups.model: TRIPP LITE UPS ups.power.nominal: 500 ups.productid: 0001 ups.status: ups.vendorid: 09ae >From talking with the te...
2018 May 08
0
Tripp Lite SU5000RT3U
...;0500...' > ups.debug.S: 31 34 30 30 30 30 0d '140000.' Status '4' means that a battery test hasn't been done recently. Other values here: https://github.com/networkupstools/nut/blob/v2.7.4/drivers/tripplite_usb.c#L1152-L1180 > ups.debug.T: 39 31 32 35 37 31 0d '912571.' 0x257 = 599 = 59.9 Hz; the following '1' indicates a nominal value of 60 Hz. You might be able to extract temperature from the first two digits. > ups.debug.V: 33 30 38 38 0d 00 00 '3088...' > You would also want to test the shutdown command(s) to make sure that ever...
2018 May 09
0
Tripp Lite SU5000RT3U
...'140000.' >> >> Status '4' means that a battery test hasn't been done recently. Other values here: >> >> https://github.com/networkupstools/nut/blob/v2.7.4/drivers/tripplite_usb.c#L1152-L1180 >> >>> ups.debug.T: 39 31 32 35 37 31 0d '912571.' >> >> 0x257 = 599 = 59.9 Hz; the following '1' indicates a nominal value of 60 Hz. You might be able to extract temperature from the first two digits. >> >>> ups.debug.V: 33 30 38 38 0d 00 00 '3088...' >>> >> >> You would als...
2013 Aug 28
3
[PATCH] x86: AVX instruction emulation fixes
- we used the C4/C5 (first prefix) byte instead of the apparent ModR/M one as the second prefix byte - early decoding normalized vex.reg, thus corrupting it for the main consumer (copy_REX_VEX()), resulting in #UD on the two-operand instructions we emulate Also add respective test cases to the testing utility plus - fix get_fpu() (the fall-through order was inverted) - add cpu_has_avx2,