Displaying 20 results from an estimated 1000 matches similar to: "upsmon says ONBATT when status: TRIM"
2013 Jun 29
2
upsrw doesn't set variable
NUT 2.6.5 on FreeBSD 9.1
Why isn't the variable outlet.1.delay.shutdown set with the following
command?
# upsc PW5125 at localhost | grep "outlet.1.delay.shutdown"
outlet.1.delay.shutdown: -1
# upsrw -u au -p ap -s outlet.1.delay.shutdown PW5125 at localhost
Enter new value for outlet.1.delay.shutdown: 10
OK
# upsc PW5125 at localhost | grep "outlet.1.delay.shutdown"
2013 Jun 29
0
upsrw doesn't set variable
On 6/29/2013 at 9:14 AM Mike. wrote:
|NUT 2.6.5 on FreeBSD 9.1
|
|
|Why isn't the variable outlet.1.delay.shutdown set with the following
|command?
|
|
|
|# upsc PW5125 at localhost | grep "outlet.1.delay.shutdown"
|outlet.1.delay.shutdown: -1
|
|# upsrw -u au -p ap -s outlet.1.delay.shutdown PW5125 at localhost
|Enter new value for outlet.1.delay.shutdown: 10
|OK
|
|# upsc PW5125
2013 Jun 29
3
upsrw doesn't set variable
On Jun 29, 2013, at 9:45 AM, Mike. wrote:
> On 6/29/2013 at 9:14 AM Mike. wrote:
>
> |NUT 2.6.5 on FreeBSD 9.1
> |
> |
> |Why isn't the variable outlet.1.delay.shutdown set with the following
> |command?
> |
> |
> |
> |# upsc PW5125 at localhost | grep "outlet.1.delay.shutdown"
> |outlet.1.delay.shutdown: -1
> |
> |# upsrw -u au -p ap -s
2017 Feb 20
2
[HCL] Powerware PW5125 with driver bcmxcp
This UPS is already listed in the compatibility list. But I wanted to
add the instant commands supported by upscmd:
============================
Instant commands supported on UPS [PW5125]:
beeper.disable - Disable the UPS beeper
beeper.enable - Enable the UPS beeper
beeper.mute - Temporarily mute the UPS beeper
load.on - Turn on the load immediately
outlet.1.load.off - Turn off the load on
2017 Feb 21
1
[HCL] Powerware PW5125 with driver bcmxcp
On 2/21/2017 8:34 AM, Charles Lepple wrote:
> On Feb 20, 2017, at 11:19 AM, Mike <the.lists at mgm51.com> wrote:
>>
>> This UPS is already listed in the compatibility list. But I wanted to
>> add the instant commands supported by upscmd:
>>
> ...
>> and note that a delayed shutoff command is not available.
>>
>> (NUT 2.7.4 on OpenBSD 6.0)
2013 Jun 29
0
upsrw doesn't set variable
On 6/29/2013 at 9:59 AM Charles Lepple wrote:
|On Jun 29, 2013, at 9:45 AM, Mike. wrote:
|
|> On 6/29/2013 at 9:14 AM Mike. wrote:
|>
|> |NUT 2.6.5 on FreeBSD 9.1
|> |
|> |
|> |Why isn't the variable outlet.1.delay.shutdown set with the
following
|> |command?
|> |
|> |
|> |
|> |# upsc PW5125 at localhost | grep "outlet.1.delay.shutdown"
|>
2013 Jun 29
2
upsrw doesn't set variable
l?rdagen den 29 juni 2013 11.28.14 skrev Mike.:
8<------------------snip---------------------
Hi Mike,
>
> Thanks for the quick reply.
>
> I checked the log file (which, admittedly, I should have done before I
> posted about the problem :) ).
>
> Here's the command and the corresponding log message:
>
> # upsrw -u au -p ap -s outlet.1.delay.shutdown=12
2013 Jun 29
1
upsrw doesn't set variable
l?rdagen den 29 juni 2013 15.22.44 skrev Mike.:
8<-------------snip-----------------
Sorry for the delay.
> Here is the console output of bcmxcp with -DDD specified:
>
>
> [snip]
> 13.721204 Auto delay on: 2
>
> 13.721243 send_command: (4 bytes) => ab 01 35 1f
> 13.821127 send_command: (4 bytes) => ab 01 33 21
> 13.920982
2008 Dec 21
1
upsd segfault.
Hi all,
Have a strange behaviour that I don't know how to debug.
This is when I use the Eaton PW5125 ups. I have it connected
And running in standby.
Starting up the drivers (pw3105 and pw5125) and they run.
Start up the upsd and can read info from both of them. The 3105 is
supplying the computer and the 5125 have a dummy load.
The 5125 is showing that it is off line. Now when I hit the on
2013 Jun 29
0
upsrw doesn't set variable
On 6/29/2013 at 6:16 PM Kjell Claesson wrote:
|l??rdagen den 29 juni 2013 11.28.14 skrev Mike.:
|8<------------------snip---------------------
|Hi Mike,
|>
|> Thanks for the quick reply.
|>
|> I checked the log file (which, admittedly, I should have done before
I
|> posted about the problem :) ).
|>
|> Here's the command and the corresponding log message:
|>
2013 Feb 21
1
NUT with Powerware 5125.
Hi,
Does anyone know how to make NUT works with Powerware 5125?
I already tried serial communication (genericups and bcmxcp) and USB
(usbhid-ups and bcmxcp_usb), but without success.
I'm using the latest version of NUT (2.6.5) under Debian amd64.
Can anyone help me?
Thanks.
Daniel
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
2009 Aug 27
2
Serial comm errors with bcmxcp on HP R3000 XR
I have setup nut-2.4.1 with the bcmxcp driver for my HP R3000 XR unit
and although it appears to work, I receive the following sorts of errors
in syslog:
Aug 27 10:33:05 sv18 bcmxcp[6373]: Communications with UPS lost: Receive
error (data): got 0 bytes instead of 64!!!
Aug 27 10:33:15 sv18 bcmxcp[6373]: Communications with UPS lost: Receive
error (data): got 0 bytes instead of 64!!!
Aug 27
2007 Apr 06
3
questions re. patching bcmxcp.c and choosing variable names
I've patched bcmxcp.c such that it can power cycle the outlet load
segments independently on a Powerware PW5125 UPS. I presume that it will
work for any XCP protocol UPS with 2 load segments.
Should these instant commands be called
outlet.1.shutdown.return
outlet.2.shutdown.return
?
Where do the descriptions displayed by upscmd -l come from? Presently it
shows
outlet.1.shutdown.return -
2007 Sep 19
1
Programming problem.
Hi,
I can't find a nice way to solve a problem. So if you have
some ideas I would be greatfull.
This is the problem.
I can ask a bcmxcp ups what commands it support, if the
firmware is after revision AE.
I was thinking about to use this in the driver. For example
' a ups that don't support battery_test would not have this
command enabled.'
The hex responce look like this from
2007 Jul 10
1
[nut-commits] svn commit r1019 - in trunk: . drivers
Hi Kjell,
a few notes:
- you should bump the DRV_VERSION upon every change
- you should track the drivers TODO list in a comment header (such as
"implement smart load segment detection" completed with your info,
...). That would help to bootstrap new contributors.
- you can also use the alioth trackers (features request, or task) to
give some external visibility on what remains to be
2019 Feb 09
1
Delay for ONBATT event
Hi,
my UPS (APC SMC1000C) goes to ONBATT every day for a few seconds. This
event is emitted because of the short daily UPS self-test, which
cannot be disabled.
Depending on the poll interval upsmon/NUT sometimes picks this event
up and a power failure is logged, even if this is not a real power
outage. I would like to prevent that.
Now I was wondering if there is a way to delay the ONBATT event
2013 Jun 28
2
How to Simulate UPS on battery?
I've recently moved from installing NUT from source to installing NUT
from the FreeBSD package (FreeBSD 9.1).
One would think that I might have learned not to change anything, but I
made the change. And here is my tale of woe.....
My first question is: is it possible to simulate a "UPS is on battery"
state?
Some background:
UPS comm port is connected to and monitored by
2023 Jun 16
1
Dummy-ups cycles between online and onbatt every 5 minutes. (Nut 2.8.0)
Now that upsstats.cgi works, I've noticed that dummy-ups changes state every 5 minutes between OL and OB (probably when the 300 second timer expires). The UPS state stays online.
Also "online" and "onbatt" are broadcast to the console probably via WALL. (The state changes don't seem to be form the ups as upsshed-cmd doesn't run). Upssched-cmd does run when the UPS
2007 Apr 17
1
HP R3000 XR, warning or perhaps error
Hi,
So far I've gleaned heaps of useful info from the list and got mostly
running with NUT. There was a thread by Paul Battaglia and Kjell
Claesson about the R3000 which has helped me get so far, but now with
the patched driver I still have this on startup:
# /usr/local/ups/bin/upsdrvctl start
Network UPS Tools - UPS driver controller 2.0.5
Network UPS Tools - BCMXCP UPS driver 0.11
2005 Nov 07
3
HP/Compaq Rackmount UPS Support?
Hi,
I have an HP R5500XR and a Compaq R3000XR that I would like to use with nut.
I searched the compatibility lists and the mail list archives but couldn't
find anything.
They both have 9 pin serial ports.
Can anyone give me any information about them, and if they are supported by
nut?
Thanks,
Denny Fox