Drivers Mge Ups

Name

I do not have an answer for you. However, I can provide you the MGE support number. Contact the MGE support at 800-438-7373(support option 2 for tech support) as they can provide you the management software information to monitor your UPS.

usbhid-ups - Driver for USB/HID UPS equipment

MGE UPS SYSTEMS is a global provider of power quality solutions designed to increase the availability and uptime of mission-critical applications or processes, from a simple desktop PC to a large. Click here to see reports of other supported models from MGE UPS SYSTEMS. When a user reports that a variable/command is not right then it will be highlighted by a red underline. Bad values/ranges/etc will get a red dashed outline or red solid left border. The MGE UPS SYSTEMS Drivers enables high level computer programs to work together with other components. The driver achieves this function by corresponding with the machine it is attached to through the communication subsystem. The driver is centrally controlled by the device manager and it also facilitates in translating data.

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 powerdevice 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,
Drivers Mge Ups
• 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).

The default value is 20 (in seconds). Usually this must be lower than ondelay, but the driver will not warn you upon startup if itisn't.

ondelay=num
Set the timer for the UPS to switch on in case the power returns after the kill power command had been sent but before the actual switch off. This ensuresthe machines connected to the UPS are, in all cases, rebooted after a power failure.

The default value is 30 (in seconds). Usually this must be greater than offdelay, but the driver will not warn you upon startup if it isn't.Some UPS'es will restart no matter what, even if the power 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 overloadedwith 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 yourUPS).
vendor=regex, product=regex, serial=regex, vendorid=regex, productid=regex
PulsarSelect 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 matchthe 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.*'
Drivers Mge 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(nut-usbups.rules, generally in /etc/udev/rules.d/) to address the permission settings problem. For more information, refer to the README file innut/scripts/hotplug or nut/scripts/udev.

On Linux with MGE equipment, you will need at least a 2.4.25 or 2.6.2 kernel as well as libusb-0.1.8 or later to disable hiddev support and avoidconflict.

Implementation

The driver ignores the 'port' value in ups.conf. Unlike previous versions of this driver, it is now possible to control multiple UPS unitssimultaneously with this driver, provided they can be distinguished by setting some combination of the 'vendor', 'product', 'serial', 'vendorid', and'productid' options. For instance:

Known Issues And Bugs

Repetitive timeout and staleness

Got EPERM: Operation not permitted upon driver startup

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 HIDPower 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'renot 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 doso 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 thesame without mains present, it should do the same, but in this case, the outputs shall remain off until mains power is applied again.

Mge Ups Costa Mesa

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

Internet resources

Drivers Mge Ups System(8),tripplite(8),tripplite_usb(8),tripplitesu(8)
Home
GitHub

Do you have a UPS? Do you want to have you system gracefully shutdown in case of a power outage? This guide will show how you can make the most out of your UPS by using NUT from the Network UPS Tools project

Installation

USE flag

To connect a UPS via USB, make sure to set the usb USE flag:

cgi Add CGI script support
ipmi Support IPMI-based UPSes.
selinux !!internal use only!! Security Enhanced Linux support, this must be set by the selinux profile or breakage will occur
snmp Add support for the Simple Network Management Protocol if available
split-usr Enable behavior to support maintaining /bin, /lib*, /sbin and /usr/sbin separately from /usr/bin and /usr/lib*
ssl Add support for SSL/TLS connections (Secure Socket Layer / Transport Layer Security)
tcpd Add support for TCP wrappers
ups_drivers_al175 Driver for Eltek UPS models with AL175 alarm module
ups_drivers_apcsmart Driver for American Power Conversion Smart Protocol UPS equipment
ups_drivers_apcsmart-old Driver for American Power Conversion Smart Protocol UPS equipment
ups_drivers_apcupsd-ups Driver for apcupsd client access
ups_drivers_bcmxcp Driver for UPSes supporting the serial BCM/XCP protocol
ups_drivers_bcmxcp_usb Experimental driver for UPSes supporting the BCM/XCP protocol over USB
ups_drivers_belkin Driver for Belkin serial UPS equipment
ups_drivers_belkinunv Driver for Belkin 'Universal UPS' and compatible
ups_drivers_bestfcom Driver for Best Power Fortress/Ferrups
ups_drivers_bestfortress Driver for old Best Fortress UPS equipment
ups_drivers_bestuferrups Driver for Best Power Micro-Ferrups
ups_drivers_bestups Driver for Best Power / SOLA (Phoenixtec protocol) UPS equipment
ups_drivers_blazer_ser Driver for Megatec/Q1 protocol serial based UPS equipment
ups_drivers_blazer_usb Driver for Megatec/Q1 protocol USB based UPS equipment
ups_drivers_clone Fake driver to clone outlets for device grouping
ups_drivers_clone-outlet Fake driver to clone outlets for device grouping
ups_drivers_dummy-ups Driver for multi-purpose UPS emulation
ups_drivers_etapro Driver for ETA UPS equipment
ups_drivers_everups Driver for Ever UPS models
ups_drivers_gamatronic Driver for Gamatronic UPS equipment
ups_drivers_genericups Driver for contact-closure UPS equipment
ups_drivers_isbmex Driver for ISBMEX UPS equipment
ups_drivers_ivtscd driver for the IVT Solar Controller Device
ups_drivers_liebert Driver for Liebert contact-closure UPS equipment
ups_drivers_liebert-esp2 Driver for Liebert UPS, using the ESP-II serial protocol
ups_drivers_masterguard Driver for Masterguard UPS equipment
ups_drivers_metasys Driver for Meta System UPS equipment
ups_drivers_mge-shut Driver for SHUT Protocol UPS equipment
ups_drivers_mge-utalk Driver for MGE UPS SYSTEMS UTalk protocol equipment
ups_drivers_microdowell Driver for Microdowell Enterprise UPS series
ups_drivers_netxml-ups Driver for Eaton / MGE Network Management Card / Proxy (XML/HTTP Protocol) equipment
ups_drivers_nut-ipmipsu Driver for IPMI Power Supply Units (PSU)
ups_drivers_nutdrv_qx Driver for Q* protocol serial and USB based UPS equipment
ups_drivers_oldmge-shut Driver for SHUT Protocol UPS equipment (older implementation)
ups_drivers_oneac Driver for Oneac UPS equipment
ups_drivers_optiups Driver for Opti-UPS (Viewsonic) UPS and Zinto D (ONLINE-USV) equipment
ups_drivers_powercom UPS driver for serial Powercom/Trust/Advice UPS equipment
ups_drivers_powerpanel Driver for PowerPanel Plus compatible UPS equipment
ups_drivers_rhino Driver for Brazilian Microsol RHINO UPS equipment
ups_drivers_richcomm_usb Driver UPS equipment using Richcomm dry-contact to USB solution
ups_drivers_riello_ser Driver for Riello UPS Protocol UPS equipment
ups_drivers_riello_usb Driver for Riello UPS Protocol UPS equipment via USB
ups_drivers_safenet Driver for SafeNet compatible UPS equipment
ups_drivers_snmp-ups Multi-MIB Driver for SNMP UPS equipment
ups_drivers_solis Driver for Brazilian Microsol SOLIS UPS equipment
ups_drivers_tripplite Driver for Tripp-Lite SmartPro UPS equipment
ups_drivers_tripplite_usb Driver for older Tripp Lite USB UPSes (not PDC HID)
ups_drivers_tripplitesu Driver for Tripp-Lite SmartOnline (SU) UPS equipment
ups_drivers_upscode2 Driver for UPScode II compatible UPS equipment
ups_drivers_usbhid-ups Driver for USB/HID UPS equipment
ups_drivers_victronups Driver for IMV/Victron UPS unit Match, Match Lite, NetUps
usb Add USB support to applications that have optional USB support (e.g. cups)
xml Add support for XML files
zeroconf Support for DNS Service Discovery (DNS-SD)
Data provided by the Gentoo Package Database · Last update: 2020-09-20 14:38 More information about USE flags

Emerge

Configuration standalone

Search a UPS with nut-scanner:

Take note of driver name and port type for configuration file.

If UPS is connected via USB port, add user nut to group usb.

Files

/etc/nut/nut.conf

Set mode to standalone if the machine is connected to the UPS directly and to run NUT on this machine.

FILE/etc/nut/nut.confDesired settings

/etc/nut/ups.conf

Drivers Mge Ups Systems

The main UPS configuration file. Make sure that the UPS name (the text in the brackets) doesn't have any spaces. For configuration specific to the UPS you need to look it up here: NUT Hardware Compatibility Lookup

FILE/etc/nut/ups.confExample ups.conf configuration

/etc/nut/upsd.users

Configure at least one user so that upsmon can be launched later. upsd will create a TCP connection that upsmon will use to check on the status of the UPS.

FILE/etc/nut/upsd.usersExample upsd.users configuration

/etc/nut/upsmon.conf

Create a MONITOR configuration in /etc/nut/upsmon.conf:

FILE/etc/nut/upsmon.confExample upsmon configuration

/etc/nut/upssched.conf

Configure operations on that upsmon will check on the status of the UPS:

FILE/etc/nut/upssched.confExample upssched.conf configuration

/usr/bin/upssched-cmd

FILE/usr/bin/upssched-cmdExample upssched.conf configuration

Services

OpenRC

To add the services to start on system boot:

root #rc-update add upsd default

To start upsd now run:

root #rc-service upsd start

To check the status of the UPS manually (adjust the UPS name as needed):

OL means that the UPS is 'online' and not drawing from the battery and is configured correctly.

Drivers Mge Ups

In the event of a shutdown due to a power failure, nut can additionally turn off the UPS by adding nut.powerfail to the shutdown runlevel:

LAN client/server configuration

Mge Ups Pulsar

Server configuration

Starting from standalone configuration, change:

Server files

/etc/nut/nut.conf
FILE/etc/nut/nut.confDesired settings
/etc/nut/upsd.conf

Drivers Mge Ups System

FILE/etc/nut/upsd.confDesired settings

Mge Pulsar Ex30 Manual

/etc/nut/upsd.users
FILE/etc/nut/upsd.usersExample upsd.users configuration