I think it would be useful to have a pid tag that can be attached to any tag with equipRef (See example below).
What would this be used as?
We could generate how the PI should work and generate the output programmatically and compare it to the real output of the logic from the controller.
We can compare the output of the logically written PI to the output of the controller and create a spark out of it.
Tags like this would useful for demand response as well. I will open a new topic on that.
ahu
ahuRef
fan
fanRef - Tag to attach pid to the fan.
pid
Alper ÜzmezlerThu 26 May 2011
Talked to John about this, this is not necessary since we can write sparks for finding loop problems. If it is written it would only be a benefit for visualization where line chart would be drawn dotted. We can reserve the keyword for future use.
Alper Üzmezler Mon 23 May 2011
Hello,
I think it would be useful to have a pid tag that can be attached to any tag with equipRef (See example below).
What would this be used as?
We could generate how the PI should work and generate the output programmatically and compare it to the real output of the logic from the controller.
We can compare the output of the logically written PI to the output of the controller and create a spark out of it.
Tags like this would useful for demand response as well. I will open a new topic on that.
ahu
ahuRef
fan
fanRef - Tag to attach pid to the fan.
pid
Alper Üzmezler Thu 26 May 2011
Talked to John about this, this is not necessary since we can write sparks for finding loop problems. If it is written it would only be a benefit for visualization where line chart would be drawn dotted. We can reserve the keyword for future use.