PlantStruxure PES [V4.0]: Why do devices that I add to the application and the topology do not communicate when I deploy them by using the Deploy Changes command?

Goals and Symptoms

Add communication objects and deploy it to communicate.


Facts and Changes

PES version V4.0
Some objects i.e. instances of $ATV61E, $MBPortM,... do not communicate when I deploy them by using the Deploy Changes command


Causes and Fixes

When you add certain device and/or communication port instances to a system that you have already deployed to a controller, using the Deploy Changes command does not update the work memory.
This applies to device templates that use the following communication protocols, and the corresponding communication port templates:
- Modbus serial (for example, $ATV71MB, $MBPortM)
- Ethernet Modbus TCP explicit messaging (for example, $ATV71EM, $EMPortM)
- The gateway template $EGtwMB

When you want to add such a device and/or port instance to a system that you have already deployed to a controller:
- Add the device instance to the application with help of ADDM block. (Ex: please find the below picture for Ethernet communication with EthAddm block in the Application Instance)

- If required, add the topological device template to the topology.
- Assign facets, generate, map facets.
- Refine the Control Participant project and verify that the communication port DFB is executed after any device DFB that communicates with it.

- Build the executable by using the appropriate command (for example, if you have added a topological device instance, you need to use the Build All command).
- Deploy the Control Participant project by using the Deploy Built Project command.

Note:
- The same applies when you rename devices and/or communication port instances.
- Using the Deploy Built Project command requires stopping the controller.

For more information on communication with devices, refer to the Process Expert User Guide, Managing Communication.
For more information on using build commands, refer to the Process Expert User Guide, Control Project Build Stage.

Publié pour: Schneider Electric Belgium