| ??? 02/03/11 14:30 Read: times |
#180979 - Can work well but big potentials for trouble Responding to: ???'s previous message |
Erik Malund said:
use 422/485 and use a proper protocol. Costly/clumsy if the two of the devices already exists and already talks RS232. That means that the OP have to convert RS232 -> logic level -> RS422 -> logic level. I had to write software once for a system where up to 16 processor boards were placed in a 19" rack system - each board had a RS232 port connected together. So the PC could send data to any of the boards by supplying an address in the message. And the individual boards had a digital signal (summary alarm) they could draw to inform that any of the boards needed service. Most funny - any slave board talking at the same time resulted in a deadlock requiring power cycling. System has been in operation for 20+ years and works well - but not worth the trouble to do something like that unless absolutely 100% totally cornered. |
| 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 |



