Very strange issue with the 8Way16 Mux - help needed!

[Reloadinger]

Hey guys!

I've looked through a lot of threads, but I did not find anyone else who had my problem.
So I've worked on my 8Way16 Mux for at least 2 days, and the error is hard to describe:
It is an issue with the And16, though I did that gate before and the .out file matched with the .cmp file.
But when I use it for my 8Way16Mux, it shows some strange behaviour.

If I connect one pin (input a) of the And16-Gate with, lets say, a number, and the other pin (input b) with
"1111111111111111", then the output of the And16-Gate should be the number I put in on input a.
Instead, the output is "0".

Little description how my Mux works:
I took two of the 4Way16 Muxes I made before, and I used the two least bits of the selection-input
for those as selection-inputs. The MSB of the selection input chooses which one of the two 4Way16Mux will be used.
The first is for the inputs A,B,C and D, and the second for E,F,G and H.

I put some pictures that explain my situation better, I hope you can understand what my problem is and help me. It really bothers me that I cannot finish the basic gates and I do not want to use the ones in the BuiltIn - folder. hdl_code.pnghdl_code_and16.pnghw_simulator.png

[cadet1620]

It looks like the connection to b[2] is missing from both And16s.  The disconnected input will default to false, and this causes and2 = 4 to become or2 = 0 when Anded with 1111 1111 1111 1011.

FWIW, you can replace the Not, And16s and Or16 with one chip that you have already made, and then you won't need all the []s.

--Mark

[Reloadinger]

Thank you very very much!
I think the most hard-to-find problems are also the most stupid ones.