similar to: Support of "shutdown.return" on a APC Back-UPS CS 500

On Nov 8, 2014, at 6:12 PM, Selva Nair <selva.nair at gmail.com> wrote: > Everything works rather well, except that the cgi-interface does not report input/output voltages and load for the C 1500 unit. > upsc also reports these values only for model 1000, not for 1500. Battery charge is and runtime are reported. For the 1000, do the values match this page?

Hi, I have setup NUT in netserver mode on debian wheezy with two APC UPS units connected to it by usb. lsusb identifies the units as Smart-UPS 1000 and Smart-UPS C1500. It appears these do not use the smart protocol and usbhid-ups is the correct driver to use. System: Debian wheezy with stock version of nut (Version: 2.6.4-2.3+deb7u1) Everything works rather well, except that the

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,

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?

Hi Charles, Thanks for your response. > For the 1000, do the values match this page? > > > http://buildbot.networkupstools.org/~buildbot/cayman/docs/latest/ddl/APC/Smart-UPS_1000.html > > Yes it does (except that mine is a 120 V model, so input/output voltage is about 125) It doesn't look like we have an entry for a C1500 yet. Would you care to > submit the output of

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:

On 03/04/17 17.24, Roger Price wrote: > On Mon, 3 Apr 2017, Jon Bendtsen wrote: > >> On 03/04/17 17.10, Roger Price wrote: >>> On Mon, 3 Apr 2017, Jon Bendtsen wrote: >>> >>>> Power seem to be lost immediately. >>>> But my APC Smart-UPS 1500 always reported everything OK. >>>> battery.charge : 100 >>> ...

[please keep the list CC'd. Thanks!] On Sep 16, 2013, at 8:11 PM, Derek Rachul <drachul at gmail.com> wrote: > On Mon, Sep 16, 2013 at 4:36 PM, Charles Lepple <clepple at gmail.com> wrote: >> On Sep 12, 2013, at 7:47 PM, Derek Rachul <drachul at gmail.com> wrote: >> >> > I tried reversing the order of the definitions in the config file, and it does

Hello, I'm trying to setup a UPS configuration whereas I have one physical UPS but two UPS entities loaded by the system used by different network slaves. In my ups.conf configuration I have ... [ups] driver = apcsmart port = /dev/ttyS0 desc = "APC UPS" [qnapups] driver = dummy-ups port = ups at localhost desc = "APC UPS for

I'm doing testing of the UPS-side code, including being able to tell the UPS to shutdown and then come back up after a while (if power has returned). I'm trying to use upscmd so that I don't have to do an actual shutdown, but when I have it list the commands for my UPS, I just see 4 commands, and they're not the ones I thought I had specified. load.on load.off shutdown.return

Hi all. UPS is Eaton 5SC 500i. I tested three solutions: 1. swap "usbhid-ups -a qnapups" with "usbhid-ups -a qnapups -k" Result: server shutdown, but ups does not shut off! 2. run prog with params "upsmon -c fsd" Result: server shutdown, but ups does not shut off! 3. run prog "upscmd -u name -p passwd qnapups shutdown.return" and next

Good day. Can not perform shutdowns Ups. Please help. Details of our installation are: OS: Turris Omnia (TO) NUT version: 2.7.4-5 Installation method: from package UPS device: EATON UPS 5SC 500i , 230V, 350W, 500VA, USB bought in jun 2018 If you connect to TO UPS via USB, the /dev/hidraw0 device will be created. No any programs from NUT package is not running. When I run: /lib/nut/usbhid-ups

Hi Yesterday I had 2 different APC UPS using USB get in power off recoverable state. dmesg said: 7705944.352083] usb 2-1: new low speed USB device using uhci_hcd and address 2 [7705944.477061] usb 2-1: device descriptor read/64, error -71 [7705944.709035] usb 2-1: device descriptor read/64, error -71 [7705944.925071] usb 2-1: new low speed USB device using uhci_hcd and address 3

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

Now I have this in /etc/nut/upsmon.conf (my QNAP NAS wants admin and 123456 or not working) RUN_AS_USER root MONITOR qnapups at localhost 1 admin 123456 master MONITOR qnapups at 192.168.222.252 3493 admin 123456 slave MINSUPPLIES 1 SHUTDOWNCMD "/sbin/shutdown -h +0" POLLFREQ 5 POLLFREQALERT 5 HOSTSYNC 15 DEADTIME 15 POWERDOWNFLAG /etc/killpower NOTIFYFLAG ONLINE SYSLOG+EXEC

Hi Rob I still have an unset draft answer to your previous mail... but you seem to have progressed... 2015-03-20 16:32 GMT+01:00 Rob Groner <rgroner at rtd.com>: > I?m doing testing of the UPS-side code, including being able to tell the > UPS to shutdown and then come back up after a while (if power has returned). > > > > I?m trying to use upscmd so that I don?t have to

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,

On Sep 12, 2013, at 7:47 PM, Derek Rachul <drachul at gmail.com> wrote: > I tried reversing the order of the definitions in the config file, and it does seem to change the order in which they're loaded (at least according to the system logs) however the error remains. I don't have any experience using the dummy-ups driver on the same host as the real UPS driver, so this is a

On 01/07/2018 11.53, icingaj at gmail.com wrote: > Good day. > > Can not perform shutdowns Ups. Please help. > > Details of our installation are: > OS: Turris Omnia (TO) > NUT version: 2.7.4-5 > Installation method: from package > UPS device: EATON UPS 5SC 500i , 230V, 350W, 500VA, USB bought in jun 2018 > > If you connect to TO UPS via USB, the /dev/hidraw0

I used strace and the result is bus is busy: clock_gettime(CLOCK_MONOTONIC, {8158, 708518222}) = 0 timerfd_settime(11, TFD_TIMER_ABSTIME, {it_interval={0, 0}, it_value={8159, 708518000}}, NULL) = 0 ioctl(12, USBDEVFS_SUBMITURB, 0x40810) = 0 poll([{fd=7, events=POLLIN}, {fd=9, events=POLLIN}, {fd=11, events=POLLIN}, {fd=12, events=POLLOUT}], 4, 60000) = 1 ([{fd=12, revents=POLLOUT}]) ioctl(12,