Overview

The Deploy command lets you transfer the executable of a control project of an M580 PAC to the CPU or communication module of the physical controller that it represents.

For a redundant PAC, you can select to deploy only to rack A or B or to both.

Depending on the value of the Build Target attribute, it may allow deployment only to the simulator.

The PAC is locked while deployment is in progress.

When you use the Deploy command when more than one PAC is selected, the DEPLOYMENT VIEW opens.

Prerequisites

The following are prerequisites to deploying the executable to a physical module:

  • The control project must be built with the Build Target value set to Real.

  • For the physical CPU module, the following applies:

    • It must be reachable at its configured main IP address and compatible.

    • Confirm that it is in STOP state or that it can be stopped.

    • It is not reserved.

    For a redundant PAC, the prerequisites apply to the CPU modules of racks A and B.

  • In case you are deploying to a NOC communication module instead, it must be reachable at its configured IP address and compatible.

  • The SODB service is running.

NOTE: Verify that in the control project whose executable you are deploying, the following conditions are satisfied:

  • The IP addresses match those of the physical module you are deploying to.

  • The security settings permit future connections to the module from your engineering stations.

Otherwise, you may not be able to connect to this module after deploying the executable.

Modifying the Control Project After Deploying

Once you have deployed the executable to a PAC, performing either action described in the following table requires that you stop the controller to deploy the modification.

For actions that you perform in the Topology Manager, a message is shown to inform you of the required controller stop. You can select to proceed or cancel the action. If you proceed, this message is not shown anymore until you deploy to the PAC.

Control project

Controller mode when the action is performed

Action in the Topology Manager

Action in Control Expert Editor

Closed

n/a

Any modification that changes the build state.

n/a

Open in Control Expert Editor

Disconnected.

Any modification that changes the build state.

Closing the control project and saving modifications that have not been deployed to the controller.

The modification can be the result of a Synchronize Changes command (except in virtual connected mode where the command is not allowed).

Virtual connected mode.

Equal online mode.

Closing the control project and saving modifications that have not been deployed to the controller online.

Password Management When Deploying by Using the Context Menu Command

The following applies when you use the Deploy > Configuration command in the context menu of a PAC.

If an application password is set in the control project that is deployed in the controller, you must enter it when prompted before you can deploy the executable.

If you select to reuse the password for next deployments, you are not required to reenter it when you deploy again to the same PAC or to another PAC by using its context menu command. This applies until you close Control Expert or the password does not match the application password that is set for project deployed in the controller.

If you copy a PAC after having selected to reuse the password and deployed, it is also reused for the pasted PAC.

Password Management When Using the DEPLOYMENT VIEW

The following applies when you deploy to a PAC by using the DEPLOYMENT VIEW .

If the Password column indicates Required - Not Set and you click Deploy, a dialog box opens and you cannot deploy. Right-click the PAC, select Edit Password , and enter the application password that is set for the control project deployed in the controller.

If you choose to use the password for all the selected PACs, you are not required to enter it when the software deploys to the next PACs in queue neither when you deploy again to the same PACs given the password matches the application password of the deployed control project (if set); this, until you close Control Expert.

If the Password column indicates Required - Set but the password does not match the application password of the control project that is deployed in the controller, the deployment is not performed and you need to enter the correct password by using the Edit Password context menu command.

Deploying to Redundant PACs

For a redundant PAC, you can select IPA and/or IPB for deployment.

Only the controller that you are deploying to is stopped.

When you deploy to both controllers of a redundant PAC, the executable is first deployed to controller A ( IP Address A) then to controller B (IP Address B). if deployment to controller A does not complete successfully, deployment to controller B is canceled.

To view the states of the controllers, edit the control project of the PAC.

Deploying to the PLC Simulator

To be able to use the PLC simulator, its listening IP address setting must be the same as the IP address that it is using. That is, 127.0.0.1 when you are connected to the local system server or the IP address of local computer when you are connected to a remote system server. You can see this IP address in the Address column of the DEPLOYMENT VIEW.

The setting applies only to simulator instances that you start thereafter.

To configure the listening IP address of the PLC simulator and apply it, proceed as follows.

Step Action

1

If no simulator instance is running, start one by using either method:

  • Selecting the check box in the DEPLOYMENT VIEW or using the Deploy > Configuration context menu command of a PAC whose Build Target attribute is set to Simulator .

  • Clicking EcoStruxure Control Expert > PLC Simulator from the Windows Start menu.

2

Right-click the icon of a simulator instance in the task bar and select Options... .

3

In the Simulator Panel Options , configure Listening IP Address with the IP address that is used by the simulator and click OK.

Result: The simulator instance closes and a message prompting you to restart it opens.

NOTE: If other simulator instances are running, close them.

4

Restart the simulator instances that were running.

NOTE: If you are using the DEPLOYMENT VIEW , clear the check boxes of the PACs that are selected and select them again.

Deploying the Executable by Using the Context Menu Command

To deploy to a PAC by using the Deploy > Configuration command, proceed as follows.

Step

Action

1

Verify that the prerequisites are satisfied.

2

Right-click the PAC and select Deploy > Configuration.

Result: The Confirm Deploy Control Project dialog box opens.

3

In the IP Address menu, select the module that you want to deploy to.

Result: The software verifies the status of the module and displays it. If the status is Not Reachable, you cannot proceed with the deployment.

NOTE: For a redundant PAC, deployment is performed only to the controller (A and/or B) for which you select an IP address.

4

Verify the information that is displayed in the Project Information section.

5

Select Run controller after deployment to send a run command to the CPU once deployment completes successfully.

NOTE: For a redundant PAC, the command is sent to the CPU modules of controllers A and B.

6

Click OK .

Result: The Deploy confirmation dialog box opens.

7

Read the information that is shown in the dialog box and click Yes .

Result: The software stops the CPU and transfers the executable to the module and indicates the status of the operation in the notification pane.

Deploying the Executable by Using the DEPLOYMENT VIEW

To deploy to selected PACs by using the DEPLOYMENT VIEW , proceed as follows.

Step

Action

1

Verify that the prerequisites are satisfied.

2

If a password-protected application has already been deployed to one of the selected PACs, set the same password by using the Edit Password command.

3

Verify that the status of each of the selected PACs and/or racks allows deploying to it.

4

In the row of a selected controller, select the check box in the Run after deployment column to send a run command to the CPU once deployment completes successfully.

NOTE: For a redundant PAC, the command is sent to the CPU modules of controllers A and B.

5

Click the Deploy button in the toolbar of the view.

Result: The Deploy: Configuration dialog box opens.

6

Read the information that is shown in the dialog box and click OK.

Result: The software stops the CPU of the first selected PAC and/or rack (if it is running) and transfers the executable to the module.

In case the deployment to a PAC does not complete successfully because the password is incorrect or it is reserved, the Deploy: Control Project dialog box opens. Otherwise, deployment to the next object in queue is initiated. Proceed to step 9.

NOTE: If a deployment does not complete successfully for another reason, the software proceeds with the next object in queue. Details about unsuccessful deployments are available in the OPERATION DETAILS tab after the last deployment is completed.

7

While deployment is in progress, you can modify the selection of objects. Selecting the check box of an object adds it to the deployment queue. Clearing its check box removes it from the queue.

8

In the dialog box, click either button:

  • Yes: Deployment to the next object in queue is initiated.

  • No: Cancels the deployment operation. Deployments that have already completed successfully are not impacted.

9

Once the entire deployment operation is completed, the status of the operation is indicated in the notification pane and the status of the objects is refreshed.
NOTE: If the selection of objects includes a device, refer to the topic describing the deployment to this type of object for more information.

Troubleshooting Information

The table describes the diagnostic messages that the software may display in the OPERATION DETAILS tab when you attempt to deploy an executable and their corrective actions.

Diagnostic message

Corrective actions

The control project is not built.

Build the control project.

The server cannot connect to the SODB service because the service is not running.

Verify that the diagnostic engine is ready.

Controller cannot be reached.

Verify that the physical CPU module is reachable.

The physical controller is different from the controller that is configured.

Verify that the physical controller you are trying to deploy to has the same configuration as the PAC (for example, CPU reference, firmware version, module reference and position) and that the IP addresses are matching.