Enter the module position of the CP243-1. If you are uncertain about the position, click the button Read Modules.Otherwise you can enter the number directly:

Figure 4: Specify Module Position Dialog Box

Enter the IP configuration of your CP243-1. Especially during the startup phase of the project, I would recommend not to use a BOOTP server. Let the module detect the connection type (Figure 5 below):

Figure 5: Module Address Configuration

Enter the numbers of connections you want to configure for the CP243-1 Default value is 0, which would not allow communication. In this example I will use 2 connections (Figure 6 below):

Figure 6: 2 Connections Now you have to configure the connections. Connection 0 (Figure 7 below) will accept all incoming client requests:

Figure 7: Connection Configuration

Always select This is a Server Connection. I recommend using the default TSAP’s as suggested by Step7-Micro/Win32.

Click Next Connection (or Prev. Connection if available) to step through all the connections to configure them.Note: If you plan to use such a connection, be sure that only one client tries to connect to the PLC via this connection at the same time. All other connection tries will be rejected.Connection 1 accepts only requests from the specified client:Figure 8: Specified Client Requests

If all connections are configured click OK. During the startup phase of a project I would recommend not to use a CRC protection:

Figure 9: No CRC Protection The wizard now needs a range in the V-Memory where to store this information. Step7-Micro/Win32 will suggest a valid range.

Click on Suggest Address if you have planned to use this range for something else. In this case Step7-Micro/Win32 will suggest another free range that has the correct size to hold this data:

Figure 10: Store Memory Allocation for Address

Click Next. The program now has enough information:Figure 11: Generate Project Components

Set the PLC to STOP mode in order to be able to download a new configuration:Figure 16: PLC STOP Mode

After the download don’t forget to set the PLC to RUN mode again. This will not be done automatically:Figure 17: PLC RUN Mode

The PLC side is now configured.

Configure the DAServer

Configuration of the DAServer is quite easy.

Since we have created two connections in the PLC, we will also create two connectionsin DASSIDirect DAServer. Connection 0 will correspond to the connection as created in Figure7:

Figure 18: DASSIDirect Connection 0

The Remote TSAP in DASSIDirect must be the Local TSAP in the PLC configuration,and vice versa.

Connection 1 shown in Figure 19 (below) will correspond to the connectionas created in Figure 8:

Figure 19: DASSIDirect Connection 1

The single parts of the remote TSAPs in DASSIDirect are called Remote RackNo, Remote Slot No and Connection Resource. This naming conventionwas meant for S7-300 and S7-400 PLC’s.

For S7-200 PLC’s it is a little bit different. The Remote Slot No (whichis the remote slot number of the CP, not the CPU) in the DASSIDirect configurationcorresponds to the Module Position as seen in Figure 4.The Remote Rack No should always be 0.

Another way to figure out the correct values for the remote TSAP’s in DASSIDirectis described in the following information:

Figure 20 (below) shows you how to figure out the meaning of the single partsof the remote TSAP in DASSIDirect from a local TSAP configuration in the PLCas seen in Figure 7 or Figure 8 (The TSAPin Figure 20 do not correspond to the TSAP’s as used in the above example. Iwanted to have different numbers for Rack and Slot in Figure 20!).

Figure 20: Remote TSAP

The TSAP in Figure 20 would correspond to the remote TSAP value in Figure7 or Figure 8.

In this example the value for Connection Resource in DASSIDirect wouldbe 02, the value for the Remote Rack No would be 0 andthe Remote Slot No would be 3.

Now create your device group(s), if necessary.

For a DDE/SuiteLink connection you need to have at least one device group perconnection, for OPC it is not necessary. For to test the communication as describedbelow, please enter a device group called S7200.

The connection between DASSIDirect and the S7-200 PLC should now be ready totest.

Test the Communication

In previous TechNotes we used wwclient for testing. This tool will nolonger be installed when installing ArchestrA (A²) products like InTouch8.0 or any DAServer. If you have InTouch 7.11 installed you will find this toolunder Program Files/Wonderware FactorySuite/Common and you can use thistool.

Create a simple InTouch application with one tag.

Select Special/Access Names from the main menu.

Select Add.The Add Access Name dialog box appears:

Figure 21: Add Access Name

Enter a meaningful name in the Access field.

Leave the Node Name blank if you have InTouch and DASSIDirect on the same node. Otherwise enter the nodename of the PC where DASSIDirect resides. The Topic Name must match the Device Group name as configured in DASSIDirect.

Select Special/Tagname Dictionary and select New.

Figure 22: New Tagname

Select Type: I/O Integer and the access name as created in the previous steps.

Use the item MB1 because it always exists in all S7-200 PLCs. Use this tag in the window you just created.

Activate DASSIDirect in the System Management Console (SMC).

Start WindowViewer™.

Open the Diagnostic in the SMC to verify the communication:Figure 23: Check Communication from the SMC If you see a Time value that is changing, and a Client Quality of 00C0, your communication is fine.

Feed Live

Disclaimer

No PDF Files stored in this site. duniaengineering.wordpress.com are not responsible if you download and distribute files or links. Noted that duniaengineering.wordpress.com not related in any way with upload files with a copyright material that available for download. Just we collects the information using google search and other search engines links hosted or posted by other website. The link Free Book Download available here are for EDUCATIONAL PURPOSES ONLY... and its recommended to buy the products from the original Owner or Publisher.