Working modes

The data source and selected action determine what you see and whether the application sends messages. These are ways of working, not a separate mode selector in the interface.

Workflow	Source	Tools	Message transmission
Observe live communication	A connected line carrying traffic	Tracer, Monitor, statistics	Opening these tools does not start polling
Inspect a recording	A saved file	Tracer	Loading a file does not send messages to the line
Analyze through MCP	Data in the selected application instance	MCP client	Reading cached observations does not query the device
Perform active MCP operations	The current connection	MCP client with permissions	Explicit read or write requests generate real traffic

Observe a connected line

Prepare a line on which devices are already communicating. For example, a master sends Modbus requests, while an external diagnostic tool sends VAG diagnostic requests. Configure the connection. Tracer shows the message sequence; Monitor shows latest observations. Save saves an already collected trace; it does not start capture.

Inspect a saved trace

Select the appropriate module and use Load in Tracer. Loading replaces the current document, so save any traffic you need first. Viewing a file does not start playback for Monitor or transmit frames to the bus. See trace files.

Work through MCP

An MCP client can analyze observations or perform separately permitted operations. Reading the Modbus cache generates no traffic, while explicitly reading registers or CANopen objects sends requests. Connection control and writes require their own permissions. See automation and permissions for available operations and conditions.