|Home > Introduction > Using the TelnetTerminal|
This virtual component permits the transfer of UART data between a TCP/IP socket on the host and a serial port on the target.
The TelnetTerminal block is what you configure when you define TelnetTerminal component parameters. The Virtual Machine is your model system.
On the target side, the console process that is invoked by your target OS relies on a suitable driver being present. Such drivers are normally part of the OS kernel. The driver passes serial data through a UART. The data is forwarded to the TelnetTerminal component, which exposes a TCP/IP port to the world outside of the model. This port can be connected to by, for example, a Telnet process on the host.
You can change the startup behavior for each of up to four TelnetTerminals by modifying the corresponding component parameters.
If the TelnetTerminal connection is broken, for example by closing a client telnet session, the port is re-opened on the host. This could have a different port number if the original one is no longer available. Before the first data access, you can connect a client of your choice to the network socket. If there is no existing connection when the first data access is made, and the start_telnet parameter is true, a host telnet session is started automatically.
The port number of a particular TelnetTerminal instance can be defined when your model system starts. The actual value of the port used by each TelnetTerminal is declared when it starts or restarts, and might not be the value that you specified if the port is already in use. If you are using Model Shell, the port numbers are displayed in the host window in which you started the model.
You can start the TelnetTerminal component in telnet mode or raw mode.
Microsoft Windows 7 does not include the Telnet application by default. Follow these steps to install it: