Displaying 20 results from an estimated 192 matches for "chrg".
Did you mean:
chr
2005 Oct 09
1
apc-hid tests with the new ups_status updates
Peter,
Here are the transitions that I have tested with your latest changes
(on the APC/Back-UPS ES 650):
1) OL ==> OB DISCHRG followed by OB DISCHRG ==> OL (no CHRG inbetween)
2) OL CHRG ==> OL
3) OL CHRG ==> OL CHRG LB (by manipulating battery.charge.low)
4) OL CHRG LB ==> OL CHRG (i.e. transition from below)
5) OB DISCHRG ==> FSD OB DISCHRG LB followed by proper shutdown
In other words, as far as I can se...
2015 Mar 30
1
On ups.status CHRG/DISCHRG Vs battery.charger.status
Hi Charles,
2015-03-29 0:44 GMT+01:00 Charles Lepple <clepple at gmail.com>:
> On Mar 25, 2015, at 4:11 AM, Arnaud Quette <arnaud.quette at gmail.com>
> wrote:
>
> > 1) Keep the legacy CHRG / DISCHRG status bits for ups.status, along with
> the complementary ones for battery.charger.status. And advocate (document)
> for the use of / switch to the latter, that is more suitable for publishing
> such information. All that with an impact on all the NUT driver, and a
> transiti...
2008 Feb 20
2
MGE pulsar evolution 3000 discharges without nut noticing
I'm running nut 2.0.1 with an MGE pulsar evolution 3000 with the
mge-utalk (serial) driver on NetBSD 3.1 .
I had a very strange occurance in my basement datacenter this early AM.
the following was logged by upslog:
20080219 023452 100.0 123.0 049.0 [OL CHRG] NA 60.00
20080219 023522 100.0 122.8 049.0 [OL CHRG] NA 60.00
20080219 023552 098.0 123.0 049.0 [OL DISCHRG] NA 60.00
20080219 023622 097.0 123.0 049.0 [OL DISCHRG] NA 60.00
...
20080219 063429 019.0 122.6 049.0 [OL DISCHRG] NA 60.00
20080219 063459 019.0 122.8 049.0 [OL DISCHRG] NA 60.00
200802...
2007 Jun 29
0
CHRG / DISCHRG status
(was: false alerts/shutdown)
2007/6/18, Arjen de Korte <nut+devel at de-korte.org>:
>
> > driver.name: newhidups
>
> [...]
>
> > ups.status: OL CHRG
>
> Euhm, there is no status 'CHRG' according to 'docs/new-drivers.txt'
> folks. If you feel the need to create new status flags, at the very
> least mention them in the section 'Status data' in this file. Unless you
> document it somewhere, it's of no use...
2015 Mar 25
2
On ups.status CHRG/DISCHRG Vs battery.charger.status
...ools/nut/tree/pull_158_bcmxcp_rebased
It has introduced the battery.charger.status variable, which is something I
wanted to implement since around 2007.
However, while considering a similar implementation for usbhid-ups, and
thinking a bit more broadly, this new variable tends to collide with the
CHRG / DISCHRG status bits from ups.status, and adding 2 more (floating and
resting).
There, we have 2 options:
1) Keep the legacy CHRG / DISCHRG status bits for ups.status, along with
the complementary ones for battery.charger.status. And advocate (document)
for the use of / switch to the latter, that...
2015 Mar 28
0
On ups.status CHRG/DISCHRG Vs battery.charger.status
On Mar 25, 2015, at 4:11 AM, Arnaud Quette <arnaud.quette at gmail.com> wrote:
> 1) Keep the legacy CHRG / DISCHRG status bits for ups.status, along with the complementary ones for battery.charger.status. And advocate (document) for the use of / switch to the latter, that is more suitable for publishing such information. All that with an impact on all the NUT driver, and a transition period to address...
2006 Nov 15
1
Tripp Lite OMNI900LCD
...fo...
dstate_init: sock /var/state/ups/newhidups-auto open on fd 5
upsdrv_updateinfo...
Waiting for notifications...
=>Got 1 HID Objects...
battery.charge = 83
upsdrv_updateinfo...
Waiting for notifications...
=>Got 8 HID Objects...
ups.status = !shutdownimm
ups.status = online
ups.status = chrg
ups.status = !dischrg
ups.status = !replacebatt
find_hid_info: unknown variable: UPS.PowerSummary.PresentStatus.
find_hid_info: unknown variable: UPS.PowerSummary.PresentStatus.
find_hid_info: unknown variable: UPS.PowerSummary.PresentStatus.
upsdrv_updateinfo...
Waiting for notifications...
=&...
2020 Feb 18
2
UPS shuts down after restart
...gt; How old is this battery?
About half a year. But I already went into this issue some months before with the 2.7.4 Raspbian package but havn't found the time to fix it.
>> 8. Seconds later the UPS reboots, killing the RasPi
>> 9. UPS and RasPi are up and running again - "OL CHRG"
>>
>> The UPS is set to "offdelay=5" and no ondelay
> What happens if you use the default values of offdelay=20 and ondelay=30
> seconds, or longer?
With defaults its the same.
But I noticed two other details:
1. I was a bit wrong with step 7 and 8 - Looks like...
2012 Mar 21
5
Socomec sicon Netys 2000 PR ups USb driver for ubuntu
Hello i tried to connect my netys 2000 pr ups to ubuntu 11.10 and i have a problem connecting it. After readin a few post i realized to dianosse the connection.
I need help resolving the connextion issue
So here is the response to??/lib/nut/usbhid-ups -u root -DDDDD -a netys:
Network UPS Tools - Generic HID driver 0.35 (2.6.1)
USB communication driver 0.31
? ?0.000000 ? ? send_to_all: SETINFO
2020 Feb 17
2
UPS shuts down after restart
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20200217/b486de30/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: usbhid.zip
Type: application/zip
Size: 4031 bytes
Desc: not available
URL:
2017 Jun 09
4
Proposed new documentation "Configuration Examples"
Most of the questions asked in the nut-user mailing list seem to me to be
either erudite technical discussion of new and exotic UPS units, or n00b
questions of the style "I have this old UPS so I installed NUT but it
didn't work".
NUT is thoroughly documented with man pages and User Manual, but from my
own experience it is not easy for Joe N00b to know what a working setup
2018 Jan 16
2
Eaton 5PX after battery replacement still says "replace battery" in NUT
...30
ups.load.high: 105
ups.mfr: EATON
ups.model: Eaton 5PX 2000
ups.power: 611
ups.power.nominal: 2000
ups.productid: ffff
ups.realpower: 504
ups.realpower.nominal: 1800
ups.serial: G098D27047
ups.shutdown: enabled
ups.start.auto: yes
ups.start.battery: yes
ups.start.reboot: yes
ups.status: ALARM OL CHRG RB
ups.test.interval: 604800
ups.test.result: Done and passed
ups.timer.shutdown: 0
ups.timer.start: 0
ups.type: offline / line interactive
ups.vendorid: 0463
And here?s the output from /usr/local/nut/bin/usbhid-ups -DD -a <ups-name>
I had to ^C it after a bit as it was just retrying. Look...
2017 Jun 21
2
Proposed new documentation "Configuration Examples"
...f the colours so that the text will be more
easily readable. The colours in the text are very easy to change, but
diagrams done with xfig need more effort. I'd like to hear from someone
with the problem what the result looks like, and get some agreement before
making the changes.
> The CHRG and DISCHRG status flags are probably confusing for an
> entry-level text, and are more informational than the critical OL/OB/LB
> flags. Some models do not indicate CHRG or DISCHRG, and others will omit
> CHRG if they are OL but not topping off the battery.
Good point, I have removed...
2006 May 02
5
Newhidups gets unbound after a while
...tdown work very well. Only
continous scanning seems to fail.
Following are the logs:
[root@xa000000 root]# newhidups -a ups_on_usb -DD
<...> Time range from 15mn to 6 hours, depending...
upsdrv_updateinfo...
Waiting for notifications...
process_status_info: online
process_status_info: !dischrg
process_status_info: chrg
process_status_info: !shutdownimm
process_status_info: !lowbatt
upsdrv_updateinfo...
Waiting for notifications...
process_status_info: online
process_status_info: !dischrg
process_status_info: chrg
process_status_info: !shutdownimm
Can't retrieve Report 1 (-32/32): Bro...
2005 Oct 09
2
Re: apc-hid tests, ups_status updates
Arnaud,
> first, even if your battery is full, and your ups is online, there is a
> small amount of power drawn. So having always is CHRG status is normal.
> In fact, these complementary status are more interesting for higher end
> UPSs.
>
> second, these status need not to be handled like LB, as each one clears the
> other. While LB had no pending event (!LB) before...
>
> or did I get you wrong?
First, I fully...
2005 Jul 19
1
MGE Evolution 1500 on Debian
...Seens I did a test.battery.start, my UPS goes off (beep!) once per week
(same day, same hour). I guess there should be a very easy explanation
for this, unfortunatly, I haven't found it yet.
I've tried to upgrade to nut-2.0.2 (Etch package), my ups.status is now
changing from: "OL CHRG OFF" to "OFF BYPASS" or "Data stale".
I've then switch back to nut-2.0.1 (Sarge package) and the UPS is
reported as "OL CHRG".
This is strange behaviour for me. Should I use mge-shut instead? Is the
mge-utalk driver report is wrong in nut-2.0.1?
Thanks fo...
2020 Feb 18
0
UPS shuts down after restart
...his battery?
> About half a year. But I already went into this issue some months before with the 2.7.4 Raspbian package but havn't found the time to fix it.
>
>>> 8. Seconds later the UPS reboots, killing the RasPi
>>> 9. UPS and RasPi are up and running again - "OL CHRG"
>>>
>>> The UPS is set to "offdelay=5" and no ondelay
>> What happens if you use the default values of offdelay=20 and ondelay=30
>> seconds, or longer?
> With defaults its the same.
>
>
> But I noticed two other details:
> 1. I was a...
2017 Jun 21
0
Proposed new documentation "Configuration Examples"
...be
>more
>easily readable. The colours in the text are very easy to change, but
>diagrams done with xfig need more effort. I'd like to hear from someone
>
>with the problem what the result looks like, and get some agreement
>before
>making the changes.
>
>> The CHRG and DISCHRG status flags are probably confusing for an
>> entry-level text, and are more informational than the critical
>OL/OB/LB
>> flags. Some models do not indicate CHRG or DISCHRG, and others will
>omit
>> CHRG if they are OL but not topping off the battery.
>
>...
2017 Mar 23
5
Fatal EEPROM fault!
Hello,
Sorry if any of this is obvious - I'm new to NUT.
NUT via upsc is displaying (edited for length):
device.model: Eaton 5P 2200
device.type: ups
driver.name: usbhid-ups
ups.alarm: Fatal EEPROM fault!
ups.status: ALARM OL CHRG
ups.test.interval: 604800
ups.test.result: Done and passed
driver.version: 2.7.2
driver.version.data: MGE HID 1.33
driver.version.internal: 0.38
Is this possibly a firmware or configuration issue?
Does NUT report the firmware version (it's not jumping out at me in
the upsc output)?
Can NUT u...
2013 Dec 07
0
Plea for a more loquacious nut
Charles Lepple wrote, On 12/4/2013 4:11 PM:
> On Dec 4, 2013, at 3:52 PM, Kris Jordan wrote:
>
>> Roger Price wrote, On 12/4/2013 12:35 PM:
>>> I would like nut to become more loquacious, and to log a much more complete report of its activity. At present nut reports that its components have started operation but does not automatically log their activity when UPS's switch