EPever MPPT Solar Charge Controller Monitoring Hardware

Cheaper MPPT solar charge controllers have become ubiquitous. Many of these sport RS232 or RS485/Modbus ports allowing the controllers to be extended via proprietary hardware/software for advanced monitoring and control use-cases.

Since this Spring I have been experimenting with the EPever (EPSolar) line of MPPT solar charge controllers which have RS485 interfaces and thought it would be worthwhile to share my learnings in the hope they will be useful to others.

This post will focus on the specific hardware I worked with, however the techniques are applicable to similar hardware.

At the bottom of this post I have linked to similar projects and build logs - while there are many, I believe the content here adds materially in terms of discussing the downsides of using the Raspberry Pi for this application and, for the esp8266 part of the build, showing the simpler wiring which results from choosing an RS485 adapter which does automatic flow control.

The First Pi

Early in the Spring I was configuring a couple tiny independent solar systems - one to power networking hardware to get internet on an off-grid property from a local WISP and another to provide incidental power for the construction phase of my skoolie conversion.

Naturally, I wanted to capture data on the performance of these systems over time to help gain a more intuitive hands-on understanding of the power small "renewable" energy systems can provide. Also I anticipate the data will be helpful in understanding the aging of the systems' batteries - and possibly panels.

My initial attempts involved a Raspberry Pi 3B and a RS485-to-RS232 adapter. I used a bit of python code and the excellent epsolar-tracer library to poll the Tracer 3210AN and publishing metrics to Carbon/Graphite.

After a fairly steep learning curve with half-duplex RS485 adapters, I got that working and was pleased to have some day-over-day performance data.

At this point my main complaint was that since only one device can connect to the RS485 port at a time, I couldn't have both remote monitoring and the handy MT-50 connected simultaneously.

The Second Pi

I set out to figure out how to get both the local display and remote monitoring working at the same time.

Since the Raspberry Pi only has 1 hardware serial port, I got some USB serial adapters and decided to proxy requests from the MT-50 while still polling for data to publish to Carbon.

Proxying the requests was unexpectedly complicated because I discovered that the MT-50 doesn't read data via the documented modbus commands. Most important of the undocumented commands the MT-50 uses is one for reading sparse/discontiguous registers which I have documented in this gist.

With the protocol bits figured out and a nice watertight box, I had a passable system component which publishes metrics and still allows the local display to work.

A Raspberry Pi in a watertight box with dual usb-serial and RS232-to-RS485 adapters

Unfortunately, there were still several issues with this strategy;

  • Raspberry Pi fail due to how quickly SD cards wear out and result in filesystem corruption - this is supposedly surmountable by limiting or completely disabling writes, but I haven't figured out how to do this while still keep the ability to remotely push control-program/OS updates
  • Raspberry Pi use quite a bit of energy - over 1 watt even idle
  • The easiest way I found to securely publish to Carbon was via an SSH tunnel which adds unnecessary complexity and failure-points
  • The Raspberry Pi is powered from the 'load' output of the charge controller - meaning the Pi can't be used for toggling power to the load without also turning itself off

And Now for Something A Little Different

I decided to drop the Raspberry Pi and MT-50 in favor of a much simpler component built around the esp8266. This has a number of advantages;

  • Low power - I haven't spent much effort optimizing here, but it seems to be on the order of half a watt under load
  • Reliability - there are many fewer points of failure without the complexities of a full OS/filesystem/etc while still supporting remote updates
  • 1 plug - since the esp8266 uses so little power, it can powered directly via the charge controller's RS485 port allowing for the unit to remain powered even when the charge controller load output is off

Maintaining the ssh tunnel from the esp8266 didn't seem practical so I switched to publishing the metrics to an authenticated InfluxDB endpoint over HTTPS.


Consumable materials used in this build

The Build

Wiring diagram showing RS485 connection through adapter to ESP8266

Start by stripping about 2" of the outer ethernet cable housing and removing the striped wires. The ground and +5v - brown and orange respectively - are left long while the RS485 A/B wires are trimmed short.

Detail image showing preparation of the cable for connection to the RS485 adapter

Next the RS485 adapter is grounded.

Detail image showing one approach for grounding the RS485 adapter

Then jumper wires are added to the adapter and the whole thing is assembled into the case.

Image showing the assembled case lid, cable, adapter, and jumper wires

Here is the fully assembled unit connected and powered up.

Image showing the fully assembled unit connected and powered up

Note: for initial programming via USB it is necessary to disconnect the green (RX) wire from the esp8266. After initial programming, OTA updates can be used to avoid that step.

In a future post I will share some sample code and provide power usage benchmarks.

Raspberry Pi