Scribd
Upload
19 views6 pages

How Are Protocols Chosen in Embedded Systems

Protocols in embedded systems are chosen based on factors such as bandwidth, power consumption, range, fault tolerance, reliability, cost, and complexity. High-speed applications require protocols like Ethernet, while low-power devices benefit from BLE to prolong battery life. The selection process ensures reliable communication tailored to the specific needs of the application, balancing performance and resource constraints.

Uploaded by

MEMES INFINITY
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
19 views6 pages

How Are Protocols Chosen in Embedded Systems

Protocols in embedded systems are chosen based on factors such as bandwidth, power consumption, range, fault tolerance, reliability, cost, and complexity. High-speed applications require protocols like Ethernet, while low-power devices benefit from BLE to prolong battery life. The selection process ensures reliable communication tailored to the specific needs of the application, balancing performance and resource constraints.

Uploaded by

MEMES INFINITY
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 6

How are Protocols Chosen in

Embedded Systems?
1. Bandwidth and Data Rate:

The choice of protocol is influenced by the volume and speed of data transfer. High-speed applications like
video streaming may require protocols like Ethernet, while low-data-rate systems can use I2C or SPI
For instance, a system of smart security cameras transmitting video to a central computer for real-time
surveillance would use a low-bandwidth technology such as Bluetooth, where the system could not keep up
with the high data rate imposed by streaming video.
This would make it show video of very poor quality or lagging, or omit frames of video altogether and
therefore, unsuitable for use in such applications.
2. Power Consumption:

Energy efficiency has to be given top priority in most embedded systems, especially the ones being used in
mobile or battery-powered applications, because prolonging the lives of the batteries is already a key factor in
communications performance.
Why it's important Low-power devices' batteries may be rapidly depleted by power-hungry protocols like
Wi-Fi, rendering them unsuitable for prolonged use. To ensure a longer operational period, a smart
wearable health monitor, for instance, must adopt a low-power protocol like BLE to avoid frequent
recharging.
3. Range and Connectivity:

Some protocols, like Wi-Fi, offer huge ranges of communication that are appropriate for devices spread over
large areas, while others, such as Bluetooth, are designed for much shorter ranges.
Why it matters: A protocol that allows the needed range ensures reliable communication between components
of a system.
For example, in smart home automation, you may go for Zigbee because it is meant for low-power, short-
range communication, while LoRa should be used for wide area outdoor use cases like smart farms
projects.
4. Fault Tolerance and Reliability:

Some applications do need robust, reliable communications under extreme conditions, where the integrity of
data is crucial. CAN stands for Controller Area Network, protocols intended for high dependability; automotive
systems and any other noisy environments are perfect.
Why it matters, for example, the employment of a less reliable protocol in automotive safety systems can
cause system failures that may have an effect on applications associated with brake control or
deployment of airbags.
5. Cost and Complexity:

The complexity and cost of implementing the communication protocol have to be considered in most systems and
particularly resource-constrained devices. Complex protocols may necessitate a number of expensive software
and hardware layers.
For a given application to be of either lower size or lower cost, one could easily say that if the cost/complexity of
the implementation of a protocol becomes prohibitive, then such would not be feasible.
Such may include I2C or UART being more suitable instead of something over-engineered as Ethernet in case of
just a simple home automation where devices would simply be sending/receiving basic information.

You might also like