search for: delaybeforeshutdown

...0, LogMax = 65535, LogMin = 0 55.348920 Report[set]: (3 bytes) => 0f 00 5e 55.348945 Set report succeeded 55.348956 instcmd: SUCCEED Value 30 is converted to 24064, and this seems the delay that is configured on the device to complete its shutdown: [...] 56.358009 Path: UPS.PowerSummary.DelayBeforeShutdown, Type: Feature, ReportID: 0x0f, Offset: 0, Size: 16, Value: 24064 58.721177 Path: UPS.PowerSummary.DelayBeforeShutdown, Type: Feature, ReportID: 0x0f, Offset: 0, Size: 16, Value: 23865 60.576175 Path: UPS.PowerSummary.DelayBeforeShutdown, Type: Feature, ReportID: 0x0f, Offset: 0, Size: 16, Valu...

...-a myups -DDD 2>&1 | tee CPS-EC750G.log > > 70 seconds of output attached. > > > Let me know if you need anything else. This is an 'on the shelf' spare > UPS for me, so there is some flexibility in playing with it... > > thx. 0.207421 Path: UPS.Output.DelayBeforeShutdown, Type: Feature, ReportID: 0x15, Offset: 0, Size: 16, Value: -60 I haven't been able to find any information on what a "-60" would signify. The value "-1" is used to cancel a timer, so maybe the internal timer is set in minutes, and read back with a times-60 scale factor? I...

...fset: 0, Size: 8, Value: 120 0.154975 Path: UPS.Flow.ConfigFrequency, Type: Feature, ReportID: 0x02, Offset: 0, Size: 8, Value: 60 0.156977 Path: UPS.Flow.ConfigApparentPower, Type: Feature, ReportID: 0x03, Offset: 0, Size: 16, Value: 1500 0.158988 Path: UPS.OutletSystem.Outlet.DelayBeforeShutdown, Type: Feature, ReportID: 0x15, Offset: 0, Size: 16, Value: 65535 0.160984 Path: UPS.OutletSystem.Outlet.ffff00bc, Type: Feature, ReportID: 0xe0, Offset: 0, Size: 16, Value: 0 0.162979 Path: UPS.OutletSystem.Outlet.ffff0091, Type: Feature, ReportID: 0x51, Offset: 0, Size: 8, Value: 0...

...ng in the driver initialization is resetting that variable. Are there any extra settings in ups.conf? Can you please send 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...

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 a...

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 for indefinite time (the same problem described by Vincenzo Colonnella here: http://lists.alioth.debian.org/pipermail/nut-upsdev/2013-February/006403.html). I suppose that recent protocol change affects a protocol specifications for DelayBeforeS...

On Sep 11, 2014, at 2:50 AM, Khokhlov Artem <khokhlov.a at pcm.ru> wrote: > Can you please kindly add our new USB-controller with productID 0X04 to NUT compatible list. Updated USB-controller compatible with previous version which is supported by your usbhid-ups driver. Confused. This commit was added in 2011:

...report ID is in the HID Report Descriptor which should be early in the Wireshark capture. I see something called GET DESCRIPTOR Response HID Report which lists the report IDs, but I don't say where it gives information to map it to the path. Other HID UPS models tend to provide both DelayBeforeShutdown and DelayBeforeStartup There is something called Path: UPS.OutletSystem.Outlet.DelayBeforeReboot, ReportID: 0x17. This is sent by the "Immediate Device Reboot" action of the Tripp lite software. Its function seems to be to turn off the load immediately and turn it back on after the...

...e something to say. My understanding from when I was working on this a couple years ago is that the main problem in getting NUT working right with Tripp-Lite equipment is to understand the mappings of the various controls. For example, we have ReportID: 0x15, which maps to UPS.OutletSystem.Outlet.DelayBeforeShutdown. I think this mapping is given by the UPS. NUT than maps this control to load.off.delay. Is that mapping correct, i.e., does setting the control in the UPS do the function that NUT expects? More importantly, is there anything in the UPS that NUT should be mapping to load.on.delay? It does not...

...foreStartup 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 bytes) => 0f 00 0.441024 Path: UPS.PowerSummary.DelayBeforeShutdown, Type: Feature, ReportID: 0x0f, Offset: 0, Size: 16, Value: 0 0.445020 Report[get]: (5 bytes) => 10 30 30 30 30 0.445051 Path: UPS.PowerSummary.DelayBeforeStartup, Type: Feature, ReportID: 0x10, Offset: 0, Size: 32, Value: 12336 You can try various encodings in drivers/powercom-hid.c:pow...

...m 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 for indefinite time (the same problem described by Vincenzo Colonnella here: http://lists.alioth.debian.org/pipermail/nut-upsdev/2013-February/006403.html). > > I suppose that recent protocol change affects a protocol specifications for DelayBe...

On Jan 22, 2018, at 3:00 PM, Ken Olum <kdo at cosmos.phy.tufts.edu> wrote: > > I tested the effect of setting UPS.OutletSystem.Outlet.DelayBeforeShutdown > using Tripp Lite's software, which appears to be as follows: > Theoretically, this should be the same as running the command "upscmd bcpers at localhost -u <upsd.user> load.off.delay <delay>". > So if you could fix nut to use UPS.OutletSystem.Outlet.DelayBefor...

...ure, ReportID: 0x0c, Offset: 16, Size: 8, Value: 1 5.481977 Path: UPS.PowerSummary.CapacityMode, Type: Feature, ReportID: 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.62...

...PS.Output.PercentLoad, Type: Feature, ReportID: 0x13, Offset: 0, Size: 8, Value: 4 0.055234 Path: UPS.Output.Test, 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.Outpu...

...nsfer, Type: Feature, Value: 90.000000 Path: UPS.Input.HighVoltageTransfer, Type: Feature, Value: 140.000000 Path: UPS.Output.Voltage, Type: Feature, Value: 123.000000 Path: UPS.Output.PercentLoad, Type: Feature, Value: 0.000000 Path: UPS.Output.Test, Type: Feature, Value: 1.000000 Path: UPS.Output.DelayBeforeShutdown, Type: Feature, Value: -60.000000 Path: UPS.Output.DelayBeforeStartup, Type: Feature, Value: 0.000000 Path: UPS.Output.Boost, Type: Feature, Value: 0.000000 Path: UPS.Output.Overload, Type: Feature, Value: 0.000000 Path: UPS.Output., Type: Feature Path: UPS.Output.ConfigActivePower, Type: Feature,...

If you'd like, shoot me over your serial number and the corner-cases you don't have answers for and I can look into it. Thank you, David Zomaya Tripp Lite david_zomaya at tripplite.com -----Original Message----- From: Nut-upsuser <nut-upsuser-bounces+david_zomaya=tripplite.com at alioth-lists.debian.net> On Behalf Of Ken Olum Sent: Tuesday, January 14, 2020 11:24 AM To: Layne

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

...tting that variable. Are there any extra settings in ups.conf? Can > > you please send 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...

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,

...e something to say. My understanding from when I was working on this a couple years ago is that the main problem in getting NUT working right with Tripp-Lite equipment is to understand the mappings of the various controls. For example, we have ReportID: 0x15, which maps to UPS.OutletSystem.Outlet.DelayBeforeShutdown. I think this mapping is given by the UPS. NUT than maps this control to load.off.delay. Is that mapping correct, i.e., does setting the control in the UPS do the function that NUT expects? More importantly, is there anything in the UPS that NUT should be mapping to load.on.delay? It does not...