DAQMaster → Web Rebuild

Detect first-run (no project in localStorage). Show a 3-step wizard: 1) Create project name + description, 2) Scan for devices on the local network or connected USB, 3) Drop user into the default runtime screen with the first tag live.

First time a user hovers a non-obvious UI element (e.g. 'OPC DA Server' in the project tree), show a one-line tooltip + a 'Learn more' link to the relevant section of the in-app docs.

Ship 3-4 example projects: 'Single temperature controller', 'Multi-zone oven', 'pH + temperature cascade'. New users can pick a template and explore without configuring hardware.

Replicate DAQMaster's three-pane layout: vertical navigation tabs on the left (Project List, Supported Device List, I/O List), the ribbon menu across the top (Project, View, Tool, Windows, Help), and the central DAQ WorkSpace. Must collapse to single-pane under 900px viewport width.

Remember which left-tab (Project List, I/O List, etc.) the user had selected when they last closed the app. Restore on next launch.

Allow runtime screens to be popped out into separate browser windows for placement on different monitors in a control room.

Pinned/favorite projects shown in the left sidebar. Add/remove via right-click context menu. Drag to reorder. Storage: localStorage (per-browser) or backend (per-user).

Tree view of the current project: Runtime Screens (Grid, Multi Panel, Panel, Line Graph, Bar, etc.), Realtime Log, TCP/IP Server, DDE Server, OPC DA Server, Scheduler, Trigger Event, Report, MQTT Publisher. Double-click any node to open its config. Right-click for context menu (Add, Rename, Delete, Duplicate).

Save/load projects as plain JSON (UTF-8, 2-space indent). The JSON schema is documented and stable. Backward-compat: schema version field, with a migration function if older versions are loaded.

Typical project (50 tags, 10 runtime screens, 20 trigger rules) should serialize to <1MB. Large projects (1000+ tags) should still load in <2s.

Project name (string, required), description (textarea, optional), log directory (path picker, default to user's Documents folder).

Default runtime screen canvas size (e.g. 1920×1080), grid snap on/off, default theme (dark/light), color-blind safe alarm palette.

Select up to 8 tags whose values get stamped into every log row for traceability. Used for batch ID, operator, shift, etc.

Two modes: (1) Buffer-then-flush — accumulate in memory, write to disk on session end or every N minutes (configurable). (2) Direct — write each row to disk immediately. Buffer mode is faster but loses data on crash; direct is slower but durable.

One-click 'Run Project' that: connects to all configured devices, starts logging per the DAQ List, starts all runtime screens, starts the trigger event engine, starts the scheduler. 'Stop' reverses all of this. Status indicators next to each subsystem (green=running, red=error, yellow=paused).

On `beforeunload`, send a 'pause' command to the backend, which holds Modbus connections open for 5 minutes. If the user returns within 5 min, resume seamlessly. After 5 min, full disconnect + close handles.

If the WebSocket drops, automatically attempt reconnection with exponential backoff (1s, 2s, 4s, 8s, max 30s). Show a banner in the UI with 'Reconnecting in Xs...' and a manual 'Retry now' button.

Sample configured tags at their configured cycle (per-tag ms, e.g. 100ms / 1s / 5s). Condition: always / on-change (deadband) / threshold (above/below). Group multiple tags to share a single read transaction (e.g. read 8 AIMS registers in one request).

Write logs as CSV (default, universal), Parquet (columnar, for analytics), or .duf (legacy DAQMaster binary format, for interop with existing DAQMaster Data Analysis tool).

Rotate log files by time (hourly, daily, weekly) or size (10MB, 100MB, 1GB). Old files can be auto-compressed (gzip) and auto-deleted (retention policy).

Buffer writes in memory + append-ahead log (WAL). On crash recovery, replay the WAL to ensure no rows are lost. Periodically checkpoint to disk.

Backend exposes a configurable TCP port (default 9001) that serves a custom line protocol: clients send `GET <tag_name> `, server responds with `<tag_value>,<quality>,<timestamp> `. Plus `SET <tag_name> <value> ` for writes. Multi-client supported.

Optional mode that emulates DAQMaster's specific TCP server protocol (look up the format in the user manual if documented) so existing client integrations don't need changes.

Dynamic Data Exchange is a Windows-only 1980s protocol. ~0% of new integrations use it. Out of scope for v1. Mark deprecated in UI; deprecation banner in the docs.

OPC DA 2.0/3.0 server. Requires Windows COM, so ships as a separate small Windows service that talks to the Linux/Docker backend via WebSocket. Exposes all tags as OPC items.

OPC UA server in the main backend. Cross-platform, modern, secure. Exposes all tags as OPC UA nodes in a hierarchical address space. Supports subscriptions with configurable publishing intervals. Security: None / Sign / SignAndEncrypt.

Schedule actions on cron-style rules: '* * * * *' (every minute), '0 9 * * 1-5' (9am weekdays), '0 0 1 * *' (first of month), plus ISO timestamps for one-shots. Actions: start/stop project, run report, push to MQTT, run script, etc.

Schedules run in a configured timezone (default: project local timezone, displayed in the UI). Daylight-saving handled correctly via IANA TZ database.

Rules expressed as JSONLogic expressions over tag values. AND/OR/NOT composition, comparison operators (>, <, ==, !=, between), string ops (contains, starts-with), arithmetic, hysteresis (different trigger vs clear thresholds), debounce (min time between fires).

Action types: (a) write a tag value (with safety check: can't write to read-only tags), (b) send notification (email, SMS, Telegram, webhook), (c) run a Lua script, (d) chain to another trigger. Actions run sequentially with configurable timeout per action.

A 'Test this rule' button that takes a snapshot of current tag values, evaluates the rule, and shows: 'If this state were live, the rule would FIRE → action X, action Y'. Without firing the actions.

User defines a report template: title, time range, list of tags with aggregation (min/max/avg/integral/count), chart image, header/footer with project info. Generates PDF via headless Chromium (Playwright).

Combine with the Scheduler: 'every Monday at 8am, generate the weekly report and email it to ops@example.com'. Per-template email recipients.

Publish tag values to an external broker. Configurable: broker URL, port, TLS, username/password, client ID, QoS (0/1/2), retain flag, last-will. Topic template with placeholders: `site/{site}/device/{device}/tag/{tag}` where {x} resolves to tag metadata.

Support MQTT 5 shared subscriptions ($share/group/topic) for horizontal scaling of consumers. Useful when multiple backend instances are running for HA.

Trigger the bundled Telegram bot service (or a server-side bot). Bot token from project settings. Chat IDs for recipients. Message template with tag value substitution: 'Reactor 3 high: {tag.pv}°C at {timestamp}'. Rich formatting (bold, links, inline keyboards for Acknowledge / Silence).

SMTP with STARTTLS or TLS. Auth: user/pass. Recipient list per trigger. HTML + plain-text body. Subject templated. Attachment optional (snapshot of dashboard, last 100 log rows).

Two backends: (a) direct serial GSM modem via AT commands, (b) via the TCG140 Ethernet gateway (if one is online). Recipient phone numbers. Per-message cost cap (don't burn money on runaway triggers).

Tree of all 54 device families. Search by vendor/category/model. Click to see specs. Double-click to add to current project. Recently-used pinned to top.

Device definitions live in a public GitHub repo as JSON. The app checks for updates weekly and pulls new devices. Old versions kept for rollback. User can pin to a specific version if needed.

Step-by-step wizard: (1) Name + vendor, (2) Modbus variant (RTU/TCP, slave ID), (3) Parameter list (name, address, data type, access, scaling, units, alarm bands) — importable from CSV, (4) Preview + save as a .dev JSON file. Saved definitions appear in the catalog next time.

For each parameter in a user-defined device, run a 'test read' that shows: raw register value, scaled engineering value, last-error, decode quality. Useful for debugging user-defined devices against a real one.

CC-Link IE Field Basic protocol master. Slave discovery via broadcast. Per-slave I/O mapping. Cyclic transmission ON/OFF per slave. Tested against Mitsubishi MELSEC iQ-R / iQ-F series.

Windows-only DDE client. Out of scope for v1. DDE is essentially dead. Use OPC UA or MQTT instead.

Connect to any ODBC/ADO database (SQL Server, MySQL, PostgreSQL, Oracle, SQLite). Run a SQL query at a configurable interval, map result columns to virtual tags. Bidirectional: write back to DB on tag change.

Connect to external broker. Subscribe with wildcards (`site/+/temp/+`). Per-subscription tag mapping: topic pattern → local tag name, with payload parsing (JSON path, regex).

Expose project tags as Modbus registers (holding/input/coil) so other Modbus masters can read/write. Configurable register map: which tag → which register, scale, swap bytes, signed/unsigned.

Connect to a remote OPC DA server, browse its address space, subscribe to items, map to local tags. Requires Windows COM, so shipped as a separate small Windows service that talks to the main backend via WebSocket.

Connect to OPC UA servers. Browse the address space. Subscribe to monitored items with configurable publishing interval. Map nodes to local tags. Support security policies (None / Sign / SignAndEncrypt) and authentication (Anonymous / UserName / Certificate).

Tag whose value is derived from other tags: arithmetic expression like `(tag_a * 1.8) + 32`, or full Lua script for state machines and complex logic. Recomputed on every input tag change, throttled to max 10Hz to avoid CPU spikes.

Expose Windows performance counters (CPU%, memory, disk I/O, NIC bytes/sec, per-process metrics) as tags. For monitoring the DAQMaster host itself.

Tree view of the current project. Root nodes: Serial ports, Ethernet interfaces, Modbus Masters. Children: devices hanging off each interface. Per-device: address, status, online/offline indicator, last-poll timestamp.

Send a broadcast UDP packet on each Ethernet interface. Devices that support the discovery protocol respond with their model, MAC, IP, firmware version. UI shows results in a list, user can pick which to add.

Save a device's current parameter set as a named file. Copy a saved set to another compatible device. Useful for commissioning identical machines.

Every readable/writable parameter on every connected device appears as a typed tag. Columns: Tag Name, Device, Source, Interface, Type (Analog/Digital), Access (R/RW), Units, Scale, Alarm Bands. Searchable and filterable.

Each tag row shows a mini line chart of the last 5 minutes of values. No need to open a runtime screen to see if a tag is live.

For each tag, set: enable (bool), cycle (ms: 100/500/1000/5000/60000), condition (always / on-change with deadband / above-threshold / below-threshold), group (so multiple tags share a single Modbus read).

Every trigger action, scheduler run, alarm, connection status change, and operator action is logged with: timestamp, source, severity (info/warn/error/critical), message text. Filterable by time, source, severity. Exportable to CSV.

react-grid-layout based canvas. Drag widgets from a palette (numeric, gauge, LED, line graph, button, slider, image) onto the canvas. Resize, align, snap to grid. Each widget binds to one or more tags from the I/O List. Save the layout per screen.

Toggle between 'Edit' and 'Live' modes. Edit: drag/resize widgets. Live: widgets receive real values, no edit affordances. Switching is instant (no reload).

Tabular view of live tag values. Sortable, filterable, with conditional formatting (color, alarm bands, blink on change). Handles 10,000+ rows without lag via TanStack Table virtualization.

Arrange multiple numeric/LED indicators in a grid. Each cell binds to one tag. Configurable cell size, font size, units display. Common for status dashboards.

Big numeric readout with units, timestamp, color-coded alarm state, optional trend sparkline. For 'zoom in on one critical measurement'.

ECharts-based real-time time-series chart. Multiple Y-axes (one per tag). Zoom/pan. Time cursors with crosshair readouts. Alarm bands. Digital-channel overlays. Up to 8 tags per graph; 10K+ samples at 100ms cycle.

Export the currently-visible time range to CSV (raw data) or PNG (the chart image). Useful for incident reports and post-mortems.

Bar chart for comparing multiple tag values at one point in time. Vertical or horizontal. Configurable colors, labels.

2D heatmap view. X and Y axes are typically sensor positions, color is the tag value. Useful for thermal imaging, oven temperature uniformity. Configurable colormap (viridis, plasma, inferno, etc.).

Analog dial gauge. Configurable min/max, scale, color bands, needle style. Mimics physical panel meters.

Histogram of recent values for a tag. Configurable bin count and time window. Useful for process capability (Cp, Cpk).

Lists every alarm condition that fired: timestamp, tag, value, severity, ack/unack status, operator who acknowledged. Filterable by time, tag, severity. Exportable to CSV.

Central workspace where runtime screens are composed and live. Multiple panels positioned, sized, and saved as a layout. Multi-monitor support: layout snaps to any screen size.

Replace the Win32 dialog tree with a web app. Step-by-step wizard: (1) name/vendor, (2) Modbus variant + slave ID, (3) parameter list (CSV upload or table editor), (4) preview, (5) save as JSON. Live test panel for verifying against a real device.

Users, Groups, Authorities. Default groups: Admin, Engineer, Operator. Per-group authorities: Change Files, Change Property, Change My System, Change Projects, Change TAG List, Change Runtime, View Audit. OIDC SSO (Google, Okta, Azure AD).

Lua IDE for writing custom device behavior, computed tag logic, and trigger actions. Syntax highlighting, autocomplete, error squiggles. Save scripts per-device or per-project. Sandbox execution: no os.execute, no file I/O, no network access (except via a whitelisted API).

Open historical .duf and .csv log files. Grid view, graph overlay, alarm grid, Analysis Spread (pivot-table-style aggregation), min/max/avg/integral/SPC calculations. Time-range scrubber. Side-by-side comparison of two time ranges.

Save analysis configurations as templates. Re-apply to new log files. Useful for repeating the same weekly report on every shift's data.

Auto-detect attached control/option modules on the TMHC backplane. Map per-module parameters to tags. Handle firmware-version-based parameter differences.

Read/write TN Series pattern steps. Step editor: setpoint, ramp rate, soak time, jumps. Drag-drop to reorder. Sync with TN device.

Custom scaling and display logic for DS/DA-T Series. Preset values, count modes, output configuration.

Input scaling, display config, output mode setting, communication parameter upload/download.

Detect new vs old hardware revisions. Configure communication mode. Run firmware upgrade with progress indicator. Rollback on failure.

Access internal record backup data from KRN50. Convert to standard format (CSV/Parquet). Download with progress indicator.

Same as KRN50 but for KRN100 (100mm form factor). 4-8 channels, color TFT.

Log data backup from KRN1000 internal memory. Higher channel count, modular expansion.

ARIO IO-Link master: communication mode config, parameter setting, I/O signal control + monitoring, tag monitoring for IO-Link devices, address map, coupler firmware update, virtual mode for offline config.

B7VA playlist create, edit, export, import. Configure playlist, save to micro SD card or as project file.

Alarm history with the special 1-minute grouping rule (all alarms within 1 min of an alarm-onset are grouped). Avoids log spam during transient bursts.

Parameter entry via Setting dialog. Batch operations: Load All, Save All, Teaching All, Copy. For fast commissioning of multi-channel installations.