search for: stat_instcmd_handl

...} @@ -179,12 +196,26 @@ { /* You do realize this will kill power to ourself. Would probably only * be useful for killing power for a slave computer */ + if ( testvar(OPTI_ZINTO) ) + { + optiquery( "Ct1" ); + optiquery( "Cs0000000" ); + sleep(2); + return STAT_INSTCMD_HANDLED; + } optiquery( "Ct0" ); optiquery( "Cs00000000" ); return STAT_INSTCMD_HANDLED; } else if (!strcasecmp(cmdname, "load.on")) { + if ( testvar(OPTI_ZINTO) ) + { + optiquery( "Ct1" ); + optiquery( "Cu0000000&quo...

Dear Andreas, some googling revealed, you created a driver for the xanto series of online-usv.de. In what state it is currently? I've to manage a S2000 and would like to use nut for it, is it usable by now? Do you need another tester? TIA, Pete

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

...urns the number of octets received). And the calling function doesn't attempt to continue, drivers/blazer.c:777 void upsdrv_shutdown(void) { int retry; for (retry = 1; retry <= MAXTRIES; retry++) { if (blazer_instcmd("shutdown.stop", NULL) != STAT_INSTCMD_HANDLED) { continue; } if (blazer_instcmd("shutdown.return", NULL) != STAT_INSTCMD_HANDLED) { continue; } fatalx(EXIT_SUCCESS, "Shutting down in %d seconds", offdelay);...

...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 negative numbers. Should the test not be "!= 0". What is clear though is that the code does not try to check...

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

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

...h this program; if not, write to the Free Software * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA * */ #include "newhidups.h" #include "powercom-hid.h" #include "extstate.h" /* for ST_FLAG_STRING */ #include "dstate.h" /* for STAT_INSTCMD_HANDLED */ #include "main.h" /* for getval() */ #include "common.h" #define POWERCOM_HID_VERSION "Powercom HID 0.1" #define POWERCOM_VENDORID 0x0d9f /* --------------------------------------------------------------- */ /* Vendor-specific usage table */ /* --...

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

.../* Ensure "ups.start.auto" is set to "yes", if supported */ if (dstate_getinfo("ups.start.auto")) { setvar("ups.start.auto", "yes"); } ret = instcmd("load.on.delay", dstate_getinfo("ups.delay.start")); if (ret != STAT_INSTCMD_HANDLED) { return ret; } return instcmd("load.off.delay", dstate_getinfo("ups.delay.shutdown")); } My understanding of this code is that it attempts to set the load.on.delay control. If that works, it then uses load.off.delay to schedule a shutdown. My unit has nothing...

...m */ /* OFF will powercycle when line power is available again */ } static int instcmd (const char *cmdname, const char *extra) { const char *p; if (!strcasecmp(cmdname, "load.off")) { printf ("powering off\n"); autorestart (0); upssend ("OFF1\r"); return STAT_INSTCMD_HANDLED; } else if (!strcasecmp(cmdname, "shutdown.return")) { p = dstate_getinfo ("ups.delay.shutdown"); if (!p) p = "1"; printf ("shutdown in %s seconds\n", p); autorestart (1); upssend ("OFF%s\r", p); return STAT_INSTCMD_HANDLED; } upsl...

Hi, Charles. Are you by any chance planning to address my problems where NUT does not know how to schedule a shutdown of this Tripp-Lite UPS? If not, could you point me in the right direction? My best understanding of the situation of the moment is that the right control is UPS.OutletSystem.Outlet.DelayBeforeShutdown but that NUT does not know to use that. Thanks.

...with this program; if not, write to the Free Software * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA * */ #include "newhidups.h" #include "dynex-hid.h" #include "extstate.h" /* for ST_FLAG_STRING */ #include "dstate.h" /* for STAT_INSTCMD_HANDLED */ #include "main.h" /* for getval() */ #include "common.h" #define DYNEX_HID_VERSION "dynex HID 0.1" #define DYNEX_VENDORID 0x0764 /* --------------------------------------------------------------- */ /* Vendor-specific usage table */ /* -----------...

...v(upsfd, buf, SEC_SIZE) != 0) /* not succeeded */ return STAT_INSTCMD_UNKNOWN; sec_send(upsfd, SEC_SETCMD, sec_varlist[SEC_SHUTDOWN_AFTER_DELAY].cmd, "0", 1); /* shutdown now */ if (sec_recv(upsfd, buf, SEC_SIZE) != 0) /* not succeeded */ return STAT_INSTCMD_UNKNOWN; return STAT_INSTCMD_HANDLED; } if (strcasecmp(cmd, "load.on") == 0) { /* send SDA:0, STD:1 */ sec_send(upsfd, SEC_SETCMD, sec_varlist[SEC_SHUTDOWN_TYPE].cmd, "0", 1); /* shutdown type: UPS output */ if (sec_recv(upsfd, buf, SEC_SIZE) != 0) /* not succeeded */ return STAT_INSTCMD_UNKNOWN...

Hi Kirill, just to notify you that your al175 driver is being removed from the NUT tree, as of 2.4.0-pre1. if you wish to see it entering the tree again, please contact the Development mailing list to talk about it. Merry Christmas and happy New Year. Arnaud -- Linux / Unix Expert R&D - Eaton - http://www.eaton.com/mgeops Network UPS Tools (NUT) Project Leader -