| LonWorks as the Master
When we ask the question "What protocol is on the network?", we are really asking "who's the master?".
The first scenario is this: You have a LonWorks network with a number of LonWorks devices. You have a device that does not talk LonWorks, but you want to integrate it into your LonWorks network. In this instance, we say that LonWorks is the "protocol on the network".
There are many other scenarios that are variations on these themes. The main thing to ask is, "Who's in charge" of communications. That will be the "protocol on the network".
|
LonWorks as the Slave
Assuming you just read the column to the left, the slave would simply be on the opposite end.
LonWorks is a peer-to-peer protocol. However, we still usually have some notion of a primary controller with one or more subordinate controllers which we might refer to as "slaves".
If we have a device which was manufactured as a LonWorks node, but we want it to be a slave on a non-LonWorks network, this requires a gateway. When we want to put this LonWorks device on a non-LonWorks network, we answer "LonWorks" to the question "What protocol does the device talk?"
|
Is this you looking for
a network gateway?
You need to start with two pieces of information:
(1) What protocol is on the network?
(2) What protocol does the device talk?
Use the Gateway Chooser to guide you through the questions while you choose from available answers to arrive at a model number.
|
|
|
|
|