1/8/2021 10:55 AM | |
Joined: 3/14/2008 Last visit: 9/23/2024 Posts: 2096 Rating: (936)
|
Hi, You need to understand the CMT concept. You have to consider a CMT as a black box. What you do inside does not matter to other systems like Plant Automation Accelerator (which is needed in case of bulk engineering CM's in a project). When you mark an IO as Technological IO, you create an input/output to this black box object, thus it becomes available to other systems. But to answer your question: No, you won't need to do this. I don't know if you are going to use EPHT and EMT? If so, you can create commands and statuses in the CMT and then use those commands in the SFC of the EPHT/EMT. You need to create role assignments before you can use the commands and statuses in the SFC. Basically, you are using placeholders to control a CM. Later on in the project, you assign the actual CM instance to the role and thus all block contacts are created. The commands configured in the SFC will control the CM instance. The same applies for Statuses in the SFC, the status is determined from the connected CM instance. But if you are going to use plain SFC types, you can create Block contacts and connect the CM instance to the block contact. PS: In a CM instance (copy of the CMT), you cannot create internal connections to IO which are not defined as technological IO. The connections must be done in the CMT and then synchronized to the CM instances. There is another way by using: "Ignore IO". The IO will change to a pink color, meaning that IO is ignored for synchronization. You can change those IO at the CM instance. If a green color (defined as tio) is set, it is allowed to change the values at the CM instance as well. Connections outside the CM CFC can always be done without setting the IO as tio or Ignore Regards, Sandor |
Last edited by: Oreca at: 01/08/2021 10:58:19If I could help you, you can use the RATE button. Thank you. |
|
This contribution was helpful to3 thankful Users |
Follow us on