Why upper sieve reports pipe blocked each few seconds?

[Angpaur]

I cannot figure out why in below setup the upper sieve each few seconds reports pipe blocked and stops sieving for a moment.

I put a bridge right before the upper resrvoir to merge packets from both sieves. Packets are coming as 5kg so should be merged without a problem.

Can somebody see what is wrong here? Thanks

EDIT:

I found reason of the problem - pipe before the bridge was too short. There must be at least one pipe segment more.

I rebuild it like below and now all works fine:

Sorry to bother.

[Angpaur]

I was merging with a bridge as I described it. But if the bridge is right after sievie output then it will not merge properly.

[badgamer123]

You can also using one bridge only and another one directly put into storage

[Angpaur]

To fix the problem an additional segment of pipe is needed. Otherwise sieve will complain about pipe blocked if bridge is right after sieve output.

Now there is a pipe going vericaly from both sieves outputs and there is one bridge that merges packets from the sievies into 10kg packet and sends it rigth to the reservoir (second screenshot).

[Angpaur]

18 minutes ago, nakomaru said:

You were using a bridge, but not to merge. You are using a T section to merge in both cases.

A bridge to merge looks like this:

You don't understand how bridges work.

What you did will give total priority for lower sieve and upper will never be working at all.

[Angpaur]

Right, forgot that packets are 5kg, not 10kg. I thought that any amount of liquid in pipe, a bridge is attached to, will always get priority.

So you're right, it will work this way too. Thanks!