įirst have a look at the permissions on that file, lets assume you are using /dev/ttyS1.

In the context of modern human interface devices, full-duplex/'host echo enabled' is by far the most common configuration.Įmbedded devices, on the other hand, are quite likely to employ custom protocols that don't involve one side echoing its input back across the connection.All devices on Unix are mapped to a device file, the serial ports would be /dev/ttyS0 /dev/ttyS1. You are somewhat likely to encounter either terminology (half/full duplex, host echo on/off) to describe this sort of configuration. This was probably necessary to interoperate with legacy devices that were hardwired for half-duplex or full-duplex only. The Unix 'stty' command can enable or disable local echoing from the host side of the connection. Mode, where the remote device was responsible for echoing any input it received. Have a DIP switch selecting between 'half duplex' mode (which echoed characters locally,įor devices that didn't support simultaneous incoming and outgoing I/O), and 'full duplex' There are two different terminologies in play, that I'm aware of.depending on whether you're talking about a terminal device, or a host computer.īack in the day.using a computer usually meant a VT-100 terminal or similar RS-232 device, connected via modem or hardline to the host. Since today's clients are far more powerful than yesterday's 'servers', we pretty much only see the old paradigm when we ssh into a CLI to do some local system admin.īut even in that case in today's world we always have a 'full duplex' (remote echo) system.

Having said all that, I'm not familiar with your application and perhaps it is simple enough that local echo makes sense.

(I'm sure it happened a few times on some pathetic and now forgotten mainframe.) Some of these systems were expensive and sophisticated, and they ran a lot of bank terminals, but they were almost universally disrespected for their interactive design.Īs a concrete example, it is unlikely that even 0.1% of all the interactive Unix remote clients ever used local echo. The few systems with local echo were more-or-less emulating punch card input and generally were used to run a single large program that cooperated with the terminal hardware to run customer information systems or other online applications, but not true interactive computer access. Even the purely electromechanical teletypes used full duplex on Unix systems. It simply wasn't possible to have any control over the user experience without it. When interactive systems with relatively or even absolutely dumb (what we now call) clients were common almost all of them used a round-trip to what is now called the server for character echo.

Samsung rs232 echos command