image description

MorningStar TriStar 60 MPPT Solar Charge Controller

Price: £620 inc VAT (+ £135 inc VAT for the remote meter) in March 2021

Having tried several solar charge controllers in the past, and been underwhelmed by their logging capabilities, a completely different make and model was chosen to control the solar system that will be used to power some of Go Green IT's infrastructure in their datacentre.

MorningStar have been in the running for previous Solar Charge Controller purchases, but in the end were not chosen.

This time, the MorningStar TriStar 60 MPPT Solar Charge Controller was chosen for the following reasons:MorningStar TriStar MPPT 60A Solar Charge Controller

  • Ethernet connection with web gui so no poorly written or OS-specific apps would be required
  • Industry standard protocols used - RS-232, RS-485/MODBUS, and SNMP
  • Passive cooling, so no moving parts that could wear out
  • MorningStar reputation
  • Good documentation written in proper English

Build quality seems good, and unlike other cheaper charge controllers, all the cable termination is hidden behind the meter/display section (see product picture). Cable entry and exit points are available behind push-out sections of the white case on the left, right and bottom, and the smaller ones take standard M20 grommets.

The controller was connected to 4x275W TrinaSolar panels in a 2p2s configuration to give ~70V input. More will be added as time allows.

The web GUI is basic, but functional, and needs a javascript-enabled browser (likely due to the real time statistics that are displayed). It displays current values, networking information, and historical data for 90-120 days (not yet confirmed). Unfortunately, this interface is buggy, and several times over the first few days of installation, the interface crashed and most of the web page sections were blank.

Disappointingly, the firmware was "v18", even though "v32" has been available since November 2018. It was decided that the firmware should be upgraded to try and fix the problem of the buggy web GUI. Unfortunately this is only possible via RS-232, and although the manual doesn't tell you, can only happen when the device is booting. Since the upgrade, the Web GUI has been a lot more stable.

There is a reset button on the device, which can be pressed using a thin pencil or similar, but this doesn't seem to do a lot, and certainly didn't fix the problem of the buggy web GUI. The only way to properly reboot the device is to disconnect it from the battery.

Pros:

  • Meter can be attached locally (as in picture to the right), or connected via a 30m cable
  • A second meter can be daisy-chained off the first
  • Supports standard protocols for configuration and statistics
  • Good documentation, good official YouTube videos, including an introduction to MPPT and their version of MPPT here
  • Notifications can be sent via email (not tested)
  • Statistics can be logged to CSV files via the MSView software which communicates via MODBUS/TCP. (Wireshark has a good MODBUS decoder so can see what registers are being requested by MSView, and what raw values are being returned)
  • Most values can be tweaked using the MSView software, including LED states and warning levels (Windows only, wine not tested yet)
  • Someone has written a python module which outputs most of the current values to JSON
  • Hardware DIP switch to disable changes via the Web GUI (although this is the only security offered)

Cons:

  • Antiquated process for updating the firmware
  • Unit cannot be powered from solar directly, a battery must be connected
  • SNMP support actually only means SNMP Traps. No polling is supported unless you buy a Morningstar Ethernet Adapter (EMC-1) at the cost of ~£150 extra
  • MIB could not be checked for completeness before purchase, as it is only available from the device web GUI, and file only contains the following: device serial number, hardware version, firmware versions, and TrapReceiver address, so it looks like no power stats can be read.
  • Pushing the reset button quickly, which should reboot the device, does nothing (long press to start equalisation process was not tested)
  • Doesn't have a built in RTC, so I assume it calculates the day history by resetting the counts after "Night" mode is exited (probably decided by panel voltage changes)