??? 02/04/11 12:27 Read: times |
#181002 - collision detection Responding to: ???'s previous message |
Indeed - you would need a protocol that both detects when such a "collision" has occurred and provides a means to recover from it.
Collision detection is one means, collisin avoidance is another. Typically master slave is collision avoidance and multimaster is collision detection. One thing that can create total havoc, if not considered, is a situation that is likely for this rig: two slaves, one getting the correct info (cksm OK) one not getting it correctly. Erik |
Topic | Author | Date |
Paralleling Max232 output | 01/01/70 00:00 | |
Revommedation On Paralleling Outputs | 01/01/70 00:00 | |
Multiple Mux | 01/01/70 00:00 | |
Adding another brain is another option. | 01/01/70 00:00 | |
RS232 is *not* a bus | 01/01/70 00:00 | |
Two UART | 01/01/70 00:00 | |
how about a hub | 01/01/70 00:00 | |
Is there really such a beast? | 01/01/70 00:00 | |
external UARTs | 01/01/70 00:00 | |
There once was... | 01/01/70 00:00 | |
use 422/485 | 01/01/70 00:00 | |
Can work well but big potentials for trouble | 01/01/70 00:00 | |
Thanks, Peter.. | 01/01/70 00:00 | |
I didn't employ anything | 01/01/70 00:00 | |
some comments | 01/01/70 00:00 | |
You really need reliable protocol | 01/01/70 00:00 | |
collision detection | 01/01/70 00:00 | |
Collision avoidance | 01/01/70 00:00 |