Full Alarm Code Maintenance Overview
Introduction
Modern solar PV, hybrid inverter, and energy storage systems rely on sophisticated self-diagnostic mechanisms to ensure safety, availability, and compliance with grid standards. The Alarm Code Maintenance dataset provides a comprehensive reference of alarm, fault, and warning messages used across grid-connected inverters, energy storage systems (ESS), batteries.
This article explains how the alarm code structure works, how to interpret different alarm types and severities, and how installers can use the alarm library to troubleshoot systems efficiently.
Full Alarm Code Maintenance Overview is attached at the bottom of this article
This article explains how the alarm code structure works, how to interpret different alarm types and severities, and how installers can use the alarm library to troubleshoot systems efficiently.
Full Alarm Code Maintenance Overview is attached at the bottom of this article
What the Alarm Code Maintenance File Contains
The Excel file acts as a single source of truth for device diagnostics. Each record describes a specific system condition and includes:
- Device scope (Grid-only, Energy Storage-only, Battery, HUB, ALL devices)
- Alarm / Fault code and sub-code
- Fault status codes for different operating modes (grid, storage, battery)
- Alarm type (Alarm Information, Warning Message)
- Severity / grade (Tip, General, Emergency)
- Readable fault name (e.g.
OV-DC,CAN-BUS-Lose,ARC-FAULT) - Clear troubleshooting steps and corrective actions
This structure allows alarms to be handled consistently across firmware versions, device types, and system topologies.
Alarm Types Explained
1. Alarm Information
These alarms indicate abnormal operating conditions detected by the system. They are subdivided by severity:
- Tip– Informational or early-warning states that often recover automatically
- Example: temporary grid voltage or frequency fluctuations
- General– Performance or stability issues that may require inspection
- Example: communication faults with meters or auxiliary devices
- Emergency– Safety-critical faults that may shut down the system
- Example: insulation faults, overvoltage, arc fault detection
Emergency alarms almost always require immediate attention.
2. Warning Messages
Warnings indicate conditions that may reduce performance or reliability but do not necessarily stop operation. Examples include:
- PV string mismatch
- Reduced generation due to shading or contamination
- Temporary communication loss
Warnings are especially useful for proactive maintenance and performance optimization.
Common Alarm Categories
Grid-Related Alarms
These alarms focus on grid safety and regulatory compliance:
- Over/under voltage (
OV-G-V,UN-G-V) - Over/under frequency (
OV-G-F,UN-G-F) - Phase errors and imbalance
- Grid loss or instability (
NO-Grid,Uac-Unstable)
Most grid alarms automatically reset when conditions return to normal, but recurring events usually indicate wiring issues or grid quality problems.
PV and DC Side Alarms
DC-related alarms protect the inverter from electrical stress and fire risk:
- DC overvoltage (
OV-DC,OV-MPPT) - Reverse polarity (
Reve-DC) - Insulation resistance issues (
PV-ISO-PRO) - Arc Fault Circuit Interrupter events (
ARC-FAULT,AFCI-Check)
These alarms often require on-site inspection of PV strings, connectors, cable routing, and grounding.
Battery and Energy Storage Alarms
Battery safety is handled with multi-level alarms spanning voltage, current, temperature, and communication:
- Cell and pack over/under voltage
- Overcurrent during charge or discharge
- Overtemperature and undertemperature
- State of Charge (SOC) protection
- BMS communication failures
Battery alarms frequently reference the manufacturer (e.g. Bo Shi, Stellar Era), emphasizing that corrective actions may involve both inverter and battery vendor coordination.
Communication and Parallel System Alarms
Complex systems using multiple inverters, hubs, or batteries rely heavily on stable communication. Typical alarms include:
- CAN bus loss (
CAN-BUS-Lose,DCanErr) - Parallel configuration conflicts (
MulMasterErr,Addr-Conflict) - Synchronization failures (
MasterSyncLose,SlaveSyncErr)
These alarms are often resolved by checking:
- DIP switch settings
- Address assignments
- Shielded cabling and grounding
- Firmware compatibility
Why Alarm Severity Matters
The Fault Grade field is critical for prioritization:
- Tip: Monitor, no immediate action required
- General: Inspect soon, may affect performance
- Emergency: Act immediately, system protection engaged
Service teams can use this grading to automate ticket priority, dispatch decisions, and SLA handling.
Using the Alarm Library in Daily Operations
For Installers
- Validate wiring, grounding, and PV string design during commissioning
- Quickly identify installation-related issues such as reversed polarity or incorrect phase sequence
- Use alarm codes to guide first-time-fix troubleshooting
- Reduce unnecessary site visits by following structured diagnostic steps
- Escalate efficiently when alarms indicate hardware replacement or manufacturer intervention
Best Practices
- Always record alarm code + sub-code + device type when opening service tickets
- Check whether faults are self-restoring before dispatching technicians
- Ensure all parallel systems run matching firmware versions
- Treat insulation, arc fault, and battery emergency alarms as high priority
Conclusion
The Alarm Code Maintenance file is far more than a list of error messages—it is a structured diagnostic framework covering the full lifecycle of modern solar and energy storage systems. When used correctly, it shortens troubleshooting time, improves safety, and ensures consistent support across devices and markets.
