There are a few different types of subnets, you can create an unlimited amount and control what network sees what via storage buses and ME interfaces. There are a few things you must keep in mind when setting up any kind of Subnetwork.
Each network needs power, no power no network, even if you only have 3 devices, no network no power.
Having Bees in your pack and throwing them into your AE2 network can be a huge pain, this network will cover separating a certain mod away from your main ME network, this could work for anything but Bee’s is what I have used in the past.
Finding what bees you have in your system while trying to work on bees could be a real nightmare. If you only had bees in one network but wanted to access via AE but not have them clogging up your main network could be useful, also sending certain products to your main network (such as honey) could also be very useful when crafting.
My Green network has all my ore, materials and wood, iot was my first network and it has grown with me, as i grew my world i got into bees and then made a new network, I only want to keep bee related items within this network.
On the green network I need to add a storage bus, attached to my purple network but directly to the Green networks storage Bus is an interface. Now my green network can see everything on the purple network but the purple network can't see what's in the green network.
Next I need to configure the Storage bus, since I don't want to see all the bees on this network I want to turn off being able to withdraw bees. First we need to add a Fuzzy card, as these bees can sometimes have funny NBT data, the input/output mode should be set to insert only. This will ensure we can not see the bees in our main system.
AE2 is clever and will know that there are already drones, princess’s and combs already in the system, it will put similar items such as other combs into the purple system. These 2 systems are connected but putting any bee items (which we might already have) into the Green system will keep them in the Purple system.
We can use 5 faces of the ME Controller and we can only use 1 controller per network, this is wrong and right at the same time. If we have one controller we can use up to 4 faces and one face to provide channels to all the busses it would be one network.
We can separate this network into 2 networks, one for handling all of our machines and interfaces (Data Network) and one that just deals with providing channels for all of the P2P tunnels (Transport Network). This removes the limit to how many p2p tunnels you can have, having one face like the above for 32 p2p tunnels is mostly enough but if you require more then having a network for just p2p tunnels solves this issue:
The above example uses a separate controller for p2p tunnels, this is a separate network and is being powered by 1 energy acceptor in the middle separated with quartz fiber! Currently one face is being used for our Transport Network, we can use more faces if we need more tunnels.
The above network gives us access to 29 Faces, which is (29X32) 928 channels for machines. We also have 5 faces for busses (5x32) which gives us around 160 channels to work with. This principle can be expanded and made bigger, having a network just for transport gives us much more room to work with.
The above example used 1 data network with 2 colours, a Blue and Green. The blue has a dense cable on the bottom face of the floating single controller (where the Orange and red dense cables are coming out). This dense blue cable is full, all 32 channels have been taken up by p2p tunnels, these blue cables are separated via anchors.
The Green cables are going into 2 faces but are only using 16 channels for each face as they are on the inside of this 7x7 square.
Power is being fed through via the middle hole via Quartz Fiber cables. This whole thing (asa it stands) when maxed out can have up to 64 p2p tunnels, this is split by the orange and the red dense cables, this is a whopping (32X64) 2048 machines and up to 64 p2P tunnels.
You should not need to go bigger then this… but you can.
There are many ways you can save up disk storage space if you get creative or if you want to use Black Hole Units as your storage option for a lot of items. You can easily set up a chain of subnets and use a feature of AE which makes this possible.
A Storage Bus on an Interface allows for a one-way connection and allows one network to see all of the items of the other network. Below you can see that the blue network, which is our main network, is connected to an Interface through a Storage Bus. The blue network shares its power with the yellow network through the quartz fiber cable on the top. We are going to use the yellow network as our Black Hole Units network now:
The yellow network, because it has no Controller, can only have 8 channels. 6 channels are used for the Black Hole Units, 1 channel for the Interface and one channel for the Storage Bus (in the middle of the picture). This is infinitely expandable and only uses one channel of your main network:
Here is how this works: Let’s say the main system is our mother network, then the first subnet is our child subnet, which is the yellow one and so on. The red subnet on the picture can only see its own items. The black subnet can see the items in its network and because it has a Storage Bus on the Interface of the red subnet it can also see the items in the red subnet. Iterate this method until we reach the mother network, which is our main network, you will find out that the mother network can access every item of every child network, because the yellow subnet has a Storage Bus on the Interface of the black subnet and the black network has a Storage Bus on the Interface of the red subnet.
It is important that the Storage Bus on the main network has a higher priority than any other storage device on your network. Of course you can also combine this method with a subnet full of drives, which we will cover in the next section.
Original video from Soaryn: http://www.twitch.tv/soaryn/c/5151564
Reference and ideas from: https://www.youtube.com/watch?v=E5e1LiATnyc
The SSD was originally designed by Soaryn, a member of the ForgeCraft server. It became popular because it was the very first design which excessively used the mechanics of subnetworks on a public basis. In this section I will try my best explaining how it works and how to build it, and maybe, how to extend it.
The SSD is based on a network of subnetworks, which serves 2 functions: the main function is to store a lot of ME Drives and the other function is to easily manage these Drives. Here is how it goes:
Here you can see the base outline of how the SSD works. On the very far left you see the blue network, which simulates our main network. The blue network is the network which wants to access all items. It has a Storage Bus between its and the yellows network. The yellow network has an Interface on the blue network. And this also the pattern in the SSD: On the left the Storage Bus and on the right the Interface. The yellow network’s only function is to bridge the top row of networks and bottom row of networks into one channel. From here on (the black line) the repetitive part of the SSD begins. The top row and bottom row are completely identical. The black network always connects to the foregone network by an Interface and to the upcoming network by a Storage Bus. This could be repeated infinitely.
Let’s come to the pink network: it spreads to the side to access all Storage Cells on all Disk Drives. It also provides energy to all black subnetworks. This is already the jist of it. Now connect all Disk Drives and Storage Buses and your SSD is ready to roll. For that, place 3 Drives beginning from the first black cable and then on every second and connect Storage Buses on the top and bottom ME Drive:
The Terminal on the pink network allows to see the current situation of the Storage Cells. The SSD allows for 480 Storage Cells in each batch of 48 Drives:
Now, if you want or need to, you can expand the SSD by another batch of drives:
The SSD can be done a lot more compact if you don't need the Storage Cell management. This way you can also very easily see which Storage Cell is full and which one isn't: