Haywire: Glossary
Terms and Concepts in Haywire
Since the abstractions used in Haywire are different from
those used in classical 1-Wire API, it would make a perfect
sense to spell them out, to avoid ambiguity.
Term |
Meaning |
Network |
Set of all adapters, wires and devices connected
to a single host.
|
Bus |
All the wires and devices connected to a single
adapter on a single host.
|
Branch |
Set of devices on a bus that can be accessed at
the same time (when a corresponding MicroLAN
coupler is activated), minus those that can be
accessed when all MicroLAN couplers are closed.
|
Trunk |
Special kind of a branch - set of all
the devices on a bus that can be accessed when
all MicroLAN couplers are closed.
|
Path |
A unique way to describe how a particular device
can be accessed. A path is a sequence that
starts with the adapter identifier, followed by
zero or more MicroLAN coupler addresses, and
ends with the device address.
|
Adapter Identifier |
A unique way to describe a particular physical
adapter. Some adapters come with ID chips
embedded - if that is the case, then the chip
address will be used as an adapter identifier.
If the ID chip is not present, a volatile unique
identifier will be assigned to the adapter for
the lifetime of the controlling application.
|
Device Container |
A logical representation of a physical
1-Wire® device.
The device container is the only non-volatile
entity in Haywire. Once instantiated, device
container survives device departure and arrival,
and can be referenced and used even when the
device itself is not present.
|
Composite Device |
A device container which represents
more than one physical 1-Wire® device
(example: pressure sensor).
|
Multipart Device |
A physical device which represents more than one
device container (example: humidity
sensor, which is also a temperature sensor).
|