Connect each site through an outbound agent or approved VPN without exposing a raw PLC port. PlcConsole Remote enforces tenant, permission and register-policy boundaries before commands reach the PLC.
PlcConsole stays local-first. Remote Server mode adds a managed operating path without handing raw site-network access to the operator.
Connect
Use an outbound site agent or existing VPN infrastructure while keeping PLC network coordinates out of the mobile client.
Control
Tenant scope, roles, permissions and PLC command policies are evaluated before the backend executes an operation.
Prove
Correlated events distinguish administrative changes, authorization decisions, agent state and PLC command results.
Choose a time window that matches the question, separate denied commands from operational failures and move from a signal to its detailed evidence.
Connectivity provides a route, not permission. Both models still carry PlcConsole-owned operations through the same tenant and policy checks.
Site Agent
A small site service opens the connection to PlcConsole Remote and identifies the site explicitly.
VPN Route
Use an approved VPN path where routing, firewall policy and operational ownership already exist.
Agent Estate
Keep lifecycle state separate from live connection health and retain a reviewable record when the authenticated agent version changes.
Permission grants the ability to attempt an operation. The assigned PLC policy narrows register families and address ranges before authoritative backend validation.
Policy-Bounded Commands
Policies describe allowed read, write and control rules per Fatek register family with optional ranges that respect the family address model.
Filter connection, configuration, authorization, version and command events, then inspect bounded request and result details without crowding the main table.
PlcConsole Remote is deployed for invited environments. Mobile Remote mode remains in private development and is not included in the current App Store release.
PlcConsole