Configuring the Logic/Motion Controller

Configuring the IP Address of the Logic/Motion Controller

Step	Action
1	In the Devices tree, double-click the controller node.
2	Click the Communication Settings tab. Result: The tab lists the controllers that are accessible by your computer (independently of their communication parameter settings). If the particular Logic/Motion Controller controller is not listed, click the Update icon on the toolbar. Result: Logic Builder scans the network for connected controllers and adds detected devices to the list.
3	Right-click your controller in the list and select Edit Communication Settings from the context menu.
4	Define the communication parameters according to the requirements in your network, select the option Save settings permanently, and click OK.

Adapting the Task Settings

You must adapt the cycle time of the cyclic task TASK_SR_VisControl. (This task is defined in the example you have used to create your project.)

Step	Action
1	In the Application tree, expand the Task Configuration node, and double-click the TASK_SR_VisControl.
2	Set the task Interval to 300 ms.

Configuring the Ethernet 1 Port

Step	Action
1	In the Devices tree, double-click the Ethernet_1 node. Result: The parameter editor opens on the right.
2	Enter the following fixed IP Address configuration: oIP Address = 172.20.0.1 oSubnet mask = 255.255.255.0

Step

Action

In the Devices tree, double-click the Ethernet_1 node.

Result: The parameter editor opens on the right.

Enter the following fixed IP Address configuration:

oIP Address = 172.20.0.1

oSubnet mask = 255.255.255.0

Defining the Sercos Bus Cycle Time

Step	Action
1	In the Devices tree, double-click the Sercos_Master node. Result: The parameter editor opens on the right.
2	Open the parameter group SercosCycletimeConfig and enter a CycleTime value of 4 ms. Refer to Best Practice below this table.

Step

Action

In the Devices tree, double-click the Sercos_Master node.

Result: The parameter editor opens on the right.

Open the parameter group SercosCycletimeConfig and enter a CycleTime value of 4 ms. Refer to Best Practice below this table.

Refer to the Sercos for M262 Logic/Motion Controller User Guide for details and further information.

Best practice: The suitable cycle time value depends on the number of connected Sercos slaves, I/O modules, and on your application requirements. If a cycle time of 4 ms results in an insufficient system performance of your application, decrease the value.

The Sercos cycle time, however, influences the available asynchronous communication. This has an impact on the start-up performance and the system reliability of the application. There are two possibilities to increase the bandwidth of the asynchronous Sercos channel:

oIncrease the Sercos cycle time.

oStop the Sercos phase-up during the second phase for a few seconds to allow the SLC to finish the parameterization of the SNs.