Drivers Mge Ups
This document describes how to install the Network UPS Tools (NUT). Network UPS Tools is compatible with thousands models of UPS. You can check the Hardware Compatibility List to see if your UPS is supported.
Jul 09, 2009 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. Cannot retrieve contributors at this time. 1570 lines (1388 sloc) 64 KB Raw Blame /. mge-hid.c - data to monitor Eaton / MGE HID (USB and serial) devices. Bridging short and longer power failures up to a period of hours – with the modular SITOP PSU8600 power supply system. The SITOP PSU8600 base units, combined with integrated buffer and DC UPS modules with appropriate battery modules, can be used to protect against power dips on the line side and thus to bridge power failures lasting up to a period of hours.
Installation of Network UPS Tools
You can install network-ups-tools with the nut package.
Configuration

NUT has 3 daemons associated with it:
- The driver which communicates with the UPS.
- A server (upsd) which uses the driver to report out the status of the UPS.
- A monitoring daemon (upsmon) which monitors the upsd server and takes action based on information it receives.
The idea is that if you have multiple systems connected to the UPS, one can communicate the status of the UPS over the network and the others can monitor that status by running their own upsmon services. NUT has extensive documentation on the configuration however this is going to walk through a simple setup of a USB UPS and the associated server and monitor all in one system (common desktop configuration).
Driver configuration
The configuration here will depend on the type of UPS you have. Consult the previously mentioned Hardware Compatibility List to find what driver will likely work for your UPS. You can run the tool nut-scanner(8) which will detect NUT-compatible devices attached to your system.
For many UPS connected by USB, use the usbhid-ups(8) driver.For UPS with serial port, use port=/dev/ttySX
, where X is the number of serial port (Example:/dev/ttyS1). For UPS with USB port, use port=auto
.
You can name the UPS device whatever you like. ups.conf(5)
Start the driver as root with upsdrvctl start
. If there's no errors, you should see a message like this one for the driver usbhid-ups
:
If the driver doesn’t start cleanly, make sure you have picked the right one for your hardware. You might need to try other drivers by changing the 'driver=' value in ups.conf.
Can't claim USB device error
If you receive an error message like this one:
Or a less specific one:
It's most likely a problem with permissions for accessing the device. You can fix that by specifying an udev rule that sets the correct group:
Where idVendor
and idProduct
are the device manufacturer and product ID. You can see these either in the error output [XXXX:YYYY]
or by using lsusb
.
/dev/ups0
when connected).
MODE='0666'
.After this is done, reload and retrigger udev rules by issuing this command:
upsd configuration
By default upsd listens only on localhost and this is fine for our purpose. Though it is not necessary for following this guide, you can configure upsd beyond the defaults by editing /etc/nut/upsd.conf
. See upsd.conf(5).
You will need to add a user for a monitor to connect to the server and issue commands. See upsd.users(5).
At this point you should be able to start/enablenut-server.service
which will automatically start nut-driver.
If it has started successfully, you can run upsc <upsname>
to get information from the UPS. Example output from the command:
upsmon configuration
The last step is to configure upsmon to listen to upsd and take action on events.
Add the following line to /etc/nut/upsmon.conf
:
Here upsname is the name of the UPS, and upsduser and password is the user and its password you set in /etc/nut/upsd.users
.
You can also configure what alerts are sent, where they are sent, what action is taken when the battery is low, and more. See upsmon.conf(5).
Then start/enablenut-monitor.service
.
Your logs should show upsmon starting and monitoring the UPS.
NUT-Monitor
NUT-Monitor is a graphical user interface to monitor and manage devices connected to the Network UPS Tools server.
You can install nut-monitor with the nut-monitorAUR package.
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) |

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.
/etc/nut/nut.conf
Desired settings/etc/nut/ups.conf
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
/etc/nut/ups.conf
Example 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.
/etc/nut/upsd.users
Example upsd.users configuration/etc/nut/upsmon.conf
Create a MONITOR configuration in /etc/nut/upsmon.conf:
/etc/nut/upsmon.conf
Example upsmon configuration/etc/nut/upssched.conf
Configure operations on that upsmon will check on the status of the UPS:
/etc/nut/upssched.conf
Example upssched.conf configuration/usr/bin/upssched-cmd
Mge Ups Usa
/usr/bin/upssched-cmd
Example upssched.conf configurationServices
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.
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
Server configuration
Mge Ups Malaysia
Starting from standalone configuration, change:
Server files
/etc/nut/nut.conf
/etc/nut/nut.conf
Desired settings/etc/nut/upsd.conf
/etc/nut/upsd.conf
Desired settings/etc/nut/upsd.users
Drivers Mge Ups System
/etc/nut/upsd.users
Example upsd.users configuration