Overview

By using the Control Expert Editor, you can modify the configuration of local racks and drops of M580 PACs that you have added to your system project.

Changes to the hardware configuration of the PAC are reflected in the various views and panes when you save the changes. When a rack is displayed in a physical view, changes that you make are visible only for the objects that normally appear in this view (for example, modules with Ethernet connectivity in the main local and main remote racks).

NOTE: When you add a module to the configuration that is not supported in the Topology Manager, it is represented as a plain module in the Rack Viewer, has minimal properties, and may not appear in some views (for example, physical views).

IP Address Management

Default IP addresses of modules that you add may be replaced in the Topology Manager when you save changes. This is because the consistency of communication parameters of the system project is managed by the Topology Manager.

Also, adding a module that manages an IP address may create an additional logical network in the system project when you save changes. This is the case, for example, when the IP address of the embedded interface of the module must belong to a different logical network than the IP address of the CPU.

Impact of CPU Module Replacement on the System Project

When you save changes after replacing an M580 CPU module, the software updates the necessary data automatically.

The table describes some specific impacts of a CPU module replacement on system project objects and data depending on the replacement scenario.

System project object or data

From standalone to standalone

From redundant to redundant

From standalone to redundant

From redundant to standalone

PAC name

No change.

PACs that have their default name are renamed Redundant_Controller_x where x is an integer suffix.

PACs that have their default name are renamed Standalone_Controller_x.

Local racks

The name is replaced by M580_A_x.

An identical local rack B is added with name M580_B_x.

Local rack B is deleted.

The name of the former local rack A is kept.

IP addresses of modules

IP addresses may be reassigned depending on the availability of specific addresses in the same logical network (for example, MainIP+1 ).

No change.

Scanner services

The Communication Mapping Views are updated depending on the scanner services of the CPU reference that you have selected.
 

Scanner services of modules in local rack A are used.

Scanner services of modules in former local rack A are used.

DHCP servers

No change.

Modules in local rack A become the DHCP server.

The name of the DHCP server is updated in clients.

Modules in former local rack A become the DHCP server.

The name of the DHCP server is updated in clients.

Modules in local racks

Modules present in local rack A are automatically added to local rack B.

Modules present in former local rack A are kept.

Physical links

Only the high-speed cable link with local rack B is created.

Physical links to and from local rack B are removed.

Deleting Modules

To delete a module from the configuration right after closing Control Expert Editor or using the Synchronize Changes command, you may need to fix incorrect configurations in the Topology Manager first.

This is required to be able to open Control Expert Editor again to delete the module or close Control Expert Editor to apply the deletion in case it is still open.

Copying and Pasting HART Modules

When you copy and paste a HART module in a rack, the following applies:

  • The DTM of the module is not copied.

  • If you have added HART field devices to the module by using the Fieldbus Editor, they are not copied.

Editing Racks of Redundant PACs

When you modify the configuration of either local rack of a redundant PAC (for example, adding or deleting a module), the modification is automatically applied to the other local rack when you save changes.