search for: charged

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 works nicely so I can select a charge, select a

I need to compare a column in TableA to a column in TableB and then select 3 columns from 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

...that "normally only charge up to a 100% level and then let their battery seep away until it hits a threshold (90-95%) so it is boosted back to 100% again". Also, for monitoring generally, there is a case of devices (especially lithium-based batteries, as I hear) that are intentionally charged to some 90-95% and avoid going to 100% due to whatever FUD or true dangers or wear-out. Windows power manager has settings/modes for that on laptops. So... I think there is a common ground of possibly different concepts here, and we somehow want to handle it, and it needs a name. So far the term...

...me more popular with LiIon > batteries hitting the UPS market (laptops and phones already do often > hover). I would suggest deferring until there is a need and an articulated use. Hover charging is a new word for me, but I understand it to mean declining to charge a battery which is mostly charged. Part of the difficulty is this is about "state of charge" which has a messy relationship to "battery voltage". > Currently the concept in NUT was somewhat addressed by a > `onlinedischarge_log_throttle_hovercharge` setting introduced (in > https://github.com/networku...

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

...t; > 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 cells")? Or an > > euphemism(*) for being "well charged" (maybe not 100% if the device > hovers > > at some 85%-95% to extend battery life)? > > I don't think we should use .high, unless a significant number of > units/protoocls issue a "battery charge is high" state with a consistent > meaning. So no. > >...

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

Hello, It looks like the nut-upsuser list is momentarily down. That's why I send it to nut-upsdev list too. I have recently bought a mustek Powermust 1000VA USB (sadly not the USB P version). I have done some tests with the latest nut 2.2.0 megatec and megatec_usb drivers. Here are my feedbacks. It works quite well but is extremely noisy in battery mode (and that is not the noise of the

Hello, It looks like the nut-upsuser list is momentarily down. That's why I send it to nut-upsdev list too. I have recently bought a mustek Powermust 1000VA USB (sadly not the USB P version). I have done some tests with the latest nut 2.2.0 megatec and megatec_usb drivers. Here are my feedbacks. It works quite well but is extremely noisy in battery mode (and that is not the noise of the

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:

I wouldn't be surprised if they both use the same driver. I think they are essentially the same model, but with one having a slightly larger battery. My issue is primarily with the UPS turning back on after having shut off like it should. @Scott Colby if you take a look at the config files I posted in the github issue I created, perhaps that will give you some hints on your issue. Maybe

...nt)", 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 cells")? Or an > euphemism(*) for being "well charged" (maybe not 100% if the device hovers > at some 85%-95% to extend battery life)? I don't think we should use .high, unless a significant number of units/protoocls issue a "battery charge is high" state with a consistent meaning. So no. If this is about having variables with...

On Sat, Jun 27, 2020, at 23:11, Manuel Wolfshant wrote: > On 6/28/20 5:54 AM, Scott Colby wrote: >> >> I'm not convinced this is the problem; I think that pfSense has an alternative way of running the NUT components: # ps aux | grep ups root 45456 0.0 0.1 6796 884 - Is 02:22 0:00.01 /usr/local/sbin/upsmon uucp 45751 0.0 0.1 6796 772 - S 02:22

...en though the UPS is reporting a nominal battery voltage of 48v and the batteries are 2 volts ABOVE that. The problem I am having appears to be the logic in the upscode2 driver. For starters, the calculated state of charge is quite wrong. 48v on a bank of 8 6v batteries is normal, it IS fully charged, it is NOT 64% charged. 50.5 volts on a 48v bank of batteries should be almost 100% charged, not 64%. Worse, however, is if there's a power failure right near the end of the 2-days-off cycle. That happened to me last week - it was a short duration 15 second loss - and the upscode2 driver...

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: PbAc battery.voltage: 39.0

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 %

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

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

> > 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 have issues with scaling on some of the voltages and frequencies. You can see

...witches 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 cells")? Or an euphemism(*) for being "well charged" (maybe not 100% if the device hovers at some 85%-95% to extend battery life)? (*) Recent work in usbhid-ups dealt with optional "OL+DISCHRG" warning throttling for known-hovering devices using a custom option; if the "euphemism" above is ratified - it could be a more sy...