Bueller? Bueller?
This is my first AX job and we have to take clicks from a gas and water meter and generate daily, weekly, monthly, and yearly reports with peak histories.
Bueller? Bueller?
What are you using to count the pulses? I've used Honeywell Spyders, XIO10Di, and NDIO. Regardless of what you use to count the pulses, pay attention to rollover values.
I've used the Sliding Window Demand Calc object (kitcontrol\energy), or if you have access to the VykonPro module, then the energy\NumericDelta along with history\NumericHistoryAnalysis does the trick quite well.
Unfortunately all this gets you is the counts, how you display and generate reports is entirely up to you. I've used component grids embedded in Px pages, along with VykonProReportSource to generate pdf reports to be emailed out.
If you want, I can send you an e-mail with some pointers I got from a pro on how to best log consumption data. hint: delta logging, instead of ever increasing, totalized number.
I would be interested in that info, email is in my profile.
tia
One more interested - email in profile.
Thanks!
Count me in as well Digo
If you dont mind - me too?
If you could add one more name to your list, I'd appreciate it very much.
A site where I stash some stuff that might be interesting to some folks.
http://cid-0554c074ec47c396.office.l...e.aspx/.Public
If you're using a Vykon jace, there is an energy suite module/doc. I think JCI had an energy module in older Niagara builds, but I don't see it in the latest build.
I think a lot of people opt to use/purchase per-built energy dashboards, especially if it's for a lot of data. However, you can build them yourself with px pages, widgets, histories, extensions, and data exporting/storage strategies.
If you want, I can send you an e-mail with some pointers I got from a pro on how to best log consumption data. hint: delta logging, instead of ever increasing, totalized number.[/QUOTE]
Id like to read this info too, if you get an opportunity to send it my way. Email in profile.
Thanks.
Room for one more?
Thanks
If it is not too much, can you please send it to me a copy?
Thanks
Knowledge is money - Ignorance is expensive!!
May I also get a copy of this information please Digo . It would be greatly appreciated, or if someone that has gotten it would pass it along that would great!
Sorry guys, I've been MIA (or missing in the field) for a while.
Here are the notes I have from the last time I had to set this up.
Disclaimers: This is not a soup to nuts guide, but contains enough pointers that should help you get started with logging consumption data in a delta fashion. This does not address how to format the data for displaying it in a report, nor sending such report via e-mail. This also requires access to the vykonPro modules.
When you look at a history extension you should see a ‘max rollover value’ property. If the device you're using to keep track of the raw counts has a rollover value, you can clear the null check box and set the value here accordingly (for example, the counter output on an XIO controller from Honeywell rolls over at 65,535).
When you have a rollover value, looking at the history chart you would notice a saw tooth pattern (as it rolls over). The value starts a zero, ramps up to the max rollover value, drops back down to zero, then ramps back up, and so on. By setting the ‘max rollover value’, when you click the delta icon in the chart/table view workbench calculates and displays the correct interval consumption based on the rollover value.
Ideally, consumption data should be logged in a delta fashion, meaning that you log the interval consumption during each period instead of logging an ever increasing (totalized) value. This is a more fault tolerant mechanism for various reasons:
• Controller fails and you cannot preset the counter register in the new controller
• Inadvertent resets of the counter output
• Counter output not being persistent and being reset by a power outage
• Erroneous change in counter value
In the vykonPro palette (energy sub folder) there is a numericDelta component. It has a property for specifying the rollover value and can be configured to execute on interval (e.g. 15 minute period). Link the delta slot to a numericWritable component with a COV history extension.
There is also another component in the vykonPro palette (history sub folder) called numericHistoryAnalysis. This requires the vykonProService to be in the station because it uses the worker thread on the service to run the calculations. It can be used to calculate the total consumption for various periods of time. You can use it to display bound labels on px views.
The numericHistoryAnalysis component runs a query against the history database and calculates the totals for each period.
Here's one catch I didn't consider when I set this up:
If you are only retaining the default record count (500) in a particular Jace and you are using the numericHistoryAnalysis component within a station running in the JACE, then you won’t have results for periods beyond whatever the 500 records and the configured interval equates to. For that reason, you should use the numericHistoryAnalysis component in the supervisor, since from there you can point it to any imported history from the JACE, where you have relatively unlimited storage.
Hope these tips are ass helpful to you as they were once to me.
Cheers,
-Digo
Nice info Digo.
I will give this a tryout.