search for: omnivs800

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 shown correctly so maybe the OMNIVSING800 just needs to be added to the list next to it. UDEV Rules are showing it correctly...

...ms <dave at opensourcesolutions.co.uk> wrote: > 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). 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 t...

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

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.) >> >> Confusingly, if the USB ProductID is 0001, the Tripp Lite specific "Protocol"...