search for: 2x0v

...context of what the UPS (and upsc) reports? My guess its what it would expect to see so you can relate input.voltage to it. In that respect its 230V for the territory the model is sold into even though Tripp lite are selling it as a 240V model. Either way the differentiation only has to deal with 2x0V versus 110V and so unlikely to be the source of any confusion. Dave

...high and low voltages.) > My guess its what it would expect to see so you can relate input.voltage > to it. In that respect its 230V for the territory the model is sold into > even though Tripp lite are selling it as a 240V model. Either way the > differentiation only has to deal with 2x0V versus 110V and so unlikely > to be the source of any confusion. In that case, I'm inclined to change it back to 230V before the next release, since we don't have any more accurate information as to what the 'V' digits really mean. -- Charles Lepple clepple at gmail

On Sep 26, 2014, at 3:48 AM, Dave Williams <dave at opensourcesolutions.co.uk> wrote: > On 22:17, Thu 25 Sep 14, Charles Lepple wrote: >> >> I think the OMNIVS800 protocol 2012 entry came from Tripp Lite test results. (There have definitely been naming collisions in the past; hence, the messages in the drivers if you accidentally choose the wrong one.) >> >>

On 22:17, Thu 25 Sep 14, Charles Lepple wrote: > > I think the OMNIVS800 protocol 2012 entry came from Tripp Lite test results. (There have definitely been naming collisions in the past; hence, the messages in the drivers if you accidentally choose the wrong one.) > > Confusingly, if the USB ProductID is 0001, the Tripp Lite specific "Protocol" number (shown in