Connection Splicers in the Topology

Connection splicers can be inserted as topology functions into a routing path network. If several connection splicers are used in one device, only one (the main function) may exist with the "Topology" representation type, and it represents the complete device.

Connection splicers without continuous connections

Connection splicers without continuous connections are treated like normal devices. Connections that end at a connection splicer are routed like any other connection directly from the source to the target.

Connection splicers with continuous connections

If you have configured connection splicers with continuous connections in a multi-line representation, the respective connections contain the information about which connection splicers they run through. This information is stored in the property Connection splicers passed through and is taken into consideration during routing.

In order for a routing connection to pass through a connection splicer, you have to define the position of this connection splicer by means of a routing point. To do so you place the connection splicer near a routing point through which the routing track runs. During routing an automatic routing path from the connection splicer to the routing point with the length "zero" is then created. Alternatively, you can connect the connection splicer via a manually inserted routing path to the routing point.

During routing the routing track from the source to the target is first determined. The routing points laying on the routing track are examined whether a connection splicer is connected directly there (meaning through a single automatically or manually placed routing path). If this is the case, the DT of the connection splicer is entered in the Topology: Connection splicers passed through (sorted) property. In this property all the connection splicers through which the connection runs are listed in the order from source to target. After the connection splicers have been determined, the connection is routed again and laid through the connection splicers in the process.

The Connection splicers passed through property determines which connection splicers the routing connection have to pass through. If not all the connection splicers are found during routing, for example because a connection splicer does not exist as a topology function or a connection splicer does not lie on the routing track, a corresponding message is output. In this case change the position of the connection splicer or change the routing of the connection so that the routing track passes the connection splicer.

Properties for connections

The following properties supply information about the existing connection splicers at a connection. Only those connections are considered that pass through at least one connection splicer.

Connection splicers exist (ID 31139): Shows whether connection passes through at least one connection splicer. This property can be used as a filter criterion for connection lists.
Connection splicers passed through (ID 31136): Outputs the DTs of the connection splicers which pass through the connection. The individual values are separated by a semicolons and sorted alphanumerically.. This property can be used in reports.
Topology: Connection splicers passed through (sorted) (ID 31137): Outputs the DTs of the connection splicers which pass through the connection at a routing connection. The individual connection splicers are differentiated in the order from source to target through the index. This property can be used in reports.
Topology: Distance between connection splicers and source (ID 31138): Outputs the position of the connection splicers passed through on this connection at a routing connection. To this purpose the distance between the connection splicer and the source of the connection is specified. The individual connection splicers are differentiated in the order from source to target through the index. This property can be used in reports.