ProtoLink 1.4.0

Test Modbus TCP and RTU without extra infrastructure

Find devices on the network, connect via TCP or RS-485, start and analyze communication — all in one application

  • Modbus TCP + RTU
  • No cloud
  • Windows · Linux · macOS
Modbus TCP connection screen in ProtoLink 1.4.0

Workflow

From device discovery to clear diagnostics

ProtoLink combines the core functions needed to verify Modbus connectivity and communication

01

Discover

Check one IP address, a CIDR subnet, or an address range with the built-in network scanner

02

Connect

Specify the host and port for TCP or COM-port settings for RTU

03

Work with data

Use read functions (FC01–FC04) and write functions (FC05/06/15/16)

04

Analyze traffic

Review requests, responses, and errors to quickly identify problems. Export the log when needed

Network scanner

Find Modbus-TCP devices on the network

The scanner accepts a single IPv4 address, a CIDR subnet, or a range, checks the specified port and Unit ID, and lets you transfer a discovered device directly to the connection form

ProtoLink network scanner
ProtoLink traffic monitor

Traffic monitor

Monitor device requests and responses

The monitor shows TCP and RTU traffic, TX/RX directions, function codes, attempts, duration, and HEX. Filters and JSONL export help troubleshoot unstable connections and device errors

Operations

Core Modbus functions in one interface

FC01 / FC02

Coils and discrete inputs

FC03 / FC04

Holding and input registers

FC05 / FC06

Single writes

FC15 / FC16

Multiple writes

Version 1.4.0

Choose a build for your system