similar to: APC Back-UPS CS 650 offdelay and startdelay

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?

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:

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 Aug 21, 2018, at 1:37 PM, Karol Olszewski <karol.olszewski at ipflow.pl> wrote: > > I'm send debug file /lib/nut/usbhid-ups -a apc -DDD in attachement. > I tested two different ones APC BackUPS CS 650 and on both problem occurred. > I borrowed PowerWalker (driver blazer_usb), and all function + offdelay, > ondelay works perfectly. unfortunately, it looks like there

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

On Aug 22, 2018, at 1:20 PM, Karol Olszewski <karol.olszewski at ipflow.pl> wrote: > > W dniu 22.08.2018 o 14:41, Charles Lepple pisze: >> /lib/nut/usbhid-ups -a apc -DDD -k > Please see attachement. 1.872180 Report[buf]: (2 bytes) => 40 00 1.872196 Path: UPS.Output.APCDelayBeforeReboot, Type: Feature, ReportID: 0x40, Offset: 0, Size: 8, Value: 0 [...] 1.872439

On Aug 23, 2018, at 10:46 AM, Karol Olszewski <karol.olszewski at ipflow.pl> wrote: > > 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,

Hello there. Have been experimenting with an APC Smart-UPS 1500 RM and would like to share the results of my research. I hope this could be of help to people having this kind of units. I would also like to give something back to the NUT community. :) Here are the details of the unit in question (a 1500 VA rack mountable one): Model: Smart-UPS 1500 RM Firmware revision: 617.3.I USB firmware

Are there plans to change the default offdelay/ondelay for the Windows versions of NUT since it can't be invoked at the end of shutdown? E.g. I have a Win2k3 server that takes just over 4min to shut down, so I set my offdelay to 600 (ondelay is +15 that) to be extra safe. Maybe a 2 min by default would be good? Most (all?) APC non-smart UPS's are hard-coded at an annoying 1min delay,

Dear All, I am running Slackware64-14.1(Linux marto 3.10.17 #1 SMP Fri Feb 14 16:39:21 CST 2014 x86_64 Intel(R) Pentium(R) CPU G3250 @ 3.20GHz GenuineIntel GNU/Linux) with kernel 3.10.17 and nut package nut-2.6.5-x86_64-1_SBo, buit from source using the build script http://slackbuilds.org/repository/14.1/system/nut/ In the README.Slackware it is suggested that the commands for killing the

On Jan 22, 2015, at 9:53 AM, Sebastian Hosche <sebastian.hosche at web.de> wrote: > Hi Charles, > > Thanks so much for your quick and detailed reply! I've added my answers and details inline. Sorry this reply wasn't as quick. > On 22.1.2015 04:46, Charles Lepple wrote: >> On Jan 21, 2015, at 9:15 AM, Sebastian Hosche <sebastian.hosche at web.de> wrote:

Thanks On Sat, 16 Mar 2024 at 18:57, Charles Lepple <clepple_at_gmail.com_chribonn at duck.com> wrote: > > On Mar 14, 2024, at 11:41?AM, Alan via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> wrote: > > > Hi, > > > > My Cyber Power reports these two values. Each pair has the same value. > > > > Would they normally be the same thing? >

Hi Charles, Thanks so much for your quick and detailed reply! I've added my answers and details inline. On 22.1.2015 04:46, Charles Lepple wrote: > On Jan 21, 2015, at 9:15 AM, Sebastian Hosche <sebastian.hosche at web.de> > wrote: > >> First issue: whatever I set as the offdelay, seems to be ignored and >> the UPS just cuts the power about 2sec after receiving

On Jan 21, 2015, at 9:15 AM, Sebastian Hosche <sebastian.hosche at web.de> wrote: > Hi there, > > I just purchased a CyberPower BR850ELCD and while setting NUT up with the install instructions from the homepage was pretty straightforward, and the UPS was detected by the usbhid-ups driver, I'm having problems getting the UPS to work properly. > > First issue: whatever I

strange i did not change anything in my windows 7 64bit. This is my full setup pretty basic. Ubuntu 14.04.2 LTS, Trusty Tahr, with sernet samba 4.1.17-9 I do have 1 user for samba. pdbedit -L xbmc:5000:MediaUser [global] workgroup = PRIVE server string = %h server dns proxy = yes ; name resolve order = lmhosts host wins bcast #### Networking #### # interfaces = 127.0.0.0/8 eth0

Hi there, I just purchased a CyberPower BR850ELCD and while setting NUT up with the install instructions from the homepage was pretty straightforward, and the UPS was detected by the usbhid-ups driver, I'm having problems getting the UPS to work properly. First issue: whatever I set as the offdelay, seems to be ignored and the UPS just cuts the power about 2sec after receiving the

Hi Michael, thanks for your feedback! I'm cc'ing the NUT users list for info. I've also added an entry for your device (Powerwalker Line Interactive VI 1400, using blazer_usb). Can you please send back an upsc output, and at least check for the shutdown behavior, if not already done: http://new.networkupstools.org/user-manual.html#Testing_shutdowns 2010/10/19 MichaelE <662435 at

Hi Louis Thank you! As i wrote in my first post, i tried even with these settings: client max protocol = SMB3 client min protocol = SMB2 client signing = required server signing = required But it was not working - as soon I use RequireSecuritySignature=1 on the client. It seems for that the client is stopping communication since the Win7-client expects something

Hi Rowland The client is stopping communication, not the server. With error 1240. And since it is working with the client setting RequireSecuritySignature=0 without any problem, ' hosts allow' cannot be either the problem nor the solution. So - setting RequireSecuritySignature=1 at the client needs a corresponding setting at the server - I guess. But even explicit settings on samba side

Hello I have an samba server with a public share. It was configured with security=share. Now I have to tight security with setting those flags in the windows client: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\LanmanWorkstation\Parameters] EnablePlainTextPassword=0 EnableSecuritySignature=1 RequireSecuritySignature=1 Since this change the public share is not working anymore. I found