24.10.2013 Views

Configuring Hardware and Communication Connections STEP 7.pdf

Configuring Hardware and Communication Connections STEP 7.pdf

Configuring Hardware and Communication Connections STEP 7.pdf

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Properties of cross-project connections<br />

Tip<br />

Working With Projects in the Multiproject<br />

Consistency of cross-project connections is maintained when projects of a<br />

multiproject are h<strong>and</strong>led. Cross-project connections within a multiproject stay fully<br />

operational a can be compiled, even if the project that contains the connection<br />

partner is removed from the multiproject.<br />

The following applies to <strong>STEP</strong> 7 connections: <strong>STEP</strong> 7 prompts you to split the<br />

connection before the properties dialog pops up only when you call this dialog to<br />

view the connection properties. You can only modify the connection properties<br />

after you have confirmed this prompt with "Yes". You must adjust the connection<br />

properties manually when you change the properties, same as with S7 connections<br />

to an unspecified connection partner. Whenever you change connection properties,<br />

there is a risk of malfunctions during runtime.<br />

Only the local ID for a connection can be changed without terminating the<br />

connection.<br />

Fault-tolerant <strong>STEP</strong> 7 connections cannot be terminated.<br />

<strong>STEP</strong> 7 uses the S7 subnet ID - an object property of a subnet - to adjust crossproject<br />

connections.<br />

When you attempt to configure cross-project connections without having merged<br />

both of the corresponding subnets (which are to form the connection path), for<br />

example because other, similarly affected projects are temporarily unavailable, you<br />

can help yourself in the following way:<br />

Adjust the S7 subnet ID at all subnets. Select the respective subnet <strong>and</strong> view its<br />

object properties via the context-sensitive menu. Enter identical S7 subnet IDs for<br />

both of the subnets.<br />

You can then specify that the nodes on "manually adjusted" subnets of the other<br />

project form the connection end point. However, this process still does not confirm<br />

the uniqueness of individual subnets from the viewpoint of NetPro. The consistency<br />

test would report an error if the projects are connected through a common, crossproject<br />

subnet. In this case, the same subnet IDs in different projects will be<br />

detected <strong>and</strong> recognized as errors.<br />

For this reason, merge the subnets in NetPro.<br />

<strong>Configuring</strong> <strong>Hardware</strong> <strong>and</strong> <strong>Communication</strong> <strong>Connections</strong> with <strong>STEP</strong> 7<br />

A5E00706939-01 16-21

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!