INTRO: I do apologize if my wording is going to be slightly off due to me still learning the lingo. I am trying to create a report that based on a tag that becomes (PROD START) and for it to be finalized when a different tag becomes true (PROD COMPLETE).
GOAL: I need each of these tags to also be represented as a time stamp for when they were last made true. along with a duration timer. to execute as a .pdf file in the C drive with the proper time for my time charts.
WHAT WAS DONE: I have created two memory tags with a date/time, but I do not know if I am missing something or just straight up doing it wrong. I have them both set up as historian and included on my data source, but I have not had any luck when it comes to the execution of said report. It is still a time-based schedule, running once at midnight. I have tried a few videos that mentions gateway event tags but to no avail… now if i can get the start and end time to work properly and execute as a .pdf file to my folder on the C drive…. will the graphs show the duration of that snippet or does that involve other shenanigans….
CONCLUSION: Please be patient with me and thank you for your support.
Welcome to the forums.
I highly recommend going through all of inductive university.
If you want help - it’s good to show what you tried, not just describe it. Show your scripts, tag setups, your gateway event change scripts etc. Otherwise we are just guessing on what you did and how to help you.
2 Likes
From what I can decipher, you are attempting to limit the span of a report to the start and end times of some production process.
My approach (knowing nothing else about your system) would be to use a database table, write the production start and end times in separate columns, along with possibly some other related/important information.
What is driving when the production 'starts' or 'stops'? I would use that to write the timestamp to either the start or stop column in the db table. Along with the start time, I would include some other identifying data (batch/serial number maybe). This would allow you to execute on demand reports for older runs.
If you are absolutely stuck on using those two tags, a gateway tag change event monitoring when the tags change to true and writing the timestamp to the appropriate db table column when it happens would be sufficient. It's also simple enough that you could make do with transaction groups, if you have the module on your gateway.
From there, when executing the report, pull the most recent row from the db table that has non-null start and end times. Use the start and end times to drive the span of the data fetched for the graphs in the report.
1 Like
I certainly appreciate it and I have been going through the university and watched a few of the videos going over the reporting. But the videos I had found on the University wasn’t specific enough for me, thank you
Thank you, Ryan. I haven’t tried an event monitoring so I will try that. But yeah, there are other bits of information as well that i was pulling to the report like statuses and graphs for temp and pressure. But I’ll let you all know if I am able to do it successfully or not with the dynamic action of the report