The Sol-Ark error codes list identifies inverter notifications and faults affecting PV input, batteries, AC loads, utility power, generators, parallel communication, and lithium BMS links. Code meanings vary by Sol-Ark model, firmware, and operating profile, so the inverter screen, event log, and model-specific manual take priority over a generic F01-F64 chart.
Key facts at a glance
Sol-Ark codes are model and firmware dependent; the same number should not be interpreted without the displayed label and inverter model.
F16, F23, F24, and F55 can indicate dangerous PV insulation, ground, or overvoltage conditions and should not be repeatedly reset.
F35, F45, F47, and F48 commonly relate to missing, abnormal, or unstable AC utility conditions.
F58 usually indicates lost communication between a closed-loop lithium battery and the inverter.
A blank screen does not prove that PV conductors, battery terminals, or internal capacitors are de-energized.
A recurring code after one controlled restart is evidence of an unresolved electrical, configuration, or communication problem.
What Does a Sol-Ark Error Code Mean?
A Sol-Ark error code is a diagnostic identifier generated when measured voltage, current, frequency, temperature, communication, or switching behavior falls outside an allowed condition. The inverter may stop one function, disconnect from a source, transfer to another operating mode, or latch a protective shutdown depending on the code and the model.
Sol-Ark hybrid inverters continuously monitor DC PV input, battery voltage, AC input, load output, generator signals, internal temperature, and communications buses. A short grid disturbance can create a temporary notification, while a ground fault or semiconductor overcurrent event can require isolation and service. The visible code is therefore a symptom, not always the failed component.
Sol-Ark documentation and installer support materials should be treated as the controlling source. Third-party lists often combine labels from the 8K, 12K, 15K, 5K, and newer product families, which can produce misleading matches. Record the exact label, not only the number.
Are all F01-F64 codes used on every Sol-Ark inverter?
No. Sol-Ark does not provide one universal interpretation that applies identically to every inverter generation, firmware release, and accessory configuration. A generic F01-F64 list is useful for triage, but the model manual and current firmware event description determine the final diagnosis.
The table below consolidates commonly documented labels and field-reported meanings. “Verify” means the code may appear differently or may not be implemented on a particular model.
| Code | Common label or meaning | Main subsystem | First diagnostic question |
|---|---|---|---|
| F01 | DC inverse or reverse-power notification | DC and parallel operation | Is one parallel inverter off while others remain active? |
| F13 | Grid mode change | Configuration | Was a grid, battery, or operating-mode setting changed? |
| F15 | AC overcurrent or overload | AC load output | Did a large load start or exceed the programmed limit? |
| F16 | GFCI failure or ground-related fault | PV and AC safety | Is there moisture, damaged insulation, or incorrect bonding? |
| F18 | AC hardware overcurrent | AC output or generator path | Is there a short circuit or motor-start surge? |
| F20 | DC hardware overcurrent | Battery or PV power stage | Did battery current or PV current surge suddenly? |
| F23 | GFCI overcurrent fault | PV insulation and ground detection | Does the fault appear only when PV is connected? |
| F24 | DC insulation fault | PV-to-ground isolation | Does rain or one PV string trigger the event? |
| F26 | Bus unbalance | Split-phase AC system | Are L1 and L2 loads materially unequal? |
| F29 | Parallel CAN bus fault | Parallel communications | Are addresses, cables, and terminators correct? |
| F35 | No utility AC detected | Grid input | Is utility voltage present at the inverter terminals? |
| F45 | AC under-voltage or over-voltage | Grid input | Does measured utility voltage leave the configured window? |
| F46 | Parallel auxiliary fault | Parallel communications | Can the master identify every slave unit? |
| F47 | AC over-frequency | Grid or generator synchronization | Is source frequency above the permitted range? |
| F48 | AC under-frequency | Grid or generator synchronization | Is source frequency below the permitted range? |
| F55 | High DC voltage | PV or battery bus | Is cold-weather PV voltage or battery voltage too high? |
| F56 | Low DC voltage | Battery bus | Has the battery reached a low-voltage or BMS cutoff? |
| F58 | BMS communication fault | Lithium battery communications | Is closed-loop CAN or RS485 data reaching the inverter? |
| F60 | Generator voltage or frequency fault | Generator input | Is the generator stable under load and within sync limits? |
| F61 | Parallel synchronization or related fault | Parallel system | Were units switched off or restarted in the correct sequence? |
Codes not shown in the table, including some entries between F02 and F64, require the exact model manual or Sol-Ark support confirmation. Publishing an invented meaning for every unused number creates a more dangerous reference than acknowledging documentation limits.
How Are Sol-Ark Faults Classified?
Sol-Ark faults generally fall into temporary, persistent, and protective conditions, although the screen label and model behavior control the classification. A notification can clear when the measured value returns to range; a latched protection event can remain active until the cause disappears and the inverter completes a controlled restart.
The important distinction is recurrence. A code that clears once during a utility disturbance is different from the same code returning every time PV, a generator, or a compressor is connected. The second pattern identifies the affected operating boundary.
| Condition type | Typical trigger | Expected behavior | User response |
|---|---|---|---|
| Temporary notification | Utility sag lasting seconds | Source disconnects or mode changes | Observe the event log and source voltage |
| Recoverable protection | Short overload or frequency excursion | Output pauses, then may resume | Reduce load and monitor recurrence |
| Latched electrical fault | Ground fault, hard short, severe overcurrent | Output remains disabled | Isolate sources and call qualified service |
| Communication fault | Lost CAN, RS485, or parallel link | Battery or parallel function changes | Check approved cable, termination, and settings |
| Configuration mismatch | Wrong battery or grid profile | Repeated warnings or poor control | Restore documented commissioning values |
| Internal hardware fault | Failed sensor, relay, or power stage | Fault returns after restart | Stop resets and escalate to Sol-Ark |
A reset is not a repair. Repeatedly clearing an overcurrent or insulation fault can stress contactors, switching devices, and connectors while leaving the original hazard energized.
Which Sol-Ark Codes Involve PV, Batteries, or Ground Faults?
PV and battery codes require the most conservative response because DC arcs can persist after AC breakers open. F16, F23, and F24 point toward ground detection or insulation problems, while F55 and F56 indicate high or low DC conditions that may originate in the array, battery, BMS, or configuration.
F16, F23, and F24: ground and insulation faults
F16, F23, and F24 can appear when a PV conductor contacts grounded metal, when water enters a damaged connector, or when array insulation resistance falls below the inverter’s detection threshold. Rain-related faults that disappear in dry weather still require repair because moisture is revealing a repeatable insulation weakness.
Common causes include pinched cable insulation, incorrectly assembled MC4 connectors, a damaged rooftop junction box, conduit water intrusion, and an unintended bond between an ungrounded PV conductor and equipment ground. A qualified technician should test strings individually with equipment suitable for the array voltage. A basic continuity check alone can miss insulation breakdown that appears only at higher voltage or in wet conditions.
F55: high DC voltage
F55 indicates that measured DC voltage exceeded a configured or hardware protection limit. A cold morning can raise PV open-circuit voltage enough to expose a string-sizing error, while an incorrect battery profile or abnormal battery charging condition can raise the battery bus.
Do not size strings from the panel’s STC voltage alone. Use the module temperature coefficient, local minimum design temperature, series count, MPPT limit, and the specific Sol-Ark model. The frequently repeated 500 V figure is not a universal permission for every Sol-Ark model or terminal; verify the product datasheet.
F56: low DC voltage
F56 commonly follows a deeply discharged battery, an undersized battery cable, a high-current motor start, or a lithium BMS shutdown. The displayed battery voltage can look acceptable at rest while collapsing under load because of poor connections, excessive cable resistance, low state of charge, or a battery protection limit.
A battery that has entered hard low-voltage protection may not accept a normal inverter restart. Follow the battery manufacturer’s wake-up procedure and do not bypass BMS protections to force operation.
| Code family | Typical field trigger | Useful observation | Unsafe assumption to avoid |
|---|---|---|---|
| F16 or F23 | Wet PV connector or conductor-to-ground leakage | Fault follows PV connection or rainfall | “The panels are disconnected, so no DC exists” |
| F24 | Reduced insulation resistance | One string differs from others during testing | “A dry-weather pass proves the array is safe” |
| F55 | Cold-weather string voltage or abnormal battery charge | Highest voltage occurs near sunrise or full charge | “STC voltage is the winter maximum” |
| F56 | Battery cutoff or voltage sag | Voltage drops sharply during load start | “The battery percentage alone proves battery health” |
| F58 | BMS data loss | Voltage remains visible but SOC or limits disappear | “Open-loop mode fixes the communication fault” |
Why Do AC, Grid, and Generator Codes Appear?
AC and source codes appear when the inverter measures excessive current, an unstable split-phase condition, missing utility voltage, or a source frequency or voltage outside its configured window. F15, F18, F20, and F26 usually relate to loads or power flow; F35, F45, F47, F48, and F60 usually relate to grid or generator quality.
Load-related codes
F15 can result from total load exceeding the inverter’s continuous output or from a programmed battery discharge limit that cannot support a starting surge. F18 is more consistent with a severe AC overcurrent event, such as a short circuit or large motor inrush. F20 concerns an abrupt DC-side current demand, often caused by a compressor, well pump, or other inductive load.
F26, labeled bus unbalance in commonly circulated Sol-Ark references, deserves split-phase testing rather than guesswork. Uneven L1 and L2 loading, incorrect wiring, or a load connected to the wrong side of the system can produce the event. A clamp meter reading under stable operation is more useful than comparing appliance nameplates.
Grid and generator codes
F35 indicates that the inverter does not detect acceptable utility input. F45 indicates utility voltage outside the configured under-voltage or over-voltage window, while F47 and F48 indicate frequency above or below that window. F60 applies to generator voltage or frequency synchronization and can occur when a generator hunts under load.
A portable generator can create multiple codes at once when its voltage regulator, frequency control, neutral arrangement, or transfer equipment does not match the installation design. Neutral-to-ground bonding must follow the Sol-Ark wiring diagram and local electrical code. Do not remove a bond or add a second bond based only on a fault-code list.
| Code | Source or load | Typical cause | Immediate low-risk check |
|---|---|---|---|
| F15 | AC load output | Combined load or battery discharge limit | Turn off large discretionary loads |
| F18 | AC output or generator breaker | Short circuit or motor inrush | Identify recently started equipment |
| F20 | Battery or PV power stage | Compressor surge or excessive DC current | Check load-start timing and current limits |
| F26 | Split-phase bus | L1/L2 imbalance or wiring issue | Compare clamp-meter readings under steady load |
| F35 | Utility input | Grid outage or open input breaker | Confirm utility presence upstream |
| F45 | Utility input | Voltage outside configured range | Measure voltage with qualified equipment |
| F47/F48 | Grid or generator | Frequency excursion | Compare source frequency with a calibrated meter |
| F60 | Generator input | Unstable generator output | Test generator unloaded and under load |
What Do F29, F46, F58, and F61 Mean?
F29, F46, F58, and F61 concern communication or coordination rather than ordinary household load size. F29 commonly identifies a CAN bus problem between parallel inverters, F46 identifies a master-to-slave registration problem, F58 identifies lost battery-management communication, and F61 is associated with parallel synchronization or related coordination behavior on some systems.
Parallel systems depend on correct unit roles, addresses, approved communication cables, termination, and synchronized firmware. A loose RJ45 plug can look like a failed inverter, while a technically intact cable with the wrong pinout can prevent a compatible lithium battery from exchanging charge and discharge limits.
F58 is especially important in closed-loop lithium operation. The inverter may lose state-of-charge data, current limits, or alarm information after communication stops. Switching permanently to open-loop voltage control can restore operation in some installations, but it removes cell-level information and must be commissioned using the battery maker’s voltage settings.
| Code | Communication path | Configuration involved | Service evidence to collect |
|---|---|---|---|
| F29 | Inverter-to-inverter CAN bus | Cable, termination, address, firmware | Master screen and all unit addresses |
| F46 | Master-to-slave auxiliary link | Slave visibility and role assignment | Parallel settings from every inverter |
| F58 | Battery CAN or RS485 link | Battery protocol, port, pinout, baud or profile | Battery model, protocol, cable part number |
| F61 | Parallel synchronization | Startup order and phase coordination | Event timestamps and unit operating states |
Battery manufacturers such as Discover publish Sol-Ark integration documents with specific communication requirements. A standard Ethernet patch cable is not automatically equivalent to a battery communication cable because connector shape does not prove pin compatibility.
How Do You Safely Reset a Sol-Ark Inverter?
A safe Sol-Ark reset begins with recording the event and following the shutdown sequence in the model-specific manual; it does not begin with repeatedly pressing a reset button. The total time is commonly 10-20 minutes for a controlled observation and discharge interval, but only a qualified person should verify de-energization or test live conductors.
Before starting
| Requirement | Typical value or condition | Why it matters |
|---|---|---|
| Event evidence | Code number, text label, timestamp, screenshot | Separates recurring faults from transient events |
| Waiting period | At least the manual-specified interval, often 10 minutes | Allows internal energy storage to decay |
| Tools for professionals | CAT-rated meter, insulated PPE, approved test leads | PV and battery DC can remain hazardous |
| Access information | Model, firmware, battery model, wiring diagram | Prevents applying the wrong sequence |
| Escalation trigger | Ground fault, smoke, heat, arcing, repeated fault | Requires qualified electrical service |
Step 1: Record the operating state
Write down the code, displayed label, battery percentage, PV voltage, battery voltage, AC input status, generator status, and active loads. Save screenshots from the Sol-Ark monitoring platform if available, because a later restart can overwrite useful context.
Step 2: Reduce and isolate loads
Turn off high-demand loads using their normal controls. A qualified person can then open the relevant AC load, grid, and generator disconnects according to the installation diagram. Do not remove covers or reach into terminals.
Step 3: Isolate DC sources
The PV disconnect and battery disconnect must be operated in the order specified for the exact inverter and battery installation. Opening an AC breaker does not isolate PV or battery energy. Rooftop strings remain energized in daylight even when the inverter display is dark.
Step 4: Wait and verify
Wait for the manual’s specified interval, commonly 10 minutes in Sol-Ark shutdown guidance, then verify status using the correct test method. A dark LCD is not a voltage measurement, and capacitors or external conductors can remain hazardous.
Step 5: Re-energize only after the cause is understood
If the event was a confirmed temporary grid interruption and no safety code remains, restore sources in the documented sequence, often battery first, followed by PV and AC sources. For F16, F23, F24, F55, persistent F18, or repeated F58, leave the system isolated and arrange service instead of testing repeated restarts.
Which Codes Can Homeowners Troubleshoot?
Homeowners can usually observe logs, reduce loads, confirm an obvious utility outage, and check whether a communication cable is visibly loose without opening the inverter. Homeowners should not test energized PV strings, alter neutral bonding, bypass BMS protections, or reset recurring ground and overvoltage faults.
Use this decision table as a boundary, not as permission to work inside energized equipment.
| Situation | Homeowner action | Qualified technician action | Stop condition |
|---|---|---|---|
| F35 during a neighborhood outage | Confirm utility outage and monitor | Test utility input and transfer equipment | Code remains after utility returns |
| F15 during appliance startup | Turn off large loads | Measure continuous and surge current | Fault returns with normal loads |
| F58 with missing SOC data | Check approved external connection | Validate pinout, protocol, and battery settings | Battery limits are unavailable |
| F55 on a cold morning | Keep PV isolated if instructed | Recalculate cold-weather string voltage | Any measured value exceeds model limit |
| F16, F23, or F24 | Do not touch PV connectors | Perform insulation and leakage testing | Rain, heat, odor, or visible damage |
| F29 or F46 in a stack | Record all unit screens | Check addressing, termination, and firmware | Units were switched under load |
An installer’s typical on-site diagnostic visit costs about $150-$400 in the United States, while PV insulation fault tracing can reach $250-$600 when roof access and connector replacement are required. These are practitioner ranges, not Sol-Ark prices, and regional labor, travel, permits, and warranty status change the total.
Why Does the Same Code Keep Returning?
A recurring code means the initiating condition remains present, the configuration does not match the equipment, or the inverter has a failing sensor, relay, communication port, or power stage. The recurrence pattern usually provides more diagnostic value than the number alone.
Track when the code appears. A fault at sunrise suggests PV voltage or insulation exposure; a fault during compressor startup suggests surge current; a fault after rain suggests moisture; and a fault after changing battery settings suggests configuration or BMS compatibility.
Three practitioner rules prevent many incorrect repairs:
- Cold-weather PV voltage is a design input, not an afterthought. Calculate maximum open-circuit voltage at the site’s design low temperature, not at the panel’s 25°C STC condition.
- Communication faults can coexist with correct battery voltage. A displayed voltage does not prove that charge current, discharge current, temperature, and state-of-charge limits are reaching the inverter.
- Parallel inverter timing matters. Switching one unit off while other units carry synchronized load can create secondary communication and phase errors that obscure the original event.
Common failure patterns
| Pattern | Most likely direction | Better next step |
|---|---|---|
| F55 only at sunrise in winter | PV string voltage margin | Recalculate cold-weather Voc |
| F24 only during rain | Wet connector or cable insulation | Insulation test each string |
| F18 when a pump starts | Motor inrush or shorted circuit | Test starting current and branch wiring |
| F58 after battery replacement | Protocol or cable mismatch | Match battery profile and approved pinout |
| F29 after adding an inverter | Address or termination error | Recommission the parallel bus |
| F35 with stable utility at panel | Breaker, wiring, or sensing path | Measure at inverter terminals |
How Do Model, Firmware, and Installation Change the Code List?
The applicable Sol-Ark model, firmware, battery protocol, and wiring topology change both the meaning and response of an error code. A code chart copied from a 15K installation should not be used to configure a 5K or newer product without checking the matching documentation.
Record these identifiers before contacting support:
- Inverter model and serial number.
- Firmware versions for the main control board and communications equipment.
- Exact code number and text label.
- Battery manufacturer, model, quantity, and closed-loop or open-loop mode.
- PV string count, module model, series count, and cold-weather design temperature.
- Grid or generator configuration, including transfer equipment.
- Whether the system is single-unit or parallel.
Sol-Ark support or an authorized installer can interpret event history more accurately when these details accompany the screenshot. The most useful report includes what changed immediately before the fault, such as heavy rain, a battery replacement, a generator start, a firmware update, or a new load.
How Much Time and Money Does Sol-Ark Fault Repair Take?
A temporary grid code may clear in 5-15 minutes after utility conditions stabilize, while PV insulation tracing commonly takes 2-5 hours and communication diagnosis often takes 30-90 minutes. Typical United States service costs range from $0 for observation of a confirmed outage to more than $800 for difficult load, wiring, or generator work.
| Problem profile | Typical duration | Typical service range | Main cost driver |
|---|---|---|---|
| Utility outage or brief frequency event | 5-15 minutes | $0-$150 | Whether a site visit is needed |
| Battery communication fault | 30-90 minutes | $100-$300 | Cable, protocol, and commissioning time |
| Parallel communication fault | 1-3 hours | $150-$500 | Number of inverters and firmware versions |
| AC overload or motor-start issue | 1-4 hours | $250-$800 | Circuit changes or soft-start equipment |
| PV insulation or ground fault | 2-5 hours | $250-$600 | Roof access and connector replacement |
| Internal inverter hardware fault | 2-8 hours or replacement lead time | $300-$2,000 plus parts | Warranty, board availability, and labor |
Do not treat a low-cost reset as a successful repair when the code returns. A recurring fault can damage equipment or create a fire and shock hazard.
What Information Should You Send Sol-Ark Support?
Send Sol-Ark support the exact code label, inverter model, firmware, event timestamp, operating mode, battery details, source status, and photographs of the screen and installation labels. A complete evidence package reduces the chance that support will recommend a generic reset for a model-specific condition.
Include the following:
- The first occurrence and recurrence pattern.
- Whether the event happens with PV, battery, grid, generator, or loads connected.
- Battery voltage, state of charge, and BMS status.
- PV voltage and weather conditions, if shown safely by the monitoring system.
- Recent wiring, firmware, battery, generator, or load changes.
- Screenshots from the inverter and monitoring application.
- Any smell, heat, visible discoloration, water entry, or sound from relays.
Do not send photographs that require removing covers or exposing live terminals. An installer can provide those images safely.
Frequently Asked Questions
Can I ignore a Sol-Ark notification if the inverter still works?
You can monitor a one-time notification caused by a confirmed utility disturbance, but you should not ignore a recurring code. Record the event and watch whether it returns under the same condition. Ground, high-voltage, overcurrent, overheating, and BMS protection messages require investigation even when backup power remains available.
Does F35 mean my Sol-Ark inverter is broken?
F35 usually means the inverter does not detect acceptable utility AC at its grid input, not that the inverter has failed. A utility outage, open breaker, transfer switch issue, loose conductor, or abnormal voltage can produce the code. If utility power is confirmed at the inverter terminals and F35 persists, qualified service should test the sensing and switching path.
Can a Sol-Ark run without a battery?
Some Sol-Ark operating modes can use PV and grid power without normal battery discharge, but the permitted behavior depends on model, firmware, settings, and local wiring. Removing or disconnecting a battery without following the installation manual can create charging, startup, or protection problems. Confirm the intended mode with Sol-Ark documentation before changing battery connections.
Why does F58 appear after installing a new lithium battery?
F58 commonly appears after a battery replacement because the inverter profile, communication protocol, cable pinout, or battery address does not match the new battery. Confirm the exact battery model’s Sol-Ark integration instructions, then check approved cabling and communication settings. Do not switch permanently to open-loop control merely to hide missing BMS data.
Is a Sol-Ark error code covered by warranty?
Warranty coverage depends on the failed component, installation quality, model warranty terms, and evidence of the fault. A manufacturing failure may qualify, while incorrect PV string sizing, water-damaged connectors, wiring errors, or unauthorized modifications may not. Preserve event logs, installer records, photographs, and serial numbers before replacing parts.
Where can I find the correct Sol-Ark error-code list?
The correct list is the manual and support documentation for the exact Sol-Ark model and firmware, supplemented by the inverter’s event log. Third-party F01-F64 charts can help identify a subsystem, but they should not override the manufacturer’s label, wiring diagram, or service instruction. Use the exact model number when searching Sol-Ark documentation.
The Bottom Line
The Sol-Ark error codes list is a starting point for identifying the affected subsystem, not a substitute for model-specific documentation or electrical testing. F35 and some brief AC events may self-clear, while F16, F23, F24, F55, persistent overcurrent codes, and recurring F58 events require controlled isolation and qualified diagnosis. Record the complete event, avoid repeated resets, and match every interpretation to the exact inverter, firmware, battery, and installation.