[0.14.21] Diff bhvr depending on # of circuitnet connections

[SupplyDepoo]

I was experimenting with a circuit-network-based lane 'splitter' (as an alternative to the popular underground belt method) and got some mildly pleasing results. It's based on the principle that lanes that are further back when side-loading get higher priority. The only major problem is that it requires manual priming before it can work.

Screen Shot 2017-01-23 at 02.04.09.png (1001.15 KiB) Viewed 1646 times

But when I attached a green wire to one of the belts and connected it to a power pole to observe the signal values, my mechanism suddenly broke. The belt starts letting the wrong item through randomly(?), eventually causing the whole lane to come to a halt (because I had the output loop back into the input). Like some kind of quantum mechanism, the magic only works when you're not looking!

Screen Shot 2017-01-23 at 02.05.03.png (883 KiB) Viewed 1646 times

Configuration of the upper left transport belt. The lower left belt is simply "read belt contents (hold)".

Screen Shot 2017-01-23 at 02.32.59.png (199.66 KiB) Viewed 1645 times

[Loewchen]

Post the save file. I don't see anything wrong.
What is the circuit logic supposed to do?

[Yoyobuae]

The belt is reading and feeding itself it's contents twice, due to duplicated connections. I'd say it's expected behavior, due to belts output looping back to it's input. Two connection == two loops.

[DaveMcW]

Yes, "enabled condition" adds the contents of red and green wires together. Just attach a red wire to the pole if you want to observe it.

If you really need red and green wires, you can double the limit (copper > 11).

[SupplyDepoo]

Ok. Thanks for the explanation.