Hi everyone,
Recap: I'm based in the US and am a newcomer to OpenEnergyMonitor (and many of the concepts surround these projects). My goal is to monitor and record the electric usage of a commercial building. I was initially going to use CT clamps, but then discovered that the building uses 3-phase power and the clamps required would blow my budget. Thankfully, our meter has an IR pulse LED that we can utilize and keep the project moving... I hope.
So, since we are just counting pulse and not using CTs, I decided to use an emonTh with a TSL257 optical sensor rather than the emonTx with all its bells and whistles. After some messy, inefficient, and potentially misguided alterations to the existing emonTh example code, I found I was able to get the pulse count reliably into emonCMS (hosted locally on a raspberry pi). I have the emonTh powered from a wall adapter, with the TSL257 connected to +5V, GND, and DIG2IRQ0. (Happy to share the messy code I used in a separate post if anyone wants to take a peek/criticize/utilize it, but it doesn't pertain to the subject at hand so I will refrain from pasting it here.)
Here's what has me scratching my head, wondering what to do next. I don't know of a good way to verify the value of each pulse. Our meter works indirectly by utilizing CTs of its own. Massively large CTs that I couldn't hope to acquire similar versions of. There are three "pages" of information on the LCD screen on our meter that are shown for about 5 seconds each (and then proceed to loop). They are as follows:
[Note: I'm sorry if I get my units / terminology wrong. Please feel free to set me straight if you notice a lack of proper use and/or understanding.)
1) As the units for this screen are kWh, this must be cumulative electric consumption, right? I think the default assumption is that 1 pulse = 1 kWh, however this is not what I have observed. Over a 44 hour period, this kWh number on the meter only increased by 8. The pulse count was ~4025 over this period. This would be simple math, but I expect the actual usage was much higher than 8kWh. The average kWh per day in December (per our service provier's bill) was 375.2 kWh. Yes, this is a different season, but it makes me believe that the meter-observed 8 kWh change over two days is not what it appears to be.
2) This is in kW, so I'm going with "instantaneous power", although this number doesn't seem to change much - if at all - over several minutes of observation. Even with our AC condensers cycling on/off during the observation period. Right now it's at 0.59 and has been the same for every reading this past week.
3) I do not know what this is. There are no units. After reading up on quasi-related material across the internet, it stuck in my head that this could be something called "power factor". Not... that I know what that would mean, regardless. It doesn't often change. It's been at 0.927 for the past week.
So calibration of what a pulse actually is something I would really like to do. It's possible that the meter display doesnt represent the data we're looking for. These meters can be programmed (by the provider) to display certain types of information depending on the specific method of electric delivery.
Here are some screens from the emonCMS installation that show the inputs and feeds:
Inputs received from the emonTh:
Input config for feed "power":
Input config for feed "pulses":
Feeds:
The relationship between the values seem to make sense when viewing the visualizations.
The power seems to be higher during the day:
The total pulse count rises at a faster rate during periods of increased usage (eg. during the day):
Likewise, the kWh rises faster during the day (although there's a weird drop in the graph that I cannot explain. I expected this number to only be able to increase, since it's essentially an accumulation of energy used. I don't think I should focus on this odd observation at this time...)
This brings us to where I currently stand. I seem to be successfully collecting data, albeit data of questionable value. Does anyone have any insight into how I might validate my findings? Perhaps I may also lean on your collective experience and ask if the values I've shared here even make real-world sense.
Once I'm confident in the accuracy of the information I can collect here, my next goal will be to figure out how people use the collected information outside of emonCMS. (Such as, if I want to use my own database that houses emon data produced from multiple physical sites, where should I start? Does one "push" the data from emonCMS to an external database, or do you command the external database to "pull" information from the various emonCMS installations? Questions like these are in my future...)
Thanks, everyone. These projects are fun and insightful. Please forgive my lack of experience with some of the inner workings / building blocks. I do have the ability to learn, and have been taking steps to acquire (well, googling) as much of the fundamentals as I can. What I seek now from this awesome community is guidance on ways to move forward from here. This data ambiguity is proving to be a formidable roadblock. Once I establish my next concrete goal, or better yet, a clearly defined roadmap, I know I'll be able to press onward.
Re: Seeking guidance. Pulse-counting data calibration/verification (setup: emonTh + TSL257 + local pi emonCMS)
I've just found your later posts on the other thread (somehow, I missed these a month ago).
First, a misconception to be dispelled. There is no inherent current limit for the emonTx - it depends solely on the CT you use to drive it and the burden. So if you have a 1000: 50 mA CT and the in-built burden, it will read 1000 A with the appropriate scaling in the software.
Now to this problem. You need to find out what your meter LED flash represents. There are principally two ways that I can think of, experiment or paper-chase. The experimental way is to wait until your plant is shut down overnight or for a holiday, then put a known load on and count and time the flashes. The paper-chase is to find out what the meter characteristics are, what those meter displays actually mean, what the ratio of those big CTs are, and work through the sums. The energy bill might have some information that helps. Even better if you can talk to a friendly engineer at your electricity company. I've no idea whether you will be able to find out everything that's necessary, so the experimental way might be the only practical way.
Certainly, the top picture says it's kWh, but they might have forgotten to scale it for the CTs, so it's 8 x (the CT ratio), which, if the CT is 200 : 5 say, makes much more sense of your 8 kWh ( x 40 = 320 kWh). That's just a theory, so treat it with caution.
The 0.48 / 0.59 kW display: If it doesn't change when the load is cycling, could it be maximum demand - again scaled by the CT ratio? Some suppliers charge a penalty if the maximum demand goes above an agreed limit within a specified time frame, usually half an hour. You might find this resets periodically.
The 0.919 could indeed be power factor. This is the ratio of real power - the power that a resistor (heater) dissipates, compared to the power that you calculate when you measure voltage and current and multiply the two numbers. For a resistor, the value is always 1 (by definition!). For a reactive load, like your compressor motors, it will be less than 1, and 0.92 is good. For a very small induction motor, it can be down to 0.6 or so. A poor power factor is bad because it means you have to have fatter cables to deliver a higher current for the same amount of power. Some suppliers charge extra if you have a poor power factor.
It took me about 5 s with Google to locate a manual for your meter:
site.ge-energy.com%2Fprod_serv%2Fproducts%2Fmetering%2Fen%2Fdownloads%2Fkv2ci_oi.pdf
I think you need to study that. I haven't done so.
That should tell you what your meter is displaying. I mentioned in the other thread about putting your own CT on the meter CT secondary side. Is that possible, or can you get a clamp ammeter on there? If you could, that might help to resolve what the meter scaling is. Let's assume those big CTs are 200:5 Then if the current into the meter correlates with the meter kWh incrementing, and the LED flashes (which I guess might actually be more like 1 Wh but again scaled by the CT ratio) then all you need to know is the metering CT ratio.
Re: Seeking guidance. Pulse-counting data calibration/verification (setup: emonTh + TSL257 + local pi emonCMS)
Having quickly looked at the manual, you also need to know kt. It should be underneath the paper label on the front of your meter - see Fig. 1-1 of the manual. It would be useful to know anything else under there too.
The manual says the meter defaults to 1 pulse = 1 Wh, as I guessed. But that doesn't necessarily mean yours is set to the default.
Also available is a comprehensive data extraction kit: http://wattmetrics.com/products/supportedpowermeters/GEkV2c.aspx is the first I noticed.
Re: Seeking guidance. Pulse-counting data calibration/verification (setup: emonTh + TSL257 + local pi emonCMS)
Ah, thanks for your input, Robert! (and sorry for the delay - honestly I'm not sure if I set up the email notification on this forum correctly.)
Okay, I have some new information to share with everyone based on Robert Wall's feedback.
So experimental vs paper-chase. This is a great way to organize the information-seeking process. I think there may a few things holding me back from being successful with either tactic. I could be wrong and these issues might be inconsequential.
Experimental
Paper-chase
I had taken a look at the meter manual as well and was discouraged when I read that they could all be programmed differently. I believe this is the reason they do not have an index of meter screen numbers (05, 07, 18 from the original post) coupled with their relevant descriptions.
I have looked into a similar data extraction kit, but there doesn't seem to be any that I can purchase outright. Unfortunately, the WattMetrics system has discontinued sales.
Does any of the provided information reduce the number of variables we have to work with, or otherwise shed some light on the situation?
Thank you for your insight!
Re: Seeking guidance. Pulse-counting data calibration/verification (setup: emonTh + TSL257 + local pi emonCMS)
That does indeed help.
There's absolutely no reason why you can't put your own 5 A c.t. on the secondary wire out of the meter c.t. But it must of course be a split-core one! You must never open-circuit a c.t. under load. If your c.t. is a 5 A : 50 mA (say, to give you a standard emonTx input and burden resistor value), then you have effectively got a 400 A : 50 mA one - you get 50 mA out of yours for 400 A through theirs. Knowing their CT ratio has removed all doubt about the calibration at that end.
"The value of kt on the meter sticker is 1.8. (It was hard to make out in the photo I snapped, so I typed over it.)" It was impossible in the original photo because there was another sticker over the top of it! Now that we know Kt also helps, it says you get 1 flash every 1.8 Wh. Therefore 4025 flashes = 7.245 kWh on the meter (that correlates with your increment of 8) x 80 (for the CT ratio) = 579.6 kWh consumed. That's way above your daily average so that apparently is not correct, but you have more information that should allow you to check - a good source would be old bills and meter readings, assuming they have been recorded.
[Starting a new thread after your first post here http://openenergymonitor.org/emon/node/4895 is a pain because it means I've got to go and find it each time - please don't open yet another thread on this topic!]
And as far as I know, email notifications have been broken for some time.