search for: delaybeforestartup

...m "ups.conf" aren't honored. This unit uses a different HID path than the stardard one for sending a "load.on.delay" command. As the driver (usbhid-ups) can't find this command, it has to revert to rebooting the UPS. The HID paths involved are: - "UPS.PowerSummary.DelayBeforeStartup": the standard command for triggering a "load.on.delay" in USB units. - "UPS.Output.DelayBeforeStartup": used in this unit for triggering a "load.on.delay". The former doesn't exist. If you add the HID path "UPS.PowerSummary.DelayBeforeStartup" to &...

...th ID 0X0d9f:0X04. For example, my Imperial IMD-825AP LCD has 0x0004, but an old examples of this model have 0Xa2. > > Also, lets take a look inside PCM_USB_protocol_2014.pdf: > "16 0x8456 Delay Before Startup R/W 5 Byte" > And old specs for BNT protocol: > "16 8456 DelayBeforeStartup *** R/W 2 Byte" > So, the length for DelayBeforeStartup report changed from 2 to 5 bytes. From the 2012 thread, it looks like the DelayBeforeStartup report might be encoded as hexadecimal: 0.440981 refresh_report_buffer: expected 3 bytes, but got 2 instead 0.441006 Report[err]: (2 b...

...end a driver log with -DDDD, gzipped and attached (so as not to wrap the lines)? Same length of 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, "UP...

Alexey, I posted this before, but never got a reply. So I'm reposting this again. In the present HID PDC implementation by PowerCOM, expect problems with the non-compliant implementation of the DelayBeforeShutdown and DelayBeforeStartup pages. Third party applications will expect that these follow the HID PDC specifications if you name them like this (and break terribly in the process). In NUT we can (for now) easily implement the PowerCOM specific formatting rules, but not all applications may be able to do so. The same...

...es will be shipped with ID 0X0d9f:0X04. For example, my Imperial IMD-825AP LCD has 0x0004, but an old examples of this model have 0Xa2. Also, lets take a look inside PCM_USB_protocol_2014.pdf: "16 0x8456 Delay Before Startup R/W *5 Byte*" And old specs for BNT protocol: "16 8456 DelayBeforeStartup *** R/W *2 Byte*" So, the length for DelayBeforeStartup report changed from 2 to 5 bytes. Or there was added a new report for example: "44 0x8436 Temperature R/O 2 Byte" This was missed in the old specification. All these things lead me to thought that powercom hid driver should h...

...portID: 0x0c, Offset: 24, Size: 8, Value: 2 5.525960 Path: UPS.PowerSummary.Country, Type: Feature, ReportID: 0x15, Offset: 0, Size: 8, Value: 1 5.575972 Path: UPS.PowerSummary.DelayBeforeShutdown, Type: Feature, ReportID: 0x09, Offset: 0, Size: 32, Value: 0 5.625970 Path: UPS.PowerSummary.DelayBeforeStartup, Type: Feature, ReportID: 0x0a, Offset: 0, Size: 32, Value: 0 5.625988 Path: UPS.PowerSummary.DesignCapacity, Type: Feature, ReportID: 0x0c, Offset: 32, Size: 8, Value: 100 5.626000 Path: UPS.PowerSummary.FlowID, Type: Feature, ReportID: 0x0b, Offset: 96, Size: 8, Value: 4 5.626009 Path: U...

On Nov 11, 2014, at 3:30 PM, Maksym Bodaniuk <max.bodaniuk at gmail.com> wrote: > Dear Charles and Artem, > > I've recently bought a new PowerCom Imperial IMD825-AP LCD which identifies itself as 0x0d9f:0x0004. > At first glance it seems that usbhid-ups driver works fine. But when I tried to shutdown UPS via DelayBeforeShutdown it started double beeping every couple seconds

...nd attached (so as not > > to wrap the lines)? Same length of 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...

On Jan 8, 2015, at 11:43 PM, Graham Menhennitt <graham at menhennitt.com.au> wrote: > Hello Nutters, > > I'm running nut 2.7.2 on FreeBSD 10-stable (via the FreeBSD port) with an APC Back-UPS CS 350 connected via USB. I get persistent (every few minutes) messages logged "battery is low" but I don't understand why. I don't think it's for the reason

...te... 163.190347 Path: UPS.PowerSummary.DelayBeforeShutdown, Type: Feature, ReportID: 0x12, Offset: 0, Size: 16, Value: -1 163.201247 Path: UPS.PowerSummary.DelayBeforeReboot, Type: Feature, ReportID: 0x13, Offset: 0, Size: 24, Value: 0 163.210345 Path: UPS.Output.DelayBeforeStartup, Type: Feature, ReportID: 0x28, Offset: 0, Size: 16, Value: 0 163.221472 Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Feature, ReportID: 0x07, Offset: 2, Size: 1, Value: 1 163.221585 Path: UPS.PowerSummary.PresentStatus.Discharging, Type: Feature, ReportID: 0x...

Oops... changing that to --with-user=nut solved one problem. I have the driver, upsd and upsmon running now. Thank you! Now I'm back to another issue, every 2 seconds I get in the logs: May 3 13:45:23 myhost upsd[2587]: Connected to UPS [eaton]: usbhid-ups-eaton It seems happy to do this forever. On Tue, May 3, 2016 at 8:17 AM, Charles Lepple <clepple at gmail.com> wrote: > On

...est, Type: Feature, ReportID: 0x14, Offset: 0, Size: 8, Value: 6 0.055670 Path: UPS.Output.Test, Type: Input, ReportID: 0x14, Offset: 0, Size: 8, Value: 6 0.058045 Path: UPS.Output.DelayBeforeShutdown, Type: Feature, ReportID: 0x15, Offset: 0, Size: 16, Value: -60 0.066782 Path: UPS.Output.DelayBeforeStartup, Type: Feature, ReportID: 0x16, Offset: 0, Size: 16, Value: -60 0.069506 Path: UPS.Output.Boost, Type: Feature, ReportID: 0x17, Offset: 0, Size: 1, Value: 0 0.070068 Path: UPS.Output.Overload, Type: Feature, ReportID: 0x17, Offset: 1, Size: 1, Value: 0 0.072352 Path: UPS.Output.ConfigActiv...

...t: 0, Size: 16, Value: 73 771.784792 Path: UPS.PowerSummary.DelayBeforeShutdown, Type: Feature, ReportID: 0x12, Offset: 0, Size: 16, Value: -1 771.804859 Path: UPS.PowerSummary.DelayBeforeReboot, Type: Feature, ReportID: 0x13, Offset: 0, Size: 24, Value: 0 771.824650 Path: UPS.Output.DelayBeforeStartup, Type: Feature, ReportID: 0x28, Offset: 0, Size: 16, Value: 0 771.833660 Path: UPS.Battery.Test, Type: Feature, ReportID: 0x16, Offset: 0, Size: 8, Value: 6 771.844717 Path: UPS.PowerSummary.AudibleAlarmControl, Type: Feature, ReportID: 0x14, Offset: 0, Size: 8, Value: 2 771.853725 P...

...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? > these should be there. as per the code pointed i...

...t;>> to wrap the lines)? Same length of 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...

...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) Why does the usbhid-ups automatically add those 4 commands to all usb subtype d...

...lue: 1 6.038597 Path: UPS.OutletSystem.Outlet.[2].Current, Type: Feature, ReportID: 0x83, Offset: 88, Size: 16, Value: 1.2 6.077774 Path: UPS.OutletSystem.Outlet.[2].DelayBeforeShutdown, Type: Feature, ReportID: 0x8d, Offset: 0, Size: 32, Value: 0 6.113789 Path: UPS.OutletSystem.Outlet.[2].DelayBeforeStartup, Type: Feature, ReportID: 0x90, Offset: 0, Size: 32, Value: 0 6.113806 Path: UPS.OutletSystem.Outlet.[2].FlowID, Type: Feature, ReportID: 0x80, Offset: 16, Size: 8, Value: 4 6.113812 Path: UPS.OutletSystem.Outlet.[2].OutletID, Type: Feature, ReportID: 0x80, Offset: 24, Size: 8, Value: 1 6....

...ure, ReportID: 0x14, Offset: 0, Size: 8, Value: 6 0.133497 Path: UPS.Output.Test, Type: Input, ReportID: 0x14, Offset: 0, Size: 8, Value: 6 0.133596 Path: UPS.Output.DelayBeforeShutdown, Type: Feature, ReportID: 0x15, Offset: 0, Size: 16, Value: -60 0.133669 Path: UPS.Output.DelayBeforeStartup, Type: Feature, ReportID: 0x16, Offset: 0, Size: 16, Value: -60 0.133754 Path: UPS.Output.Boost, Type: Feature, ReportID: 0x17, Offset: 0, Size: 1, Value: 0 0.133758 Path: UPS.Output.Overload, Type: Feature, ReportID: 0x17, Offset: 1, Size: 1, Value: 0 0.133855 Path: UPS.Out...

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

...he HID Power Devices specification, it will do just that and is effectively the same as 'shutdown.stayoff'. If there is mains power at that time, the output will remain off. There are generally two ways to shut down a HID UPS, compatible with NUT: 1) DelayBeforeReboot (shutdown.reboot) 2) DelayBeforeStartup (shutdown.return) and DelayBeforeShutdown (shutdown.stayoff, to make sure the output is off before the startup time= r expires) #1 has the advantage that it is just a single command (but it will act immediately), while #2 allows to shutdown with a delay (making sure that DelayBeforeStartup > De...