Displaying 4 results from an estimated 4 matches for "upscsend".
Did you mean:
upsched
2009 Jan 29
1
Fwd: upscode2.c
...ode2.c driver but could not find a way
to do that from the NUT website.
Here is the problem code and what I have noticed in upscode2.c:
void upsdrv_shutdown(void)
{
if (can_upsd && can_uppc) {
upslogx(LOG_EMERG, "Emergency shutdown");
upscsend("UPSD"); /* Set shutdown delay */
upscsend("1"); /* 1 second (lowest possible.
0 returns current.*/
upslogx(LOG_EMERG, "Shutting down...");
upscsend("UPPC"); /* Powercycle UPS */...
2010 Mar 03
1
using upscode2 driver with Powerware 5119 RM
...will reboot %ld seconds after shutdown",
strtol(dstate_getinfo("ups.delay.reboot"),NULL,10));
upslogx(LOG_EMERG, msg);
snprintf(msg, 100, "UPS shutting down in %ld seconds...",
strtol(dstate_getinfo("ups.delay.shutdown"),NULL,10));
upslogx(LOG_EMERG, msg);
upscsend("UPPC"); /* Powercycle UPS */
upscsend("IJHLDMGCIU"); /* security code */
/* do something so connection doesn't drop right after UPPC command */
upsc_getvalue("UPTP", NULL, "NNAME", "ups.model", NULL);
}
I'm sure a real C hacker could f...
2023 Jul 05
1
failed after upgrade - upscode2: Missing UPCL after UPCL
...for UPCL
UPSS
UPDS
UPDV
UPTP
UPSN
UPPN
UPSD
UPCD
UPPC
UPPU
UPIS
UP??
UPEA
UPDA
UPCL
Looks like a list of supported commands? UPCL(Ups Command List?)
Takes a couple of seconds.
Looking at the debug output of /usr/lib/nut/upscode2 -a malaysia -DDDD
I see a problem at :
0.954763 [D3] upscsend: 'UPCD'
0.956318 [D3] upscsend: '0000'
2.958427 [D3] upscrecv: Timeout
4.960535 [D3] upscrecv: Timeout
4.960566 [D2] Got value:
4.960580 Bad response to UPCD 0000:
4.960596 dstate_setflags: base vari...
2023 Jul 05
1
failed after upgrade - upscode2: Missing UPCL after UPCL
Ah, I thought you missed in my earlier reply the part about a bug with
debug printouts in 2.8.0 (fixed on master since), did not comment on that
when you replied with quoting... So, for now options are to bump debugging
to 3+ or to build your own in one of many ways possible :\
On Wed, Jul 5, 2023, 06:23 Karl Schmidt <karl at lrak.net> wrote:
> On 7/4/23 10:01PM, Jim Klimov wrote:
>