similar to: Flushing the report buffer

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

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 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, 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

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

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

On Monday 22 June 2020 15:36:21 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 >

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

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: > >

Hello, the code below the failing part mentions this flavor of protocol, drivers/blazer_ser.c:463 /* * If a command is invalid, it will be echoed back. * As an exception, Best UPS units will report "ACK" in case of success! */ I prepared a patch, it adds a similar check and also checks (in both occurencies) for blazer_command()<0, the latter

On Aug 11, 2013, at 2:12 PM, ????????? ???????? wrote: > I see no problem with how the device communicates the Blazer/Megatec protocol. > I must have found a bug in the driver. It is possible that the shutdown was tested with a different implementation of the protocol. What do you get from the "I" command? On Aug 11, 2013, at 11:25 AM, ????????? ???????? wrote: > So I

Hi Folks, I'm trying to use a ZIGOR Danubio 2000 ups with NUT on Debian squeeze (AMD64). OS/NUT are all the latest official release (as of last week) with NUT installed from packages. As the usb descriptor presents MEC (and the Fry's electronics) I chose to use the blazer_usb driver. All appears to work well excepting that the UPS does not appear to accept the shutdown instcmd to turn

Hi, Lei and I have been working on the project, based on community input. We have implemented two way sync between github and pagure as suggest by many. Now we want build the site and display it to user. There are number of options mkdocs, hugo(docker uses it now) etc. There are pros and cons to each site generator. To use hugo, we need the user to have hugo installed too, and than he needs to

Hi All, I'd like to know what is the best way to organize R code in multiple modules= and files. The R code we are writing is too much for a single file. Besides= , there are a lot of reusable functions we'd like to factor out. But writing= a package for that is quite an over-kill and might be too inflexible. So what is the best way to organize R code into multiple files and reusable=

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:

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, my Atlantis UPS (model on "subject" line) fails to cycle off the outlet power after a power failure on the mains followed by an automatic shutdown of the computer. The UPS simply remains always on, preventing the computer from restarting. ** Setup: ** Nut version 2.7.2 Nut driver blazer_usb Linux 4.1.1 The config files are pretty default; the peculiar customization is

Hello, I recently switch over from Splus to R and I have not been able to generate right axis labels that face inwards. This is accomplished in Splus with the command srt=270 but this option is not supported in R. In addition the par argument las=0 or 3 does not rotate the right axis labels. The editor of a journal is demanding that the right axis labels face inwards in the figures I recently

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi there! I don't know if you are able to help me. Have tried almost everything at this point.. I recently switched from a BlueWalker(Powerwalker?) PW UPS VI2000 LCD 2000VA offline UPS to a BlueWalker(Powerwalker?) PW UPS VFI 1500 LCD 1500VA Online UPS. Seems like the driver is accepting both, however, the shutdown command wont work. And this