Forum Home › Forums › Understanding the Software › ModDiffCalculator
- This topic has 10 replies, 2 voices, and was last updated 1 year, 5 months ago by
Mikhail.
-
AuthorPosts
-
March 6, 2024 at 5:27 am #14137
kcks66
ParticipantHi Mikhail,
Thanks for the ModDiffCalculator module to try. I wish to get energy usage for every 30 minutes. My source channel 101 is cumulative kWh from energy meter, destination channel 102 is energy consumption every 30 minutes calculated channel type.
Kindly advice whether my configuration is correct?
One more thing is I set 30 minutes different; am I getting data timestamp at every HH:00:00 and HH:30:00 exactly?
Thank you.
March 6, 2024 at 12:00 pm #14138Mikhail
ModeratorHi,
Tee configuration looks correct. Note that you use Minute archive to read and write data.> am I getting data timestamp at every HH:00:00 and HH:30:00 exactly?
Yes, if Offset is 00:00:00.March 6, 2024 at 12:00 pm #14139Mikhail
ModeratorLook for useful info in the module log.
March 6, 2024 at 1:31 pm #14140kcks66
ParticipantHi Mikhail,
I have one question; example if there is no data/data lost (channel 101) before 9:00:00 PM but resume back before 9:30:00 PM, what happen to the ModDiffCalculator module to calculate (channel 102) at 9:30:00 PM?
Channel 102 (9:30:00 PM, data?) = Channel 101 (9:30:00 PM, got data) – Channel 101 (9:00:00 PM, no data)
Pls advice and thank you.
March 6, 2024 at 3:17 pm #14141Mikhail
ModeratorHi,
To calculate the difference, the both data points must be defined. Otherwise, the difference is not calculated. In that case, you can set data manually, and then send a command to recalculate diffs for the period of time.March 7, 2024 at 6:33 am #14146kcks66
ParticipantHi Mikhail,
Noted. Going to give it a try. Thanks.
March 7, 2024 at 7:23 am #14147kcks66
ParticipantHi Mikhail,
I configured custom period to 00:30:00. Somehow after I saved and upload to server the custom period became 00:00:00. I tried many times the custom period looks like always reset to 00:00:00.
<?xml version=”1.0″ encoding=”utf-8″?>
<ModDiffCalculator>
<GeneralOptions>
<CmdCode />
</GeneralOptions>
<Groups>
<Group active=”true” name=”30 Minutes” periodType=”Minute” offset=”00:00:00″ delay=”10″ archiveBit=”1″>
<Item srcCnlNum=”101″ destCnlNum=”102″ />
</Group>
</Groups>
</ModDiffCalculator>The module log:
I checked result from excel is the different calculation is based on 1 minute.
Pls advice and thank you.
March 7, 2024 at 7:31 am #14148kcks66
ParticipantI should select custom period then is ok.
<?xml version=”1.0″ encoding=”utf-8″?>
<ModDiffCalculator>
<GeneralOptions>
<CmdCode />
</GeneralOptions>
<Groups>
<Group active=”true” name=”30 Minutes” periodType=”Custom” customPeriod=”00:30:00″ offset=”00:00:00″ delay=”10″ archiveBit=”1″>
<Item srcCnlNum=”101″ destCnlNum=”102″ />
</Group>
</Groups>
</ModDiffCalculator>March 7, 2024 at 11:35 am #14157Mikhail
ModeratorHi,
Right, you need to set Period type = Custom before saving the configuration.March 8, 2024 at 2:29 am #14161kcks66
ParticipantHi Mikhail,
I got the result in Minute archive as shown below:
I see every 30 minutes got data as expected. Somehow there is always 0 if out of HH:00:00 and HH:30:00. Is ModDiffCalculator working like this?
The other part is data channel 102 always 0 in the Table, as below:
Since the Channel 102 always show 0 I couldn’t use to attach to a Dynamic Text in Scheme as well as use as source channel for another calculated channel to further formula function.
Pls advice for my ModDiffCalculator configuration:
Thank you.
March 8, 2024 at 9:54 am #14165Mikhail
ModeratorHi,
I suggest to use the hourly archive instead of the minute archive. This helps to avoid 0 between data points. You can set 30 mins period for the hourly archive.Schemes display the current data, while ModDiffCalculator works with historical data. To display historical data, use table views and reports.
> The other part is data channel 102 always 0 in the Table
Because a table view displays data from the hourly archive by default. -
AuthorPosts
- You must be logged in to reply to this topic.