Getting Started with SCADA Desktop: Local PLC Monitoring on Windows (2026)

July 3, 2026 · 10 min read

SCADA Desktop is a Windows application for local industrial monitoring. It connects directly to your PLCs and Modbus devices on the local network, displays live data on configurable dashboards, logs historical readings, and triggers alarms — all without any internet connection or cloud service.

This guide walks through the complete setup from install to your first live dashboard in under 30 minutes.

Before you start: Have your device's IP address (Modbus TCP) or COM port and baud rate (Modbus RTU) ready. You'll also need Windows 10 or 11 — SCADA Desktop is a Windows-only application.

Step 1 — Download and Install

1. Download the installer

Download SCADA-Setup.exe from modbussimulator.com/scada-desktop. The file is approximately 85 MB.

2. Run the installer

Double-click SCADA-Setup.exe. Windows SmartScreen may show a warning — click More info → Run anyway. The app is safe; the warning appears because it's unsigned freeware.

3. Create a local account

On first launch, click Register and enter a username, email, and password. This account is stored locally on your machine — no internet connection required. Your login credentials are for the local SCADA instance only.

Step 2 — Add Your First Modbus Device

SCADA Desktop supports Modbus TCP and Modbus RTU (RS-485/RS-232). Add one or more devices before creating tags or dashboards.

Modbus TCP device

Go to Devices → Add Device. Select Modbus TCP. Enter:
• Device name (e.g. "PLC-01" or "Energy Meter")
• IP address (e.g. 192.168.1.100)
• Port (default 502)
• Unit ID / Slave address (usually 1)
• Poll interval in milliseconds (e.g. 1000 = 1 second)

Modbus RTU device (RS-485/RS-232)

Go to Devices → Add Device. Select Modbus RTU. Enter:
• COM port (e.g. COM3 — check Device Manager if unsure)
• Baud rate (common: 9600, 19200, 38400, 115200)
• Parity (usually None or Even)
• Stop bits (usually 1)
• Slave address (1–247)

Connection test: After saving, the device status indicator turns green if SCADA Desktop successfully polls the device. If it stays red, verify the IP/port (Modbus TCP) or COM port settings (Modbus RTU) and check that no firewall is blocking port 502.

Step 3 — Configure Tags

Tags are individual data points — a holding register value, a coil state, an input register — that SCADA Desktop polls from your device.

Add a tag

Select your device → click Add Tag. Configure:
• Tag name: e.g. "Motor Speed", "Tank Level", "Phase A Voltage"
• Function code: FC01 (coils), FC02 (discrete inputs), FC03 (holding registers), FC04 (input registers)
• Register address: the register number from your device manual (0-based or 1-based — check your manual)
• Data type: INT16, UINT16, INT32, UINT32, FLOAT32, BOOL
• Scale / offset (optional): apply a multiplier or offset to convert raw values to engineering units

Add as many tags as needed. SCADA Desktop polls all active tags at the configured interval. Each tag's current value, last update time, and status are visible in the tag list.

FLOAT32 registers: Float values occupy two consecutive 16-bit registers. Enter the starting register address and select FLOAT32 — SCADA Desktop reads the register pair automatically. Check your device manual for byte order (big-endian vs little-endian).

Step 4 — Build Your Dashboard

SCADA Desktop includes a live dashboard with configurable widgets. No coding required.

Create and configure a dashboard

Go to Dashboard → Edit Mode. Drag widgets from the panel onto the canvas:
• Number display — shows raw or scaled tag value with unit label
• Gauge — circular or linear gauge with configurable min/max and color zones
• Trend chart — real-time and historical line chart for one or more tags
• Status indicator — binary LED for coil/discrete input status
• Bar chart — comparative view across multiple tags

Bind each widget to a tag by clicking the widget → selecting the tag from the dropdown. Click Save when done.

Step 5 — Configure Alarms

Alarms trigger automatically when a tag value crosses a threshold, and optionally send email notifications.

Add an alarm rule

Go to Alarms → Add Alarm:
• Select a tag
• Set condition: above, below, or equals
• Set threshold value
• Set priority: Critical, High, Medium, Low
• Optional: enter email address for alert notifications

Triggered alarms appear in the Alarm panel with timestamp. Acknowledge alarms to clear them from the active list.

Email alarms: Configure SMTP credentials in Settings → Email to enable alarm email notifications. SCADA Desktop uses your SMTP server — works with Gmail, Outlook, or any SMTP provider.

Step 6 — View Historical Trends

SCADA Desktop logs all tag values to a local SQLite database. Go to Historian → Trend Viewer, select one or more tags, and set the time range. Zoom in/out, compare tags, and export data to CSV for reporting.

Data is stored on your local machine — no cloud upload, no retention limits other than your disk space.

Troubleshooting Common Issues

Device stays red / polling fails

Modbus TCP: ping the device IP from Windows cmd — if it doesn't respond, check network/firewall. Verify port 502 is open on the device.
Modbus RTU: verify COM port in Device Manager. Check baud rate and parity match the device manual. Try different cable if using USB-to-RS485 adapter.

Tag shows "0" but device has real data

Check register address — some devices use 0-based addressing (register 0 = address 0), others 1-based (register 1 = address 0). Try address - 1.
Verify function code — holding registers use FC03, input registers use FC04. Wrong FC returns exception response.

Float values look wrong

Check byte order. If your device uses little-endian (CDAB) instead of big-endian (ABCD), the value will be garbage. Use Modbus Simulator's register viewer to see the raw bytes and verify byte order.

Download SCADA Desktop Free

15-day free trial. Full HMI, Modbus TCP/RTU, alarms, historian. Windows 10/11.

Download SCADA Desktop →