# Counting operating time

**URL:** <https://community.openenergymonitor.org/t/counting-operating-time/13921>\
**Category:** Getting Started\
**Created:** [20 April 2020 14:54 UTC](https://community.openenergymonitor.org/t/counting-operating-time/13921 "2020-04-20T14:54:01Z")\
**Posts on this page:** 15\
**Page:** 1

<div class="post-metadata">

**Author:** ![pagaille](https://community.openenergymonitor.org/letter_avatar_proxy/v4/letter/p/df705f/32.png) [@pagaille](https://community.openenergymonitor.org/u/pagaille)\
**Post date:** [20 April 2020 14:54 UTC](https://community.openenergymonitor.org/t/counting-operating-time/13921/1 "2020-04-20T14:54:01Z")

</div>

Hi,

For my pellet stove I’d like to monitor my pellet consumption in real time. My idea is monitoring the time a feeder screw motor is operated to compute the quantity of pellet burned by the stove.

Question : is it possible to count the amount of time a device is operated, wether using a CT or voltage detection ?

Thanks for your ideas.

Matthieu

---

<div class="post-metadata">

**Author:** ![borpin](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/borpin/32/193_2.png) [@borpin](https://community.openenergymonitor.org/u/borpin)\
**Post date:** [20 April 2020 15:00 UTC](https://community.openenergymonitor.org/t/counting-operating-time/13921/2 "2020-04-20T15:00:21Z")

</div>

> [@pagaille](#):
>
> My idea is monitoring the time a feeder screw motor is operated to compute the quantity of pellet burned by the stove.

Is the power to it hard wired or a plug?

---

<div class="post-metadata">

**Author:** ![Robert.Wall](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/robert.wall/32/38246_2.png) [@Robert.Wall](https://community.openenergymonitor.org/u/Robert.Wall)\
**Post date:** [20 April 2020 15:08 UTC](https://community.openenergymonitor.org/t/counting-operating-time/13921/3 "2020-04-20T15:08:53Z")

</div>

Welcome to the OEM forum, Matthieu.

Do you want the time to go into emonCMS (or similar?) I think it might be easier to count revolutions of the feed screw, because that will give you a direct measurement of the quantity - always assuming the pellets don’t run out.

You can do that either with a commercial proximity detector, with a magnet on the shaft going past a reed switch, or with a reflective optical sensor. Without knowing exactly what the feeder looks like, it’s hard to say which would be the best. Optical might not be a good idea if the pellets create a lot of dust, and a reed switch might have problems with vibration.

If the feeder is “industrial”, then my inclination would be to use a proper industrial inductive proximity sensor to detect a metal flag on the shaft - or maybe bolt heads on a coupling? Power might present a problem, because those are likely to require 12 V or 24 V d.c. They are not cheap, but reliable.

---

<div class="post-metadata">

**Author:** ![pagaille](https://community.openenergymonitor.org/letter_avatar_proxy/v4/letter/p/df705f/32.png) [@pagaille](https://community.openenergymonitor.org/u/pagaille)\
**Post date:** [20 April 2020 15:09 UTC](https://community.openenergymonitor.org/t/counting-operating-time/13921/4 "2020-04-20T15:09:00Z")

</div>

@borpin I can access the wires. The real deal I guess is wether the software is able to count the time the device is operated and how.

---

<div class="post-metadata">

**Author:** ![pagaille](https://community.openenergymonitor.org/letter_avatar_proxy/v4/letter/p/df705f/32.png) [@pagaille](https://community.openenergymonitor.org/u/pagaille)\
**Post date:** [20 April 2020 15:17 UTC](https://community.openenergymonitor.org/t/counting-operating-time/13921/5 "2020-04-20T15:17:13Z")

</div>

Thanks @Robert.Wall !

The feeder is driven by a small 230V AC motor (probably 100W or so).

The motor is directly hooked to a speed reducer, there is no easily accessible moving asset. That’s why I wanted to measure the time it was operated.

![image](https://community.openenergymonitor.org/uploads/default/original/2X/8/8524b7b7ed79064a0c54688919cafbd1a98ab852.jpeg)

---

<div class="post-metadata">

**Author:** ![pagaille](https://community.openenergymonitor.org/letter_avatar_proxy/v4/letter/p/df705f/32.png) [@pagaille](https://community.openenergymonitor.org/u/pagaille)\
**Post date:** [20 April 2020 15:26 UTC](https://community.openenergymonitor.org/t/counting-operating-time/13921/6 "2020-04-20T15:26:49Z")

</div>

> [@Robert.Wall](#):
>
> Do you want the time to go into emonCMS (or similar?) I think it might be easier to count revolutions of the feed screw, because that will give you a direct measurement of the quantity - always assuming the pellets don’t run out.

Since there is a speed reducer behind the motor, counting the time the motor is operated should be roughly the same as counting the amount of revolution, isn’ it ?

---

<div class="post-metadata">

**Author:** ![Bill.Thomson](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/bill.thomson/32/1834_2.png) [@Bill.Thomson](https://community.openenergymonitor.org/u/Bill.Thomson)\
**Post date:** [20 April 2020 15:31 UTC](https://community.openenergymonitor.org/t/counting-operating-time/13921/7 "2020-04-20T15:31:36Z")

</div>

> [@pagaille](#):
>
> The real deal I guess is wether the software is able to count the time the device is operated and how.

Sounds like an ideal candidate for the emonCMS _Input on-time_ function.

---

<div class="post-metadata">

**Author:** ![pagaille](https://community.openenergymonitor.org/letter_avatar_proxy/v4/letter/p/df705f/32.png) [@pagaille](https://community.openenergymonitor.org/u/pagaille)\
**Post date:** [20 April 2020 15:37 UTC](https://community.openenergymonitor.org/t/counting-operating-time/13921/8 "2020-04-20T15:37:36Z")

</div>

> [@Bill.Thomson](#):
>
> Sounds like an ideal candidate for the emonCMS _Input on-time_ function.

That’s probably what I was looking for ! I can’t find any documentation mentioning “input on-time”, could give me some pointers to it ?

Txs !!

---

<div class="post-metadata">

**Author:** ![Bill.Thomson](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/bill.thomson/32/1834_2.png) [@Bill.Thomson](https://community.openenergymonitor.org/u/Bill.Thomson)\
**Post date:** [20 April 2020 16:12 UTC](https://community.openenergymonitor.org/t/counting-operating-time/13921/9 "2020-04-20T16:12:10Z")

</div>

> [@pagaille](#):
>
> could give me some pointers to it ?

I wish I could. But I’ve never actually _used_ it. (just know that it exists in the emonCMS “Input”  
pull-down menu)

---

<div class="post-metadata">

**Author:** ![Robert.Wall](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/robert.wall/32/38246_2.png) [@Robert.Wall](https://community.openenergymonitor.org/u/Robert.Wall)\
**Post date:** [20 April 2020 16:20 UTC](https://community.openenergymonitor.org/t/counting-operating-time/13921/10 "2020-04-20T16:20:38Z")

</div>

> [@pagaille](#):
>
> I wanted to measure the time it was operated.

I’d forgotten about on-time. My thinking was: the quantity is proportional to time if the speed is constant. OK, it should be. But also, if the calorific value of your pellets is constant, then the amount of heat you get is directly proportional to the pulse count. And emonCMS can directly relate pulses to kWh.

---

<div class="post-metadata">

**Author:** ![Bill.Thomson](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/bill.thomson/32/1834_2.png) [@Bill.Thomson](https://community.openenergymonitor.org/u/Bill.Thomson)\
**Post date:** [20 April 2020 16:26 UTC](https://community.openenergymonitor.org/t/counting-operating-time/13921/11 "2020-04-20T16:26:58Z")

</div>

This might be of some help:

> [@Gas total to consumption per hour](https://community.openenergymonitor.org/t/gas-total-to-consumption-per-hour/2272):
>
> I use emoncms now already for several years and recently got gas meter reading working. The only problem is that I can read just the absolute gas usage (current gas meter reading since the meter was installed). I want to change this so I can get the hourly consumption. I know how to do it the other way around (as I do for electricity → daily → monthly) but cannot figure out how to do make this work. Does anyone know how this can be done through input processing? Logically it would be THISHOURCO…

---

<div class="post-metadata">

**Author:** ![pagaille](https://community.openenergymonitor.org/letter_avatar_proxy/v4/letter/p/df705f/32.png) [@pagaille](https://community.openenergymonitor.org/u/pagaille)\
**Post date:** [25 April 2020 12:05 UTC](https://community.openenergymonitor.org/t/counting-operating-time/13921/12 "2020-04-25T12:05:51Z")

</div>

I can’t believe there is nowhere to find any documentation on that setting. I have to say that while the hardware looks nice and promising, the software lacks of everything.

The learning curve is steep, the interface is nowhere from user friendly, the documentation is basically non-existent appart explaining some ready made receipts for some popular use case.

There are no demo versions, no dummy sensors to help understand how the cms works (when one gets it working by installing it himself).

It’s not possible to get an idea of what’s possible and what’s not. The software doesn’t look so open to other data that the sensors sold on the website. For anything else you must develop some code to make it fit to the cms.

I’m really hesitant to put any money in this project.

---

<div class="post-metadata">

**Author:** ![borpin](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/borpin/32/193_2.png) [@borpin](https://community.openenergymonitor.org/u/borpin)\
**Post date:** [25 April 2020 15:42 UTC](https://community.openenergymonitor.org/t/counting-operating-time/13921/13 "2020-04-25T15:42:30Z")

</div>

@pagaille It is an open project. You are more than welcome to contribute. You’ve not **paid** anything for it. As ever, it is a tool which might or might not fit the job.

---

<div class="post-metadata">

**Author:** ![pagaille](https://community.openenergymonitor.org/letter_avatar_proxy/v4/letter/p/df705f/32.png) [@pagaille](https://community.openenergymonitor.org/u/pagaille)\
**Post date:** [25 April 2020 16:01 UTC](https://community.openenergymonitor.org/t/counting-operating-time/13921/14 "2020-04-25T16:01:59Z")

</div>

Sorry if it sounds rude. I’m an open source project advocate and I don’t want to complain if it the project doesn’t fulfil my need.

My point is that it is really difficult to know it it will to the job or not, and that there is no doc, which is strange for such a mature project.

Regarding the money, buying the hardware makes you contribute to the project, right ?

---

<div class="post-metadata">

**Author:** ![Bill.Thomson](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/bill.thomson/32/1834_2.png) [@Bill.Thomson](https://community.openenergymonitor.org/u/Bill.Thomson)\
**Post date:** [25 April 2020 17:12 UTC](https://community.openenergymonitor.org/t/counting-operating-time/13921/15 "2020-04-25T17:12:06Z")

</div>

Not having a device that switches on and off at fairly short intervals, I used my PV systm’s time importing and exporting as the values to track the _on-time_ function. Plotting them on a bar chart yielded:

 ![image](https://community.openenergymonitor.org/uploads/default/original/2X/e/e23a3ae171126fdd1ff700949ac0b227a2b59bb2.png)  
The plot on the left shows the amount of time my system exported energy. The plot on the right,  
shows the amount of time the system imported energy. Time is in seconds.
