| ??? 02/14/13 09:11 Read: times |
#189361 - Please explain a bit more Responding to: ???'s previous message |
Jim Granville said:
Perhaps better suited to 8051 / Small uC is what I've called a twisted ring. All uC are connected in a ring, using 9 bit UARTS, and all controllers look for an EDGE on the 9th bit. They then extract an agreed count, and replace with replies, and move the signal edge as they do so. So the 9th bit looks just like a twisted ring counter, as it moves along the loop. This is well suited to similar-slaves, and modern 8051 can do this to > 1MBd Address is automatic, by location in the loop, and even the total count present can be found by checking how far the 9th bit moved. You also know the slaves are awake, and not crashed, every transaction. I can see that a ring is a really good topology for a small number of 8051 class nodes, but can you explain your twisted ring a bit more as it sounds really interesting. How many bits or bytes make up a packet? Can any slave inject a packet? Where does the twist come in? |
| Topic | Author | Date |
| Multi-CPU designs | 01/01/70 00:00 | |
| Commonly Done | 01/01/70 00:00 | |
| Fun with network protocols | 01/01/70 00:00 | |
| and also a twisted ring network | 01/01/70 00:00 | |
| Please explain a bit more | 01/01/70 00:00 | |
| more details | 01/01/70 00:00 | |
I'd use I²C | 01/01/70 00:00 |