table of contents
RIELLO_USB(8) | NUT Manual | RIELLO_USB(8) |
NAME¶
riello_usb - Driver for Riello UPS Protocol UPS equipment via USB
SYNOPSIS¶
riello_usb -h
riello_usb -a UPS_NAME [OPTIONS]
Note
This man page only documents the hardware-specific features of the riello_usb driver. For information about the core driver, see nutupsdrv(8).
SUPPORTED HARDWARE¶
riello_usb supports all recent Riello UPS with USB.
Older Riello UPS products are not supported.
EXTRA ARGUMENTS¶
port = string
Note
This could be a device filesystem path like /dev/usb/hiddev0 but current use of libusb API precludes knowing and matching by such identifiers. They may also be inherently unreliable (dependent on re-plugging and enumeration order). At this time the actual value is ignored, but syntactically some port configuration must still be there.
It is possible to control multiple UPS units simultaneously by running several instances of this driver, provided they can be uniquely distinguished by setting some combination of the vendor, product, vendorid, productid, serial, bus and/or device options detailed below. For devices or operating systems that do not provide sufficient information, the allow_duplicates option can be of use (limited and risky!)
vendorid = regex, productid = regex, vendor = regex, product = regex, serial = regex
Try lsusb(8) or running this NUT driver with -DD command-line argument for finding out the strings to match.
Examples:
bus = regex
device = regex
Note
device numbers are not guaranteed by the OS to be stable across re-boots or device re-plugging.
busport = regex
Note
this option is not practically supported by some NUT builds (it should be ignored with a warning then), and not by all systems that NUT can run on.
allow_duplicates
Normally the driver initialization would abort at this point claiming "Resource busy" or similar error, assuming that the otherwise properly matched device is unique — and some other process already handles it.
Warning
This feature is inherently non-deterministic! The association of driver instance name to actual device may vary between runs!
If you only care to know that at least one of your no-name UPSes is online, this option can help.
If you must really know which one, it will not!
usb_set_altinterface = bAlternateSetting
usb_config_index, usb_hid_rep_index, usb_hid_desc_index, usb_hid_ep_in, usb_hid_ep_out
As a rule of thumb for usb_hid_desc_index discovery, you can see larger wDescriptorLength values (roughly 600+ bytes) in reports of lsusb or similar tools.
EXTRA ARGUMENTS¶
You may need to tweak some settings, depending on the make and model of your UPS (see ups.conf(5)):
localcalculation
You may want to also configure default.battery.voltage.low and default.battery.voltage.high in case the built-in default range (from 10.7V to 12.9V) does not match your hardware, or give a shot to default.battery.voltage.nominal (e.g. 24) if your device does not serve that either.
Note
Lead (PbAc) battery charge graph is not linear, so guesstimated charge value may not be perfectly accurate. However it should be good enough to determine battery actual status and roughly estimate the time it can power the system.
Warning
This keyword may be deprecated in future releases of the driver, in favor of runtimecal and other settings which it requires (as seen in nutdrv_qx(8), blazer_ser(8) and blazer_usb(8) drivers).
AUTHOR¶
Massimo Zampieri
SEE ALSO¶
Related drivers¶
The core driver¶
Internet resources¶
The NUT (Network UPS Tools) home page: https://www.networkupstools.org/
09/29/2024 | Network UPS Tools 2.8.2 |