How to Link a Wireless Terminal in Applied Energistics 2 (AE2)
Applied Energistics 2 is one of the most powerful storage and automation mods available for Minecraft, but its network infrastructure can feel intimidating at first. The Wireless Terminal is one of its most useful tools — it lets you access your ME (Matter Energy) storage system from anywhere in your base without physically standing next to a terminal. Getting it linked correctly, however, requires a few specific steps that trip up a lot of players.
Here's exactly how it works. 🔧
What Is the AE2 Wireless Terminal?
The Wireless Terminal is an item that mirrors the functionality of a standard ME Terminal. Once linked and charged, you can open your full ME storage interface from a distance — no cables, no standing at a fixed block.
To make this work, the terminal doesn't communicate directly with your ME system through the air. Instead, it communicates through a dedicated block called the Wireless Access Point (WAP), which must be connected to your ME network. The terminal then acts as a remote client for whatever WAP it's linked to.
This distinction matters: the terminal is linked to a specific WAP, not to the network as a whole.
What You Need Before Linking
Before you can link a Wireless Terminal, you need to have a few things in place:
- A functioning ME Network with at least one ME Controller or a basic drive setup
- A crafted Wireless Access Point placed and connected to the network
- A crafted Wireless Terminal item in your inventory
- A Charger (to power the terminal)
- A Memory Card (used as the linking medium in most AE2 versions)
The Charger is important: the Wireless Terminal runs on AE2's internal energy system, and an uncharged terminal simply won't work even if it's linked correctly.
Step-by-Step: Linking the Wireless Terminal to Your Network
Step 1 — Place and Connect the Wireless Access Point
Place your Wireless Access Point somewhere on your ME network. It needs to be connected via ME Cable (or directly to the controller). Once connected, it should display a colored status light indicating it's receiving power and network connection.
The WAP has a configurable range. By default it covers a limited radius, but you can expand this by inserting Wireless Boosters into the WAP's upgrade slots — each booster increases the effective range at the cost of more power consumption.
Step 2 — Use the Memory Card to Bind the Link
Right-click the Wireless Access Point while holding a Memory Card to store the WAP's network address onto the card.
Then, right-click your Wireless Terminal with that same Memory Card. This transfers the binding data from the card to the terminal, associating the terminal with that specific access point.
You should see a confirmation message in chat or the item's tooltip will update to reflect the linked status.
Step 3 — Charge the Terminal
Place the linked Wireless Terminal into a Charger connected to your ME network (or any compatible power source). Wait for it to reach full charge before using it.
An uncharged terminal will open but immediately display a "not connected" or low-power warning. Keeping the terminal charged is an ongoing maintenance task — it drains power while open and while idle in some configurations.
Step 4 — Test Within Range
Hold the Wireless Terminal in your hand and right-click to open it. If you're within range of the linked WAP, you'll see your full ME storage inventory just as you would at a wired terminal.
If it doesn't connect, check:
- That the WAP is still receiving network power
- That you're within the WAP's configured range
- That the terminal is charged
- That the ME network itself is healthy (no missing channels, no controller issues)
Variables That Affect How Well This Works 📡
Not every AE2 setup behaves the same way. Several factors shape the experience:
| Variable | Effect |
|---|---|
| AE2 Version | Older vs. newer versions have different linking mechanics (some skip Memory Cards) |
| Modpack | Some packs swap AE2 for AE2-based forks like Refined Storage or AE2 Extended Life, which have different UIs |
| Power setup | Insufficient energy to the WAP causes dropped connections mid-use |
| Range boosters | Without boosters, the default range covers a small area — large bases need multiple WAPs |
| Channel usage | In complex networks, the WAP consumes channels; networks near their channel limit may behave unpredictably |
| Minecraft version | AE2 behavior varies between 1.12, 1.16, 1.18, and 1.20 builds |
Multiple Access Points, Multiple Terminals
You're not limited to one WAP. Many players set up multiple Wireless Access Points across their base — one in a farm area, one near a smelting array, one in a resource processing room — each linked to a separate terminal or the same terminal depending on how you configure it.
The Memory Card method makes it straightforward to rebind a terminal to a different WAP as your base layout evolves.
When Things Don't Link Correctly
The most common failure points:
- Skipping the Memory Card step — you can't just hold the terminal near a WAP; the binding must be done explicitly
- WAP not on the network — placing it without connecting it to cable or a controller means it has no network address to bind to
- Wrong mod version assumptions — if you've watched a tutorial from a different Minecraft version, the exact steps may differ slightly
- Energy system misconfigured — AE2 needs a continuous power source; if energy stops, so does the WAP's broadcast
How straightforward or complex your specific linking process turns out to be depends heavily on which version of AE2 you're running, how your network is architected, and what other mods are interacting with your energy and storage systems.