Ядро & Оборудование
   290

Помогите подключить ИБП Powerman

Друзья всем привет, в общем суть проблемы, никогда до этого с установкой на linux не сталкивался.

Имеем:
UPS PowerMan Back PRO 800 Plus (800VA, USB)
Linux 4.4.24-1-MANJARO 1 SMP PREEMPT Sat Oct 8 07:49:12 UTC 2016 x86_64 GNU/Linux

Подключил по USB
вывод dmesg

[189137.429852] usb 5-1: new low-speed USB device number 3 using xhci_hcd
[189147.577842] usb 5-1: ep 0x81 — rounding interval to 64 microframes, ep desc says 80 microframes
[189147.681887] hid-generic 0003:0001:0000.0008: hiddev0,hidraw4: USB HID v1.00 Device [MEC0003] on usb-0000:06:00.0-1/input0

решил воспользоваться network-ups-tools

PowerMan этих серий RealSmart 800 RealSmart 1000 BackPro работают с драйвером genericups upstype=4
Судя по networkupstools.org/stable-hcl.html

Почитал linuxoid.in/Network_UPS_Tools

изменил под себя
<spoiler cat ups.conf t=«ups.conf»>root@Samoilov ups # cat /etc/ups/ups.conf
# Network UPS Tools: example ups.conf
#
# — SECURITY NOTE — #
# If you use snmp-ups and set a community string in here, you
# will have to secure this file to keep other users from obtaining
# that string. It needs to be readable by upsdrvctl and any drivers,
# and by upsd.
#
# — #
# This is where you configure all the UPSes that this system will be
# monitoring directly. These are usually attached to serial ports, but
# USB devices and SNMP devices are also supported.
#
# This file is used by upsdrvctl to start and stop your driver(s), and
# is also used by upsd to determine which drivers to monitor. The
# drivers themselves also read this file for configuration directives.
#
# The general form is:
#
# [upsname]
# driver =
# port =
#
#
# The section header ([upsname]) can be just about anything as long as
# it is a single word inside brackets. upsd uses this to uniquely
# identify a UPS on this system.
#
# If you have a UPS called snoopy, your section header would be "[snoopy]".
# On a system called «doghouse», the line in your upsmon.conf to monitor
# it would look something like this:
#
# MONITOR snoopy@doghouse 1 upsmonuser mypassword master
#
# It might look like this if monitoring in slave mode:
#
# MONITOR snoopy@doghouse 1 upsmonuser mypassword slave
#
# Configuration directives
# — #
# These directives are common to all drivers that support ups.conf:
#
# driver: REQUIRED. Specify the program to run to talk to this UPS.
# apcsmart, bestups, and sec are some examples.
#
# port: REQUIRED. The serial port where your UPS is connected.
# /dev/ttyS0 is usually the first port on Linux boxes, for example.
#
# sdorder: optional. When you have multiple UPSes on your system, you
# usually need to turn them off in a certain order. upsdrvctl
# shuts down all the 0s, then the 1s, 2s, and so on. To exclude
# a UPS from the shutdown sequence, set this to -1.
#
# The default value for this parameter is 0.
#
# nolock: optional, and not recommended for use in this file.
#
# If you put nolock in here, the driver will not lock the
# serial port every time it starts. This may allow other
# processes to seize the port if you start more than one by
# mistake.
#
# This is only intended to be used on systems where locking
# absolutely must be disabled for the software to work.
#
# maxstartdelay: optional. This can be set as a global variable
# above your first UPS definition and it can also be
# set in a UPS section. This value controls how long
# upsdrvctl will wait for the driver to finish starting.
# This keeps your system from getting stuck due to a
# broken driver or UPS.
#
# The default is 45 seconds.
#
# synchronous: optional. The driver work by default in asynchronous
# mode (i.e *synchronous=no*). This means that all data
# are pushed by the driver on the communication socket to
# upsd (Unix socket on Unix, Named pipe on Windows) without
# waiting for these data to be actually consumed. With
# some HW, such as ePDUs, that can produce a lot of data,
# asynchronous mode may cause some congestion, resulting in
# the socket to be full, and the driver to appear as not
# connected. By enabling the "synchronous' flag
# (value = 'yes'), the driver will wait for data to be
# consumed by upsd, prior to publishing more. This can be
# enabled either globally or per driver.
#
# The default is 'no' (i.e. asynchronous mode) for backward
# compatibility of the driver behavior.
#
# Anything else is passed through to the hardware-specific part of
# the driver.
#
# Examples
# — #
# A simple example for a UPS called «powerpal» that uses the blazer_ser
# driver on /dev/ttyS0 is:
#
# [powerpal]
# driver = blazer_ser
# port = /dev/ttyS0
# desc = «Web server»
#
# If your UPS driver requires additional settings, you can specify them
# here. For example, if it supports a setting of «1234» for the
# variable «cable», it would look like this:
#
# [myups]
# driver = mydriver
# port = /dev/ttyS1
# cable = 1234
# desc = «Something descriptive»
#
# To find out if your driver supports any extra settings, start it with
# the -h option and/or read the driver's documentation.

[powermanwork]
driver = genericups
port = /dev/usb/hiddev0
port = auto
desc = «Archwork»


sudo upsd
Network UPS Tools upsd 2.7.4
fopen /var/state/ups/upsd.pid: No such file or directory
listening on 127.0.0.1 port 3493
listening on ::1 port 3493
Can't connect to UPS [powermanwork] (genericups-powermanwork): No such file or directory

Блин помогите мне может я туплю, или у меня драйвера этого нет. Поискал в ауре и через пакман genericups ничего не нашел. Что делать дальше?

Создал сообщение на форуме archlinux.org.ru/forum/topic/16659/?page=1post-176006
но меня закидали тапками и итоге я написал тут.

1 комментарий

avatar
Возможно Вам поможет мой мануал Подключение ИБП (UPS) через USB и настройка NUT в Porteus правда данная инструкция для другого дистрибутива.
0
Только зарегистрированные и авторизованные пользователи могут оставлять комментарии.