Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
en:iot-open:embeddedcommunicationprotocols2 [2023/11/19 11:20] ekontoturboen:iot-open:embeddedcommunicationprotocols2 [2024/03/05 13:43] (current) pczekalski
Line 1: Line 1:
-====== Embedded communication ====== +====== Embedded Communication ====== 
 +{{:en:iot-open:czapka_p.png?50| General audience classification icon }}{{:en:iot-open:czapka_b.png?50| General audience classification icon }}{{:en:iot-open:czapka_m.png?50| General audience classification icon }}{{:en:iot-open:czapka_e.png?50| General audience classification icon }}\\
 IoT systems and related data flows are typically structured into three primary layers {{ref>iotstack3}}, eventually into five {{ref>iotstack5}}, which is less popular and mainly used in advanced research  IoT systems and related data flows are typically structured into three primary layers {{ref>iotstack3}}, eventually into five {{ref>iotstack5}}, which is less popular and mainly used in advanced research 
 ((Internet of Things: Architectures, Protocols, and Applications; P. S. Smruti, R. Sarangi. https://doi.org/10.1155/2017/9324035)) ((Internet of Things: Architectures, Protocols, and Applications; P. S. Smruti, R. Sarangi. https://doi.org/10.1155/2017/9324035))
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, e.g. communication from 3.3 V output to 5 V input, without a need for the conversion (note, the reverse conversion is usually not so straightforward, as 3.3 V inputs driven by the 5V output may burn quickly). A sample sensor providing binary data is a button (On/Off).\\ 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, e.g. communication from 3.3 V output to 5 V input, without a need for the conversion (note, the reverse conversion is usually not so straightforward, as 3.3 V inputs driven by the 5V output may burn quickly). A sample sensor providing binary data is a button (On/Off).\\
-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 [[en:iot-open:embeddedcommunicationprotocols2:pwm|PWM]]. +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). 
  
-  * [[en:iot-open:embeddedcommunicationprotocols2:spi|SPI]], +<WRAP excludefrompdf> 
-  * [[en:iot-open:embeddedcommunicationprotocols2:twi|I2C]], +Details for selected protocols are presented in the following chapters: 
-  * [[en:iot-open:embeddedcommunicationprotocols2:1wire|1-Wire]], +  * [[en:iot-open:embeddedcommunicationprotocols2:PWM]], 
-  * [[en:iot-open:embeddedcommunicationprotocols2:uart|UART]]. +  * [[en:iot-open:embeddedcommunicationprotocols2:spi]], 
 +  * [[en:iot-open:embeddedcommunicationprotocols2:twi]], 
 +  * [[en:iot-open:embeddedcommunicationprotocols2:1wire]], 
 +  * [[en:iot-open:embeddedcommunicationprotocols2:uart]]. 
 +</WRAP>
  
en/iot-open/embeddedcommunicationprotocols2.1700392839.txt.gz · Last modified: 2023/11/19 11:20 by ekontoturbo
CC Attribution-Share Alike 4.0 International
www.chimeric.de Valid CSS Driven by DokuWiki do yourself a favour and use a real browser - get firefox!! Recent changes RSS feed Valid XHTML 1.0