similar to: How to lower float charge voltage of an APC Smart UPS - corrected

You can lower the float charge voltage that APC Smart UPS units such as SU1000NET or SU700NET supply to the battery. This is important when substituting Lead Acid Deep Cycle batteries for the usual sealed maintenance free batteries provided. Here are the instructions: 1) Only do this if you are fully trained and qualified to work on Lead Acid powered UPS. These units contain lethal voltages

Jim Klimov via Nut-upsdev <nut-upsdev at alioth-lists.debian.net> writes: > During discussion at > https://github.com/networkupstools/nut/pull/2430#discussion_r1592317940 I > found that while `nut-names.txt` documents the `battery.charge.low` as the > "Remaining battery level when UPS switches to LB (percent)", there is no > counterpart as `battery.charge.high`.

Thanks Cristoph, I have that code in my backend, but unless I do the following, the registers are never considered 'live' into the call. / Handle a function call let isCall = 1, Defs = [ R0, R1, R2, R3, R4, R5, R6, R7, R8, R9, R10, R11, R12, R13, R14, R15, R16, R17, R18, R19, R20, R21, R22, R23, R24, R25, R26, R27, R28, R29, R30, R31, R32, R33, R34, R35, R36, R37, R38, R39, R40, R41,

Dear Sir, Please tell me if u have any method to increase the charging current of APC smart 1000/1400VA with and without external battery bank option. I am using externally 40 and 80 Amp lead acid batteries but charging time is too long. Please help me ASAP. Regards, Afzaal Ahmad UPS Engineer afzaal.ahmad at sbp.org.pk -------------- next part -------------- An HTML

Hello all, During discussion at https://github.com/networkupstools/nut/pull/2430#discussion_r1592317940 I found that while `nut-names.txt` documents the `battery.charge.low` as the "Remaining battery level when UPS switches to LB (percent)", there is no counterpart as `battery.charge.high`. First I thought one could be just added... but for that matter, what could one logically mean -

>From my understanding, alone with other NUT behaviors it would not. Even if NUT drivers already do (or are changed to) react to the actual charge/runtime going below this setting to fabricate an LB status, this as a driver setting/override would have immediate effect on all clients like `upsmon` watching the device status on their shared data server. This simultaneously requested shutdown

>From my understanding, alone with other NUT behaviors it would not. Even if NUT drivers already do (or are changed to) react to the actual charge/runtime going below this setting to fabricate an LB status, this as a driver setting/override would have immediate effect on all clients like `upsmon` watching the device status on their shared data server. This simultaneously requested shutdown

Hi Jim, I was thinking about setting different values for each device , so the first system has higher values and shutdowns?earlier:override.battery.charge.lowoverride.battery.runtime.low Won?t it work ? Best Regards,Strahil Nikolov? On Sunday, August 6, 2023, 7:41 PM, Jim Klimov via Nut-upsdev <nut-upsdev at alioth-lists.debian.net> wrote: Yeah, I have no lack of imagination about

Hi Jim, I was thinking about setting different values for each device , so the first system has higher values and shutdowns?earlier:override.battery.charge.lowoverride.battery.runtime.low Won?t it work ? Best Regards,Strahil Nikolov? On Sunday, August 6, 2023, 7:41 PM, Jim Klimov via Nut-upsdev <nut-upsdev at alioth-lists.debian.net> wrote: Yeah, I have no lack of imagination about

Hello all again, While looking at https://github.com/networkupstools/nut/issues/2014 I understood that I am not sure if currently NUT has a standard way of triggering a shutdown based on remaining charge or runtime, if a device/driver lacks a `battery.charge.low` setting but has readings for the values themselves. Such an ability rings a bell to me, but maybe it is specific to some drivers

Hello all again, While looking at https://github.com/networkupstools/nut/issues/2014 I understood that I am not sure if currently NUT has a standard way of triggering a shutdown based on remaining charge or runtime, if a device/driver lacks a `battery.charge.low` setting but has readings for the values themselves. Such an ability rings a bell to me, but maybe it is specific to some drivers

I think it can be useful in a scenario like: - Large UPS, that powers 2 hosts: one is VMServer with just a small boot driver and the second is a NAS with all the disks for the first server. - UPS is connected by USB to another host (such as a small Raspberry PI), acting as the NUT primary. - Both machines served by UPS are NUT secondaries. - The NAS box can only shutdown one the VMware is fully

I think it can be useful in a scenario like: - Large UPS, that powers 2 hosts: one is VMServer with just a small boot driver and the second is a NAS with all the disks for the first server. - UPS is connected by USB to another host (such as a small Raspberry PI), acting as the NUT primary. - Both machines served by UPS are NUT secondaries. - The NAS box can only shutdown one the VMware is fully

Yeah, I have no lack of imagination about scenarios where that can be useful - just was surprised to see no apparent "here's how you do it" sort of man page or something, Although technically the shutdown scenario like yours, where a NAS server only is told to go down - or actually does so (which is substantially different and can be implemented elsewhere) - after its consumers go

Yeah, I have no lack of imagination about scenarios where that can be useful - just was surprised to see no apparent "here's how you do it" sort of man page or something, Although technically the shutdown scenario like yours, where a NAS server only is told to go down - or actually does so (which is substantially different and can be implemented elsewhere) - after its consumers go

Hi guys, I've been experiencing a very strange issue with my Digium Card TDM400 as of this week. It has two FXS and two FXO. The FXO modules (both of them) never goes on-hook after hanging up in Asterisk. It had worked perfectly well for over four years. I put an ammeter in series with the line and the card, and immediately after plugging the connector to the card, I got 26mA in the circuit

This is really cool! PREMIUM CHANNELS........Descrambled! EASY to assemble plans for only $7.00 ! YOU WILL BE WATCHING all your FAVORITE PAY STATIONS featuring MOVIES, SPORTS. Adult entertainment, and any other scrambled signal NEXT WEEK! You can EASILY assemble a cable descrambler in less

Hi list! Running Asterisk 20.0.0 on CentOS 7, logging CDRs using cdr_adaptive_odbc to mariadb-server-5.5.68 (via mariadb-connector-odbc-3.1.7-ga-rhel7) Using chan_sip. I'm facing the problem when there is a sudden spike of calls, some of the calls that are being made during those spikes hang forever basically. This looks like this: [root at voip]# asterisk -rx 'core show channels

Hej! Hope nut-upsuser is an appropriate place to post additional info about the smartups protocol, please tell me if not. I got an APC Smartups 2200 (5U Rack Mount, European/230V version, 48V batteries) a couple of days ago, was very happy to find the protocol description at http://www.networkupstools.org/protocols/apcsmart.html, and started to play. At the point when everything was working

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 between OB and OL. I believe that this under-reporting of