
Connect, inspect and keep the evidence.
Diagnostics · simulation · live bridging · field calculators
Download Inspector and Emulator for Windows, or use the field calculators in your browser. They are free, practical and ready to use without an account. If something is good—or bad—tell us. We will make the next build better together.

Connect, inspect and keep the evidence.

Change the behaviour and test your assumptions.
00 / HOW IT WORKS
Download it. Use it. Tell us what worked—and what did not.
Useful feedback becomes a clearer workflow, a fixed edge case or a better tool.
01 / DOWNLOADS
Inspect what is happening at the endpoint, recreate the condition safely, or decode the data directly in your browser.

Prove the difference between network reachability and protocol truth.
Unsigned test build—Windows may display an Unknown Publisher warning.
The boundary: diagnostics and evidence—not PLC programming or control.

Create a predictable industrial peer when the real device is unavailable—or too important to experiment on.
Unsigned test build—Windows may display an Unknown Publisher warning.
The boundary: a controlled lab companion, loopback-safe by default.
02 / PROTOCOL BRIDGE

When a test needs to become a dependable data path, Bridge connects industrial sources and destinations without tying the solution to a dedicated protocol card.
Enquire about ProtoCall Bridge →Windows desktop first. Industrial PC and ARM / Raspberry platform profiles follow after field validation.
Use it during migrations, cutovers, trials and proof-of-concept work where the data path may only be needed for a bounded period.
Run the validated configuration as a managed service for an ongoing protocol exchange on the host you control.
03 / FEEDBACK
You do not need to write a report. Tell us which tool you used, what you expected and what actually happened. Good and bad feedback are equally useful.
Send feedback →The result that saved time, explained the problem or gave you evidence you could use.
The rough edge, confusing label or result that made you stop trusting the tool.
The controller, protocol or awkward field case you wish the toolkit covered next.
04 / THE SIMPLE DEAL
Use a Windows build or one of the browser tools.
Start with the protocol problem already in front of you.
Save the useful evidence—or the point where it went wrong.
Your experience helps decide what should be fixed or built next.
FREE PROTOCOL TOOLS