What this page solves

Remote connect/disconnect modules give utilities and panel builders a safe, remotely controlled way to cut or restore power to a branch circuit or customer, with built-in state feedback and fault diagnostics.

Modern smart meters and low-voltage panels increasingly require remote connect/disconnect capability. Prepaid tariffs depend on controlled cut-off and reconnection, field visits are expensive, and safety incidents may demand rapid disconnection of a single user or branch circuit. A remote connect/disconnect module makes it possible to perform these actions from a control room or cloud platform while still knowing whether the switching device actually opened or closed.

Traditional breakers and contactors remain the primary protection devices and are usually operated locally. A remote connect/disconnect module is different: it acts as a commanded actuator inside a smart meter or LV panel, linked to a controller and head-end system, and reports state and fault information through its sensing path. This page focuses on that switching actuator for low-voltage AC lines; energy metering accuracy, residual-current protection, insulation monitoring and LV panel-wide control are handled on dedicated pages elsewhere in the smart grid cluster.

Scope & boundaries for Remote Connect/Disconnect

This page focuses on the remote switching actuator inside a smart meter or low-voltage panel: the solid-state or relay-based element that opens and closes the branch circuit on command, together with its driver, sensing and diagnostics path. Related smart grid functions such as metering accuracy, ground-fault protection, insulation monitoring and LV panel-wide control are covered on dedicated pages so that topics do not overlap.

This page focuses on:

• Remote switching devices for LV AC circuits, including single- and bi-directional SSRs, MOSFET bridges and latching relays used to connect or disconnect a customer or branch.
• Driver and logic interfaces between the meter or panel controller and the switching element, with or without galvanic isolation depending on the chosen topology.
• Electrical state detection of the branch (open, closed or stuck) using voltage and current feedback around the remote connect/disconnect device.
• Local fault and lifetime diagnostics within the remote C/D module, including short-circuit, over-temperature and failed-operation reporting back to the controller or head-end.

This page does not cover:

• Energy metering accuracy, anti-tamper algorithms or tariff profiles, which are handled on the Smart Meter (Single-/Three-Phase) page.
• LV panel-wide busbar current, thermal monitoring and multi-branch coordination, which belong to the Smart LV Panel Unit topic.
• Residual-current and ground-fault protection functions, including leakage thresholds and tripping curves, which are discussed under Ground Fault / Leakage Monitor.
• Insulation monitoring of feeders and equipment, including injection methods and response thresholds, which is covered on the Insulation Monitoring (MV/LV) page.
• General-purpose high-voltage isolation components and sensing front-ends, which are treated in the HV Isolation & Sensing topic.

Typical deployment scenarios

Use these patterns to map a project to a known scenario. Each example shows who issues the remote connect/disconnect command, what LV voltage and current range is typical, and how the remote C/D module acts as a controlled actuator rather than a primary protection device.

Electrical architecture & switching devices

A remote connect/disconnect module must switch mains-rated AC safely and repeatedly. Typical installations involve 50/60 Hz, 120–230 V single-phase or 230/400 V three-phase circuits, with inrush currents far above the nominal rating and potential short-circuit currents that are ultimately interrupted by breakers and protection relays. The switching element and its architecture need to withstand these stresses without welding, nuisance failures or unsafe leakage paths.

Remote connect/disconnect designs typically use one of three device families: mechanical latching relays or compact contactors, solid-state switches based on triacs, thyristors or back-to-back MOSFETs, and hybrid solutions that combine a solid-state path with a relay contact. Each choice affects conduction loss, audible noise, mechanical wear, surge capability and the complexity of the driver and sensing circuits around it.

The switching topology can break only the line conductor, use a bidirectional solid-state device on AC mains or disconnect all poles in applications that demand higher safety. Understanding the trade-offs between latching relays, solid-state switches and hybrids is a key step before sizing drivers, isolation and state-detection circuits in the following sections.

Latching relays fit many cost-sensitive residential meters where operations per day are modest. Solid-state switches suit fast or frequent connect/disconnect and acoustically sensitive environments. Hybrid solutions appear in higher-current branches where reduced loss and extended lifetime justify the extra circuitry. These decisions set the tone for driver, isolation and sensing design in the remote connect/disconnect module.

Driver & control path

The driver and control path translates high-level connect or disconnect commands into safe, repeatable actuation of the remote C/D switch. Commands from the meter MCU or panel controller travel through digital interfaces and optional isolation before a driver stage generates the required coil current or gate voltage. The same path also carries status and fault information back from the switching device towards the control system.

Control inputs

• Simple digital outputs from the meter MCU or panel controller drive single-line on/off signals or complementary set/reset pulses for latching relays.
• Pulse-width or timing-controlled outputs define coil energisation time or gate drive duration, avoiding over-energising the remote C/D device.
• SPI or I²C interfaces configure advanced driver ICs and read back fault flags, enabling multi-channel remote disconnect modules in compact form factors.

Driver stage options

• Non-isolated drivers are used when the remote C/D element shares a common reference with the logic domain, for example in low-side arrangements or low-voltage sections.
• Isolated drivers are required when the switching device sits on the mains side and the meter MCU or panel controller is on a safety-isolated low-voltage domain.
• Latching relays require bidirectional or H-bridge style drivers that can deliver short set and reset pulses, while MOSFET and SSR devices need controlled gate drive with appropriate dv/dt immunity.

Auxiliary supplies and protection

• Driver stages require auxiliary supplies that match the coil voltage or gate drive level, often derived from the meter or panel auxiliary rails with local decoupling.
• Latching relays benefit from energy storage capacitors that guarantee a defined pulse even under brown-out conditions, while avoiding continuous holding current.
• Integrated driver protection typically covers overcurrent, overtemperature and shorted outputs, allowing the control system to detect abnormal switching attempts and log faults.

A well-designed driver and control path keeps logic interfaces simple, manages auxiliary power efficiently and exposes clear fault flags. These choices directly influence how reliably the remote connect/disconnect module responds to commands and how effectively the control system can supervise switching behaviour in the field.

State detection & confirmation

In a remote connect/disconnect design the controller cannot rely on visual inspection or mechanical feel to know whether the switch truly opened or closed. Reliable state detection combines electrical feedback and decision logic to confirm that a command has produced the intended result, to detect welded or stuck contacts and to distinguish upstream outages from local switching faults.

Electrical feedback methods

• Load current sensing uses a shunt or current transformer to verify that current falls to a low threshold after an open command and rises to an expected band after a close command.
• Load-side voltage sensing monitors the voltage on the downstream side of the remote C/D device to distinguish a true open circuit from a welded contact or upstream outage.
• Line-versus-load comparison evaluates both sides of the switch to decide whether the branch is simply unpowered or whether the remote C/D device failed to change state.
• Auxiliary contacts on relays can report mechanical position but still need to be combined with electrical measurements for safety-critical confirmation.
• Integrated diagnostics from solid-state switches provide overcurrent, overtemperature and fault flags that complement external voltage and current sensing.

Logic to qualify on/off state

• A timing window between issuing a command and sampling feedback allows mechanical movement and current zero crossings to complete before evaluating the state.
• Combined thresholds on voltage, current and device fault flags classify outcomes such as ON_OK, OFF_OK, welded contact, open-circuit or unknown.
• Welded contacts are detected when an open command is followed by persistent downstream voltage or current that exceeds defined off-state limits.
• In lightly loaded or no-load conditions, voltage feedback and auxiliary contacts are used to confirm a successful close event even if current remains near zero.
• Debounce and minimum-stability timers prevent transient spikes and noise from causing false state changes or spurious fault flags.

Robust state detection turns a basic remote switch into a supervised actuator that can be trusted in prepaid metering, commercial load control and public charging. Combining well-designed sensing paths with clear decision logic makes it possible to log failures, flag unsafe conditions and support field diagnostics over the lifetime of the equipment.

Fault & protection strategies

A remote connect/disconnect module must cope with inrush currents when closing, cooperate with upstream breakers during short circuits and handle long-term overload and thermal stress. Protection strategies define how the switch behaves around turn-on events, how fast it reacts to abnormal currents and whether it fails in a safe or secure default state when something goes wrong.

Inrush and turn-on behaviour

• Many loads present inrush currents several times higher than nominal, especially motors, compressors, switched-mode power supplies and capacitive input stages.
• Solid-state switches and relay contacts must be sized and driven with these peaks in mind to avoid exceeding their safe operating area during the first few milliseconds.
• Zero-cross switching with triacs or SSRs can reduce stress by turning on near mains voltage zero, while mechanical relays may rely on timing and upstream soft-start circuits.
• In systems with dedicated pre-charge or soft-start paths, the remote C/D module should coordinate sequencing rather than trying to absorb all inrush energy directly.

Design tip: size the switching element and driver for the worst-case inrush profile of the installation, not just the nominal current printed on the breaker.

Short-circuit and overload coordination

• Upstream breakers and protection relays are responsible for interrupting kA-level short-circuit currents and enforcing coordination rules for the installation.
• The remote C/D module can still implement fast electronic cut-off thresholds to limit energy in solid-state switches before the breaker trips.
• I²t and pulse energy ratings from device datasheets guide how long a switch may carry an overload before a controlled shut-down is required.
• Repeated overloads and moderate overcurrents should be tracked as stress events and linked to thermal design and derating rather than ignored.

Design tip: let breakers and protection relays handle hard faults, while the remote C/D module limits energy and avoids repeated abuse of the switching device.

Fail-safe and fail-secure behaviour

• Fail-safe behaviour aims for a default-open outcome so that loss of control, power or severe internal faults remove energy from the branch and reduce safety risk.
• Fail-secure behaviour keeps the circuit energised across certain faults where loss of power would be more hazardous or unacceptable, and requires careful system-level justification.
• Latching relays can preserve their last state through power loss, so system logic must define whether power-up sequences should restore, open or close the remote C/D path.
• Solid-state devices naturally turn off when drive is removed, which often aligns with fail-safe requirements but may need redundancy in critical circuits.

Design tip: define fail-safe or fail-secure behaviour at system level first, then select device types and default states to enforce that choice under realistic fault scenarios.

Diagnostics, lifetime & logging

A remote connect/disconnect module becomes more valuable when it is treated as a monitored asset rather than a hidden switch. Diagnostics and logging functions track operations, electrical stress and fault history so that utilities and panel operators can plan maintenance, understand failures and decide when a relay or solid-state stage is approaching the end of its useful life.

Diagnostic parameters inside the module

• Operation counters record how many open and close actions have been executed, and can distinguish between loaded and no-load switching.
• Load profile snippets capture peak current and basic duration information around each switching event to characterise stress without storing full waveforms.
• Temperature metrics track maximum observed temperature and accumulated time spent above key thresholds, reflecting thermal ageing of the switch.
• Fault logs record the last fault reason, such as suspected welded contact, overcurrent, overtemperature or driver error, along with counters for each category.
• Simple health indicators can be derived from these parameters, such as a remaining lifetime estimate or health grade for the remote C/D module.

Storage and retention

Reporting and maintenance planning

• Diagnostic parameters can be exposed as structured fields such as total operations, last fault reason, last fault timestamp and hours in on-state.
• Periodic reports carry slowly changing metrics like lifetime counters, while event reports focus on new faults and abnormal switching attempts.
• Simple rules can flag when operation counts or stress metrics approach predefined thresholds based on relay or switch lifetime ratings.
• Head-end systems use these fields to prioritise replacements, schedule maintenance windows and avoid unnecessary truck rolls for healthy devices.
• Even without complex analytics, consistent logging and reporting greatly improves visibility of how remote disconnect hardware behaves in real-world duty cycles.

Treating the remote connect/disconnect path as a monitored component rather than a black box enables targeted maintenance, better field diagnostics and more predictable lifecycle planning for meters and low-voltage panels.

Variants & selection guide

Remote connect/disconnect functions can be implemented with latching relays, solid-state switches or hybrid combinations. The best choice depends mainly on current level, operation frequency and installation context, such as integrated inside a smart meter, mounted in a low-voltage panel or delivered as a stand-alone module.

Matching device type to application

Recommended combinations by scenario

For prepaid residential meters carrying tens of amperes and operating only a few times per year, a latching relay integrated inside the meter enclosure is usually the most efficient option, paired with a low-power driver and basic diagnostics.

For commercial building branch circuits that support lighting or HVAC control, solid-state switches offer silent and frequent operation in a compact panel-mounted form, provided leakage current and thermal performance are acceptable.

For industrial feeders, public EV chargers and harsh-duty loads, hybrid relay plus SSR modules combine fast electronic protection with robust mechanical contacts, and are often deployed as stand-alone assemblies with their own thermal and safety approvals.

IC mapping & bill-of-material roles

A remote connect/disconnect function is built from several IC building blocks working together: switching devices, drivers and isolation, sensing and conversion, control and logging, and protection. Mapping these roles helps structure the bill of materials and compare solutions from different vendors.

Function blocks and IC roles

When shortlisting ICs, pay attention to:

• Alignment between device ratings and the installation envelope, including mains voltage, short-circuit capability and applicable grid or safety standards.
• Thermal limits and expected lifetime under real duty cycles, including inrush events and ambient temperature in sealed enclosures.
• Diagnostic and protection features that expose current limiting, overtemperature, open-load or short-circuit flags to the control and logging firmware.
• Package options, creepage and clearance that match the PCB layout rules for meters and low-voltage panels.
• Second-source strategies and long-term availability, especially for key switches and driver ICs that are hard to redesign late in the product lifecycle.

This page focuses on switching, driver, sensing and protection ICs for the remote connect/disconnect function. For metering SoCs and tariff processing, refer to the smart meter pages; for LV panel-wide busbar monitoring, see the smart LV panel unit pages; for cryptography, secure boot and key storage, follow the grid cybersecurity module topics.

Design checklist

Use this checklist as a final review before freezing the PCB and sending a remote connect/disconnect design to prototyping or certification. Each item links back to the section where the underlying assumptions, parameters and trade-offs are explained in more detail.

1. Confirm line and load assumptions: mains voltage (for example 230 V single-phase or 400 V three-phase), maximum continuous current, expected inrush and short-circuit levels are defined and used to size switches, drivers and PCB clearances (see sections H2-3 and H2-4).
2. Verify the switching device choice matches current level and operation frequency: latching relay, solid-state relay or hybrid relay + SSR. Check surge, leakage and dv/dt ratings with margin, using families such as HE/HF-class latching relays, G3VM-class SSRs or MOSFET arrays from major relay and solid-state switch vendors (see sections H2-4 and H2-9).
3. Check driver and supply margins: relay or MOSFET driver ICs must supply the required peak coil or gate current across voltage and temperature, and auxiliary supplies must tolerate worst-case inrush and brown-out. This applies to latching relay drivers, high-side drivers and isolated gate drivers from common power IC families (see section H2-5).
4. Confirm state detection coverage: current feedback, voltage feedback and any auxiliary contacts should be combined to distinguish successful operations from welded, stuck or mis-operated switches, using current-sense amplifiers and ADCs from standard metering and analog lines (see section H2-6).
5. Review fault thresholds and time constants for overcurrent, overload duration, temperature and turn-on strategy. Values should be derived from switch, driver and protection IC datasheets, including eFuse or protection switches and temperature sensors, rather than guessed (see section H2-7).
6. Ensure diagnostics and lifetime logging are implemented: total operations, last fault reason, overload counters, hours in on-state and peak inrush are defined, stored in FRAM/EEPROM or MCU flash, and mapped to upstream reporting fields for concentrators or head-end systems (see section H2-8).
7. Define and verify integration and safety behaviour on reset, power loss and firmware update: default-open or default-closed strategy, latching relay reinitialisation, interaction with breaker or protection relay trips, and how driver and protection IC enable or fault pins enforce the intended default state (see sections H2-5 and H2-7).
8. Run a sourcing and documentation check on key BOM items: chosen latching relay or SSR families, driver and isolation ICs, local MCU and protection devices should have clear lifecycle status, second-source options and access to required safety and grid documentation for the target market (see section H2-10).

If several checklist items cannot be ticked with confidence, it is usually better to revisit the corresponding sections and update switching devices, drivers or diagnostics before committing the remote connect/disconnect design to volume deployment.

FAQs about remote connect/disconnect design

This FAQ collects the most common questions engineers raise when planning or reviewing a remote connect/disconnect function. Use it as a quick way to align requirements, verify design choices and jump back to the detailed sections on architecture, protection and diagnostics.