Re: Positional/physical addressing

Liste des GroupesRevenir à e design 
Sujet : Re: Positional/physical addressing
De : blockedofcourse (at) *nospam* foo.invalid (Don Y)
Groupes : sci.electronics.design
Date : 25. Jun 2025, 18:43:59
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <103hchi$2t06h$2@dont-email.me>
References : 1 2 3 4 5 6
User-Agent : Mozilla Thunderbird
On 6/25/2025 10:30 AM, Ian wrote:
On 2025-06-24, Jeroen Belleman <jeroen@nospam.please> wrote:
WS2812 LED chips do something like that. The first chip in the chain
absorbs the first three bytes and passes on all that come after, and
so on down the chain. Wait 50 us and the first chip in the chain is
ready again to intercept its three bytes.
 That's not quite how they work. The whole chain is one big shift register,
(24 bits per device), with 1's and zero's being shifted along as broad
or narrow pulses. When the pulses stop for a while*, the 24 bits sitting
in the "shift register" are latched into the "DAC register" and the
colour changes.
And, you (the controller) have to send the entire bit pattern; you can't
"address" the 47th device without also having sent the data for the
preceding 46.
Nor can those devices talk to each other (even if they had something to
say).
The UART "trick" makes the fabric more capable with the biggest
(operating) downside being non-constant latency.

I think I saw that there was some variant of the WS2812 that went into
a bypass mode on failure, to avoid breaking all that follow. Exactly what
counted as failure wasn't clear.
Yes.  It's possible to create a bypass much like removing a device
from a fiber optic "tap" and letting the optical switch act to bypass
its removal.

* An intersting / irritating bug had the firmware not waiting long enough
(= at all) between sending updates, so although the string was buisily
clocking data through it, nothing was happening on the lights. Getting the
bit count wrong can produce some pretty patterns, if you like migraines.
It is actually amusing that this even works, at all (given there are no
semi-precise timing references in the technology!)

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 Jun 25 i  i`* Re: Positional/physical addressing3Ian
25 Jun 25 i  i +- Re: Positional/physical addressing1Don Y
25 Jun 25 i  i `- Re: Positional/physical addressing1Jeroen Belleman
24 Jun 25 i  `- Re: Positional/physical addressing1Don Y
25 Jun 25 +* Re: Positional/physical addressing11Liz Tuddenham
25 Jun 25 i`* Re: Positional/physical addressing10Don Y
25 Jun 25 i `* Re: Positional/physical addressing9Liz Tuddenham
25 Jun 25 i  `* Re: Positional/physical addressing8Don Y
26 Jun 25 i   +* Re: Positional/physical addressing4Liz Tuddenham
26 Jun 25 i   i`* Re: Positional/physical addressing3Don Y
26 Jun 25 i   i `* Re: Positional/physical addressing2Liz Tuddenham
26 Jun21:48 i   i  `- Re: Positional/physical addressing1Don Y
26 Jun 25 i   +* Re: Positional/physical addressing2bitrex
26 Jun21:50 i   i`- Re: Positional/physical addressing1Don Y
26 Jun 25 i   `- Re: Positional/physical addressing1bitrex
25 Jun 25 +* Re: Positional/physical addressing4Ian
25 Jun 25 i`* Re: Positional/physical addressing3Don Y
25 Jun 25 i `* Re: Positional/physical addressing2Dennis
25 Jun 25 i  `- Re: Positional/physical addressing1Don Y
25 Jun 25 `- Re: Positional/physical addressing1john larkin

Haut de la page

Les messages affichés proviennent d'usenet.

NewsPortal