Both sides previous revisionPrevious revisionNext revision | Previous revision |
en:iot-open:embeddedcommunicationprotocols2:1wire [2023/11/21 20:52] – pczekalski | en:iot-open:embeddedcommunicationprotocols2:1wire [2024/05/27 11:18] (current) – ktokarz |
---|
====== 1-Wire ====== | ====== 1-Wire ====== |
| {{:en:iot-open:czapka_b.png?50| General audience classification icon }}{{:en:iot-open:czapka_e.png?50| General audience classification icon }}\\ |
1-Wire is a master-slave communication asynchronous bus interface designed formerly by Dallas Semiconductor Corp((https://www.maximintegrated.com/en/products/digital/one-wire.html)). It can transmit data at long distances at the cost of transmission speed. The typical data speed of the 1-Wire interface is about 16.3 kbit/s, and the maximum length is approx. 300m. Name 1-Wire comes from the feature that the data line can directly power elements connected to the bus. A network chain of 1-Wire devices consists of one master device and many slave devices (figure {{ref>1wire0}}). Such a chain is called a MicroLAN. 1-Wire devices may be a part of a product's circuit board, a single component device such as a temperature probe, or a remote device for monitoring purposes. | 1-Wire is a master-slave communication asynchronous bus interface designed formerly by Dallas Semiconductor Corp((https://www.maximintegrated.com/en/products/digital/one-wire.html)). It can transmit data at long distances at the cost of transmission speed. The typical data speed of the 1-Wire interface is about 16.3 kbit/s, and the maximum length is approx. 300m. Name 1-Wire comes from the feature that the data line can directly power elements connected to the bus. A network chain of 1-Wire devices consists of one master device and many slave devices (figure {{ref>1wire0}}). Such a chain is called a MicroLAN. 1-Wire devices may be a part of a product's circuit board, a single component device such as a temperature probe, or a remote device for monitoring purposes. |
| |
| |
<figure 1wire0> | <figure 1wire0> |
{{ en:iot-open:embeddedcommunicationprotocols2:1wire_bus.png?nolink&450 | 1-Wire bus connection}} | {{ en:iot-open:embeddedcommunicationprotocols2:1wire_bus.png?450 | 1-Wire bus connection}} |
<caption>1-Wire bus connection</caption> | <caption>1-Wire bus connection</caption> |
</figure> | </figure> |
| |
<figure 1wire1> | <figure 1wire1> |
{{ en:iot-open:embeddedcommunicationprotocols2:1wire_reset.png?nolink&450 | 1-Wire reset timings}} | {{ en:iot-open:embeddedcommunicationprotocols2:1wire_reset.png?450 | 1-Wire reset timings}} |
<caption>1-Wire reset timings</caption> | <caption>1-Wire reset timings</caption> |
</figure> | </figure> |
| |
<figure 1wire2> | <figure 1wire2> |
{{ en:iot-open:embeddedcommunicationprotocols2:1wire_read.png?nolink&450 | 1-Wire read timings}} | {{ en:iot-open:embeddedcommunicationprotocols2:1wire_read.png?450 | 1-Wire read timings}} |
<caption>1-Wire read timings</caption> | <caption>1-Wire read timings</caption> |
</figure> | </figure> |
| |
<figure 1wire3> | <figure 1wire3> |
{{ en:iot-open:embeddedcommunicationprotocols2:1wire_write.png?nolink&450 | 1-Wire write timings}} | {{ en:iot-open:embeddedcommunicationprotocols2:1wire_write.png?450 | 1-Wire write timings}} |
<caption>1-Wire write timings</caption> | <caption>1-Wire write timings</caption> |
</figure> | </figure> |