search for: batt

...attachments/20130422/ddad99d5/attachment-0001.html> -------------- next part -------------- ./mge-utalk -DDD -a ups0 Network UPS Tools - MGE UPS SYSTEMS/U-Talk driver 0.93 (2.6.5) 0.000000 debug level is '3' 2.105848 Got model name: NAK 3.193505 Syst Stat >NAK< 3.741509 Batt Stat >NAK< 4.280759 Load Stat > < 4.828750 Bypass Stat >ACK< 5.376322 Syst Stat >NAK< 5.924311 Batt Stat >NAK< 6.464392 Load Stat > < 7.012386 Bypass Stat >ACK< 7.559960 Syst Stat >NAK< 8.107945 Batt Stat >NAK< 8.64719...

UPS: http://www.eaton.com/Eaton/ESeriesUPS/DXUPS/index.htm?wtredirect=www.eaton.com/DXUPS I have the same problem on two different computers. The first one is running Ubuntu 12.10 i386 , the second one is running Debian 6.0 x64. Both of them are updated. I tried using different serial cable but the result is the same. The connection to the ups using Windows 7 and Winpower is working fine on

...8+ 0 - Ai --> 5 0 It's not recognized very well by the current (from CVS) mge-utalk driver: [root@srv01 ~]# /home/rog/src/nut/drivers/mge-utalk -i 20 -DDD -u root /dev/ttyS0 Network UPS Tools - MGE UPS SYSTEMS/U-Talk driver 0.86 (2.1.0) debug level is '3' UPS response to 30% Low Batt Level was ? initups: OnDelay unavailable initups: OffDelay unavailable initinfo: 'Si 1' unavailable, switching to 'Si' command initinfo: Si == >3000 44 0< . CAUTION : This is an older model. It may not support too much polling. Please read man mge-utalk and use pollinterval No...

Hello all, long time away from this list, glad to be around again! I have this Powercom Vanguard VGN VGD-20K31. Some details of this model: * 3-phase input, single phase output * Model has 240V / 12V9AH x 20 x 2SET, plus another set of 20 batteries. All in all, 3 sets * Serial connection to Windows 2k3 server with UPSMon Now I was strongly considering replacing the bundled no-good upsmoon crap, with NUT, in order to enable shutdown of other systems powered the same ups, using a NUT master-slave installation. So, I installed NUT on a...

...applied the patch you sent me (https://github.com/zykh/nut/tree/issue-441) and it works correctly (obviously in Level 5 of Debug I see "missing CR...etc.."). As for now there are 2 modification I'd like to suggest you: - For Online Type UPSs the Megatec protocol describes that the battery voltage is provided in the form of V per Cell, not V per block, but the driver doesn't care because I see 2.21V instead of 36V in UPSC (Battery.voltage). I think that this should be corrected so the customer can see the string voltage and not the single Cell voltage (Megatec 0.06). - About...

It there a way to get the genericups driver to set a output on the serial port? On the APC BackupPro the will pull the BattLow line low with a pull down resistor it's up to you to from the PC side to pull the line high with a pullup resistor from one of the RS232 output pins. Then monitor the line with another pin. Regards Rabie -------------- next part -------------- An HTML attachment was scrubbed... URL: http:/...

...41>) and it works correctly (obviously in Level 5 of Debug I see "missing CR...etc.."). > > Good to hear. > > > As for now there are 2 modification I'd like to suggest you: > > > > > > - For Online Type UPSs the Megatec protocol describes that the battery voltage is provided in the form of V per Cell, not V per block, but the driver doesn't care because I see 2.21V instead of 36V in UPSC (Battery.voltage). I think that this should be corrected so the customer can see the string voltage and not the single Cell voltage (Megatec 0.06). > &gt...

...hen the KRAULER subdriver check these UPS answers it uses wrong constants to check the lenght of the received packets, so these commands are considered as "not available" by NUT. In particular, without the availability of the "F" command, is not possible for NUT to calculate the battery capacity level. In my opinion this is a problem of the driver, because our UPSs respect the communication protocol document from Megatec and also because the blazer_ser works fine. We have tested different UPSs models but the problem is the same. - "Q1": in this case the problem is on...

.... However, I fear both do not feature the LB warning via ups.status. We can shut down all less important servers (conencted to a single UPS) via upssched and a 30s timer after OB, but I still struggle hard to arrive at a working schema how to shut down more important servers based on remaining battery charge/projected run time and/or low batt warning. Looking at clients/upsmon.c I think, without the flag ST_LOWBATT set for ups->status, MINSUPPLY will never truly be considered a usable threshold and thus I'm left with a machine which would not shutdown. Thus, what would e the best w...

My $0.02: LB is baked in to nut behavior. So if a UPS doesn't report LB, then it makes sense to synthesize it. Synthetic LB is the cleanest fix at the earlier processing point. One could have a config that is basically synthetic-lowbatt-percent that generates LB if (as Jim says) on battery, not calibrating, and batt% <= that. One could have a similar config synthetic-lowbatt-voltage same thing except voltage. The mapping from voltage and current (and history) to % is difficult, but this lets people have another...

Hi all, On 5/16/23 20:08, Carsten Aulbert wrote: > Idly browsing the client sources, I guess I could try to add our logic > here[1] and use [2] to gather the battery stats from our UPS and then > decide if this UPS is considered critical or not. But for this, I would > need to dust off/excavate my ancient poor C knowledge ;-). > > I guess I will give this a try unless someone has a brilliant idea and > could save my sanity. I've given...

...d document this for ups.conf (man page and examples), including a note that for devices which do provide a healthy LB these values may be set to 0 safely. Wondering if non-zero defaults should be there anyway. @Community, WDYT? Also, this critical-state check should be done only when the UPS is on battery (and perhaps not calibrating), to avoid shutdowns as soon as we start after an outage :) (In a similar fashion, enterprise UPSes are known to raise an FSD to their subscribers, if manually powered on before criticality thresholds are cleared, since they can't guarantee a safe shutdown to kee...

Hi Gene, On 5/16/23 21:08, gene heskett wrote: > Take an extra vitamin b1 and start hacking ;o) yeah ;-) > > Seriously, if its that important, do as I did when my last wife was > dying of COPD. :( sorry to hear > Leave your ups setup as is but for under $10k (USD), > have an automatic home sized standby generator installed to run the > important stuff, no room for

...anced over the server/ directory and was not sure where even to begin hooking this in. Should this be directly in upsd (upsd.c) or rather in/near the driver level (driver/main.c)? > > Yes, this could be in upsmon, but that's not synthetic LB, it's > choosing to shutdown if battery is below X. Yeah, this should be independent and fully on the client side (and thus upsmon) where each client can choose how to react to a UPS on battery. > We should be clear on "critical" vs "LB" and clean up the language to > be consistent. For upsmon, I wo...

Hi David As per the link http://www.llondel.org/ups.shtml & the final testing paragraph. I have set up a Lantech UPS similiar to your write up for your Powersure Proactive and Powersure Personal UPS's On LOW BATT it shuts down OK. BUT as with other many UPS's during the wait period from low batt to start of shutdown ... IE [SHUTDOWNCMD "/sbin/shutdown -h +20"] 20 minutes in this case. Reapplying AC power before the 20 minute mark stops the shutdown & all is normal again. This op...

...certain tag that specifies which image should be booted. How difficult would it be to make this modification to PXElinux? What problems can you see with this plan? What resources are available for those of us that are new to PXElinux development? Thanks for your time and insight. -- Cody Batt codyb at byu.edu

...power when the > mains go down. > > We shut down the compute nodes via upssched and a 30s timer. If the > power cut is shorter than that, they will simply continue running as the > timer is cancelled by nut. Otherwise they will simply power down and > stretch our 6-8 minutes battery buffer to much longer. > > What I'm more worried about then are the storage servers, networking, > head nodes and a couple of special nodes which are powered by both UPSes. > > We could use upssched also for those nodes, but the pipelining of > messages makes it a bit h...

...relb? flag is set. >> 2. In status_set(), if ignorelb is set, and the status being set >> (presumably from the UPS) is LB, it?s ignored. In other words, LB >> reported by the UPS is ignored. >> 3. In status_commit(), if ignorelb is set, there?s code to compare >> battery.charge against battery.charge.low and battery.runtime >> against battery.runtime.low. If either is below the ?low? setting, ? >> LB? is added to the status. (So ?OL? would become ?OL LB? and ?OB" >> would become ?OB LB?. And note that the two ?.low? settings can be &...

...end. Anyway, I setup the VPN Concentrator to auth off of the samba box, and when I test it with the test option, and it works, but when I try to auth a pptp tunnel, it fails saying the password is wrong. Any ideas? My vote is for the stupid concentrator to meet some thermite or a metal baseball batt. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part Url : http://lists.samba.org/archive/samba/attachments/20031031/3027eb72/attachment.bin

...I would appreciate your comments. Thanks for your consideration. Best wishes to all Said K?K?AM -------------- next part -------------- Extended megatec protocol [CMD] [RESPONSE] *UPS information (Mfg, Model, FW) [I] # HV 1K 00001903 *UPS ratings (Voltage, Current, Nominal BattVolt, Nominal frequency) [F] #220.0 004 036.0 50.0 *UPS ratings (new) [QRI] (220.0 004 036.0 50.0 *UPS status (input V, fault V, output V, load, output freq, batt current, UPS temp, flags -> 8 bit) [Q1] (209.7 209.7 219.7 019 50.0 2.32 23.3 00000001 *UPS status (input V, fault V, output V, load,...