Yes, the changeable address is a neat feature! Finally, I could make a shorter video, there was not too much to explain here.

You are welcome! I am glad that I could help.

Yes, it is a very nice circuit! As I mentioned in the video, I will check it with two AS5600 circuits. Since I will need to read them fast, it will be a great test for this circuit.

From TI datasheet, should be plenty fast and not noticeable. In standard mode supports a max I2C clock frequency of 100kHz and in Fast Mode goes all the way up to 400kHz. I don't know the downsides of using the Fast mode to be honest.

@@CuriousScientist Hi friend ... Have you uploaded the video with the mux and the AS5600 yet?

Hi! Yeah, about a year ago... Maybe you should subscribe to the channel. :)

@@CuriousScientist claro que si estoy suscrito... muy buen contenido!!!

Cheers!

You're welcome!

I don't know what the hell "tuturai" is, but you might find this video interesting: kzfaq.info/get/bejne/f8Bgedyasr-4ZGw.html

You can use up to 8 i2c devices with this multiplexer.

Hi and thanks! Why would you multiplex the MCP23017? You can create 8 different addresses using its A0, A1, A2 pins. Thus, you can chain up 8 of these chips using the same i2c bus. But if you need even more I/O expanders, then yes, you can use this i2c MUX. But as long as you are below 8 chips, I recommend using the MCP23017's address pins. It is much simpler.

@@CuriousScientist Hello, thank you very much for your feedback. I wanted to control 2 MCP23017 with an arduino board using I2C but since the MCP23017 devices have the same address, I planed to rely upon the TCA9548A multiplexer which can control devices with the same address. -On one hand, the TCA9548A multiplexer would be connected to the arduino board -On the other hand, the TCA9548A multiplexer would be connected to the 2 MCP23017 devices I prefer your solution of using the pins A0, A1, A2 of the MCP23017. Just to be sure : Does it mean I have to connect the pin A0, A1 and A2 of each of my MCP23017 to the pins of my arduino (for example the pin 4,5 and 6 for the first MCP23017 and 7,c8 and 9 for the second ) and send on pin A0 to A2 a byte? Do you have a link explaining how to do so? Thank you in advance for your precious support 😁. Cordially 😊

Hi! They do not have the same address unless you give them the same address on purpose (or leave their address pins untouched). There are three pins A0, A1 and A2 on the MCP23017 chip and depending on how you configure these pins (HIGH or LOW), the address will be different. Read the datasheet of the chip about how to configure their address if you are unsure. Just to clarify. You do not need to connect the A0, A1 and A2 pins anywhere on the Arduino. Depending on what board you use for the MCP23017, there will be 3 jumper pins, or DIP switches, or solder tabs. You have to play with those, the Arduino does not have to be involved with the addressing. I recommend you learn this first because working with an i2c multiplexer is much more complicated.

@@CuriousScientist Hello, thank you very much for your feedback 😁 and your explanation. Ok, I'll check how to set up the address for the 2 MCP23017. I'll come back to you if I have other questions. Have a nice weekend, 😁. Cordially 😊

Hi! I have never worked with the above mentioned sensors, but you just have to switch between the different channels on the MUX board and then reach the different sensors.

Well, "doesn't work" is a very vague description, so I can't figure it out either.

Yes, sorry, probably it's a problem with SDA SCL , on the due I don't use A4 or A5 . I tried on A4 and A5 to make sure but nothing works...

Due uses pin 20 (SDA), and 21 (SCL), you must use those pins.

@@CuriousScientist yes , i did

Well, that's the problem that you want to update them individually while they hold the same address. The video shows how to solve that issue with the multiplexer.

@@CuriousScientist You said there is a conflict, there is no conflict. There is only a conflict when there are two devices (or more) at the same address, the same functionality and the MCU asking for data or at a totally different functionality (different devices). The last one with different devices on the same address and asking for data, ruin your I2C communiction completely. You can also make a sniffer, a listener, to any address you want, doesn't matter.

It depends on how you want to interpret the word "conflict". I am not a native English speaker, so let me have a few mistakes. I provided a useful solution for an issue for free, so let's not get stuck with some "misuse" of words. 😉

English please.