What ar the potential strategies to communicate 2 microcontrollers?

Communicate two microcontrollers

Two microcontrollers will exchange data victimisation either wired or wireless protocols.

Wired include:

Parallel port
I²C (Inter-Integrated Circuit)
SPI (Serial Peripheral Interface)
UART (Universal Asynchronous Receiver-Transmitter)
USB (Universal Serial Bus)
CAN (Controller Area Network), often used in automobiles
LIN (Local Interconnect Network), a replacement for CAN
Ethernet

Of these decisions, Ethernet is the fastest, with USB 3.0 next. However, most microcontrollers solely support USB a pair of.0 high-speed, if that. In addition to the wired protocols, there are many of wireless options:

Bluetooth SPP (Serial Port Profile), wireless version of UART
BLE (Bluetooth Low Energy)
Wi-Fi
ISM (Industrial, Scientific and Medical band radio)
Zigbee
ANT+
Cellular, such as GSM

Selecting Between I2C and SPI for Your Project

SPI

Serial to Peripheral Interface may well be a very-low-power four-wire serial communication interface designed for IC controllers and peripherals to talk with each other. The SPI bus may well be a full-duplex bus, that permits communication to flow to and from the master device at the same time at rates of up to 10Mbps. The high-speed operation of SPI typically limits it from being used to talk between components on separate PCBs because of the increase in capacitance that longer-distance communication adds to

the signal lines. PCB capacitance might limit the length of SPI communication lines.

While SPI is a longtime protocol, it’s not a political candidate commonplace. SPI offers many differences and customizations that lead to compatibility problems.

SPI implementations should be checked between master controllers and slave peripherals to confirm that the mix won’t have any surprising communication issues that may have an effect on the event of a product.

I2C

I2C is a political candidate commonplace serial communication protocol that exclusively wants a pair of signal lines that were designed for communication between chips on a PCB.

I2C was originally designed for 100kbps communication but faster information transmission modes ar developed over the years to achieve speeds of up to 3.4Mbps.

The I2C protocol has been established as a political candidate commonplace, that gives smart|permanently} compatibility among I2C implementations and sensible backward compatibility.

Selecting Between I2C and SPI

Select one from I2C & SPI, the tow main serial communication protocols, needs an honest understanding of the benefits and limitations of I2C, SPI, and your application. every communication protocol will have distinct blessings which may tend to differentiate itself as a result of it applies to your application.

The key distinctions between I2C and SPI are:

I2C wants exclusively a pair of wires, whereas SPI needs 3 or four.
I2C attracts a lot of power than SPI.
I2C supports multiple devices on an identical bus whereas not any opt for signal lines through in-communication device addressing whereas SPI wants any signal lines to manage multiple devices on a similar bus.
I2C ensures that information sent is received by the slave device whereas SPI does not verify that information is received properly.
I2C is also secured up by one device that fails to unleash the communication bus.

SPI willnot transmit off the PCB whereas I2C can, albeit at low knowledge transmission speeds.
SPI exclusively supports one master device on the bus whereas I2C supports multiple master devices.
I2C may be a smaller quantity susceptible to noise than SPI.
SPI can exclusively travel short distances and sometimes off of the PCB whereas .
I2C can transmit information over superabundant larger distances, though at low knowledge rates.
The lack of a correct commonplace has resulted in several variations of the SPI protocol, variations that are for the most part avoided with the I2C protocol.

If you want extra News, Check out Our Blog Section www.eduengteam.com