search for: usbpcap

...box in order to try and figure out what is wrong, but I am not expert enough to figure out what. > > On my NAS box there is no implementation of lsusb or usbdevs, which is rather annoying? > On my SuSE 12.2 running under a VM lsusb fails trying to get the descriptors. > Windows XP and usbpcap appear to happily read the UPSs device descriptors, and finally? > SuSE Live CD (i.e. not under a VM) gets the following output (again apparently reading the descriptor OK) > [moved to attachment] > ?and finally > > Trying to start /usr/local/libexec/nut/usbhid-ups ?a ups ?DDDD...

Hello Charles, Thank you for your reply. For the discrete value thing, this morning I did try to run sudo upsrw -s input.transfer.low=x -u * -p * ups I changed "x" value from 60 to 96 then checked upsc result. All the script return OK but only 84 and 96 got picked up and working. Out model is Eaton 3S 500. And in windows it has a Eaton Personal Solution Pac. In Battery transfer

...ox in order to try and figure out what is wrong, but I am not expert enough to figure out what. > > On my NAS box there is no implementation of lsusb or usbdevs, which is > rather annoying. On my SuSE 12.2 running under a VM lsusb fails trying to get the descriptors. > Windows XP and usbpcap appear to happily read the UPSs device > descriptors, and finally. SuSE Live CD (i.e. not under a VM) gets the > following output (again apparently reading the descriptor OK) > [moved to attachment] > .and finally > > Trying to start /usr/local/libexec/nut/usbhid-ups -a ups...

On Jun 5, 2014, at 10:53 PM, Charles Lepple wrote: > As you have seen, the "default.*" and "overwrite.*" names are not actual variables: they are configuration options to change what is returned from upsc. That is why you get VAR-NOT-SUPPORTED. typo; should have been "override.*" -- Charles Lepple clepple at gmail