search for: charges

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 rollup and e...

...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 end...

Kicking the old tyre a bit once more: In my recent reading I saw "float charge", "float mode", "float voltage" etc. Maybe that is what I meant in the earlier discussion - similar concept, similar word. In case of PbAc per https://chargetek.com/basic-information.html : "Float mode is where the voltage on the battery is maintained at approximately 2.25 volts

Jim Klimov <jimklimov+nut at gmail.com> writes: >> "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 >> failure. > > Well, given that a "battery.charge.high" is

...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 laptop plugged in most of the time and this constant charging state is apparently very bad for battery lifetime. So a charge/drain cycle is supposedly better. Thanks, Kwan

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

...ll 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", "offense_level", @charge_types, :id, :full_name %> but that doesn''t work either. @charges contains multiple records obtained from a find_by_sql query. each record has 3 fields: charge_name, charge_id_number, offense_level @charge_type.id should be equal to the @charge.offense_level the view - update_charges.rhtml: <h2>Add missing records to charges table</h2> <%= start...

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

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`.

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

Hi All, 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

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

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 -