Views

1. Which views are active

Views are independent of the capture: switching a view never reopens the port or restarts monitoring.

• The default workspace opens Table, Hex Dump, Line and Terminal.
• Modbus, Protocol and any other view you enable are added from the Views menu in the tab bar.
• A view that is turned off is not fed any data, so it costs nothing while it is off.
• The menu itself is always available, so a view can always be found again.

2. Table

One row per frame: sequence, time, direction, process, port, IRP, length, hex and ASCII. It is the best view for scanning a capture and for spotting the frame where things went wrong.

Table stays where it is while capture continues, which is what you want when reading a row. Use the clear or jump actions to move it.

3. Hex Dump, Line and Terminal

• Hex Dump shows offset, hex and text columns - the view for byte patterns and encodings.
• Line groups each frame into an IRP line, a status line and the data or sub-function lines.
• Terminal shows the same traffic as a terminal would, which is what NMEA and AT work looks like in practice.

These three can follow the tail of a running capture, which is useful while you are waiting for a device to answer.

4. Modbus and Protocol

Modbus decodes function code, register address and CRC for Modbus RTU and ASCII traffic. Protocol shows the field names produced by the active protocol plugin - including DL/T 645, IEC 60870-5-101, NMEA 0183 and AT commands.

Both views show decoded fields next to the raw bytes, so a decoding bug is visible rather than hidden behind an interpretation.

Decoding is a Professional feature. Without it both views still list the frames, and every decoded value - the protocol name, the Modbus fields and the summary - reads ****.

5. Dashboard

Dashboard is the same capture served as a read-only local web page. It is covered on its own documentation page.