Automating machines that require multiple inputs (assembly tables, GT assembling machine, etc)

[dieselfuelonly]

I've been trying to figure out a way to automate machines that require multiple material inputs, and that are also used in several "stages" of an items crafting recipe. I'm using AE to handle the movement and crafting of items.

Here is an example - I have a BC assembly table that is used for making various types of chipsets, etc. During some crafting processes, or also in the case of multiple (unrelated) crafting requests) the tables can get multiple materials placed inside them from an ME interface, and get confused on what they are supposed to be making and hang up. The "do not push while crafting" setting of the ME interface doesn't really seem to help in this situation.

Another is using the Gregtech Assembly Machine, say, for example, to make circuits.

The machine is used in several steps of making the circuits, first to make the basic circuit board with iron and electrum, and then a second time with copper cable and the basic circuit board to make the actual circuit itself.

Oftentimes due to the way that AE crafting requests works, the machine may end up with one material from 2 different steps in each of its two slots, bringing everything to a halt.

Someone recommended using Steves Factory Manager as a way to solve this, however I'm unable to figure out a way to build a list of commands to prevent items from multiple recipes from getting pushed in at the same time.

I've tried different setups with itemducts, routers, steves factory manager, etc., just had no luck. Anyone else got some creative solutions to automating a single machine that is used in several steps of a crafting process?

 

[ratchet freak]

easiest/most straightforward is to use a machine per crafting recipe

after this you can also find which recipes don't interfere with each other and group those

 

[dieselfuelonly]

Man thats going to be a ton of work for all the GT recipes. I actually got it to WORK with steves factory manager... but the amount of time it took to set up reach recipe was just too much. I would be sitting there spending hours and hours with a factory manager trying to set up all the recipes for it.

Here is how I had it set up:

ME Interface > Chest > Factory Manager > Machine

Factory Manager Config:
Trigger
Input from chest set to filter blacklist, left empty
Condition set to filter whitelist the recipe items + the actual number of items required in the recipe
Output set to filter whitelist the recipe items + the actual number of items required in the recipe, outputs to assembly machine

Just way too tedious to set up for each recipe... but it did work.

Any other ideas?

 

[ratchet freak]

Man thats going to be a ton of work for all the GT recipes.

that's why you set up autocrafting just set up the crucial recipes first and then build out as you need to

 

[epidemia78]

Hmm, Ive set up my IC2 plate and wire machines as part of my autocrafting setup and I havent run into this problem yet. (although i think my MAC is between chunk borders because it forgets the wire recipe sometimes unless I kick it) Those machines only have one input slot unlike the assembly table. Why dont you try filling all of the extra slots with something not used in your autocrafting recipes? just leave empty however many slots is needed for the operation? Dunno if that will work.

 

[malicious_bloke]

Re: the assembly table, I found it easier to just turn off the redstone chipset in the active recipes panel (the one on the right).

Basically it uses a single redstone dust, so if you have it active when you're trying to make any other chipset involving redstone it'll just pile through tons of those and leave all your other ingredients sitting in the inventory.

That's the only problem I ever had with it though.

If you want a machine that's really annoying to automate due to input slots, try the thermionic fabricator from forestry. *erk*

 

[rhn]

I would also suggest using several BC assembly tables and then with the proper tactic spreading the recipes among them. Remember that the same lasers can service several tables(not at the same time, but still). So you can for example put the recipe for the redstone chipset in the same table as all the facade recipes you use.

 

[belgabor]

I would also suggest using several BC assembly tables and then with the proper tactic spreading the recipes among them. Remember that the same lasers can service several tables(not at the same time, but still). So you can for example put the recipe for the redstone chipset in the same table as all the facade recipes you use.

This. In fact two or three should be enough, I usually build four for symmetry reasons =)
I haven't bothered to set it up completely in my current world, but iirc in my previous one three was what I actually needed for automated BC + AE needs, I used the fourth one for manual access (mostly facades and QuarryPlus stuff).

 

[namiasdf]

Multiple assembly table, covered by redundant lasers.

One handles chipsets and autarchic gates.

One handles gates and wires.