Routing rules can be created to limit what type of products can enter a rail or bridge. They are assigned directly as a property on the rail.
- Routing rules on station rails are validated during routing, that is when it is assigned a destination. It is not checked when the carrier is unloaded from line to rail, so if it is already assigned to a rail a newly created rail rule won't change the carrier destination.
- However, routing rules on bridge rails are validated in real-time when a carrier passes the bridge reader. They are also validated during routing to determine what bridges a carrier is allowed to pass to get to its destination.
Name ✎
Name of the routing rule.
Description ✎
An optional descriptive text for what this routing rule does.
Exclusive ✎
Exclusive rules affect all rails in a station group, according to the following logic:
- Non-exclusive rule
- Carriers matching the rule can enter any rail
- Carriers not matching the rule will not enter the rail, but any other rail
- Exclusive rule
- Carriers matching the rule will enter only the rails with the rule, and not enter other rails
- Carriers not matching the rule will still not enter the rail, but any other rail
In the case of different sets of destination rails with rules that exclude each other, the carrier will get a routing error.
See Routing Rules for example
Rule ✎
One or more parts that will apply to the rule.
A rule is made up of three parts:
- A field, eg. "article number", "order number", "criteria"
- A comparer, eg. "Is", "Contains", "Equal or Less Than"
- A value, eg. "T-Shirt", "34786", "Size: M"
Please see topic Routing Rules for more info
Unexpected Product Route ✎
Part of Product Detector logic.
This is the route that carriers that should be empty, but has a detected product, will be sent on. Since the carriers are empty in the system, you can only pick from routes of type Return Empty Carrier.
This only applies to carriers addressed to a rail with this rule, or carriers attempting to use a bridge with this rule.
Unexpected Product Rail ✎
Part of Product Detector logic.
This is the rail that carriers that should be empty, but has a detected product, will be sent to.
Carrier will be mechanically adressed to this rail.
This only applies to carriers addressed to a rail with this rule, or carriers attempting to use a bridge with this rule.
Setting this to 0 will clear the current destination of the carrier, and the carrier will be re-routed to a different destination if one is available. If none is available it will stay on the line.
Missing Product Route ✎
Part of Product Detector logic.
This is the route that carriers that should have a product, but does not have any product detected, will be sent on.
Since the carriers are have a product in the system, you can only pick from routes of type Inspect.
This only applies to carriers addressed to a rail with this rule, or carriers attempting to use a bridge with this rule.
Missing Product Rail ✎
Part of Product Detector logic.
This is the rail that carriers that should have a product, but does not have any product detected, will be sent to.
Carrier will be mechanically adressed to this rail.
This only applies to carriers addressed to a rail with this rule, or carriers attempting to use a bridge with this rule.
Setting this to 0 will clear the current destination of the carrier, and the carrier will be re-routed to a different destination if one is available. If none is available it will stay on the line.