Generic Relay
A planned Mirox-Agent application that turns the switching outputs of an mrxnode into managed, software-controlled relays — so you can drive contactors, pumps, alarms, and other on-site equipment from the same place you monitor the rest of your plant.
Planned Capability
The relay hardware exists today — the mrxnode ships with switching outputs and contact inputs. The control application that exposes those relays in the Mirox platform — switching them on and off, naming each channel, and reacting to plant conditions — is on the roadmap and has no user-facing controls yet. This page describes the intended scope.
Concept
The Mirox-Agent already runs on-site to collect data from your plant and reach its network devices. The generic-relay application extends that same on-site presence to physical switching: each relay output on the mrxnode becomes a named channel you can drive, and each contact input becomes a state the platform can read back.
Because it builds on the existing hardware and the agent's secure link to the Mirox platform, an authorized operator could control a relay from the same interface they use for monitoring — no separate switching controller to install and maintain.
Planned Features
The following are intended capabilities, not current behavior:
- Named output channels — label each relay output for what it switches (for example, a contactor, a pump, or an alarm), instead of working with bare channel numbers.
- On/off and momentary switching — hold a relay closed, or pulse it for a configurable duration.
- Input state read-back — read a contact input so the platform can show the current state of switched equipment in real time.
- Role-gated control — only operators with the appropriate job role on that plant could change a relay state.
- Audit trail — every switching action recorded alongside the rest of your plant activity for traceability.
How It Fits
The generic relay is the switching building block other on-site applications run on. Door Control, for example, is a planned application that drives these same relay outputs to release a door strike or open a gate. Both are deployed through the mrxnode on-site and would be governed by the same role model as the rest of the plant.
Related Features
- Door Control — a planned access-control application built on these relay outputs
- mrxnode — the on-site hardware that hosts the agent and its switching outputs
- Mirox-Agent Overview — the on-site agent the relay application runs on
- Permission System — the role model that would gate who can switch a relay