similar to: UPS commands

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

>>I still have an unset draft answer to your previous mail... but you seem to have progressed... Heh?that?s been known to happen. ? I have the luxury of relatively un-interrupted development on this project, so it goes a lot faster now. Hopefully that lasts? >>>Could you please check if "usbhid-ups -D ..." does list the above HID data

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 Apr 5, 2014, at 10:39 AM, Charles Lepple wrote: > 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,

I'm probably spending WAY too much time on this question, but.... If the goal is just to perform a clean shutdown, and the power might cycle a few more times before coming back completely, then shutdown.stayoff might make more sense. A human could come along and manually power it back on. ...by plugging the PC into a new power source? Because the UPS outlet would be shut off, so hitting the

On Mar 20, 2015, at 11:32 AM, Rob Groner <rgroner at RTD.com> wrote: > 3) Finally?what is the usefulness of shutdown.stayoff? It tells the UPS to shut off its load and not to turn it back on when the power comes back. If so?how does the UPS ever know to turn that load back on? You would have to hook a different PC to the UPS and run nut just to send the ?load.on? command? If the

On Saturday 05 Apr 2014 16:28:24 Charles Lepple wrote: > On Apr 5, 2014, at 10:39 AM, Charles Lepple wrote: > > 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

On Mar 23, 2015, at 8:25 AM, Rob Groner <rgroner at RTD.com> wrote: > If the goal is just to perform a clean shutdown, and the power might cycle a few more times before coming back completely, then shutdown.stayoff might make more sense. A human could come along and manually power it back on. > > ?by plugging the PC into a new power source? Because the UPS outlet would be shut

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

On Jun 3, 2014, at 1:28 AM, Mick wrote: > On Saturday 05 Apr 2014 16:28:24 Charles Lepple wrote: >> On Apr 5, 2014, at 10:39 AM, Charles Lepple wrote: >>> 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

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

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

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 described in the FAQ (but I'm not 100% sure). In the trace output I can see that

On Nov 12, 2014, at 3:53 AM, Maksym Bodaniuk <max.bodaniuk at gmail.com> wrote: > Hi Charles, > >> Sigh, I wish the vendors wouldn't change operation without changing identifiers. >> >> Do you have any recommendations on how the driver should decide whether it is an old 0x0004 or new 0x0004 device? > > No-no, there is no an old 0x0004 or new 0x0004

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

This took a long time because I had problems with my system. After I reloaded my operating system several times I found I had a bad memory module. Here is the output from newhidups for my Geek Squad GS1285U. It just kept repeating until I hit ctl-z. I think that this means nut will work for this ups. My computer is not powered by the ups yet. I did not want it to be powered down by accident.

On Mar 10, 2015, at 11:20 AM, Rob Groner <rgroner at RTD.com> wrote: > I added "_RTD" to the version string in configure.ac and ran autogen.sh and then configure, and it now shows the _RTD version string during configure. I did a clean make and install, but don't see where else the version number may be showing. When the executables startup, they show 2.7.2-signed-*. I

Hi, I just decided to fix some scaling issues for my UPS (TRIPP-LITE SMART1500LCDT). Apparently that issue existed for some time (and I knew about it as well:-() See http://thread.gmane.org/gmane.comp.monitoring.nut.devel/6482 for a thread. My little patch is attached (against 2.7.3). It seems to be working better for me but I don't have any other TRIPP-LITE's to test that I did

Hi, I just decided to fix some scaling issues for my UPS (TRIPP-LITE SMART1500LCDT). Apparently that issue existed for some time (and I knew about it as well:-() See http://thread.gmane.org/gmane.comp.monitoring.nut.devel/6482 for a thread. My little patch is attached (against 2.7.3). It seems to be working better for me but I don't have any other TRIPP-LITE's to test that I did

Ok, so the reason I keep asking about this is in case I have to actually implement this in our UPS. I meant that a human could power the UPS back on. Nearly all of the UPSes I have worked on have momentary power buttons (either toggle on/off, or a pair of on and off buttons). So, when a power-off-stay-off comes through, then the UPS *itself* shuts down as well, and essentially goes into a