Re: Re:Positional/physical addressing

Liste des GroupesRevenir à e design 
Sujet : Re: Re:Positional/physical addressing
De : blockedofcourse (at) *nospam* foo.invalid (Don Y)
Groupes : sci.electronics.design
Date : 24. Jun 2025, 18:05:06
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <103elsj$24a8c$2@dont-email.me>
References : 1 2 3
User-Agent : Mozilla Thunderbird
On 6/24/2025 9:49 AM, Don Y wrote:
On 6/24/2025 9:18 AM, Martin Rid wrote:
CAN network?
 Each CAN node either needs a unique address to which messages can be
directed;  *or*, to KNOW to listen for particular BROADCAST messages.
 So, you either send a message to node 5 to do something
OR, you send a message about that something and expect
that node to know that *it* should process that message.
 If all of the nodes are *identical* (hardware and software),
there is nothing to distinguish one device from any other.
By way of example, in the 70's, we would do "poor man's networking"
by daisy-chaining IDENTICAL devices with serial ports:
HOST---->[]----->[]---->[]----->[]
(each set of brackets represents a device with its serial input
on the left side and output on the right)
If I pass a message (from the host) of the form "1xxxxxx", the
first device receives the message, notices that it begins with
a '1' and assumes it is meant for it; the message is absorbed
by that device.
If the message is of the form "2xxxxxxx", the first device receives
the message, notes that it does NOT begin with a '1' and, therefore,
is not intended for it's use.  It "decrements" the first character
('2') and passes along the message payload ("xxxxxx") with this
new "address" -- "1xxxxxxxx".
The SECOND device sees this message, notes that the first character
is a '1' and assumes it is meant for it; the message is absorbed by
this SECOND device.
[There are other equivalent schemes]
The point is, ALL of the devices are identical, run identical
software, etc.  Their physical position in the chain determines
their "address".
Note that the HOST can begin sending the next message immediately;
devices have stored (temporary) copies of earlier messages so the
communication link need not be left idle while earlier messages
percolate down the chain.
The problem with this approach is that any device failure renders
inoperative everything downstream!
[This approach also introduces latency proportional to the
"distance" (number of hops) from the HOST.  But, there are
ways around that.]

Date Sujet#  Auteur
24 Jun 25 * Positional/physical addressing25Don Y
24 Jun 25 +* Re: Positional/physical addressing8Martin Rid
24 Jun 25 i`* Re: Positional/physical addressing7Don Y
24 Jun 25 i `* Re: Positional/physical addressing6Don Y
24 Jun19:18 i  +* Re: Positional/physical addressing4Jeroen Belleman
25 Jun18:30 i  i`* Re: Positional/physical addressing3Ian
25 Jun18:43 i  i +- Re: Positional/physical addressing1Don Y
25 Jun22:29 i  i `- Re: Positional/physical addressing1Jeroen Belleman
24 Jun22:36 i  `- Re: Positional/physical addressing1Don Y
25 Jun09:52 +* Re: Positional/physical addressing11Liz Tuddenham
25 Jun10:14 i`* Re: Positional/physical addressing10Don Y
25 Jun11:14 i `* Re: Positional/physical addressing9Liz Tuddenham
25 Jun18:04 i  `* Re: Positional/physical addressing8Don Y
26 Jun09:59 i   +* Re: Positional/physical addressing4Liz Tuddenham
26 Jun10:46 i   i`* Re: Positional/physical addressing3Don Y
26 Jun17:53 i   i `* Re: Positional/physical addressing2Liz Tuddenham
26 Jun21:48 i   i  `- Re: Positional/physical addressing1Don Y
26 Jun20:58 i   +* Re: Positional/physical addressing2bitrex
26 Jun21:50 i   i`- Re: Positional/physical addressing1Don Y
26 Jun21:00 i   `- Re: Positional/physical addressing1bitrex
25 Jun18:40 +* Re: Positional/physical addressing4Ian
25 Jun20:41 i`* Re: Positional/physical addressing3Don Y
25 Jun21:35 i `* Re: Positional/physical addressing2Dennis
25 Jun22:53 i  `- Re: Positional/physical addressing1Don Y
25 Jun19:25 `- Re: Positional/physical addressing1john larkin

Haut de la page

Les messages affichés proviennent d'usenet.

NewsPortal