LinuxGuruz
  • Last 5 Forum Topics
    Replies
    Views
    Last post


The Web Only This Site
  • BOOKMARK

  • ADD TO FAVORITES

  • REFERENCES


  • MARC

    Mailing list ARChives
    - Search by -
     Subjects
     Authors
     Bodies





    FOLDOC

    Computing Dictionary




  • Text Link Ads






  • LINUX man pages
  • Linux Man Page Viewer


    The following form allows you to view linux man pages.

    Command:

    usbhid-ups

    
    
    

    NOTE

           This man page only documents the hardware-specific features of the
           usbhid-ups driver. For information about the core driver, see
           nutupsdrv(8).
    
           This driver, formerly called newhidups, replaces the legacy hidups
           driver, which only supported Linux systems.
    
    
    

    SUPPORTED HARDWARE

           usbhid-ups brings USB/HID UPS monitoring to NUT on all platform
           supporting USB through libusb. It should detect any UPS that uses the
           HID power device class, but the amount of data will vary depending on
           the manufacturer and model.
    
           At the present time, usbhid-ups supports:
    
           ?   the newer Eaton USB models,
    
           ?   all MGE USB models,
    
           ?   all Dell USB models,
    
           ?   some APC models,
    
           ?   some Belkin models,
    
           ?   some Cyber Power Systems models.
    
           ?   some TrippLite models
    
           For a more complete list, refer to the NUT hardware compatibility list,
           available in the source distribution as data/drivers.list, or on the
           NUT website. You may use the "explore" driver option to gather
           information from HID UPSes which are not yet supported; see below for
           details.
    
           This driver is known to work on:
    
           ?   most Linux systems,
    
           ?   FreeBSD (beta stage) and maybe other *BSD,
    
           ?   Darwin / Mac OS X,
    
           ?   Solaris 10.
    
    
    

    EXTRA ARGUMENTS

           This driver also supports the following optional settings:
    
           offdelay=num
               Set the timer before the UPS is turned off after the kill power
               command is sent (via the -k switch).
               is (still) out at the moment this timer elapses. In that case, you
               could try if setting ondelay = -1 in ups.conf helps.
    
           pollfreq=num
               Set polling frequency, in seconds, to reduce the USB data flow.
               Between two polling requests, the driver will wait for interrupts
               (aka UPS notifications), which are data changes returned by the UPS
               by itself. This mechanism allow to avoid or reduce staleness
               message, due to the UPS being temporarily overloaded with too much
               polling requests. The default value is 30 (in seconds).
    
           pollonly
               If this flag is set, the driver will ignore interrupts it receives
               from the UPS (not recommended, but needed if these reports are
               broken on your UPS).
    
           vendor=regex, product=regex, serial=regex, vendorid=regex,
           productid=regex
               Select a specific UPS, in case there is more than one connected via
               USB Each option specifies an extended regular expression (see
               regex(7)) that must match the UPS's entire vendor/product/serial
               string (minus any surrounding whitespace), or the whole 4-digit
               hexadecimal code for vendorid and productid. Try -DD for finding
               out the strings to match.
    
               Examples:
    
               ?    -x vendor="Foo.Corporation.*"
    
               ?    -x vendorid=051d* (APC)
    
               ?    -x product=".*(Smart|Back)-?UPS.*"
    
           bus=regex
               Select a UPS on a specific USB bus or group of busses. The argument
               is a regular expression that must match the bus name where the UPS
               is connected (e.g. bus="002", bus="00[2-3]").
    
           explore
               With this option, the driver will connect to any device, including
               ones that are not yet supported. This must always be combined with
               the "vendorid" option. In this mode, the driver will not do
               anything useful except for printing debugging information
               (typically used with -DD).
    
    
    

    INSTALLATION

           This driver is not built by default. You can build it by using
           "configure --with-usb=yes". Note that it will also install other USB
           drivers.
    
           You also need to install manually the legacy hotplug files (libhidups
           and libhid.usermap, generally in /etc/hotplug/usb/), or the udev file
    
               [mge]
                       driver = usbhid-ups
                       port = auto
                       vendorid = 0463
               [tripplite]
                       driver = usbhid-ups
                       port = auto
                       vendorid = 09ae
    
    
    

    KNOWN ISSUES AND BUGS

       Repetitive timeout and staleness
           Some models tends to be unresponsive with the default polling
           frequency. The result is that your system log will have lots of
           messages like:
    
               usb 2-1: control timeout on ep0in
               usb 2-1: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 128 rq 6 len 256
               ret -110
    
           In this case, simply modify the general parameter "pollinterval" to a
           higher value (like 10 for 10 seconds). This should solve the issue.
    
       Got EPERM: Operation not permitted upon driver startup
           You have forgotten to install the hotplug files, as explained in the
           INSTALLATION section above. Don't forget to restart hotplug so that it
           applies these changes.
    
       Unattended shutdowns
           The hardware which was used for development of this driver is almost
           certainly different from what you have, and not all manufacturers
           follow the USB HID Power Device Class specifications to the letter. You
           don't want to find out that yours has issues here when a power failure
           hits your server room and you're not around to manually restart your
           servers.
    
           If you rely on the UPS to shutdown your systems in case of mains
           failure and to restart them when the power returns, you must test this.
           You can do so by running upsmon -c fsd. With the mains present, this
           should bring your systems down and then cycle the power to restart them
           again. If you do the same without mains present, it should do the same,
           but in this case, the outputs shall remain off until mains power is
           applied again.
    
    
    

    AUTHORS

           Originally sponsored by MGE UPS SYSTEMS. Now sponsored by Eaton
           http://opensource.eaton.com Arnaud Quette, Peter Selinger, Arjen de
           Korte
    
    
    

    SEE ALSO

       The core driver
           nutupsdrv(8)
    
  • MORE RESOURCE


  • Linux

    The Distributions





    Linux

    The Software





    Linux

    The News



  • MARKETING






  • Toll Free

webmaster@linuxguruz.com
Copyright © 1999 - 2016 by LinuxGuruz