Internal PDF reports
Generate FAT evidence from captured behavior, test outcome, remarks, command results, and timestamp context.
Native C# DNP3 master • FAT evidence • Open source
DNP3 master testing with traceable FAT evidence.
A Windows desktop tool for protection relay FAT, SCADA troubleshooting, and interoperability validation. The current source tree uses a native C# DNP3 master stack, configurable point databases, SOE audit, command lifecycle checks, and an internal PDF report engine.
Open source
Native C# DNP3 master
Internal PDF report
Configurable point DB
SOE audit
Integrity poll evidence
Event class polling
Point mapping review
Analog verification
Command acceptance
Feedback matching
SOE timestamp audit
Internal PDF FAT report
Integrity poll evidence
Event class polling
Point mapping review
Analog verification
Command acceptance
Feedback matching
SOE timestamp audit
Internal PDF FAT report
Core value
Built to help engineers create proof, not just protocol traffic.
DNPTester focuses on the practical work around a DNP3 master session: verify device response, decode values, inspect event behavior, preserve trace context, and export evidence that can be reviewed outside the tool.
Native DNP3 master path
Run communication checks through a native C# protocol path built for relay, RTU, and SCADA interoperability testing.
User configurable point database
Define binary inputs, analogs, counters, command indexes, labels, and expected behavior to match the device under test.
Inspectable engineering source
Published for protection, SCADA, SAS, RTU, and substation automation engineers who want inspectable tooling.
Why engineers try it
One workspace for real DNP3 test bench work.
Use it when you need more than a connect button and a raw log. The app is organized around the practical questions engineers face during relay FAT, SCADA integration, protocol communication testing, data communication learning, and field troubleshooting.
Test IEDs and relays
Connect to a DNP3 outstation, run polling, inspect decoded points, and confirm that the device is truly responding.
Troubleshoot SCADA signals
Follow values, events, SOE rows, source reasons, flags, and link traces when a signal is missing, stale, inverted, or timestamp-invalid.
Build FAT evidence
Collect identity, point verification, command, non-operation, recovery, SOE, and trace evidence into an exportable report.
Check interoperability behavior
See how the outstation behaves under class polling, static reads, events, command response, feedback, and recovery workflows.
Application screens
Designed for fast evidence scanning during live communication.
Report Workspace
Guided FAT flow with internal PDF preview and export-ready evidence.
SCADA Events
Operator-facing events with IED timestamp basis and quality context.
SOE Audit
Forensic rows for timestamp quality, variation, qualifier, and source reason.
Evidence engine
The report is generated from captured behavior, not wishful labels.
The app separates open-port state from real device response and stores protocol evidence that can be reviewed before exporting a FAT report.
Connection evidence
Device response, decoded values, SOE rows, and protocol trace context.
Point evidence
Binary, analog, counter, command index, operator verdict, and remarks.
Timestamp evidence
IED/source timestamp when valid, captured-time fallback when not.
Command evidence
Prepared, requested, accepted, feedback matched, and final verdict.
Negative test evidence
Guarded non-operation workflow records blocked invalid command paths.
PDF evidence
Preview and export use the same internal PDF render path.
FAT reporting
Readable for customers, traceable for engineers.
The report workspace is built to avoid the common FAT problem: beautiful output with unclear evidence. It tracks executed items, open items, failed items, warnings, and technical result separately.
FAT matrixObjective, evidence, recognition rule, and verdict.
Completion statusSeparates partial FAT from protocol failure.
Timestamp qualityFlags valid, invalid, missing, and captured timestamp basis.
Command lifecycleShows acceptance, feedback, latency, and final result.
Windows release
Get the source and releases from GitHub.
GitHub is the canonical place for the source, release notes, installer assets, checksums, and version history. Review the project license and third-party notices before production use.
Source readiness
Inspectable source with a native master stack.
The application source is published under the Apache License, Version 2.0. The master tester uses the native C# DNP3 master stack included in this repository, with project license and third-party notice files kept alongside the source and release assets.