In computer telecommunications, echo is the display or return of sent data at or to the sending end of a transmission. Echo can be either local echo, where the sending device itself displays the sent data, or remote echo, where the receiving device returns the sent data that it receives to the sender (which is of course simply no local echo from the point of view of the sending device itself). That latter, when used as a form of error detection to determine that data received at the remote end of a communications line are the same as data sent, is also known as echoplex, echo check, or loop check. When two modems are communicating in echoplex mode, for example, the remote modem echoes whatever it receives from the local modem.
Terminological confusion: echo is not duplex
Whilst local echo and remote echo are sometimes referred to as "half-duplex" and "full-duplex", those latter appellations are strictly incorrect, and are misleading (see duplex for their correct meanings). Whilst local echo is often used with half-duplex transmission, so that bandwidth is not wasted upon remotely echoing data from the remote end of the communications channel, it is not the same as half-duplex transmission. A full-duplex communications channel can still employ local echo, and a half-duplex channel can still (albeit wastefully) employ remote echo, or no echo at all.
Similarly, for another example, in the case of the TELNET communications protocol a local echo protocol operates on top of a full-duplex underlying protocol. The TCP connection over which the TELNET protocol is layered provides a full-duplex connection, with no echo, across which data may be sent in either direction simultaneously. Whereas the Network Virtual Terminal that the TELNET protocol itself incorporates is a half-duplex device with (by default) local echo.
The devices that echo locally
Terminals are one of the things that may perform echoing for a connection. Others include modems, some form of intervening communications processor, or even the host system itself. For several common computer operating systems, it is the host system itself that performs the echoing, if appropriate (which it isn't for, say, entry of a user password when a terminal first connects and a user is prompted to log in). On OpenVMS, for example, echoing is performed as necessary by the host system. Similarly, on Unix-like systems, local echo is performed by the operating system kernel's terminal device driver, according to the state of a device control flag, maintained in software and alterable by applications programs via an
ioctl() system call. The actual terminals and modems connected to such systems should have their local echo facilities switched off (so that they operate in no echo mode), lest passwords be locally echoed at password prompts, and all other input appear echoed twice. This is as true for terminal emulator programs, such as C-Kermit, running on a computer as it is for real terminals.
Controlling local echo
Most terminal emulator programs have the ability to perform echo locally (which sometimes they misname "half-duplex"):
- In the C-Kermit terminal emulator program, local echo is controlled by the
SET TERMINAL ECHOcommand, which can be either
SET TERMINAL ECHO LOCAL(which enables local echoing within the terminal emulator program itself) or
SET TERMINAL ECHO REMOTE(where disables local echoing, leaving that up to another device in the communications channel — be that the modem or the remote host system — to perform as appropriate).
- In ProComm it is the Alt+E combination, which is a hot key that may be used at any time to toggle local echo on and off.
- In the Terminal program that came with Microsoft Windows 3.1, local echo is controlled by a checkbox in the "Terminal Preferences" dialogue box accessed from the menu of the terminal program's window.
In the Hayes command set, the AT command that switches local echo off (in command mode) is E0 and the command to switch it on is E1. For local echo in data mode, the commands are F1 and F0 respectively. (Note the reversal of the numbers. The "F" commands are not part of the EIA/TIA-602 standard, but the "E" commands are.)
Some host systems perform local echo themselves, in their device drivers and so forth.
- In Unix and POSIX-compatible systems, local echo is a flag in the POSIX terminal interface, settable programmatically with the
tcsetattr()function.[fn 1] The echoing is performed by the operating system's terminal device (in some way that is not specified by the POSIX standard). The standard utility program that alters this flag programmatically is the
sttycommand, using which the flag may be altered from shell scripts or an interactive shell. The command to turn local echo (by the host system) on is
stty echoand the command to turn it off is
stty -echo.[fn 2]
- On OpenVMS systems, the operating system's terminal driver normally performs echoing. The terminal characteristic that controls whether it does this is the
ECHOcharacteristic, settable with the DCL command
SET TERMINAL /ECHOand unsettable with
SET TERMINAL /NOECHO. [fn 3]
- In the older and superseded Seventh Edition Unix terminal interface, BSD version 4 terminal interface, and System III/System V terminal interface, it was settable via the
- This may not seem to work if used interactively. It does work. It's just immediately overridden. Some shells, such as tcsh, reset the terminal modes, including turning local echo off, when they are about to prompt for input. They actually place the terminal into non-canonical mode with local echo off, and handle echoing themselves, restoring the prior terminal attributes when the input line has been read. Any shell or other program that uses GNU readline also exhibits this interaction with
- Note that this is not the same as the
LOCAL_ECHOterminal characteristic, settable with the DCL command
SET TERMINAL /LOCAL_ECHOand unsettable with
SET TERMINAL /NOLOCAL_ECHO. That characteristic controls whether the terminal itself performs local echo.
What supports what
- Graf 1999, p. 230.
- Anmol 2000, p. 80.
- Rosch 1999, p. 1161.
- Weik 2000, "echo check" p. 478.
- Weik 2000, "echoplex" p.479.
- Jordan & Churchill 1987, p. 24.
- Hill Associates 2002, p. 341.
- Daintith 2004, p. 171.
- Bagad & Dhotre 2009, p. 9—4.
- Black 1987, p. 203.
- Socolofsky & Kale 1991, p. 24.
- IBM 1995, p. 2.
- Postel & Reynolds 1983, p. 2.
- Duffy 2002, p. 43.
- Leffler et al. 1989, p. 38,262,272.
- Da Cruz & Gianone 1997, p. 158–159.
- Bigelow 2000, p. 308.
- Woggon 1995, p. 101.
- Cowart 1992, p. 283.
- Sheldon 1991, p. 678.
- Norton & Kent 1993, p. 347.
- Durda 2004.
- Robbins & Robbins 2003, p. 204–205.
- Leffler et al. 1989, p. 262.
- Robbins & Robbins 2003, p. 203.
- Sobell & Seebach 2006, p. 855.
- Sobell & Seebach 2006, p. 856.
- Ramey 2009.
- Miller 1992, p. 30.
- Leisner & Cook 1990, p. 136,158.
- Bagad, V.S.; Dhotre, I.A. (2009). Data Communication & Networking. Technical Publications. ISBN 978-81-8431-759-6.
- Black, Uyless D. (1987). Data communications and distributed networks (2nd ed.). Prentice-Hall. ISBN 978-0-8359-1341-6.
- Bigelow, Stephen J. (2000). PC Technician's Troubleshooting Pocket Reference (2nd ed.). McGraw-Hill Professional. ISBN 978-0-07-212945-8.
- Cowart, Robert (1992). Mastering Windows 3.1. Sybex. ISBN 978-0-89588-842-6.
- Daintith, John (2004). "echo". Oxford dictionary of computing (5th ed.). Oxford University Press. ISBN 978-0-19-860877-6.
- Da Cruz, Frank; Gianone, Christine M. (1997). Using C-Kermit: communication software (2nd ed.). Digital Press. ISBN 978-1-55558-164-0.
- Duffy, Michael D. (2002). Getting started with OpenVMS: a guide for new users. Digital Press. ISBN 978-1-55558-279-1.
- Durda, Frank (2004). "Section 3: Unprefixed AT Commands". The AT Command Set Reference.
- Graf, Rudolf F. (1999). "echo". Modern dictionary of electronics (6th ed.). Newnes. ISBN 978-0-7506-9866-5.
- Hill Associates (2002). Telecommunications: a beginner's guide. Network professional's library. McGraw-Hill Professional. ISBN 978-0-07-219356-5.
- IBM (June 1995). "Telnet and the Telnet Protocol" (PDF).
- Jordan, Larry E.; Churchill, Bruce (1987). Communications and networking for the IBM PC & compatibles (2nd ed.). Brady. ISBN 978-0-89303-634-8.
- Leffler, Samuel J.; McKusick, Marshall Kirk; Karels, Michael J.; Quarterman, John S. (1989). "Terminal Handling". The Design and implementation of the 4.3BSD UNIX operating system. Addison-Wesley series in computer science. Addison-Wesley. ISBN 978-0-201-06196-3.
- Leisner, K. M.; Cook, David B. (1990). VAX DCL programmer's reference VMS 5. Van Nostrand Reinhold. ISBN 978-0-442-31834-5.
- Miller, David Donald (1992). VAX/VMS: operating system concepts. VAX-VMS Series. Digital Press. ISBN 978-1-55558-065-0.
- Norton, Peter; Kent, Peter (1993). Peter Norton's user's guide to Windows 3.1. Bantam Books. ISBN 978-0-553-37148-2.
- Ramey, Chet, ed. (2009). "2.5 Readline Signal Handling". GNU Readline Library.
- Postel, Jon; Reynolds, J. (May 1983). "RFC 0857: TELNET ECHO OPTION".
- Robbins, Kay A.; Robbins, Steven (2003). UNIX systems programming: communication, concurrency, and threads (2nd ed.). Prentice Hall PTR. ISBN 978-0-13-042411-2.
- Rosch, Winn L. (1999). Winn L. Rosch hardware bible (5th ed.). Que. ISBN 978-0-7897-1743-6.
- Sheldon, Thomas (1991). Windows 3: the complete reference. Osborne McGraw-Hill. ISBN 978-0-07-881679-6.
- Sobell, Mark G.; Seebach, Peter (2006). A practical guide to Unix for Mac OS X users. Prentice Hall PTR. ISBN 978-0-13-186333-0.
- Socolofsky, T.; Kale, C. (January 1991). "RFC 1180: A TCP/IP Tutorial".
- Weik, Martin H. (2000). Computer Science and Communications Dictionary 1. Springer. ISBN 978-0-7923-8425-0.
- Woggon, Michele (1995). Telecommunications using ProComm & ProComm Plus made easy. Prentice Hall. ISBN 978-0-13-148412-2.
- "local echo". Advanced learner's dictionary of journalism. Advanced Learner's Dictionary Series. Anmol Publications PVT LTD. 2000. ISBN 978-81-261-0469-7.