I wrote a wall, but I wrote your name for the part I wanted to ask you about and thank you for.
I bolded my questions.
I hope it is easy to read.
@dkhayes117 @bschroeder @jlandwerlen
First, thanks for helping me. I really appreciate the help, effort, and patience with me.
Irritatingly, some of you are telling me the parts I do know and not the parts I don't.
I know about duratonOn and historian queries.
I don't know how anyone meant to implement that.
You mean instead of this?:
Script sets the uptime tag to 0 at shift start.
Running boolean tag on-change script to adds time to the uptime for running time.
Script toggles the boolean at -2 to shift end to insure I get the time.
I collect data at -1 minutes to shift end.
This?:
Script sets the uptime tag to 0 at shift start.
Running boolean tag on-change script to query durationOn for time of the shift
Script toggles the boolean at -2 to shift end to insure I get the time.
I collect data at -1 minutes to shift end.
If so, then I probably will stick with the calculation script because I don't think it will ding the database at all and a script has to run anyway.
Or am I missing something?
As I get better with Ignition, it gets harder for me to depict the parts that I am missing and there are more parts that I do know already. Sorry, I wasn't more articulate beyond "how?".
Why isn't there a historian query tag type?
@lcardenas2 Thanks, does that work with SLC 500s and ControlLogix?
I think you mean for it to be connected to the internet and we avoid that for the machines.
@pturmel
Forgive me, what does "For ControlLogix prior to L8x," mean?
It won't work with SLC 500s?
That TM2000B also has to be connected to the internet or can you set time on it and all devices sync?
Thanks for all the help. I really do appreciate the help prior and to help me fill in these gaps of information.