Hello,
Does anyone know how I can establish communication between IPFIRE and the MD-30001 UPS?
The UPS has RS232, USB and a network card.
Simply connecting via USB does not seem to work, the log window only shows that it is connected.
I would rather prefer a network solution, as the IPFIRE does not have to be so close to the UPS. 
I have my UPS setup on ipfire .
And have APCUPSD on setup on ipfire
as a network server.
My NAS is setup with APCUPSD
to use the ipfire net server as a UPS.
Works fine.
You could do it the other way around.
May be possible with nut?
Don’t know if your UPS is supported by either program? Can’t find your model.
Or maybe the correct UPS type name is MD-3000I
Below is a link to the manual of MD-3000I
Edit:
The link has changed but the instructions are still available on the seller’s product page.
Instead of a link, I have attached a compressed user manual for UPS
MD-3000I.zip (3,0 MB)
Here is some links.
http://www.apcupsd.org/manual/#supported-upses-and-cables
If you are installing your UPS on a server or desktop. Install apcupsd and configure
to be network server.
Then install apcupsd on ipfire and configure
It to use your network server.
Not sure if your device is compatible.
So install UPS first.
apcupsd or nut.
There is a chance it is not supported by Linux at all.
Looks like the manufacture has proprietary software for Linux and Windows.
Hopefully will work with apcupsd or nut.
Hi,
Reading the conf file should provide you all details you need!
Example:
USB: you need to copy the cable model (written on the USB cable!!) or a close one on the /etc/apcupsd/apcupsd.conf
I use cable 940-0127D but that is not supported by apcupsd so I used a close one from the list in the CFG file - see below that list
# UPSCABLE <cable>
# Defines the type of cable connecting the UPS to your computer.
#
# Possible generic choices for <cable> are:
# simple, smart, ether, usb
#
# Or a specific cable model number may be used:
# 940-0119A, 940-0127A, 940-0128A, 940-0020B,
# 940-0020C, 940-0023A, 940-0024B, 940-0024C,
# 940-1524C, 940-0024G, 940-0095A, 940-0095B,
# 940-0095C, 940-0625A, M-04-02-2000
# My cable is 940-0127D !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
UPSCABLE 940-0127A
UPSTYPE usb
DEVICE
for Network, you must use in /etc/apcupsd/apcupsd.conf the examples provided for this case.
I use one IPFire to connect to UPS and all the rest machines that are powerd from SAME UPS use the port 3551 the APCUPSD from IPFire → all other machines know from IPFire when UPS is on battery.
# UPSCABLE <cable>
# Defines the type of cable connecting the UPS to your computer.
#
# Possible generic choices for <cable> are:
# simple, smart, ether, usb
#
# Or a specific cable model number may be used:
# 940-0119A, 940-0127A, 940-0128A, 940-0020B,
# 940-0020C, 940-0023A, 940-0024B, 940-0024C,
# 940-1524C, 940-0024G, 940-0095A, 940-0095B,
# 940-0095C, 940-0625A, M-04-02-2000
UPSCABLE ether
# To get apcupsd to work, in addition to defining the cable
# above, you must also define a UPSTYPE, which corresponds to
# the type of UPS you have (see the Description for more details).
# You must also specify a DEVICE, sometimes referred to as a port.
# For USB UPSes, please leave the DEVICE directive blank. For
# other UPS types, you must specify an appropriate port or address.
#
# UPSTYPE DEVICE Description
# apcsmart /dev/tty** Newer serial character device, appropriate for
# SmartUPS models using a serial cable (not USB).
#
# usb <BLANK> Most new UPSes are USB. A blank DEVICE
# setting enables autodetection, which is
# the best choice for most installations.
#
# net hostname:port Network link to a master apcupsd through apcupsd's
# Network Information Server. This is used if the
# UPS powering your computer is connected to a
# different computer for monitoring.
#
# snmp hostname:port:vendor:community
# SNMP network link to an SNMP-enabled UPS device.
# Hostname is the ip address or hostname of the UPS
# on the network. Vendor can be can be "APC" or
# "APC_NOTRAP". "APC_NOTRAP" will disable SNMP trap
# catching; you usually want "APC". Port is usually
# 161. Community is usually "private".
#
# netsnmp hostname:port:vendor:community
# OBSOLETE
# Same as SNMP above but requires use of the
# net-snmp library. Unless you have a specific need
# for this old driver, you should use 'snmp' instead.
#
# dumb /dev/tty** Old serial character device for use with
# simple-signaling UPSes.
#
# pcnet ipaddr:username:passphrase:port
# PowerChute Network Shutdown protocol which can be
# used as an alternative to SNMP with the AP9617
# family of smart slot cards. ipaddr is the IP
# address of the UPS management card. username and
# passphrase are the credentials for which the card
# has been configured. port is the port number on
# which to listen for messages from the UPS, normally
# 3052. If this parameter is empty or missing, the
# default of 3052 will be used.
#
# modbus /dev/tty** Serial device for use with newest SmartUPS models
# supporting the MODBUS protocol.
# modbus <BLANK> Leave the DEVICE setting blank for MODBUS over USB
# or set to the serial number of the UPS to ensure
# that apcupsd binds to that particular unit
# (helpful if you have more than one USB UPS).
#
UPSTYPE net
DEVICE <UPS IP ADDRESS>:<UPS PORT>
# POLLTIME <int>
# Interval (in seconds) at which apcupsd polls the UPS for status. This
# setting applies both to directly-attached UPSes (UPSTYPE apcsmart, usb,
# dumb) and networked UPSes (UPSTYPE net, snmp). Lowering this setting
# will improve apcupsd's responsiveness to certain events at the cost of
# higher CPU utilization. The default of 60 is appropriate for most
# situations.
POLLTIME 30
If the UPS has a network card, then you can also try communicating over the network using the SNMP protocol.
Looking at the description/manual of your multimatic md-3000i reveals that your UPS network card is a SNMP card ( as shown by @tphz ).
Therefore you should configure apcupsd according this, UPSTYPE snmp( see at @hjkl 's post above ).
Hello,
it is indeed a MD-3000I from Multimatic, my fault (mole :).
the link to the manual of the MD-3000I is unfortunately not / more.
I did not find the part in the hardware compatibility list.
The network card is the CS121BSC.
It provides me with these interfaces:
So SNMP would be one way.
So the UPS becomes master and all other devices slave.
Let’s see what will happen.
After all, different systems have to be used:
Regards
Finally time to do something again.
Apcupsd is installed and running.
The IPFire should only send an email when the UPS switches to battery power and back and whether the connection to the UPS is established, nothing more.
In the /etc/apcupsd/apcupsd.conf I have entered the following.
UPSTYPE snmp
DEVICE 192.168.2.102:161:APC:private
Now the question is which values I still need to realise this.
The display is not the most important thing as I can view the values from the UPS in the web browser.
Snmp versions 2 and 3 are available, which one should I take?
Thank you.
Translated with DeepL Translate: The world's most accurate translator (free version)
Things are moving.
But what next?
Ideal would be the reaction to snmp traps from the USV.
However, it would be sufficient if the IpFire read out the values and reacted to them.
How do I find out if there is any communication with the UPS at all?
It runs !!!
Why are there still the choices APC, RFC and MGE which do not lead to any success.
JUST LEAVE THEM OUT !!!
UPSTYPE snmp
DEVICE 192.168.2.102:161::private
