Mapping a Functional

Message to a Network Message

After you have added a functional message to a functional design, you can map it to a network message stored in Capital Signal Modeler. This allows you to manage which network signals are included in that message instance.

If you want to use the same network message for different connections, you can map multiple functional messages to it. That means, you can have multiple instances of a network message and network signal in a design. Attributes on a mapped functional message in the design allow you to view and edit details about that instance of the network message (see the Results section in this topic).

Prerequisites

• The network message must exist in your network messages and signals library in Capital Signal Modeler.

• The functional message must exist in your functional design.

• If you have object type information specified for messages in Capital Project Manager, you are offered those names when you click the Name ellipsis (…) button for a functional message in Capital Systems Modeler. This means, you are not offered the network messages from Capital Signal Modeler and you cannot map the functional message to a network message. If you want to map functional messages to network messages, there must be no object type information for messages in Capital Project Manager.

Procedure

1. Right-click on the message and choose Properties: a properties dialog box displays. Then click the ellipsis button next to the Name field.The Name Selection Dialog Box (for Message) displays. Caution You can also access the Name Selection dialog box by double-clicking on the functional message name in the diagram window and clicking the ellipsis (...) button next to the Name field. However, this will update the message name only. It will not update other attributes and properties with values from the dictionary message.

2. Select the network message from the table.Note The table headers allow you to sort and filter each column.

3. Click OK.

Results

• The system maps the functional message to the network message.

• The system sets the functional message attributes as follows: Name attribute has the network message’s name. You can edit this so that you can avoid duplicate functional message names in the design.

Three read-only attributes are populated to provide details of the network message instance: Design, Dictionary Message Name, Dictionary Message Revision. These are blank if the functional message is not mapped to a network message. Note You can run a design rule check “Dictionary signal/message out of date” that identifies where these attribute values on a functional message in a design are different from those attributes on the mapped network message in Capital Signal Modeler. See Running Design Rule Checks. This means, a network message attribute has been changed in Capital Signal Modeler but the change is not reflected in the functional message. To fix this, re-map the functional message to the network message.

Message Instance attribute is blank by default but you can edit this to have a meaningful name for this instance of the network message. This is only of use if you are mapping multiple functional messages to one network message. Note The Message Instance attribute on any signals in the instance also update with the value specified here.

• In the Design Browser (Design tab) at the bottom left of the application, the functional message name updates and all of the signals associated with the network message are listed below it. Note By default, all of the signals associated with the network message are included in the message instance. However, you can change (manage) which of these signals are included. See Managing the Network Signals in a Message Instance.

Parent Topic:

Networks in Capital Systems Modeler

Capital Systems Modeler User Guide, 2512.2606

Unpublished work. © 2026 Siemens