search for: blazer_command

Displaying 7 results from an estimated 7 matches for "blazer_command".

2013 Aug 11
1
N-Power MEV-3000LT compatibility report and problem
...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 condition indicates a communication error). I have yet no chance to try it, I have a RAID controller which does a live rebuild and I find too risky to combine my experimentation with this operation. Once rebuild is finished I will try and if no other problems found will send the...
2013 Oct 25
1
Shutdown problem with Mecer 1000VA Online UPS
...es to cancel the pending shutdown, a "(NAK" is sent, and not a 'operation not permitted' error. In any case, this is 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...
2013 Aug 11
0
N-Power MEV-3000LT compatibility report and problem
...>Probably best to delay adding this to the HCL until we can get the driver to shut down the UPS properly. I debugged the problem. From the source, drivers/blazer.c:418 /* * 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 ba...
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 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
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
2013 Dec 07
0
[nut] Ippon response length fix (#80)
On Dec 7, 2013, at 5:43 AM, Denis Yantarev wrote: > Ippon Back Power Pro responses are always padded to 64 bytes beyond \r payload terminator. When checking that command was successful (i.e. not echoed back) code relies on the response length reported by blazer_command which will always be 64. To fix this ippon_command should return actual payload length. This change also affects blazer_rating. Currently it assumes that battery voltage should be in %06.2f format, but in reality (and according to documentation) it may also look like %05.2f. > > You can merg...