search for: v_valu

...360 [...] > given ups.debugV[1] has the value 0. Ugh, that code is a mess. I should find the guy who wrote that driver and... never mind. For some reason that made sense at the time, the "ups.debug.*" variables in tripplite_usb actually start printing from value+1 (I suppose because v_value[0] is always 'V'). So the input.voltage.nominal value gets set properly because v_value[1] is actually '2'. I went ahead and changed the 230V nominal to 240V. https://github.com/networkupstools/nut/commit/f61edb5161de97944074867832edc014323340b1 If you want to rebuild the driver...

Using this UPS in the UK on 240V mains. Connected via USB: Bus 001 Device 002: ID 09ae:0001 Tripp Lite Requires tripplite_usb driver as it is (Product ID: 0001). There is an entry in the compatibity list for OMNIVS800 USB (protocol 2012) using usbhid-ups which is little misleading (although I guess maybe correct for some instances of the UPS). OMNIVS1000 USB (older; product ID: 0001) is

...240 > > https://github.com/networkupstools/nut/blob/master/drivers/tripplite_usb.c#L1360 > Yes I found that conversation. > > For some reason that made sense at the time, the "ups.debug.*" variables in tripplite_usb actually start printing from value+1 (I suppose because v_value[0] is always 'V'). So the input.voltage.nominal value gets set properly because v_value[1] is actually '2'. > Actually if this is reliable across models we could use it to scale actual input/output voltages respectively > I went ahead and changed the 230V nominal to 240V. T...

...et; } static void ups_sync(void) @@ -301,14 +285,17 @@ void upsdrv_initinfo(void) int va; long w, l; - /* Detect the UPS or die. */ ups_sync(); - send_cmd(":W\r", w_value, sizeof w_value); - send_cmd(":L\r", l_value, sizeof l_value); - send_cmd(":V\r", v_value, sizeof v_value); - send_cmd(":X\r", x_value, sizeof x_value); + while (send_cmd(":W\r", w_value, sizeof w_value) < 1) + sleep(1); + while (send_cmd(":L\r", l_value, sizeof l_value) < 1) + sleep(1); + while (send_cmd(":V\r", v_value, sizeof v_v...

...upstools/nut/commit/f61edb5161de97944074867832edc014323340b1 Still a magic constant, but now it has the nominal voltage factored in. >> For some reason that made sense at the time, the "ups.debug.*" variables in tripplite_usb actually start printing from value+1 (I suppose because v_value[0] is always 'V'). So the input.voltage.nominal value gets set properly because v_value[1] is actually '2'. >> > Actually if this is reliable across models we could use it to scale actual input/output voltages respectively That's the thing, due to the patchwork of me...