??? 12/22/05 13:46 Read: times |
#105731 - RS232 Tests Responding to: ???'s previous message |
Hi Shruthi,
I think you should start by separating the tests. Physical - electrical tests Packet data tests (there is probably a better term for this like data Integrity tests). a) Packet - Integrity - you can generate your own packets of data in hyper terminal or realterm or what ever serial program and send the data to your micro. You can create bad data packets and see how your micro handles them. b) For the Physical tests. Read the data sheet carefully on the RS232 level converter as this device determines if a '0' or '1' is being sent or received. You can test level converter using bit patterns like 01010101 (use a square wave generator etc) + noise.... Use a dual trace cro on input and output. You can then get an idea how the RS232 level converter stands up. You can then see what noise threshold is achieved before the RS232 levels become corrupted. I am sure the group might have other ideas. JG |
Topic | Author | Date |
RS232 tests | 01/01/70 00:00 | |
why would you do that in a loopback test | 01/01/70 00:00 | |
loop back test | 01/01/70 00:00 | |
why not DOS copy /b phread.xxx comN | 01/01/70 00:00 | |
Used timer | 01/01/70 00:00 | |
faulty UART | 01/01/70 00:00 | |
RS232 Tests | 01/01/70 00:00 | |
Try this | 01/01/70 00:00 | |
Thank you![]() | 01/01/70 00:00 |