Smarter Robot Arms

1 votes

What I mean by smarter here is:

Currently the Robot Arm is aware of the contents of the belt/chest/bench it is taking the items from, and does not care what happens in the place it puts these items.

It would be awesome if we could have Robot Arms be aware of the end recipient(*) of the item it drops, have a "pending" state(*) and account for the 9999 stack limit when trying to move the items. Picture this for a better understanding:

Let's say I have a smelting system which consists of a Robot Arm taking raw ore from my chest(1) and dropping it on a belt, belt that later down the road has 7 other Robot Arms connected, filtered to pick up ores from Copper to Galaxite (one Robot Arm for one ore type). I have an additional Robot Arm connected directly to the chest(1) which is filtered to pick up Solarite ores and drop them directly into a Fury Forge.

In my view, the main Robot Arm should be aware of the state(*) of the other 7 Robot Arms which are linked to the belt it drops items to, meaning that if 6 Robot Arms have a state of Running, and the last one has a state of Waiting, it knows not to pick up the ore of the respective Robot Arm until it goes back to the Running state.

The 7 Robot Arms should be aware of the state(*) of the smelters/forges they drop items to, meaning that if its smelter is full (has 9999 raw ores, regardless of how many smelted ones are in it), the Robot Arm goes into a Waiting state, waiting for the smelter to smelt some ores and free up some space for raw ores, and once it does the Robot Arm goes into the Running state, continuing to drop items into the smelter.

* End recipient: the bench/smelter the system leads to
* "Pending" state: a state of the Robot Arm which tells the Robot Arm to pause all activity (triggered when the Arm has an item and has no free space to drop it).
* "Running" state: a state of the Robot Arm which tells the Robot Arm to continue all activity (normal state).

Open Automation Inventory Suggested by: legend Upvoted: 07 May Comments: 0

Comments: 0