search for: omnivsing800

...greater than 0001, the ProductID and Protocol should match. > Your messages in the driver helped me when I initially chose the wrong one and got the usual "Driver Not Connected" error!" > > 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. Thanks > > > You're right, we have a "magic constant" in the "input.voltage" and "output.voltage" calculations for your protocol. > > https://github.com/networkupstools/nut/blob/ma...

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

...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 shown correctly so maybe the OMNIVSING800 just needs 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....

...oductID is 0001, the Tripp Lite specific "Protocol" number (shown in "ups.firmware.aux") is probably not 0001. But if the ProductID is greater than 0001, the ProductID and Protocol should match. > 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. > 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....

...oductID and Protocol should match. >> > Your messages in the driver helped me when I initially chose the wrong > one and got the usual "Driver Not Connected" error!" > >>> 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. > Thanks >> >> >> You're right, we have a "magic constant" in the "input.voltage" and "output.voltage" calculations for your protocol. >> >> https://githu...