Hi,
In the prototype machine building industry I have made a standard that is continously improved. It is made in TIA with the use of UDT's, FACEPLATE's and all made in a TYPE library. So for each device I have a standard FC with UDT and a FACEPLATE. So far so good. By working this way I am working in OOP. What I miss in my Faceplates is the linking with Alarms and datalogs. It would be amazing if that was possible too. Maybe some of you know Archestra, in Archestra you can add objects that contain everything of the object.
What am I looking for:
I want a method for alarm creation in the same faceplate, maybe I should use text list inside the faceplate as a workaround... or maybe I should consider PDiag...
Datalog can also not be added in the faceplate...
OOP is nice, but my feel is that TIA misses those 2 things to be able to think completely OOP about FC + UDT + Faceplate.
How do you guys feel about this OOP thing in TIA ?
In the prototype machine building industry I have made a standard that is continously improved. It is made in TIA with the use of UDT's, FACEPLATE's and all made in a TYPE library. So for each device I have a standard FC with UDT and a FACEPLATE. So far so good. By working this way I am working in OOP. What I miss in my Faceplates is the linking with Alarms and datalogs. It would be amazing if that was possible too. Maybe some of you know Archestra, in Archestra you can add objects that contain everything of the object.
What am I looking for:
I want a method for alarm creation in the same faceplate, maybe I should use text list inside the faceplate as a workaround... or maybe I should consider PDiag...
Datalog can also not be added in the faceplate...
OOP is nice, but my feel is that TIA misses those 2 things to be able to think completely OOP about FC + UDT + Faceplate.
How do you guys feel about this OOP thing in TIA ?