1-Wire1-wire is a wiring protocol and series of devices designed and manufactured by Dallas Semiconductor, Inc.
The bus is a low-power low-speed low-connector scheme where the data line can also provide power.
Each device is uniquely and unalterably numbered during manufacture. There are a wide variety of devices,
including memory, sensors (humidity, temperature, voltage, contact, current), switches, timers and data
loggers. More complex devices (like thermocouple sensors) can be built with these basic devices. There
are also 1-wire devices that have encryption included.
The 1-wire scheme uses a single busmaster and multiple slaves on the same wire. The bus master initiates
all communication. The slaves can be individually discovered and addressed using their unique ID.
Bus masters come in a variety of configurations including serial, parallel, i2c, network or USB adapters.
OWFSdesignOWFS is a suite of programs that designed to make the 1-wire bus and its devices easily accessible. The
underlying principle is to create a virtual filesystem, with the unique ID being the directory, and the
individual properties of the device are represented as simple files that can be read and written.
Details of the individual slave or master design are hidden behind a consistent interface. The goal is to
provide an easy set of tools for a software designer to create monitoring or control applications. There
are some performance enhancements in the implementation, including data caching, parallel access to bus
masters, and aggregation of device communication. Still the fundamental goal has been ease of use,
flexibility and correctness rather than speed.
owserverowserver(1) is the backend component of the OWFS 1-wire bus control system. owserver(1) arbitrates
access to the bus from multiple client processes. The physical bus is usually connected to a serial or
USB port, and other processes connect to owserver(1) over network sockets (tcp port).
Frontend clients include a filesystem representation: owfs(1) , and a webserver: owhttpd(1). Direct
language bindings are also available, e.g: owperl(3).
There are also many light-weight clients that can only talk to owserver(1) and not to the 1-Wire bus
directly. They include shell and multiple language modules (perl, Visual Basic, python,...)
owserverprotocol
All the owserver(1) clients use the owserverprotocol for communication. The owserverprotocol is a well
documented tcp/ip client/server protocol. Assigned the "well known port" default of 4304.
owtapowtap(1) is interposed between owserver(1) and clients, to display and help resolve communication
problems. Network communication is forwarded in both directions, but a visual display is also created,
with statistics and "drill-down" of individual packets.
Install Now
PNG Icons
