1
Motor Protection Settings
The MX-1P module does not include a built-in overload relay — motor overcurrent protection is provided by the overload relay in the existing starter. The MX-1P settings cover coil output voltage and software-level protection.
- 1COIL VOLTAGE: Before first power-on, set the coil voltage selector on the MX-1P to match your contactor coil (230V AC or 24V DC). The selector is a small switch or jumper inside the module cover — check the module label for the location.
- 2RESTART DELAY: Set a minimum restart delay to prevent rapid cycling. In the app: Device Settings → Motor → Restart Delay. Recommended: 30–60 seconds for submersible pumps to allow the water column to drain and prevent water hammer.
- 3RUNTIME LIMIT: Set a maximum continuous run time as a safety backstop. Device Settings → Motor → Max Runtime. If the pump exceeds this time without a stop command, the controller stops the motor and raises an alert.
- 4FAULT LATCH: When an overload relay trips the hardware coil circuit, the MX-1P detects the loss of motor feedback and logs a fault event. Enable Fault Latch (Device Settings → Motor → Fault Latch) to prevent automatic restart after a hardware trip — requires manual reset in the app.
2
Dry-Run Protection
Dry-run protection automatically stops the motor when the water source is empty, preventing motor burn-out from running dry. This requires an HPzenAi LS-PRE level sensor connected to the same gateway.
- 1Ensure the LS-PRE level sensor is installed in the water source (borewell, tank, or sump) and linked to the same gateway as the MX-1P.
- 2In the app, go to Automation → Add Rule.
- 3Set Trigger: Level Sensor [your sensor] → Level Low (or Tank Empty threshold).
- 4Set Action: Motor Controller [MX-1P name] → Stop Motor.
- 5Optionally add a second rule: Trigger: Level Sensor → Level Restored → Action: Start Motor (for fully automatic refill operation).
- 6Set a dry-run delay (Trigger: Level Low → Wait 2 minutes → Stop) to avoid false trips from momentary sensor fluctuations.
- 7Test the protection: manually trigger the level-low condition in the app (Sensor → Simulate → Low) and confirm the motor stops.
3
Scheduling
- 1Open the motor controller tile in the app and tap Schedules → Add Schedule.
- 2Set the schedule type: Daily (runs at the same time every day) or Weekly (select specific days).
- 3Set the Start Time and Stop Time for each scheduled run period.
- 4Multiple schedule entries can be added — for example, morning run (06:00–08:00) and evening run (18:00–19:30).
- 5Enable or disable individual schedules without deleting them using the toggle on each schedule entry.
- 6Schedules are executed by the gateway — the motor will run on schedule even if the app is not open, as long as the gateway has power and connectivity.
4
Automation Rules
- 1Automation rules allow the motor controller to respond to inputs from other devices on the same gateway — level sensors, timers, relay controllers, or remote triggers.
- 2Example — Tank Fill: Level Sensor Low → Start Motor; Level Sensor Full → Stop Motor. Creates a fully automatic fill cycle.
- 3Example — Irrigation Sync: Relay Controller Zone 1 ON → Start Motor; Relay Controller Zone 1 OFF → Stop Motor. Syncs the pump to valve zones.
- 4Example — Time Override: Manual Stop command from app overrides any active schedule or automation rule immediately.
- 5Rules are created at Automation → Add Rule. Each rule has a Trigger (device state or time), optional Conditions (e.g., only run between 06:00–20:00), and an Action (start, stop, alert).
- 6Rules run on the gateway — they work even without an active internet connection as long as the gateway and devices are online on the local RS485 bus.
5
Alerts & Notifications
- 1Enable push notifications in the app: Account → Notifications → Motor Controller Alerts → On.
- 2FAULT ALERT: Triggered when the MX-1P detects loss of motor feedback (overload relay trip, phase loss, or hardware fault). Configure at Device → Alerts → Fault Alert.
- 3DRY-RUN ALERT: Sent when the level sensor triggers a dry-run stop. Sent with the sensor reading and time of event.
- 4RUNTIME ALERT: Triggered when the motor exceeds the configured Max Runtime. Configure threshold at Device Settings → Motor → Max Runtime Alert.
- 5OFFLINE ALERT: Sent when the device loses RS485 communication with the gateway for more than the configured timeout period. Configure at Device → Alerts → Offline Alert → Timeout (recommended: 5 minutes).
- 6All alert events are also logged in the device event history: Device → Event Log.