search for: charg

I''m working with three models: - Charge. has_many :budget_plans - BudgetPlan. belongs_to :charges, :rollups - Rollup. has_many :budget_plans This works out perfectly. A budget plan contains the ID of a charge and rollup and then there''s a 3rd attribute for hours. So working with data is no problem. My budget plan scaffold...

...m TableA for all the records in TableA that don''t exist in TableB. TableA and TableB are different but do have one field in common that i am comparing. The tables are not related in anyway. right now I have a find_by_sql query located in a model that looks like this: def self.absent_charges find_by_sql <<-QUERY SELECT sources.charge_id_number, sources.charge_name, sources.offense_level FROM sources LEFT JOIN charges ON sources.charge_id_number = charges.charge_id_number WHERE charges.id IS NULL QUERY end I also need to dedupe what e...

Hello all: Does anyone know of a tool/project that will allow me to read the battery condition (not the charge status) on a Dell laptop battery? Under XP there is a utility that warns that the battery is still holding a charge but that the battery is degraded and should be replaced. Also, not sure if this is possible, but I would like to control how the laptop charges the battery. I tend to have the lapt...

Thanks for the insights, especially these: > If this is about having variables with thresholds that control devices or cause synthetic setting of some variable (like turning on LB if charge% is < battery.charge.low), then it makes sense. > "battery voltage is unreasonably high" is a reasonable concept. <...> I would not call it HB, though because that makes it sound parallel to LB, which is about believed remaining capacity, not detection of overcharging failur...

I can''t figure out how to get the collection_select to correctly identify and select the appropriate option in the drop down to begin with. i have checked that charge.offense_level contains the correct value to begin with (a number between 1 and 10) but the view still defaults to the first option and not the one contained in the charge.offense_level. what am i doing wrong? any suggestions? I have also tried: <%= collection_select "charge", &quo...

...s is powered off. To stop it, unplug the wall socket ;) I proceed 3 tests, - with the serial interface and the megatec driver - with the usb interface and the megatec_usb driver - a forced shutdown with upsmon 1. Monitoring with the serial interface The output gives me, # upsc mustekups battery.charge: 100.0 battery.voltage: 27.60 battery.voltage.nominal: 24.0 driver.name: megatec driver.parameter.pollinterval: 2 driver.parameter.port: /dev/ttyS0 driver.version: 2.2.0-export? driver.version.internal: 1.5.4 input.frequency: 50.1 input.voltage: 230.5 input.voltage.fault: 230.5 input.voltage.maxim...

...s is powered off. To stop it, unplug the wall socket ;) I proceed 3 tests, - with the serial interface and the megatec driver - with the usb interface and the megatec_usb driver - a forced shutdown with upsmon 1. Monitoring with the serial interface The output gives me, # upsc mustekups battery.charge: 100.0 battery.voltage: 27.60 battery.voltage.nominal: 24.0 driver.name: megatec driver.parameter.pollinterval: 2 driver.parameter.port: /dev/ttyS0 driver.version: 2.2.0-export? driver.version.internal: 1.5.4 input.frequency: 50.1 input.voltage: 230.5 input.voltage.fault: 230.5 input.voltage.maxim...

Hello all, I have a CyberPower Systems CP850PFCLCD that I'm hooking up to NUT 2.4.3 from apt running under Ubuntu 10.04. Using the usbhid-ups driver, things *seem* to work at first glance, but there are some odd issues. The most notable issue is that the battery.charge indicator reads 120 when at full charge. I came across this post here: http://lists.alioth.debian.org/pipermail/nut-upsuser/2007-September/003222.htmlbut it looks like the user never supplied the necessary data. The other issue that I found was that the LB flag is sent way to early when I unplug...

...the second case, the UPS shut off after 20 seconds. However, it did not turn back on after I reconnected it to power. Fifth Experiment ################ To answer Roger's questions, I did the following: - ran `upslog -f '{"time": "%TIME @Y- at m-@dT at H:@M:@S%", "charge": %VAR battery.charge%, "status": "%VAR ups.status%", "runtime": %VAR battery.runtime%}' -i 10 -l upslog.jsonl -s AVR750U` and tailed its output - unplugged from the mains and observed a wall message and status change from upslog - reconnected to the mains...

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`. First I thought one could be just > added... but for that matter, what could one logically mean - an overcharge > (as in, "possibly harmful to t...

...t down the UPS but did not ever bring it back up. I tried this both on mains power and on battery. In the latter case, I reconnected the UPS to the mains and waited 5 minutes. It didn't turn itself back on. I'm now becoming suspicious of a couple of the values reported by `upsc`: - battery.charge.warning = 30, but there is no battery.charge.low. Does this mean that the low battery flag will never be raised? - ups.timer.reboot, ups.timer.shutdown, and ups.timer.start all are 65535. I know this is FFFF, and so there's a chance that it's just the default response for an unsuppor...

...I have what is probably a 12 year old (or older) Compaq R3000 UPS plugged into a FreeBSD 8 system running NUT version 2.6.5 This UPS contains a total of 16 batteries in 2 banks of 8, each battery is 6 volts and the bank produces 50 volts. The UPS monitors battery voltage and the battery charger in the UPS works like this. For about 2 days it will apply a charge/float/topping voltage of 55.2 volts to the batteries. During that time the battery voltage measures 55.2 volts both with a voltmeter on the batteries and as reported by upsc, and the "calculated state of charge" of the...

Hi there, my HP R1500 G3 UPS doesn't apply my battery.charge.low value i set via upsrw. Is this a common problem with this model in nut 2.6.4? Any ideas how to force the UPS to accept this value? Regards Jan % upsc hp1500 battery.charge: 100 battery.charge.low: 20 battery.charge.warning: 20 battery.runtime: 23917 battery.temperature: 49.0 battery.type:...

I am using the usbhid-ups driver with a Belkin UPS. upsc shows several parameters which I would like to both understand and probably change. In particular the following part of upsc output: battery.charge.low: 30 battery.charge.warning: 30 battery.runtime: 120 My questions are: 1) What is the difference between battery.charge.low and battery.charge.warning? I presume these are % thresholdsWhich of these triggers the low battery event? 2) Is there some way to change these? 30% charge seems to me...

Dear Arnaud, Now I started to write a driver that simulates continous power breaks. (E.g. in every 30 minutes.) This could be used for testing of setup of client upsmons. I have to simulate a behaviour of a real UPS. The physical model contains an extra attribute: the charging current that needed to compute recharge time and actual battery charge during the recharge process. Can we call this variable "battery.current.recharge"? Or should I put it into "driver.*" name space? Cheers Gabor

Dear Arnaud, Now I started to write a driver that simulates continous power breaks. (E.g. in every 30 minutes.) This could be used for testing of setup of client upsmons. I have to simulate a behaviour of a real UPS. The physical model contains an extra attribute: the charging current that needed to compute recharge time and actual battery charge during the recharge process. Can we call this variable "battery.current.recharge"? Or should I put it into "driver.*" name space? Cheers Gabor

> > battery.charge: 3 > battery.charge.low: 10 > battery.charge.warning: 30 > battery.runtime: 93 > battery.temperature: 32.9 > battery.type: PbAC > battery.voltage: 46.4 > battery.voltage.nominal: 48.0 Is it possible that battery.charge is really 30% rather than 3%? The 3016 protocol models h...

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 - an overcharge (as in, "possibly harmful to the chemistry of 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.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 > overrid...

Hello all, I would like to get billing/charging informations of all outgoing calls of any PSTN numbers made with my IP-Phone via asterisk. Can I obtain in * an accurate charge information of outgoing call via CAPI which destination is any PSTN number? Does the ISDN "signal" contain charging informations ? Thank for advice Rasti...