Channel Reservation Error when Using NI Switch Executive

Issue Details

I get one of the following errors when I manually try to edit a route in NI Switch Executive or when I try to put a route in the Parent Route Group. 
 
Channel reservation error. The route [example/b0c2->example/b0r0->example/b0c3] conflicts with another route Route0 [example/b0c0->example/b0r0->example/b0c1]. To use these routes together, make them share a common endpoint or make them use different reserved for routing channels.



Cannot connect a leg in route Route2.
Channel reservation error. The route Route2 [example/b0c0->example/b0r0->example/b0c1] conflicts with another route Route0 [example/b0c0->example/b0r0->example/b0c1]. To use these routes together, make them share a common endpoint or make them use different reserved for routing channels.
Do you want to break Route2 and find an alternate route?

Solution

This error occurs when a route with a conflict is added to a Parent Route Group or when a route in a group is edited manually. To prevent the error, remove the route from the group, make the routes share a common endpoint, or use different reserved for routing channel. The current configuration contains routes that cannot co-exist. In order to share a midpoint, you need to have an overlapping endpoint. 

The main use case of route groups is to prevent signals from different routes from being mixed together. A route group allows the user to connect all the members of the group using one alias name. A route group also provides route conflict checks for the members of the group.

When designing a switching system using NI Switch Executive, you typically create individual routes first and then group them to according to what routes need to be connected simultaneously. For each point in the test sequence, you would connect a route group and Switch Executive would in turn connect the routes that are members of that route group. The route group makes things more convenient, allowing for a route group to be connected all at once, rather than having to connect individual routes. 

An example of a route group would be all the switch routes needing to be connected at a given point in the test sequence, example: Route1 connects DUT1_Pin1 to PowerSupply1, Route2 connects DUT1_Pin2 to Instrument1, etc.