search for: hu_type_cmd

...ted 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, "UPS.Output.APCDelayBeforeReboot", NULL, "1", HU_TYPE_CMD, NULL }, > > For reference, here's the thread related to adding that mapping: https://alioth-lists.debian.net/pipermail/nut-upsuser/2011-January/006550.html > Hi I'm bit closer :) Acctually change "UPS.Output.APCDelayBeforeReboot" to   { "shutdown.return", 0, 0...

W dniu 23.08.2018 o 02:16, Charles Lepple pisze: > > For some reason, this is being hardcoded to 1: > > drivers/apc-hid.c- /* used by APC BackUPS CS */ > drivers/apc-hid.c: { "shutdown.return", 0, 0, "UPS.Output.APCDelayBeforeReboot", NULL, "1", HU_TYPE_CMD, NULL }, > > Can you rebuild the NUT drivers as described here? https://github.com/networkupstools/nut/wiki/Building-NUT-on-Debian,-Raspbian-and-Ubuntu Ok, this is version from today github sync and compile (Ubuntu 18.04): Network UPS Tools - Generic HID driver 0.42 (2.7.4-490-g5dc80953) /l...

...it adds the 4 commands shown above. Now, load.on.delay and load.off.delay are the only two commands I *want* to support. So I put them in my hid2nut table: /* Commands to control UPS */ { "load.off.delay", 0, 0, "UPS.PowerSummary.DelayBeforeShutdown", NULL, DEFAULT_OFFDELAY, HU_TYPE_CMD, NULL }, { "load.on.delay", 0, 0, "UPS.PowerSummary.DelayBeforeStartup", NULL, DEFAULT_ONDELAY, HU_TYPE_CMD, NULL }, So there's a few things I am trying to figure out: 1) Where are the commands that I said the UPS had (via HU_TYPE_CMD, I thought) when I use upscmd? 2...

..., load.on.delay and load.off.delay are the only two commands I **want** > to support. So I put them in my hid2nut table: > > > > /* Commands to control UPS */ > > { "load.off.delay", 0, 0, "UPS.PowerSummary.DelayBeforeShutdown", NULL, > DEFAULT_OFFDELAY, HU_TYPE_CMD, NULL }, > > { "load.on.delay", 0, 0, "UPS.PowerSummary.DelayBeforeStartup", NULL, > DEFAULT_ONDELAY, HU_TYPE_CMD, NULL }, > > > > So there?s a few things I am trying to figure out: > > 1) Where are the commands that I said the UPS had (via HU_TYP...

W dniu 24.08.2018 o 23:13, Karol Olszewski pisze: > Hi > I'm bit closer :) > Acctually change "UPS.Output.APCDelayBeforeReboot" to > >   { "shutdown.return", 0, 0, "UPS.Output.APCShutdownAfterDelay", NULL, > "90", HU_TYPE_CMD, NULL }, > > Now, UPS turn off load after 90 sec, but not power ON when power is back > Dear nut users, Two APC Back-UPS CS 650 1) Firmware 817.v4.I 2) Firmware 817.v3.I File apc-hid.c line 431  { "shutdown.return", 0, 0, "UPS.Output.APCDelayBeforeReboot", NULL, &quot...

Hi all, I am trying to get a APC Back-UPS CS 500 running on my QNAP 419P Nas. Since on all my work I figure out the following: from Network UPS Tools upscmd 2.4.1 [~] # upscmd -l qnapups Instant commands supported on UPS [qnapups]: beeper.disable - Disable the UPS beeper beeper.enable - Enable the UPS beeper beeper.mute - Temporarily mute the UPS beeper beeper.off - Obsolete (use

...18 o 02:16, Charles Lepple pisze: >> >> For some reason, this is being hardcoded to 1: >> >> drivers/apc-hid.c- /* used by APC BackUPS CS */ >> drivers/apc-hid.c: { "shutdown.return", 0, 0, "UPS.Output.APCDelayBeforeReboot", NULL, "1", HU_TYPE_CMD, NULL }, >> >> Can you rebuild the NUT drivers as described here? https://github.com/networkupstools/nut/wiki/Building-NUT-on-Debian,-Raspbian-and-Ubuntu > Ok, this is version from today github sync and compile (Ubuntu 18.04): > > Network UPS Tools - Generic HID driver 0.42 (...

W dniu 22.08.2018 o 14:41, Charles Lepple pisze: > /lib/nut/usbhid-ups -a apc -DDD -k Please see attachement. -- Karol Olszewski ipflow.pl -------------- next part -------------- A non-text attachment was scrubbed... Name: APC_BackUPS_CS_650_fsd.log.gz Type: application/gzip Size: 5735 bytes Desc: not available URL:

...f the string */ The above is clear, if the element is flagged as a string, the size of this string is put in this variable, so that we can use this in dstate_setaux(). But strangely enough, we use a 'float' here and not an 'int'. Why? Do we expect *very* long strings? > /* if HU_TYPE_CMD: command value ; multiplier otherwise */ This comment puzzles me. It looks to me that this deals with the dfl element (and this is just misplaced), since the this is where this flag ends up when used by the subdrivers, so probably this comment should be on a different line. But what does this '...

Now tackling sending the UPS commands to have it turn off and back on (with some delay), I'm just putting this out there to make sure I'm on the right track. I want to design this to be as close as possible to "industry standard", or at least concensus. Looking through the other HU_TYPE_CMDs out there, it seems that most UPSs use "UPS.PowerSummary.DelayBeforeShutdown" for load.off.delay, and "UPS.PowerSummary.DelayBeforeStartup" for load.on.delay. Belkin appears to use custom codes (reserved for vendors), which I know I could do, but guess I don't see the reas...

...nstcmd(shutdown.return, [NULL]) 1.884650 Report[set]: (2 bytes) => 40 01 For some reason, this is being hardcoded to 1: drivers/apc-hid.c- /* used by APC BackUPS CS */ drivers/apc-hid.c: { "shutdown.return", 0, 0, "UPS.Output.APCDelayBeforeReboot", NULL, "1", HU_TYPE_CMD, NULL }, Can you rebuild the NUT drivers as described here? https://github.com/networkupstools/nut/wiki/Building-NUT-on-Debian,-Raspbian-and-Ubuntu

...he data I sent you, please? > > I?ve done some more work myself and the conclusion I?ve reached is that if the minibus OpenUPS doesn?t support instant commands, then sending ?upsdrvctl shutdown? won?t ever work, as it would need to send instant commands! You are correct; I don't see any HU_TYPE_CMD entries in openups-hid.c. I latched on to the other error you mentioned (about claiming the device). The other HID drivers seem to trigger shutdown by writing to the various timers (e.g. UPS.PowerSummary.DelayBeforeReboot). Your firmware seems to have UPS.PowerSummary.PresentStatus.ShutdownRequest...

...OK, NULL }, { "ups.delay.start", 0, 0, "PowercomUPS.PowercomPowerConverter.PowercomDelayBeforeStartup", NULL, "%.0f", HU_FLAG_OK, NULL }, { "load.off", 0, 0, "PowercomUPS.PowercomPowerConverter.PowercomDelayBeforeShutdown", NULL, "0", HU_TYPE_CMD | HU_FLAG_OK, NULL }, /* end of structure. */ { NULL, 0, 0, NULL, NULL, NULL, 0, NULL } }; /* shutdown method for Powercom */ static int powercom_shutdown(int ondelay, int offdelay) { char delay[7]; /* 1) set DelayBeforeStartup */ sprintf(delay, "%i", ondelay); if (setvar("...

..., please? >> >> I?ve done some more work myself and the conclusion I?ve reached is that if the minibus OpenUPS doesn?t support instant commands, then sending ?upsdrvctl shutdown? won?t ever work, as it would need to send instant commands! > > You are correct; I don't see any HU_TYPE_CMD entries in openups-hid.c. I latched on to the other error you mentioned (about claiming the device). > > The other HID drivers seem to trigger shutdown by writing to the various timers (e.g. UPS.PowerSummary.DelayBeforeReboot). Your firmware seems to have UPS.PowerSummary.PresentStatus.Shutd...

Charles, Did you get chance to look at the data I sent you, please? I?ve done some more work myself and the conclusion I?ve reached is that if the minibus OpenUPS doesn?t support instant commands, then sending ?upsdrvctl shutdown? won?t ever work, as it would need to send instant commands! Also from the trace I sent you, it appears that after the ?RunTimeToEmpty? query, the interface tries to

Charles, Thanks again for your help, and sorry I didn?t :cc - noted for the future! I?m suspicious that the OpenUPS doesn?t behave properly in a number of ways, of which the USB traffic is the one of immediate concern. It seems to me that NUT can read from it but probably not write to it: and the OpenUPS doesn?t flag ?low battery? conditions correctly either. It does shut itself down at a

...abilities enumeration */ > + case HU_WALKMODE_RESET: > + if (item->hiddata == NULL) > + continue; > + > + /* Reset the NUT-to-HID translation */ > + item->hiddata = NULL; > + > + /* If this was a command, remove it... */ > + if (item->hidflags & HU_TYPE_CMD) { > + dstate_delcmd(item->info_type); > + continue; > + } > + > + /* ...otherwise, remove variable */ > + dstate_delinfo(item->info_type); > + continue; > + > case HU_WALKMODE_INIT: > /* Special case for handling server side variables */...