Displaying 7 results from an estimated 7 matches for "stat_instcmd_fail".
Did you mean:
stat_instcmd_failed
2013 Oct 25
1
Shutdown problem with Mecer 1000VA Online UPS
...s actually considered to be a success by the code.
This is not right.
Code as follows:
418 /*
419 * If a command is invalid, it will be echoed back
420 */
421 if (blazer_command(buf, buf, sizeof(buf)) > 0) {
422 upslogx(LOG_ERR, "instcmd: command [%s] failed", cmdname);
423 return STAT_INSTCMD_FAILED;
424 }
425
426 upslogx(LOG_INFO, "instcmd: command [%s] handled", cmdname);
427 return STAT_INSTCMD_HANDLED;
As far as I understand the code line 421 tries to test for a 'comms failure' (e.g. driver disconnection) or any return string. I also suspect that comms failures are ne...
2013 Aug 11
1
N-Power MEV-3000LT compatibility report and problem
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
2013 Oct 24
0
Shutdown problem with Mecer 1000VA Online UPS
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
2013 Oct 24
2
Shutdown problem with Mecer 1000VA Online UPS
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
2011 Mar 05
19
[RFC apcsmart V3 00/18] apcsmart driver updates
Sorry for a bit longer delay than I anticipated, I was stuffed with the work.
This is the next iteration of the patch adding some functionality to apcsmart
driver, and relying on 'ignorelb' recently added.
Follow up from previous thread:
http://www.mail-archive.com/nut-upsdev at lists.alioth.debian.org/msg02331.html
Main differences is that V3 is split into many small patches, so the
2013 Aug 11
0
N-Power MEV-3000LT compatibility report and problem
.../*
* If a command is invalid, it will be echoed back
*/
if (blazer_command(buf, buf, sizeof(buf)) > 0) {
upslogx(LOG_ERR, "instcmd: command [%s] failed", cmdname);
return STAT_INSTCMD_FAILED;
}
I see the following differences from the protocol implemented in the driver.
1. Instead of echoing back the command on failure, the UPS does the following:
a. Returns " \r" (space, then CR) if the command was not recognized.
This is where echo is expected.
b....
2013 Aug 11
2
N-Power MEV-3000LT compatibility report and problem
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