Easy Modbus
  1. Home
  2. Modbus register maps
  3. Morningstar
  4. SunSaver MPPT solar charge controller (Modbus RTU via MeterBus)

Solar charge controller (MPPT, battery charger) · Modbus register map

Morningstar SunSaver MPPT solar charge controller (Modbus RTU via MeterBus) Modbus register map

Updated 17 November 2026

Short answer

The SunSaver MPPT is a Morningstar MPPT solar charge controller with a load output. It speaks Modbus RTU on its RJ-11 meter port through Morningstar's MSC adapter (MeterBus to RS-232). RAM registers give battery, array and load readings, charge and load state and fault bitfields; EEPROM registers hold the charge setpoints and LO-first copies of the Ah and hour counters; coils force load/charge disconnect and clear counters.

This page lists 56 Modbus registers for the Morningstar SunSaver MPPT solar charge controller (Modbus RTU via MeterBus) — 21 writable — with the table, 0-based wire address, data type, word order, scale, units and access of each, re-typed from Morningstar’s own free documentation (linked below) and checked against it.

Manufacturer
Morningstar
Model
SunSaver MPPT solar charge controller (Modbus RTU via MeterBus)
Equipment type
Solar charge controller (MPPT, battery charger)
Registers
56 (21 writable)
Transport
Modbus RTU
Default unit ID
1
Default serial
9600 baud, 8N2
Documented addressing
hexadecimal, 0-based
32-bit word order
CDAB low word first (word-swapped)
Firmware
Va_ref_fixed registers need firmware v08 or later.
Also known as
SunSaver MPPT, SS-MPPT
Source document
SunSaver MPPT MODBUS Specification · v11 · rev. 2017-04-03
Download CSV all columns JSON Manufacturer PDF ↗

Integration notes: Morningstar SunSaver MPPT solar charge controller (Modbus RTU via MeterBus)

Integration in brief

Connect through the Morningstar MSC adapter at 9600 8N2, ID 1. Read 0x0008-0x0014 for live data; multiply raw voltages by 100/32768 and currents by 79.16/32768. Use coils 0x0001/0x0002 to switch the load or charger off remotely.

Minimum registers to map

Addresses are 0-based wire addresses. Enough to monitor and run the unit; map more as the job needs.

RegisterNameTypeWhyAccess
HR 8Adc_vb_f - battery voltageUINT16Battery voltageRead
HR 9Adc_va_f - array voltageUINT16Array voltageRead
HR 11Adc_ic_f - charging currentUINT16Charging currentRead
HR 17Charge stateUINT16Charge stateRead
HR 18Array fault bitfieldBITMAP16Array faultsRead
HR 39Power_out - charge output powerUINT16Charge output powerRead
CO 1Load disconnectBITRemote load disconnectRead/write

Enable Modbus control & writes

Set the comm DIP switch (switch 4, reported as bit 3 of register 0x0025) to MODBUS protocol instead of Meterbus, and connect via the MSC RS-232 adapter.

Byte order & addressing

Network setup

Watch out for

Morningstar SunSaver MPPT solar charge controller (Modbus RTU via MeterBus) Modbus registers

Address = 0-based wire address (the documented number is shown under it when it differs) · Order: ABCD = high word first, CDAB = low word first · Scale: engineering value = raw × scale.

56 of 56 shown
Morningstar SunSaver MPPT solar charge controller (Modbus RTU via MeterBus) Modbus register map
TableAddressNameDescriptionTypeOrderScaleUnitsAccessValues / bits
CO0doc 0x0000Equalize triggeredBITRead/write
CO1doc 0x0001Load disconnect1 forces the load output off.BITRead/write
CO2doc 0x0002Charge disconnect1 forces the charger off.BITRead/write
CO16doc 0x0010Clear Ah resettableSet only; reads 0.BITWrite
CO17doc 0x0011Clear Ah totalSet only; reads 0.BITWrite
CO18doc 0x0012Clear kWhSet only; reads 0.BITWrite
CO22doc 0x0016Force EEPROM updateSet only; reads 0.BITWrite
CO255doc 0x00FFReset controlRestarts the controller (needed after EEPROM writes).BITWrite
HR8doc 0x0008Adc_vb_f - battery voltageFiltered (about 1 s).UINT16× 0.0030517578VRead
HR9doc 0x0009Adc_va_f - array voltageSolar input terminal voltage.UINT16× 0.0030517578VRead
HR10doc 0x000AAdc_vl_f - load voltageUINT16× 0.0030517578VRead
HR11doc 0x000BAdc_ic_f - charging currentUINT16× 0.0024157715ARead
HR12doc 0x000CAdc_il_f - load currentUINT16× 0.0024157715ARead
HR13doc 0x000DT_hs - heatsink temperatureINT16°CRead
HR14doc 0x000ET_batt - battery temperatureAmbient sensor, or RTS if connected.INT16°CRead
HR15doc 0x000FT_amb - ambient temperatureINT16°CRead
HR16doc 0x0010T_rts - remote temperature sensor0x80 if no RTS is connected.INT16°CRead
HR17doc 0x0011Charge stateUINT16Read0 = START; 1 = NIGHT_CHECK; 2 = DISCONNECT; 3 = NIGHT; 4 = FAULT; 5 = BULK_CHARGE; 6 = ABSORPTION; 7 = FLOAT; 8 = EQUALIZE
HR18doc 0x0012Array fault bitfieldBITMAP16Readbit 0 = Overcurrent; bit 1 = FETs shorted; bit 2 = Software bug; bit 3 = Battery HVD; bit 4 = Array HVD; bit 5 = EEPROM setting edit (reset required); bit 6 = RTS shorted; bit 7 = RTS was valid, now disconnected; bit 8 = Local temperature sensor failed
HR19doc 0x0013Vb_f - battery voltage, slow filterAbout 25 s filter.UINT16× 0.0030517578VRead
HR20doc 0x0014Vb_ref - charge target voltageTemperature-compensated regulation reference.UINT16× 0.0029500427VRead
HR25doc 0x0019kWh chargeThe spec marks it as possibly resettable.UINT16× 0.1kWhRead
HR26doc 0x001ALoad stateUINT16Read0 = START; 1 = LOAD_ON; 2 = LVD_WARNING; 3 = LVD; 4 = FAULT; 5 = DISCONNECT
HR27doc 0x001BLoad fault bitfieldBITMAP16Readbit 0 = External short circuit; bit 1 = Overcurrent; bit 2 = FETs shorted; bit 3 = Software bug; bit 4 = HVD; bit 5 = Heatsink over-temperature; bit 6 = EEPROM setting edit (reset required)
HR28doc 0x001CV_lvd - LVD voltageCurrent-compensated low voltage disconnect point.UINT16× 0.0030517578VRead
HR37doc 0x0025DIP switch settingsBITMAP16Readbit 0 = Custom battery settings; bit 1 = Custom load settings; bit 2 = Equalize enabled; bit 3 = MODBUS protocol selected (else Meterbus)
HR38doc 0x0026LED stateSOC LED pattern code (0-19).UINT16Read
HR39doc 0x0027Power_out - charge output powerUINT16× 0.0150985718WRead
HR40doc 0x0028Sweep_Vmp - array VmpFound during last MPPT sweep.UINT16× 0.0030517578VRead
HR41doc 0x0029Sweep_Pmax - array max powerFound during last sweep.UINT16× 0.0150985718WRead
HR42doc 0x002ASweep_Voc - array VocUINT16× 0.0030517578VRead
HR43doc 0x002BVb_min_dailyToday's minimum battery voltage.UINT16× 0.0030517578VRead
HR44doc 0x002CVb_max_dailyToday's maximum battery voltage.UINT16× 0.0030517578VRead
HR45doc 0x002DAhc_dailyCharge Ah today.UINT16× 0.1AhRead
HR46doc 0x002EAhl_dailyLoad Ah today.UINT16× 0.1AhRead
HR47doc 0x002FArray fault bitfield, dailySticky for the day.BITMAP16Readbit 0 = Overcurrent; bit 1 = FETs shorted; bit 2 = Software bug; bit 3 = Battery HVD; bit 4 = Array HVD; bit 5 = EEPROM setting edit (reset required); bit 6 = RTS shorted; bit 7 = RTS was valid, now disconnected; bit 8 = Local temperature sensor failed
HR48doc 0x0030Load fault bitfield, dailySticky for the day.BITMAP16Readbit 0 = External short circuit; bit 1 = Overcurrent; bit 2 = FETs shorted; bit 3 = Software bug; bit 4 = HVD; bit 5 = Heatsink over-temperature; bit 6 = EEPROM setting edit (reset required)
HR51doc 0x0033Vb_min - minimum battery voltageUINT16× 0.0030517578VRead
HR52doc 0x0034Vb_max - maximum battery voltageUINT16× 0.0030517578VRead
HR57doc 0x0039Va_ref_fixed - fixed array voltageNon-zero stops MPPT and holds this array voltage. FW v08+.UINT16× 0.0030517578VRead/write
HR58doc 0x003AVa_ref_fixed_pct - array voltage % of VocNon-zero holds array at this % of Voc. FW v08+.UINT16× 0.390625%Read/write
HR57344doc 0xE000EV_reg - regulation voltage @25°CUINT16× 0.0030517578VRead/write
HR57345doc 0xE001EV_float - float voltage @25°C0 disables float.UINT16× 0.0030517578VRead/write
HR57346doc 0xE002Et_float - absorption time before floatUINT16sRead/write
HR57351doc 0xE007EV_eq - equalize voltage @25°C0 disables equalize.UINT16× 0.0030517578VRead/write
HR57352doc 0xE008Et_eqcalendar - days between equalizeUINT16daysRead/write
HR57371doc 0xE01BEV_hvd - high voltage disconnect0 disables HVD.UINT16× 0.0030517578VRead/write
HR57372doc 0xE01CEV_hvr - high voltage reconnectUINT16× 0.0030517578VRead/write
HR57378doc 0xE022EV_lvd - load low voltage disconnectUINT16× 0.0030517578VRead/write
HR57379doc 0xE023EV_lvr - load low voltage reconnectUINT16× 0.0030517578VRead/write
HR57396doc 0xE034Emodbus_id - Modbus ID1-247.UINT16Read/write
HR57400doc 0xE038Eic_lim - charge current limitUINT16× 0.0024157715ARead/write
HR57408doc 0xE040Ehourmeter (EEPROM copy)LO word at 0xE040, HI word at 0xE041.UINT32CDABhRead
HR57414doc 0xE046EAhc_r - Ah charge resettable (EEPROM)LO word first.UINT32CDAB× 0.1AhRead
HR57416doc 0xE048EAhc_t - Ah charge total (EEPROM)LO word first.UINT32CDAB× 0.1AhRead
HR57418doc 0xE04AEkWhc - kWh charge (EEPROM)The spec marks it as possibly resettable.UINT16× 0.1kWhRead

Notes on this map

Check it against the live device. A register map tells you what the controller can expose; the unit in front of you may differ by firmware or options. Read a few registers and compare them with the unit’s own display; for a 32-bit value the float and byte-order decoder shows all four word orders at once, so a wrong word order or scale is obvious. New to this? Read what a register map is and why addresses are off by one.

Questions about the Morningstar SunSaver MPPT solar charge controller (Modbus RTU via MeterBus)

What Modbus registers does the Morningstar SunSaver MPPT solar charge controller (Modbus RTU via MeterBus) have?

This map lists 56 registers: 8 coils, 48 holding registers. 21 of them can be written. Registers vary with firmware, options and configuration, so confirm against the device.

Are the Morningstar SunSaver MPPT solar charge controller (Modbus RTU via MeterBus) Modbus addresses 0-based or 1-based?

The manufacturer's document numbers registers hexadecimal, 0-based. Every address on this page is the 0-based wire address you put in the request; the documented number is shown under it where it differs. Morningstar prints a PDU address (hex, goes on the wire as-is) and a logical address (PDU + 1). The manual states all listed addresses are request-PDU addresses; its scaling example reads battery voltage at 0x0008.

What byte order does the Morningstar SunSaver MPPT solar charge controller (Modbus RTU via MeterBus) use for 32-bit values?

Multi-register values in this map use CDAB (low word first (word-swapped)). Set your client to this order for every 32/64-bit value in the table.

What are the minimum Modbus registers to integrate the Morningstar SunSaver MPPT solar charge controller (Modbus RTU via MeterBus)?

Start with HR 8 Adc_vb_f - battery voltage (Battery voltage); HR 9 Adc_va_f - array voltage (Array voltage); HR 11 Adc_ic_f - charging current (Charging current); HR 17 Charge state (Charge state); HR 18 Array fault bitfield (Array faults); HR 39 Power_out - charge output power (Charge output power); CO 1 Load disconnect (Remote load disconnect).

How do I enable Modbus control of the Morningstar SunSaver MPPT solar charge controller (Modbus RTU via MeterBus)?

Set the comm DIP switch (switch 4, reported as bit 3 of register 0x0025) to MODBUS protocol instead of Meterbus, and connect via the MSC RS-232 adapter.

Where is the official Morningstar SunSaver MPPT solar charge controller (Modbus RTU via MeterBus) Modbus documentation?

The source is SunSaver MPPT MODBUS Specification (v11), revision 2017-04-03, published free by Morningstar at https://www.morningstarcorp.com/wp-content/uploads/technical-doc-sunsaver-mppt-modbus-specification-en.pdf.

More Morningstar Modbus register maps

Other solar & battery inverters register maps

All solar & battery inverters Modbus register maps →

Source: SunSaver MPPT MODBUS Specification · v11 · rev. 2017-04-03. Register numbers, types, scaling and units are reproduced as published; descriptions are our own.