| ??? 04/05/07 07:48 Read: times |
#136659 - Recipe for a short circuit? Responding to: ???'s previous message |
You can simply tie the TXD pins of both micros together and the tie both RXD pins of the micros together. Now both micros will get the same message from the PC.
Give each micro an ID so that it knows when the PC is 'talking' to it so that it will only respond when addressed. So ... micro 01 is being addressed by the PC and sends a response by driving its TX line low, while micro 02 is not being addressed and keeps driving its TX line high ... |
| Topic | Author | Date |
| multiple 8052 communication with PC | 01/01/70 00:00 | |
| RS485 | 01/01/70 00:00 | |
| More COM: Ports | 01/01/70 00:00 | |
| Further additional COM: ports | 01/01/70 00:00 | |
| multiple 8052 communication with PC | 01/01/70 00:00 | |
| Simple solution | 01/01/70 00:00 | |
| Recipe for a short circuit? | 01/01/70 00:00 | |
| Not on a standard 8051? | 01/01/70 00:00 | |
| whether that is a problem is for the OP to determi | 01/01/70 00:00 | |
| protocol ?? | 01/01/70 00:00 | |
| yes - no - see above | 01/01/70 00:00 | |
| master slave PC performance | 01/01/70 00:00 | |
| multi-GHz PC can get a lot done in a few ms! | 01/01/70 00:00 | |
| Slave comms controller? | 01/01/70 00:00 | |
| expanding on th above | 01/01/70 00:00 | |
| For just two devices | 01/01/70 00:00 | |
| been there, done that | 01/01/70 00:00 | |
In this case... | 01/01/70 00:00 | |
| Interrupt Request? | 01/01/70 00:00 | |
| not really | 01/01/70 00:00 | |
| Not on a PC | 01/01/70 00:00 | |
| Not that it can't be done | 01/01/70 00:00 | |
| Another recipe is a ring!!! | 01/01/70 00:00 | |
| sure, if you have all the time in the world | 01/01/70 00:00 |