search for: upsc_commandlist

...s and then based on the output of the UPCL command to the UPS, they get set to a one if the UPS supports those commands. However, if you call the driver with the -k option to force a shutdown, which my shutdown scripts do, it fails because those variables are never set, because the routine upsc_commandlist is never called. That is the routine where the output of the UPCL command to the UPS is checked to see if the UPS supports those commands. I noticed that in version 408 those checks didn't exist, but in SVN 743 they were added. I checked NUT 2.0.5 and the upscode2.c driver didn't...

...erial communication being dropped so abruptly? 2. UPS Code II spec says you can view the values of UPSD and UPPC by sending the command string followed by a parameter of "0". However for my UPS this sets the value to 0! In order to view the value you must send "0000". So in upsc_commandlist I changed upsc_getvalue(cp->upsc, "0", cp->upsp, cp->cmd, NULL); to upsc_getvalue(cp->upsc, "0000", cp->upsp, cp->cmd, NULL); and all works correctly. 3. I want to specify a custom shutdown delay value. I can use upsrw upsrw -s ups.delay.shutdown...