Prefer Route Constraint for Defining a Preferred Route for a Signal

You can use a Prefer Route constraint to define a preferred route that a signal could use in a configuration during wiring synthesis. With this constraint applied (on a route), the route is considered as lower cost than alternate routes considered by synthesis. This constraint will only be evaluated for a signal if synthesis does consider the route containing the object on which the constraint is applied. Hence, using this constraint does not guarantee that the signal will be routed through the preferred route.

Note

Wiring synthesis applies this constraint only when the preferred route is considered as a potential routing solution. If it is not considered as a potential routing signal, the given signal is reported as "Routed (non-preferred)" in the wiring synthesis output and in the Design Assistant.

The option expression can have a maximum of 255 characters.

You can run a ‘Preferred route is never used’ design rule check to report cases where preferred routes are never used by wiring synthesis.

Note

A signal may appear to not follow its preferred route if one of the signal splices is on a junction node owned by a bundle on which the preferred route is defined. The signal appears to not follow the preferred route even though, according to the data, it does. Accordingly, we don't report this signal as not following the preferred route.

• Use Cases for Prefer Route Constraint

Parent Topic:

Usage Examples for Rules and Constraints in Capital Systems Integrator

Capital Systems Integrator User Guide, 2512.2606

Unpublished work. © 2026 Siemens