When the operator pushes the operator switch, the system will attempt to route the carrier to its next destination. If the destination cannot be reached, a routing error will be displayed on the terminal and the carrier will not leave the work position. There may also be other reasons for the carrier not leaving, see Station Locks.
The system will automatically retry to route the carrier until it succeeds, at which point the "Continue" message will be shown on the terminal indicating to the operator that the operator switch can be pushed again to send the carrier away. Pushing the operator switch while there is a routing error displayed will not have any effect.
Destination Full
Displayed on terminal: [Rail] +X Full
This is a common message if all the recieving rails are filled to capacity. For some use cases this may be quite normal, such as when an empty carrier buffer is constantly feeding loading stations with empty carriers.
If this error frequently shows up on work stations, it may indicate that the system is not balanced correctly.
The terminal message will show the first full rail, and the total number of rails available.
Solution
Free up space on the recieving stations to continue
Station Group Not Available
Displayed on terminal: GroupNotValid
The destination station group is not configured as being available for routing, but is still used in the route. This indicates a misconfiguration.
Solution
Reconfigure the station group used in the route to be available for routing or use a different station group.
No Stations in Station Group
Displayed on terminal: NoStationInGroup
This error will occur if there is no station configured in the destination group. This indicates a misconfiguration.
Solution
Add stations to the station group that is configured in the route
No Stations Online
Displayed on terminal: NoStationsOnline
No station in the station group configured in the route is online.
Solution
Investigate if there is a hardware issue and why the stations are not online.
Rails Blocked
Displayed on terminal: RailsBlocked
All the rails are blocked from receiving carriers.
Solution
Unblock the rails via station settings
No Rails Match Rail Rules
Displayed on terminal: BlockByRailRules
Will happen if there is no rail in the station group for the route that has routing rules allowing this carrier entry. This indicates a possible misconfiguration.
Solution
Reconfigure the route or modify the routing rule to allow the carrier.
No Reachable Stations
Displayed on terminal: NoReachableStn
This error will happen if the system does not detect any available path between the currently sending station and any station in the recieving station group. This indicates a possible misconfiguration.
Solution
- Check if the recieving stations in the station group are set up correctly and that the stations are physically connected via bridges
- Check if the rail rules on bridges allow this carrier
No Collection Route
Displayed on terminal: NoCollectRoute
A carrier that is not currently on any route will by default be adressed to a colleciton station group that is set up as a system setting. This error will happen if there is no station group configured for collection.
Solution
Configure a station group for collection in the system settings.
Invalid Mechanical Destination
Displayed on terminal: InvalidMechRail
This can happen if mechanical addressing is used, and the rail entered does not exist.
Solution
Readress the carrier mechanically to a rail that does exist.
Operator Address Missing
Displayed on terminal: EnterAddress
If the operation is set up as being operator addressed, but no destination has been entered by the operator, this error may occur.
Solution
Enter a destination via terminal commands.
Invalid Operator Address
Displayed on terminal: InvalidAddress
The operator has entered an invalid destination when selecting the destination.
Solution
Enter a valid destination via terminal commands.
Overflow Unavailable
Displayed on terminal: NoOverflow
The destination stations are full and the operation has an overflow route set. However the overflow stations cannot be reached due to some other routing error. If the overflow station is full, you will instead get the Destination Full error.
Solution
Check that the overflow route is correctly configured
Call Destination Blocked
Displayed on terminal: CallSequence
The station is routing a carrier that is part of a buffer call, but the destination is currently recieving another blocking call order. This error should not happen on a regular work station, but is quite normal on a buffer station when blocking call orders are in use.
Solution
Wait for the blocking buffer call to complete.
Blocked by Call Order
Displayed on terminal: BlockByCallOrder
This error is very similar to Call Destination Blocked, but will only happen when we are attempting to route a carrier that is not part of a call order to a destination that is blocked by a call order. This error is more likely to show up on a work station than a buffer.
Solution
Wait for the blocking buffer call to complete
All Excluded
Displayed on terminal: AllExcluded
The addressing strategy does not provide any allowed destination for this carrier.
Solution
Check the addressing strategy for the operation to find how it is configured and work to resolve the problem from that point
Blocked in Station Group
Displayed on terminal: BlockInStnGroup
The rails are blocked in the station group.
Solution
Edit the station group and remove the blocks.
No Operations
Displayed on terminal: NoOperations
We are on a route that does not have any configured operations. This is due to a misconfiguration.
Solution
Add operations to the route.
Special Errors
These should never occur during normal operation and may require assistance from Eton Systems support. There are no fixed procedures to solve these errors.
Carrier Not Found
Displayed on terminal: CarrierNotFound
The carrier we are attempting to route is no longer found in the database
Next Operation Unknown
Displayed on terminal: NoNextOperation
The system has failed to determine what operation should be performed next
No Stations Available
Displayed on terminal: NoStnsAvailable
The adressing strategy has not found any stations to send to.
No Best Rail Found
Displayed on terminal: NoBestRailFound
The system has failed to find a rail to route this carrier to.
Unknown Addressing Strategy
Displayed on terminal: BadStrategy
The current operation is set up with an addressing strategy that is unknown to the system.
General Error
Displayed on terminal: GeneralError
Something unexpected has happened when the system attempted to route this carrier. Contact support.