The echo part is delivered within your terminal emulator program (look up its code yourself if it is OSS), the received part is delivered through the serial line. That is, you will probably see the text you enter echoed on the "INPUT" side (type it once, read it right there) as well as once in the window on the "OUTPUT" side (which depicts what came through the serial connection. Since experimenting with loopbacks is not the main purpose of terminal emulators, the default configuration is often to have this echo activated. Well, plus one extension: Usually, terminal emulators "echo" the input text to their local output part so that the user can verify (and remember) what has earlier entered and transmitted to the underlying line. You are typing to one instance, and the received text shows up at the other one. If you run a "host loopback" between two ports, you normally need two running instances of the terminal emulator (or emulators - you could also have Hyperterminal talk to PuTTY for example). If you were running a "port loopback" (special cabling at a single COM port), the output text would show up in the receiver window of the same terminal emulator where you posted your input text. If you use one USB-emulated COM port as you wrote, the signal runs through the adapter dongle and its corresponding driver software instead of the simpler way the data takes This is where you are viewing the data transfer.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |