6/3/2016 10:12 AM | |
Joined: 7/19/2013 Last visit: 5/15/2024 Posts: 68 Rating: (3) |
Yes, they are in the same project |
6/6/2016 7:15 AM | |||||
Joined: 3/14/2008 Last visit: 9/20/2024 Posts: 2095 Rating: (936)
|
Hello, What is the exact error you got when trying to "Make" textual interconnections? A textual interconnection is not created in the following cases: If the source of an interconnection is deleted. In this case the real interconnection is deleted.If the interconnection source (hierarchical chart or block) of internal interconnections to chart connections is deleted or moved. In this case the assignment to the chart connection is lost.If, in the case of a central type change, there is a name change with interface change. The interconnection is retained if it is just a pure name change without interface change. See below for a part of AS wide interconnections.. Maybe you missed something? ___________________________________________________________________ Setting up AS-wide interconnections General information on AS-wide interconnectionsWith the CFC, you can set up interconnections to partners located on other automation systems. Interconnection partners are always block I/Os. Requirements for AS-wide interconnections:
Setting up AS-wide interconnectionsYou make the interconnection as you would for a chart-wide interconnection. To do this, open both charts and arrange them in the CFC so you can connect the source to the destination, in other words, click on the I/O to be connected in one of the charts and then click on the I/O partner in the other chart. For connections, an interconnection line is drawn to the sheet bar. The AS-wide interconnection is marked as a green triangle in the small field of the sheet bar. The project/station/CPU type/ or hierarchical path and chart name/block/connection is entered in the large box. Notes on AS-wide interconnections
Effects of moving a projectIf you move a project out of a multiproject that is the source or destination of an AS-wide interconnection, the interconnection partner is recorded in the ES database. The interconnection to the sheet bar is retained; the sheet bar entry is deleted and replaced by a question mark. When the project is reintegrated, the previously existing AS-wide interconnection is automatically reestablished upon update (F5) if the interconnection partner is available unchanged as before.
General information on the procedureOnce AS-wide interconnections have been created, the affected S7 programs need to be compiled and loaded. The S7 connection in NetPro must not be deleted manually. The NetPro IDs must not be changed. To view the NetPro IDs, proceed as follows:
You can now read the NetPro IDs from the table. The user does not need to undertake any special measures to perform the data transfer via the AS-wide interconnection. The blocks required for the data transfer are made available and loaded by the ES when loading is performed. These blocks are not instanced in the chart and cannot be seen in the catalog. The data transfer is called directly from the corresponding OBs of the AS (OB1, OB3x). The handling instructions are located in special DBs created by the code generator and transferred from the loader to the CPU. The "IK STATE" block is located in the "ELEM_400" folder in the CFC library. This can be integrated into the program in order to respond to communication errors in the process. You can find a description of the "IK STATE" block in the Help for CFC elementary building blocks > AS-wide blocks > IK STATE If the last AS-wide interconnection is deleted, the S7 connection in NetPro is also deleted. Following this, compiling and loading is required. Synchronizing AS-wide interconnections Synchronizing AS-wide interconnectionsThis menu command can be used to determine all one-sided AS-wide interconnections.
After the command has been executed, a log is displayed showing the deleted and remaining one-sided AS-wide interconnections.
|
||||
If I could help you, you can use the RATE button. Thank you. |
|||||
This contribution was helpful to3 thankful Users |
Follow us on