Unable to communicate with controller - Multiple ME Systems

  • Please make sure you are posting in the correct place. Server ads go here and modpack bugs go here
  • The FTB Forum is now read-only, and is here as an archive. To participate in our community discussions, please join our Discord! https://ftb.team/discord

infantrash

New Member
Jul 29, 2019
2
0
0
i have a big problem with my ME-Systems.

I joined a private server of some friends (FTB-Unleashed 1.1.7). They first installed their ME-Systems with controller, terminals, crafting tables and so on...

Now i crafted all that stuff too and set up my system. The problem i have is, that my system randomly stops working. All ME machines tell "Unable to communicate with controller". You can see then, that the ME-cable is not connected to the controller anymore. The only solution is to put the controller back to my inventory with the wrench and then set up again.

We checked/tried a lot of stuff:

  • Different colored ME-cable in my setup
  • Not a power problem
  • Place my controller in their house and build a long network cable (chunk loading problem)
Their system works perfectly but mine fails constantly, sometimes it works for 15minutes, sometimes 2 hours...

Help please :)

EDIT:

i figured it out, it was a power problem! :(

i was powering my controller with an energy tesseract. so the chain looked like this:

array of ultimate solar panels -> mfsu -> sending energy tesseract -> receiving energy tesseract -> powerconverters -> me controller.

the mfsu on the sending side was always fully charged, even at night, no ups and downs there.
placing a redstone energy cell between the receiving tesseract and the controller solved the problem.
 
Last edited:

ThatOneSlowking

New Member
Jul 29, 2019
3,520
0
0
Have you tried using 2 controllers in the same network?(quantum bridges are the same network)that would cause this. Other than that, it is a very strange problem
 

budge

New Member
Jul 29, 2019
273
0
0
Yeah, I've had some of these issues in AE dev version 14, and previously in my 1.5.2 pack with version 13. Make sure every network-aware block is in a loaded chunk. That's the only thing that fixed my network.

And if you ever find yourself using the (deprecated) dev14, p2p tunnels *consistently* cause the controller to reset when the player leaves the area, chunkloaded or not. Something to keep in mind until AE2.