search for: hu_flag_absent

...f time as before is good. Mick, hold that thought. 1.006824 Path: UPS.PowerSummary.DelayBeforeShutdown, Type: Feature, ReportID: 0x0f, Offset: 0, Size: 24, Value: 60 1.010820 Path: UPS.PowerSummary.DelayBeforeStartup, Type: Feature, ReportID: 0x11, Offset: 0, Size: 24, Value: 0 Arnaud, is HU_FLAG_ABSENT the right flag here? That seems to indicate that the variable is not actually implemented on the UPS: drivers/idowell-hid.c:99: { "ups.delay.start", ST_FLAG_RW | ST_FLAG_STRING, 10, "UPS.PowerSummary.DelayBeforeStartup", NULL, DEFAULT_ONDELAY, HU_FLAG_ABSENT, NULL},...

...t; >> 1.006824 Path: UPS.PowerSummary.DelayBeforeShutdown, Type: Feature, >> ReportID: 0x0f, Offset: 0, Size: 24, Value: 60 >> 1.010820 Path: UPS.PowerSummary.DelayBeforeStartup, Type: Feature, >> ReportID: 0x11, Offset: 0, Size: 24, Value: 0 >> >> Arnaud, is HU_FLAG_ABSENT the right flag here? That seems to indicate that >> the variable is not actually implemented on the UPS: >> >> drivers/idowell-hid.c:99: >> { "ups.delay.start", ST_FLAG_RW | ST_FLAG_STRING, 10, >> "UPS.PowerSummary.DelayBeforeStartup", NULL,...

...hold that thought. > > 1.006824 Path: UPS.PowerSummary.DelayBeforeShutdown, Type: Feature, > ReportID: 0x0f, Offset: 0, Size: 24, Value: 60 > 1.010820 Path: UPS.PowerSummary.DelayBeforeStartup, Type: Feature, > ReportID: 0x11, Offset: 0, Size: 24, Value: 0 > > Arnaud, is HU_FLAG_ABSENT the right flag here? That seems to indicate that > the variable is not actually implemented on the UPS: > > drivers/idowell-hid.c:99: > { "ups.delay.start", ST_FLAG_RW | ST_FLAG_STRING, 10, > "UPS.PowerSummary.DelayBeforeStartup", NULL, DEFAULT_ONDELAY, &...

On Wed, Sep 24, 2008 at 2:27 PM, Arjen de Korte <adkorte-guest at alioth.debian.org> wrote: > - /* Server side variables */ > - { "driver.version.internal", ST_FLAG_STRING, sizeof(DRIVER_VERSION), NULL, NULL, DRIVER_VERSION, HU_FLAG_ABSENT, NULL }, > - { "driver.version.data", ST_FLAG_STRING, sizeof(APC_HID_VERSION), NULL, NULL, APC_HID_VERSION, HU_FLAG_ABSENT, NULL }, Just curious, why were the subdriver versions removed? -- - Charles Lepple

...e: Feature, > >> > >> ReportID: 0x0f, Offset: 0, Size: 24, Value: 60 > >> > >> 1.010820 Path: UPS.PowerSummary.DelayBeforeStartup, Type: Feature, > >> > >> ReportID: 0x11, Offset: 0, Size: 24, Value: 0 > >> > >> Arnaud, is HU_FLAG_ABSENT the right flag here? That seems to indicate > >> that the variable is not actually implemented on the UPS: > >> > >> drivers/idowell-hid.c:99: > >> { "ups.delay.start", ST_FLAG_RW | ST_FLAG_STRING, 10, > >> > >> "UPS.Powe...

On Apr 5, 2014, at 8:52 AM, Mick <michaelkintzios at gmail.com> wrote: >> The upsrw command was designed for changing variables that are typically >> stored in non-volatile memory on the UPS. Unfortunately, your UPS doesn't >> seem to do that. > > Well, if it doesn't do that, how come upsc reports the changed value? It is > only after I reboot the PC

W dniu 24.08.2018 o 13:10, Charles Lepple pisze: > Sorry, I didn't mean to imply that the master branch was necessarily going to be different, just wanted to make sure you had everything set up to recompile. The real test is to see if things change after commenting out that line (such as by changing it to start with "//"): > > // { "shutdown.return", 0, 0,

On Wed, 4 Jun 2014, Mick wrote: >> Some of the variables (those with HU_FLAG_ABSENT) are apparently not stored >> on the UPS itself-- they are sent to the UPS when the shutdown command is >> executed. Sending the value starts the timer, in some cases, but I think >> the ups.delay.start value should be safe to send at the time when it is >> set. > > I...

Thanks Charles, On Saturday 05 Apr 2014 12:53:06 Charles Lepple wrote: > On Apr 5, 2014, at 7:18 AM, Mick wrote: > > $ upsrw -s "ups.delay.shutdown"="30" iDowell at localhost > > Username (suzy): admin > > Password: > > OK > > This command is sending the value to the UPS (via the usbhid-ups driver). > > > $ upsc iDowell at localhost

...info_type); > + continue; > + } > + > + /* ...otherwise, remove variable */ > + dstate_delinfo(item->info_type); > + continue; > + > case HU_WALKMODE_INIT: > /* Special case for handling server side variables */ > if (item->hidflags & HU_FLAG_ABSENT) { > @@ -1018,23 +1042,30 @@ > continue; > } > > + /* Apparently, we are reconnecting, so > + * NUT-to-HID translation is still good */ > + if (item->hiddata != NULL) > + break; > + > /* Get pointer to the corresponding HIDData_t item */ &gt...