ME System not recognizing patterns in interfaces

[mattp_12]

I have some interfaces and molecular assemblers and plenty of channels. I set up the assemblers and interfaces in a bunch of different ways but my system only wants to see one or 2 interfaces at a time. I can provide screenshots if necessary.

 

[immibis]

You should provide screenshots, it's necessary.

 

[mattp_12]

You should provide screenshots, it's necessary.

That's logic if I've ever heard of it.. Okay I'll have them in a bit.

 

[mattp_12]

You should provide screenshots, it's necessary.

Okay.. I changed the design up a bit, but I still have the same problem. Sort of. What is happening is that I have an ME controller with a dense cable coming off of it and that goes into the interfaces/molecular assemblers. The problem is that the dense cable refuses to detect more than 8 interfaces (I have 12). Also, there is nothing else connected to that one dense cable. The first picture shows the cable having 8 channels being used. The second one is the interface/assembler setup. That dense cable has glass cable going directly to the back of one interface and assembler (all of the assemblers are lit up). I have tried everything
Screenshots:

 

[Dentvar]

Do glas cables support more then 8 channels?! oO

Also you have to power all of the assamblers. Interfaces won´t give them power.

 

[Azzanine]

Do glas cables support more then 8 channels?! oO

Also you have to power all of the assamblers. Interfaces won´t give them power.

What do you mean by glass cables? Regular fluix and smart cables can only carry 8 channels. If you mean quartz fibre cable. They only transmit energy.

Also full block intefaces will transmit power but aparently the fixture versions don't. I don't think fixtures (terminals and the like) can connect to dense cables too.

Sent from my GT-I9100 using Tapatalk

 

[ScottulusMaximus]

There's power coming in thru the 5th assembler, why it's lit up but there's too many interfaces on that line, the white lights indicate no channels.

 

[desht]

There's power coming in thru the 5th assembler, why it's lit up but there's too many interfaces on that line, the white lights indicate no channels.

Yep. There are 8 interfaces with a blue light (they have a channel), and the remaining 4 have a white light (powered but no channel).

@mattp_12
The first screenshot shows one piece of dense cable out of the controller, then regular cable for the rest of the run. One lonely piece of dense cable isn't magically going to make the regular cable carry 32 channels

Either run dense cable all the way to all of your assemblers, or use a p2p tunnel to save on dense cable a bit (tunnel your 32 channels over a run of regular cable). But you can't have 12 interfaces on one run of regular cable.

 

[Ieldra]

@mattp_12 :
A simple change may fix this: put the interfaces on two different cable lines (i.e. unconnected to each other) and connect those to the dense cable from different sides. That way the channels combine to more than 8 only in the dense cable, and all interfaces should come online. You can prevent the two glass cable lines from connecting with each other at the two neighbouring interfaces by using a cable anchor.

 

[malicious_bloke]

Assemblers in that configuration are going to be using a channel each, you can see the 8 in the middle of the bottom pic are channelled but the one on the left end and three on the right end aren't.

It's MUCH more efficient to hang 5 of them off each ME interface, that way you only use one channel per interface and you can have 40 assemblers run from one line of glass cable.

 

[mattp_12]

Thanks for the help. For some reason I thought that glass cables supported more channels if it was connected to a dense cable.

Assemblers in that configuration are going to be using a channel each, you can see the 8 in the middle of the bottom pic are channelled but the one on the left end and three on the right end aren't.

It's MUCH more efficient to hang 5 of them off each ME interface, that way you only use one channel per interface and you can have 40 assemblers run from one line of glass cable.

I didn't do this because I already tried it and it didn't work (that's what this thread was about initially).

Yep. There are 8 interfaces with a blue light (they have a channel), and the remaining 4 have a white light (powered but no channel).

@mattp_12
The first screenshot shows one piece of dense cable out of the controller, then regular cable for the rest of the run. One lonely piece of dense cable isn't magically going to make the regular cable carry 32 channels

Either run dense cable all the way to all of your assemblers, or use a p2p tunnel to save on dense cable a bit (tunnel your 32 channels over a run of regular cable). But you can't have 12 interfaces on one run of regular cable.

I'll probably just either run dense cable all the way down, or use p2p. Probably p2p cause they are cleaner
Again, thanks for the help guys!
Haven't used AE2 in a few months so I kinda forgot some basics!

 

[desht]

I'll probably just either run dense cable all the way down, or use p2p. Probably p2p cause they are cleaner

I realise when I said "all the way" that could be a bit misleading. Run a trunk of dense cable or P2P tunnel from your controller down to your assemblers. From there you can have up to 32 interfaces connected on several separate spurs of regular cable.

Super-high-tech ASCII-vision diagram:

              |--------
              |
C==P-------P==|--------
              |
              |--------
              |
              |--------

Where = and | is dense cable, - is regular cables (I left out the interfaces), C is the controller and P is a P2P endpoint.

 

[Dentvar]

I realise when I said "all the way" that could be a bit misleading. Run a trunk of dense cable or P2P tunnel from your controller down to your assemblers. From there you can have up to 32 interfaces connected on several separate spurs of regular cable.

Super-high-tech ASCII-vision diagram:

              |--------
              |
C==P-------P==|--------
              |
              |--------
              |
              |--------

Where = is dense cable, - and | are regular cables (I left out the interfaces), C is the controller and P is a P2P endpoint.

You can also concect the P2P directly on the Controller.

CP-----------------------P=

 

[mattp_12]

Got it fixed after a LOT of misbehaving p2p tunnels Thanks guys. I did run the dense cable at first but I switched to p2p FYI.

 

[Bagman817]

Looks like you're up and running, but just wanted to chime in. You're aware that you can have more than one interface per assembler, are you not?

 

[mattp_12]

Looks like you're up and running, but just wanted to chime in. You're aware that you can have more than one interface per assembler, are you not?

Yes, I am aware.