This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
en:iot-open:embeddedcommunicationprotocols2 [2023/11/19 11:20] – ekontoturbo | en:iot-open:embeddedcommunicationprotocols2 [2024/03/05 13:43] (current) – pczekalski | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Embedded | + | ====== Embedded |
+ | {{: | ||
IoT systems and related data flows are typically structured into three primary layers {{ref> | IoT systems and related data flows are typically structured into three primary layers {{ref> | ||
((Internet of Things: Architectures, | ((Internet of Things: Architectures, | ||
Line 30: | Line 30: | ||
=== Digital === | === Digital === | ||
Simple, true/false information can be processed via digital I/O. Most devices use positive logic, where, e.g. +5 V (TTL) or +3.3 V (the most popular, yet other voltage standards exist) presents a logical one, also referenced as //HIGH//. In contrast, 0V gives a logical zero, referenced as //LOW//. In real systems, this bounding is fuzzy. It brings some tolerance, simplifying, | Simple, true/false information can be processed via digital I/O. Most devices use positive logic, where, e.g. +5 V (TTL) or +3.3 V (the most popular, yet other voltage standards exist) presents a logical one, also referenced as //HIGH//. In contrast, 0V gives a logical zero, referenced as //LOW//. In real systems, this bounding is fuzzy. It brings some tolerance, simplifying, | ||
- | Alternating //HIGH// and //LOW// constitutes a square wave signal, usually used as a clock signal (when symmetrical) or used to control the power delivered to the external devices with means of so-called | + | Alternating //HIGH// and //LOW// constitutes a square wave signal, usually used as a clock signal (when symmetrical) or used to control the power delivered to the external devices with means of so-called PWM. |
=== Communication Protocols === | === Communication Protocols === | ||
Line 42: | Line 41: | ||
Asynchronous data transmission does not need any separate synchronization signal, but the transmitter and receiver must use the exact timings, and synchronization information must be included in the information transmitted. Examples of asynchronous interfaces implemented in microcontrollers are 1-Wire and UART (Universal Asynchronous Receiver Transmitter). | Asynchronous data transmission does not need any separate synchronization signal, but the transmitter and receiver must use the exact timings, and synchronization information must be included in the information transmitted. Examples of asynchronous interfaces implemented in microcontrollers are 1-Wire and UART (Universal Asynchronous Receiver Transmitter). | ||
- | | + | <WRAP excludefrompdf> |
- | * [[en: | + | Details for selected protocols are presented in the following chapters: |
- | * [[en: | + | * [[en: |
- | * [[en: | + | |
+ | * [[en: | ||
+ | * [[en: | ||
+ | * [[en: | ||
+ | </ | ||