PlcConsole

Monitoring

These screens tell you what the PLC is doing right now, how the command path behaves and where to look when something fails.

Manual Home

Monitoring Overview Monitoring Tools Dashboard Dashboard Failure PLC Status Diagnostics History Use Monitoring

Monitoring Model

The monitoring workflow is broader than a single dashboard view. It is where the app shows the live PLC state, the command feedback and the audit trail after each action.

All of these screens require an active PLC profile. A command failure appears first as a PLC Command Failed popup and remains in Last Error until the next successful command or disconnect clears the screen state.

Dashboard: Runs and stops the PLC, but the view model prevents overlapping commands so the user cannot queue conflicting actions.

Failures: Command failures are shown twice on purpose: once as a popup and again as a persistent screen section.

Snapshots and history: PLC Status, Diagnostics and History keep the screen useful after reconnects, view changes or repeated actions.

Monitoring Tools

Dashboard

Description

The Dashboard is the operational front page. It shows the current run-state title and exposes the three commands that matter most in practice: Refresh Status, Run and Stop.

Busy states: The UI keeps the command buttons disabled while a request is in flight.

Fresh state: The Run State is Unknown until a status response is received. Dashboard reads status on first appearance and refreshes it again after a successful Run or Stop command.

Refresh loop: Refreshing after Run or Stop is intentional because the status snapshot is what updates the displayed state.

Immediate control: Run and Stop send their PLC commands immediately. Confirm the active profile and connected equipment before tapping; the screen does not ask for a second confirmation.

Dashboard Failure

Description

When a dashboard command fails, the app uses the shared command-failure popup and also stores the message in the page’s last-error section.

One popup: The popup appears once per new error occurrence, not repeatedly for the same stale value.

Persistent state: The underlying screen keeps the error section visible, which makes later troubleshooting easier when the user switches away and comes back.

Command source: The failure message comes from the command layer, so it can represent transport problems, PLC rejection or a timeout.

PLC Status

Description

PLC Status breaks the device state into the individual flags and capacity counters that are useful when diagnosing real hardware behavior.

Flags: The detailed flag rows cover run, battery, checksum, watchdog, PLC ID and stop-related states.

Capacity: The capacity section summarizes the unit type and the available discrete, analog, relay, register, timer and counter resources.

OS version: FATEK detailed status reports a version family rather than the complete patch version, so a value such as 4.7x covers installed versions including 4.74.

Diagnosis: This screen is useful when the Dashboard says nothing unusual but the hardware still behaves differently than expected.

Snapshot: Detailed status loads when the screen opens and Refresh Status requests a new snapshot. The displayed flags and capacity remain the latest successful response; this screen does not poll continuously.

Diagnostics

Description

Diagnostics is the smallest end-to-end communication test in the app. It sends a payload and expects the PLC path to echo it back, which helps separate a transport issue from a higher-level register or status screen problem.

Echo check: The result appears as an echoed payload when the path is healthy.

Failure signal: If this fails while the profile is active, the problem is likely transport-related rather than a screen-specific validation bug.

Payload: Enter a non-empty payload, then run the test. The Connection section shows the active state and endpoint; Echo appears only after a successful response.

Input rule: The payload is editable text and must not be empty. The Run Loopback button stays unavailable until the active profile is ready and a payload has been entered.

History

Description

History is the local audit trail for the app. Every command that is recorded by the view models ends up here with a title, a short result summary and optional register details when the command returned values that can be displayed meaningfully.

Filters: The filter bar can narrow by kind, outcome, sort order and optional date range.

Pagination: Pagination acts on the already filtered list, which keeps the page count stable even when many rows are hidden.

Details: Expandable rows reveal protocol ASCII details when the preference is enabled and register reads can render using the current display format.

Local record: History is stored on this device. Clear Command History is intentionally available in Preferences, not here; connection-test commands are not offered as a History command-kind filter.

Use Monitoring in Order

Start with Dashboard for the current run state and routine Run or Stop commands. Use PLC Status when a flag or unit capability needs closer inspection. Use Diagnostics when you need a small echo check of the active endpoint. Use History to review what PlcConsole recorded after the event.

In History, filter by command kind or outcome, choose newest or oldest ordering and optionally narrow results with a date range. Tap a command row to expand its details. Pagination applies after filters and sorting; protocol request and response details are shown only when enabled in Preferences and captured for that command.