This guide is for technicians and integrators who want to:
- evaluate the application without PLC hardware,
- connect a first Modbus or Siemens device,
- understand where configuration and archive data are stored.
- Windows 10/11 x64
- Visual Studio 2019+ or Windows build tools if building from source
- NuGet CLI and
msbuildonPATHfor source builds
- Build and start
IOBusMonitor. - On first launch, let the app create
Settings/Settings.db. - When the shell prompt appears, click
Enable Demo Mode. - Click
Start Monitoring. - Open
Dashboardto see synthetic live values. - Open
Historyto view archived demo samples.
What demo mode does:
- seeds sample Modbus TCP, Modbus RTU, and Siemens S7 configuration,
- marks the shell with a
DEMO MODEbadge, - generates synthetic values locally through the normal archive path,
- avoids real serial or network polling while enabled.
- Open the relevant settings page for the protocol.
- Add a device.
- Add a point under that device.
- Add one or more measurements.
- Save the changes.
- Use test connection or validation actions where the page exposes them.
- Click
Start Monitoring.
nuget restore .\IOBusMonitor.sln
msbuild .\IOBusMonitor.sln /p:Configuration=Release /p:Platform=x64The WPF application must be built from Windows. Current repository docs do not claim WSL build support for the app.
.\build\package-release.ps1The script creates a clean ZIP in dist/ and excludes local Settings, Data, and Logs by default.
Settings/Settings.db # app settings + configured devices/points/measurements
Data/Data_yyyyMMdd.db # daily measurement archive
Logs/ # optional diagnostic logs