If a carrier is going around on the line and does not enter the expected station or bridge:
Start by opening carrier history and entering the id of the carrier. The most recent events of that carrier might contain a clue as to why the carrier is not unloading.
Rail Overload
A carrier will not enter a rail or a bridge that has the overload sensor activated. To check this, open the station in the station settings, expand the setting to view the rail(s) and check if the overload switch has been activated.
Missing Routing
Using the Carrier Status Page, you can enter a carrier number and determine where it is heading. Check that the carrier is heading to the expected rail. If there is a routing error for the carrier, that will also be shown on this page.
Sequenced Unloading
Open Station Settings for the target station. Check if the Sequenced Unloading setting is activated.
If this is the case, you can use the terminal command
Show what carrier is next expected to the first rail of the current station.
Current station must have sequenced unloading enabled.
on the target station to check what is the next expected carrier, it might be a different number than the carrier you are expecting to enter.
You can also use carrier search to find all carriers heading to the same rail. If you sort the search results on the sequence, you should be able to see the "oldest" article/order line and where they are in the system.
Blocking Buffer Calls
If you are using blocking buffer calls, the rail may not be accepting carrier because it needs to wait for earlier buffer calls to arrive first. Check the Buffer Calls page to determine if there are blocking calls heading to this rail.
Line Reader not working / Bad Tag
There may be a problem with a station RFID reader. You can enable the line reporting to check that the reader is correctly scanning carriers.
If the station is reading carriers properly, except the carrier you are interested in, there may be a problem with a bad tag on that carrier. In that case, manually take the carrier down from the line, or use test mode to force it to enter a rail. see Extract carrier with bad tag.
Non functional unloading arm
Use test mode to verify that the unloading arm is functioning correctly. The unloading arm works on air pressure, so the air compressor must be running.
Extract carrier with bad tag
âšī¸ Ensure that the terminal account account which will be used has a role with 0027 âĸ Test Mode permission enabled.
- Go to the station where carrier should be unloaded to.
- Log in on the primary terminal and enter Test Mode with:
Enters test mode. This is a mode that runs locally on the node where a mechanic may check each of the inputs and outputs of the station to diagnose mechanical issues.
đ Requires Permission 0027 âĸ Test ModeOnly works on primary terminal. Node is not required to be online for this command to work.
- Choose TEST with F1
- Wait until the carrier you want to unload is close to the station
- Press F4 to toggle the unloading arm to be in unload-position
- Once the carrier has been unloaded to the rail, Press F4 again to put the unloading arm in closed position
- Exit Test Mode by pressing 0 + F8
- Press F8 again to exit the Test mode menu
- Physically detach the carrier at the rail or on the station work position.
- Make sure that the station has the correct rail load on Station Settings-page. If the rail load is incorrect, reset
the carriers that don't physically exist, if there have been any
read.
Issues on Newly Setup Systems
Some issues can occur because of incorrect configuration. This is mostly noticed on a newly added or re-configured line.
Incorrect setup station rail
If the carrier is trying to reach a rail on the same line as it's currently on
- If the rail unloading arm is opening and closing too early or too late, that would most likely be due to an incorrectly configured unloading delay.
- Check that the rail it's going to has the correct configuration (Hardware Configuration > Rails). The unloading node id, the internal rail number and the unloading line must be correctly set.
- Check that the station headline reader is reporting the carriers passing by. (Hardware Configuration > Rails > Right click the rail > "Spy (Unload Node"). When carriers pass by on the headline the node should report this with a message line 1234T. Alternatively just use the headline report terminal command.
- Are there other messages going to and from the node / does the terminal show as online?
- YES: Check that the correct unloading node is set on the rail, check that the headline reader is connected to the correct IO and working.
- NO: Check that the node has power, that the node id has been set in local setup mode and that the CAN cables have been properly connected.
Incorrectly setup bridge
If the carrier is trying to reach a destination rail on a different line (and it's not part of a buffer call) then it should go on a bridge.
Checklist
- Check that the bridge rail is not blocked
- Check that there are not rail rules set on the bridge rail, preventing this carrier from using it.
- The bridge station has to have the flag "Bridge" (or "Secondary Bridge")
- The bridge station type should be a transporter type (for example 12 or 50), except if it's a secondary bridge.
- Confirm that the nodes on either side of the bridge have the correct line set. (Navigate menu to Hardware Configuration > Nodes)
- If there is a bridge from line 1 to line 2, it would normally be named 1291. The first number (1) is the line it unloads from, the second number (2) the line it loads to. 91-99 indicates the bridge number, 91 being the first bridge, 92 the second and so on.
- Check that the station 1292 is using the node that is located on line 2. The station always uses the node on the line it loads to.
- Check that the rail 1292 is using the unloading node on line 1, and the rail also has "Unload Line" set to 1.
If it's trying to reach a line several bridges away, the issue might also be with one of the later bridges. Attempt to address something to the neighbouring line and see if that uses the bridge, otherwise repeat the above process for the other bridges.