search for: status_set

...ich the timer is reset is much higher than once per minute, so it won't slip and accidentaly let the UPS shutdown. However, I guess some UPSes may be innacurate with values <= 1 minute. This may be a good idea. > - if (query.flags[FL_LOAD_OFF] == '1') { > - status_set("OFF"); > - } else if (query.flags[FL_ON_BATT] == '1' || query.flags[FL_BATT_TEST] == '1') { > +// } else > + if (query.flags[FL_ON_BATT] == '1' || query.flags[FL_BATT_TEST] == '1') { > status_set("OB");...

...+ ret = ser_send(upsfd, "C\r"); if (ret != 2) *************** *** 258,263 **** --- 282,290 ---- double bvoltp; float lowbattvolt = 0; + + sendcr_and_clear_buf(); + ret = ser_send(upsfd, "Q1\r"); if (ret != 3) *************** *** 320,331 **** status_set("OL"); /* on line */ /* only allow these when OL since they're bogus when OB */ ! if (pstat[2] == '1') { /* boost or trim in effect */ ! if (util < lownorm) ! status_set("BOOST"); ! ! if (util > highnorm) ! status_set("TRIM")...

Dear Andreas, some googling revealed, you created a driver for the xanto series of online-usv.de. In what state it is currently? I've to manage a S2000 and would like to use nut for it, is it usable by now? Do you need another tester? TIA, Pete

...TE_OMNIVS2) { + switch(s_value[2]) { + case '0': + dstate_setinfo("battery.test.status", "Battery OK"); + break; + case '1': + dstate_setinfo("battery.test.status", "Battery bad - replace"); + break; + case '2': + status_set("CAL"); + break; + case '3': + status_set("OVER"); + dstate_setinfo("battery.test.status", "Overcurrent?"); + break; + case '4': + /* The following message is confusing, and may not be accurate: */ + /* dstate_setinfo(&qu...

Hi Kirill, just to notify you that your al175 driver is being removed from the NUT tree, as of 2.4.0-pre1. if you wish to see it entering the tree again, please contact the Development mailing list to talk about it. Merry Christmas and happy New Year. Arnaud -- Linux / Unix Expert R&D - Eaton - http://www.eaton.com/mgeops Network UPS Tools (NUT) Project Leader -

...or on battery (0) */ online = (reply[3]&4)>>2; /* * 2nd bit of 4th byte indicates battery status; normal (1) * or low (0) */ battery_normal = (reply[3]&2)>>1; status_init(); if (online) { status_set("OL"); } else { status_set("OB"); } if (!battery_normal) { status_set("LB"); } status_commit(); dstate_dataok(); } /* * The shutdown feature is a bit strange on this UPS IMHO, it * swi...

...* or on battery (0) */ online = (reply[3]&4)>>2; /* * 2nd bit of 4th byte indicates battery status; normal (1) * or low (0) */ battery_normal = (reply[3]&2)>>1; status_init(); if (online) { status_set("OL"); } else { status_set("OB"); } if (!battery_normal) { status_set("LB"); } status_commit(); dstate_dataok(); } /* * The shutdown feature is a bit strange on this UPS IMHO, it * switches the...

...* or on battery (0) */ online = (reply[3]&4)>>2; /* * 2nd bit of 4th byte indicates battery status; normal (1) * or low (0) */ battery_normal = (reply[3]&2)>>1; status_init(); if (online) { status_set("OL"); } else { status_set("OB"); } if (!battery_normal) { status_set("LB"); } status_commit(); dstate_dataok(); } /* * The shutdown feature is a bit strange on this UPS IMHO, it * switches the...

...;, "%3d", temp); + dstate_setinfo("ups.load", "%3d", load); + dstate_setinfo("input.frequency", "%02.2f", freq); status_init(); /* Battery Voltage Condition */ - switch (buf[0]) { + switch (bcond) { case '0': /* Low Battery */ status_set("LB"); break; case '1': /* Normal */ break; default: /* Unknown */ - upslogx(LOG_ERR, "Unknown battery state: %c", buf[0]); + upslogx(LOG_ERR, "Unknown battery state: %c", bcond); break; } /* Load State */ - switch (buf[1]) { + switc...

Arjen de Korte wrote: > > + * drivers/apc-hid.c: > + - Commented out the 'fullycharged' status. If anyone can explain the > + use of this, please step forward. This flag is defined on p.36 of the "Universal Serial Bus Usage Tables for HID Power Devices", Release 1.0 November 1, 1997, a USB standards document available on the web. The document defines this

Hmm. Is there maybe something there already that will do this? Maybe kind of back-handed. In drivers/dstate.c, I see: In status_init(), if ?driver.flag.ignorelb? is set in the driver state, the ?ignorelb? flag is set. 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. 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...

...checking with the list, to ask if the functionality that I describe above is already available with NUT or if I need to modify the driver so that a building alarm gets treated in the same way as an 'On battery' event. If I need to modify the driver, it might be as simple as my calling status_set("OB") in the right place. But this is based from ten minutes of browsing the code, so it could be naive. PS: I'd be grateful if you could copy me in any replies, not just reply 'to the list'. Cheers, Bruce

...'; low_batt = fromhex(p[21]) & 8 || fromhex(p[20]) & 1; is_off = p[11] == '0'; trimming = p[33] == '1'; boosting = 0; /* FIXME, don't know which bit gets set (brownouts are very rare here and I can't simulate one) */ status_init(); if (low_batt) status_set("LB "); else if (trimming) status_set("TRIM"); else if (boosting) status_set("BOOST"); else status_set(is_online ? (is_off ? "OFF " : "OL ") : "OB "); /* setinfo(INFO_STATUS, "%s%s", * (util < lownorm) ? "...

Hi, I'm having a hard time configuring a Mustek Powermust 600VA ups to work via USB with nut. I read somewhere that nut works OK via the rs232 cable, but unfortunately I don't have a COM port in my computer. The kernel detects the ups as an Xbox pad :) and loads the xpad module. I tried running /lib/nut/megatec with different /dev/ttySx but it displays megatec protocol UPS was not

...ch) to do the HAL init and specifics. So it *doesn't* touch the drivers code at all. One code base to rule them all ;-) * each time the driver calls dstate_setinfo() to add/update a data, a lookup function will translate it into HAL data, using a lookup table in dstate-hal.c * the same goes for status_set(), for updating UPS status data. 3) Some limitations and remainders ------------------------------------------------- * we can't support multiple identical UPS (== using the same driver!) for the moment, due to the fact that we use the "auto" value for the port. We will need a way t...

Hi again, I've succeeded in compiling the svn trunk with the automake tools and wish to say thank you to Charles Lepple for his help. After fixing some parameters in the hotplug script I can now get access to the UPS on /dev/usb/hiddev0 (I added productid and vendorid of my ups to the usermap). I've decided to try the newhidups driver with -x generic parameter and got this response :

...lowing the remarks in: http://www.mail-archive.com/nut-upsdev at lists.alioth.debian.org/msg02294.html Major changes from v1: - handle battery.charge and battery.runtime checks at main.c level - handle "immutable but writable" conflict gracefully at driver level - dstate_getflags() and status_set_uniq() added (hope this is fine) Apart from that, minor changes and adjusted help. Michal Soltys (3): drivers/dstate: add dstate_getflags() and status_set_uniq() drivers/main.c: add tests for LB condition drivers/apcsmart: updates drivers/apcsmart.c | 562 +++++++++++++++++++++++++++++++...

reported through launchpad: https://bugs.launchpad.net/bugs/253999 the possible regression is between nut 2.0.1 (sarge) and 2.2.1 (confirmed Jamie?) @Arjen: it may be related to some of your changes there... @Jamie: we'll need some debug output from the drivers (-DDD) Arnaud

This patch introduces a handful of new options, I mentioned earlier in: http://www.mail-archive.com/nut-upsdev at lists.alioth.debian.org/msg02088.html See the large commit message in the follow-up for the details and rationale. I realize it's a bit larger diff - so if it's required I can split it into few smaller ones. Michal Soltys (1): APC smart driver update and new features.

...via Nut-upsuser wrote: > Hmm. Is there maybe something there already that will do this? Maybe > kind of back-handed. > > In drivers/dstate.c, I see: > > 1. In status_init(), if ?driver.flag.ignorelb? is set in the driver > state, the ?ignorelb? 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...