Re:Positional/physical addressing

Liste des GroupesRevenir à e design 
Sujet : Re:Positional/physical addressing
De : martin_riddle (at) *nospam* verison.net (Martin Rid)
Groupes : sci.electronics.design
Date : 24. Jun 2025, 17:18:32
Autres entêtes
Organisation : news.eternal-september.org
Message-ID : <103ej4q$246v0$1@dont-email.me>
References : 1
User-Agent : PiaoHong.Usenet.Client.Free:2.02
Don Y <blockedofcourse@foo.invalid> Wrote in message:r
I have a large group (hundreds) of switches and displays.Their state needs to be determined/updated rather slowly(a few hertz).  Each has local smarts so it can retainsome state information and processing capability.Their physical arrangement varies from one installation tothe next.  So, there is no economy of scale available by"settling" on a specific configuration or physical arrangement.I would like to be able to address them (the entire *set*) -- andpass data to/fro -- with a small, fixed number of conductors /havingbuilt them all identically/.  The amount of data exchanged beingtraded off vs.  update rate for a given interface bandwidth.The obvious "one wire" scheme would have a gazinta and cumzoutafor each device so the device could modify a serial bit streamto account for its "position" in that stream.I can pipeline processing between devices so the overall accessrate remains high (though latency obviously suffers).But, a single device failure renders all downwind devicesinaccessible (or, possibly ALL devices, depending on implementation)I'm looking at a two wire solution that piggybacks the datastream on power and ground (those "two wires").  But, itadds complexity to the devices (I want to keep them REALLYsmall and dirt cheap)Any existing schemes that allow this without the failure mode cited?

CAN network?

--


----Android NewsGroup Reader----
https://piaohong.s3-us-west-2.amazonaws.com/usenet/index.html

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 Jun 25 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 Jun 25 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