A configuration mismatch between the PCS (aPower, the inverter/charger) and aGate (EMS/controller) triggers protective safety behaviors, communication errors, and operational limitations — this is not a fault but a deliberate safeguard to protect the system.

Main Consequences of Conflict

1. Communication Loss & System Instability

2. PV Disconnection & Generation Curtailment

3. Battery Protection & Charging Limits

4. Grid‑Tied/Backup Mode Failures

Common Conflict Scenarios

PV string mismatch: PCS configured for 2 DC strings; aGate set for 3 strings.

Non‑export rule conflict: PCS allows export; aGate enforces HECO/CA non‑export.

Grid code mismatch: PCS set for US grid; aGate set for international grid.

Firmware version gap: Outdated PCS firmware incompatible with aGate EMS.

Resolution Steps

Re‑sync configurations: Use the FranklinWH App (installer account) to reset PCS/aGate settings to match the site’s utility rules (e.g., HECO CSS, NEM‑MT).

Update firmware: Upgrade both aGate and aPower/PCS to the latest compatible firmware to eliminate version conflicts.

Verify CAN wiring: Check CAN IN/OUT cables (568B standard) for correct connections; test with a cable tester.

Reboot system: Power off aGate and all aPower units for 2 minutes, then restart to re‑establish communication.

Re‑commission: If issues persist, have a FranklinWH‑certified installer re‑commission the system to align PCS and aGate configurations.

Key Note

Configuration conflicts are preventable and resolvable. The system’s protective responses (PV disconnection, charging limits) are designed to avoid equipment damage and safety hazards. Always ensure firmware and settings are aligned during installation or maintenance.

Support Articles

Role

Region

Language