search for: default_offdelay

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,

...{ "shutdown.return", 0, 0, "UPS.Output.APCDelayBeforeShutdown", NULL, "120", HU_TYPE_CMD, NULL }, Now, UPS shutdown after 120sec from FSD command, and start from hibernation automaticaly when power is back. Excelent! (I tested 120,180,300 all work) I'm try to set DEFAULT_OFFDELAY and define in ups.conf time to poweroff (offdelay and ondelay), but this is not work. UPS set to poweroff after ~20sec I think this line set to 20sec off time: usbhid-ups.h:#define DEFAULT_OFFDELAY   "20"    /* Delay before power off, in seconds */ Where DEFAULT_OFFDELAY is change to va...

...this puts an end to our misery with regard to the shutdown functionality of the usbhid-ups driver. I have tested this on the MGE Evolution 650, developers with access to other machines are encouraged to try this out on theirs. One thing that is still open to debate, is how long DEFAULT_ONDELAY and DEFAULT_OFFDELAY should be. Peter Selinger has raised some good arguments for lowering DEFAULT_OFFDELAY. I feel that he is right and that we should lower this value (maybe to 1 second, so that devices that only act upon the change from 1->0 will work by default). The only problem to this, is that some people (m...

...: { "ups.delay.start", ST_FLAG_RW | ST_FLAG_STRING, 10, "UPS.PowerSummary.DelayBeforeStartup", NULL, DEFAULT_ONDELAY, HU_FLAG_ABSENT, NULL}, { "ups.delay.shutdown", ST_FLAG_RW | ST_FLAG_STRING, 10, "UPS.PowerSummary.DelayBeforeShutdown", NULL, DEFAULT_OFFDELAY, HU_FLAG_ABSENT, NULL}, It is not clear how this value is being used. -- Charles Lepple clepple at gmail

..."ups.delay.start", ST_FLAG_RW | ST_FLAG_STRING, 10, > "UPS.PowerSummary.DelayBeforeStartup", NULL, DEFAULT_ONDELAY, > HU_FLAG_ABSENT, NULL}, { "ups.delay.shutdown", ST_FLAG_RW | > ST_FLAG_STRING, 10, "UPS.PowerSummary.DelayBeforeShutdown", NULL, > DEFAULT_OFFDELAY, HU_FLAG_ABSENT, NULL}, > > It is not clear how this value is being used. Was there ever a conclusion to this thread? I didn't get any other messages. -- Regards, Mick -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/...

...e.nominal / UPS.Input.ConfigVoltage > > - input.voltage.nominal / UPS.Flow.ConfigVoltage > > - battery.voltage.nominal / UPS.PowerSummary.ConfigVoltage > > - battery.voltage.nominal / UPS.BatterySystem.Battery.ConfigVoltage > > 4. What's the reason for not using DEFAULT_OFFDELAY and > > DEFAULT_ONDELAY in the 'dfl' field of the load.off.delay and > > load.on.delay instant commands? > > Keor PDU is a commercial name for a Rack UPS, in the USB_DEVICE() macro I tried to add a small description, I don't know if it's enough for you, what kind o...

...start", ST_FLAG_RW | ST_FLAG_STRING, 10, >> "UPS.PowerSummary.DelayBeforeStartup", NULL, DEFAULT_ONDELAY, >> HU_FLAG_ABSENT, NULL}, { "ups.delay.shutdown", ST_FLAG_RW | >> ST_FLAG_STRING, 10, "UPS.PowerSummary.DelayBeforeShutdown", NULL, >> DEFAULT_OFFDELAY, HU_FLAG_ABSENT, NULL}, >> >> It is not clear how this value is being used. > > Was there ever a conclusion to this thread? I didn't get any other messages. > I asked Arnaud about this off-list, and didn't get a complete reply. He said the code looked right. Not sur...

...ad.off.delay, then 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 u...

...h> #include <ctype.h> -#define ENDCHAR '\n' /* replies end with CR LF -- use LF to end */ -#define IGNCHAR '\r' /* ignore CR */ -#define MAXTRIES 3 -#define SER_WAIT_SEC 3 /* allow 3.0 sec for ser_get calls */ -#define SER_WAIT_USEC 0 -#define DEFAULT_OFFDELAY 64 /* seconds (max 0xFF) */ -#define DEFAULT_STARTDELAY 60 /* seconds (max 0xFFFFFF) */ -#define DEFAULT_BOOTDELAY 64 /* seconds (max 0xFF) */ -#define MAX_VOLT 13.4 /* Max battery voltage (100%) */ -#define MIN_VOLT 11.0 /* Min battery voltage (10%) */ - -/* We calculate ba...

...wn 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 ha...

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

...following ones static? - input.voltage.nominal / UPS.Input.ConfigVoltage - input.voltage.nominal / UPS.Flow.ConfigVoltage - battery.voltage.nominal / UPS.PowerSummary.ConfigVoltage - battery.voltage.nominal / UPS.BatterySystem.Battery.ConfigVoltage 4. What's the reason for not using DEFAULT_OFFDELAY and DEFAULT_ONDELAY in the 'dfl' field of the load.off.delay and load.on.delay instant commands? > - metasys --> this driver should be replaced (if possible) with the new one we made called "Legrand_megawhad". This driver was for MetaSystem UPSs, but this company has been a...

...TRING, 10, > >> > >> "UPS.PowerSummary.DelayBeforeStartup", NULL, DEFAULT_ONDELAY, > >> HU_FLAG_ABSENT, NULL}, { "ups.delay.shutdown", ST_FLAG_RW | > >> ST_FLAG_STRING, 10, "UPS.PowerSummary.DelayBeforeShutdown", NULL, > >> DEFAULT_OFFDELAY, HU_FLAG_ABSENT, NULL}, > >> > >> It is not clear how this value is being used. > > > > Was there ever a conclusion to this thread? I didn't get any other > > messages. > > I asked Arnaud about this off-list, and didn't get a complete reply. He...

Dear Daniele, nice to meet you, I'm a collegue of Gabriele. The problem with "blazer_usb" driver ("blazer_ser" works correctly) is related to the following commands: - "F" and "I": when the KRAULER subdriver check these UPS answers it uses wrong constants to check the lenght of the received packets, so these commands are considered as "not

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