similar to: shutdown.* and load.*, and how to possibly add more instcmd for bcmxcp

Hi Inspired by the changes by Prachi Gandhi to use the command map from the UPS in the bcmxcp driver, I think the map should be used, if available, to control all commands the driver adds using "dstate_addcmd". The following patch is an attempt at doing so. The patch is against the bcmxcp branch. Since my UPS also supports : #define PW_UPS_ON (unsigned char)0x89 /* UPS on

While working on the mge-hid subdriver, I wanted to add the 'beeper.mute' command. Unfortunately, the description I intended to use was used already by the 'beeper.off' instcmd: CMDDESC beeper.off "Temporarily mute the UPS beeper" Now of course we could add another instcmd 'beeper.reallyoff', but instead I would prefer to bite the buller and do the following:

Hi Here is a very minor patch for the bcmxcp.c driver, mainly fixing the function name used in debug statement, and at the same time fix indentation. Regards Alf Hogemark From 86c7940d0ea11b5b38a7f4518095ee2428d658c7 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Alf=20H=C3=B8gemark?= <alf at i100.no> Date: Mon, 1 Jul 2013 21:11:40 +0200 Subject: [PATCH] bcmxcp: Fix method name outputted in

Hi, I can't find a nice way to solve a problem. So if you have some ideas I would be greatfull. This is the problem. I can ask a bcmxcp ups what commands it support, if the firmware is after revision AE. I was thinking about to use this in the driver. For example ' a ups that don't support battery_test would not have this command enabled.' The hex responce look like this from

The meter map is basically a bitmap that indicates what variables are output (and in what format) by the UPS. You will likely see a variable, 'not mapped' or nothing. The variables and 'not mapped' items are output by the UPS in the measurement block, and the map tells nut how to read it. 'Unmapped' means that there is a variable there that nut is ignoring, and the xcp

On Jul 2, 2013, at 5:16 PM, Kjell Claesson wrote: >> I hope other people can also test this. >> >> Regards >> Alf Hogemark > > Due to some crashes on the disks and lack of time I don't have the git on the > pc now. But maybe some other can commit this. I'd like to ask people to specifically try the bcmxcp branch on GitHub - it includes some changes

On 10/14/2015 10:17 AM, Roger Price wrote: > What does "ps aux | grep ups" report? ps aux | grep ups nut 2902 0.0 0.0 20588 1140 ? Ss 00:10 0:02 /lib/nut/nutdrv_qx -a myups nut 2946 0.0 0.0 37632 1428 ? Ss 00:10 0:00 /lib/nut/upsd root 2970 0.0 0.0 37616 1436 ? Ss 00:10 0:00 /lib/nut/upsmon root 2973

Device manufacturer: Fideltronik INIGO Device name: Viper 1200 Device type: UPS Bus type: USB WWW: http://fideltronikinigo.com/viper/viper-1200/ " nut-scanner -U" output: [nutdev1] driver = "blazer_usb" port = "auto" vendorid = "0001" productid = "0000" product = "MEC0003" vendor =

It seems that the UPS I wrote in my previous mail uses the Megatec protocol, but does not support the S<n>R<m> "Shut Down and Restore" Command. This means that the server will shut down cleanly, but it will not boot automatically when the utility power comes back. There is another shutdown command according to the protocol description, although I do not really understand the

Hi, They say one should never argue with people that know more than you, so please bear with me. On 2013/10/24 09:47 PM, hyouko at gmail.com wrote: > The driver is expecting either 'ACK' or no reply at all in case of > success and the command itself echoed back in case of errors. > On the other hand, your UPS replies '(ACK' in case of success and > '(NAK' on

Hello, we have a problem using APC Back-UPS CS 500 (connected via USB, usbhid-ups-apc) and UPS-NUT. We've tried different Versions of UPS-NUT (2.2.1 and 2.2.2), including the latest from SVN (28th November 2008). We've also tried apcupsd, which works fine for our requirements, but we don't want use it. What we need is simple: The UPS should turn off after power loss and shutdown

On Jun 22, 2020, at 3:36 PM, Charles Lepple wrote: > > On Jun 22, 2020, at 1:26 PM, Gene Heskett wrote: >> >> So I just edited /etc/nut/upsd.users to add both the commands it claims >> to have but get this response to either: > > In your original example, you had multiple “instcmd =“ lines for one user- I think the allowed commands all need to be listed on one

On Wed, 14 Oct 2015, Davide Baldini wrote: > upsdrvctl shutdown > ... > instcmd(shutdown.return, [NULL]) > instcmd: FAILED > Shutdown failed! > Driver failed to start (exit status=1) > > This time /var/log/syslog doesn't register anything about the UPS after > issuing the command above. Instead, It logged some errors after a > upscmd -u admin -p mypass

Hello world! Please, help me :-) I have a APC RS-800 usb and it don't shutdown. I try every things but nothing: don't shutdown. Uhmmmm My actual situation: tux:/home/effem# uname -a Linux tux 2.6.26-1-686 #1 SMP Wed Aug 20 12:56:41 UTC 2008 i686 GNU/Linux tux:/home/effem# wajig policy nut nut: Installato: 2.2.2-6 Candidato: 2.2.2-6 Tabella versione: 2.2.2-7 0 -20

Hi, This patch adds a BSD compatible install script (copied from gcc-2.95.2) to 1.2pre14. The script has a X-style license. The script will be used if configure doesn't find a proper install program on the system. Remember to run autoconf and set execute (755) permissions for install-sh when the patch has been applied. -- Niels Kristian Bech Jensen -- nkbj at image.dk --

Hello list, first of all, I'd like to report that my UPS N-Power MEV-3000LT (http://www.380v.ru/catalogue/micro-ups/mega-vision , in Russian), which is not in the hardware compatibility list, is mostly supported by the blazer_ser driver. I have very strong grounds to believe that this (and other) N-Power UPS'es are rebranded for Russian and Italian markets from their counterparts

Hi Johan, The driver is expecting either 'ACK' or no reply at all in case of success and the command itself echoed back in case of errors. On the other hand, your UPS replies '(ACK' in case of success and '(NAK' on failure. So.. when the driver first tries to stop pending shutdowns and you get the 'operation not permitted' error, the driver interprets it as a

Hi, There seems to be a problem turning of the inverter on a Mecer online 1000VA UPS. OS: Debian Wheezy Nut: Installed via apt - version 2.6.4-2.3 Debug output from driver. root at proxmox1:~# /lib/nut/blazer_usb -DDDDD -a mecer -k Network UPS Tools - Megatec/Q1 protocol USB driver 0.08 (2.6.4) 0.000000 send_to_all: SETINFO driver.parameter.port "auto" 0.000023

On Monday 22 June 2020 18:50:25 Gene Heskett wrote: > On Monday 22 June 2020 18:03:16 Charles Lepple wrote: > > On Jun 22, 2020, at 3:36 PM, Charles Lepple wrote: > > > On Jun 22, 2020, at 1:26 PM, Gene Heskett wrote: > > >> So I just edited /etc/nut/upsd.users to add both the commands it > > >> claims to have but get this response to either: > >