search for: omnivsint80

> > > OMNIVS1000 USB (older; product ID: 0001) is shown correctly so maybe > > > the OMNIVSING800 just needs to be added to the list next to it. > > > > Will do. Don't see the model in the compatibility web page yet at http://www.networkupstools.org/stable-hcl.html. Am I missing something? Dave

On Sep 26, 2014, at 8:31 AM, Dave Williams <dave at opensourcesolutions.co.uk> wrote: > On 08:09, Fri 26 Sep 14, Charles Lepple wrote: >> Well, I ended up linking to the latest version of those files, so this shows the change better: >> >> https://github.com/networkupstools/nut/commit/f61edb5161de97944074867832edc014323340b1 >> >> Still a magic constant,

On 08:09, Fri 26 Sep 14, Charles Lepple wrote: > Well, I ended up linking to the latest version of those files, so this shows the change better: > > https://github.com/networkupstools/nut/commit/f61edb5161de97944074867832edc014323340b1 > > Still a magic constant, but now it has the nominal voltage factored in. Just building your latest code now. Which commit is this in (just to

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.) >> >>

...V Rules are showing it correctly when decoding the USB ID as above. > > Seems to work as far as I have tested so far but upsc reports: > > upsc reports > battery.charge: 100 > battery.voltage: 14.56 > battery.voltage.nominal: 12 > device.mfr: Tripp Lite > device.model: OMNIVSINT800 > device.type: ups > driver.name: tripplite_usb > driver.parameter.pollinterval: 2 > driver.parameter.port: auto > driver.version: 2.6.4 > driver.version.internal: 0.20 > input.voltage: 124.00 <============ WRONG > input.voltage.nominal: 230 > output.voltage: 12...

...eeds to be added to the list next to it. UDEV Rules are showing it correctly when decoding the USB ID as above. Seems to work as far as I have tested so far but upsc reports: upsc reports battery.charge: 100 battery.voltage: 14.56 battery.voltage.nominal: 12 device.mfr: Tripp Lite device.model: OMNIVSINT800 device.type: ups driver.name: tripplite_usb driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.version: 2.6.4 driver.version.internal: 0.20 input.voltage: 124.00 <============ WRONG input.voltage.nominal: 230 output.voltage: 120.0 <============ WRONG ups.debug.lo...

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