If communication to multiple slave subsystems is required, which protocol would be suitable?

Study for the Internet of Things (IOT102) Test. Access comprehensive flashcards and multiple choice questions, each with hints and explanations. Get prepared for your exam!

Multiple Choice

If communication to multiple slave subsystems is required, which protocol would be suitable?

Explanation:
The key idea here is using a bus that can connect many devices with simple wiring and addressing. I2C fits this perfectly: it uses just two wires (SDA for data, SCL for the clock) and allows every device on the bus to have a unique address. The master can talk to any chosen slave by addressing it, and data is transferred with ACK/NACK, so multiple subsystems can share the same wires without needing a separate line for each one. This makes it scalable for several slaves on the same board or in a single system. In contrast, point-to-point RS232 isn’t designed for many devices on one bus, USB is host-centric and relies on hubs and a host controller, and SPI needs a dedicated chip-select line for each slave, which becomes unwieldy as the number of slaves grows.

The key idea here is using a bus that can connect many devices with simple wiring and addressing. I2C fits this perfectly: it uses just two wires (SDA for data, SCL for the clock) and allows every device on the bus to have a unique address. The master can talk to any chosen slave by addressing it, and data is transferred with ACK/NACK, so multiple subsystems can share the same wires without needing a separate line for each one. This makes it scalable for several slaves on the same board or in a single system.

In contrast, point-to-point RS232 isn’t designed for many devices on one bus, USB is host-centric and relies on hubs and a host controller, and SPI needs a dedicated chip-select line for each slave, which becomes unwieldy as the number of slaves grows.

More practice questions