Using the TCP (Socket) Adapter

Content outdated

We are in the process of migrating all content to impulse version 2.0.

The TCP Adapter fetches signal data from a TCP socket. The adapter acts as a TCP client and assumes that a server process (simulation, device under test,..) is writing the signal data into the socket while connected. The raw input data will be processed by a configurable reader.

Screen Cast: Using the TCP Adapter


  • In "Normal" mode, the adapter tries to connect to the given server and returns with an error if not possible.
  • If "Wait" mode is chosen, the adapter tries continuously to connect to the server without error exit.


  • Server: Server address or "localhost".
  • Socket: Socket number
You may specify a file "Write input to file" to store the raw input for debugging purpose.


Configure the serializer by selecting a reader and optionally a reader configuration (some reader require a configuration, e.g. the CSV reader).
You may use the buttons '+' and '...' to add and manage existing reader configurations (Preferences).
You may use the "Test Line Reader" (extracts lines from the raw input) and "Test Block Reader" (extract fixed size byte blocks) for debugging purpose.


Using a multi port adapter, you can combine an unlimited number of different input ports. The synchronization section of the adapters allows you to synchronize inputs with different domain bases (e.g. each input has its own time base). See 11 Synchronisation.


There may be cases where the server need to be stimulated before sending signal data.
In this case, enable the "Enable Stimulation" check and extend the stimulation script according to your needs.
The script is executed after connection.
	// socket:
	// out:
	// console: console output of type MessageConsoleStream

technical software and tooling


Contact Us

This email address is being protected from spambots. You need JavaScript enabled to view it.