#Easy LCR automation with AE2 subnets and fluid crafting

13 messages · Page 1 of 1 (latest)

magic radish
#

Main downside is you will require one LCR per circuit (although you can get away with only a 1 and 24 for quite a while).

This setup has a few notable advantages - using fluid AE means we don't need a bunch of whitelist filters, which kill scalability. Not having to deal with cells is also super helpful (letting us store much more fluid with less complexity) and this setup is easy to deploy, simple, as well as applicable to many other multiblocks. Because the LCR will empty the hatches/busses as soon as it starts a recipe, you won't have any issue with downtime unless you're running really fast recipes. Finally, this design allows up to 5 interfaces with patterns per subnet interface, allowing huge pattern capacity.

The basic idea is we're going to use an AE2 subnet to push recipes into the LCR hatches/busses, while ensuring we have proper blocking to prevent recipe conflicts when we're crafting many things at once.

The subnet should have a dual interface (block form) which uses storage busses to connect to the hatches/busses. Notable, you'll need an advanced blocking card on the dual interface, with blocking and loose mode enabled.
Your main net should have up to 5 dual interfaces (thin form) pointed at the subnet dual interface. These should have blocking enabled.
From here, make sure you add a circuit to the LCR controller (if needed), and then use the fluid AE recipes which you can put in the thin interfaces on your main network. Use either another subnet, conduits, or GT pipes to get the LCR output back into a dual interface.

Image 1 shows the meat-n-potatos of the setup. Red is your main network, pink is your subnet, and yellow is the quartz fiber connecting the two.

Image 2 shows how to configure the subnet (block form) dual interface.

image.png image.png
#

Easy LCR automation with AE2 subnets and fluid crafting

gentle mist
#

To add on this, for very fast LCRs and especially MCRs, using advanced blocking mode introduced an additional tick of delay between AE recipe inserts, which means you will need to wait for the next recipe check cycle (a couple seconds)

#

So to get around that you would want item and fluid p2p from the receiving interface to the inputs

little garden
#

Im not understanding the advantage of this setup over something like the greginator lcr guide. This one requires several channels from main vs just one for 1 dual interface?

magic radish
gentle mist
#

Yeah increasing pattern size works, until your MCR happily one ticks 2 million ammonia :)

magic radish
# little garden Im not understanding the advantage of this setup over something like the gregina...

Advantages are twofold:
Much higher pattern capacity, since you can get up to 5 dual interfaces (thin, main net) with patterns per one dual interface (block, subnet). If you do need to add another dual interface on the subnet, you don't need to add anything else (except main net thin interfaces to hold patterns), unlike the Greginator where I believe you'd need more P2P (or it might just not work?)
No P2P needed - only dual interfaces, requiring less different components and simpler setup

#

In the first image, you can surround every side of that dual interface (block form, subnet) with a dual interface (thin, main net) loaded up with patterns. That's a crap ton of pattern capacity, especially if you use the capacity upgrade cards.

#

To add on, you only need one channel per pattern interface, and a way to get stuff back into the network (which might require another channel)

little garden
#

ah i see, this doesnt REQUIRE several interfaces from main, it has CAPACITY for them. u can do it with just one

#

that does seem nice

magic radish
#

Oh yeah that's correct, you can scale from 1-5 easily by just adding another dual interface (no additional blocking cards required)