Monitors EPEVER XTRA and DuoRacer MPPT charge controllers via Modbus TCP.
Overview
This template reads solar charge controller data from EPEVER XTRA and DuoRacer MPPT controllers via Modbus TCP. It provides battery status, PV input values, load output, and energy consumption. Connection requires the EPEVER-TCP-RJ45 converter.
Key readings
Battery voltage and SOC
Battery temperature
PV array input power and voltage
Load voltage, current, and power
Consumed energy today
Min/Max battery voltage today
Use cases
Monitor battery voltage and state of charge on a live cloud dashboard for off-grid solar sites.
Track daily consumed energy to identify load patterns and optimize battery sizing.
Create an alert when battery voltage drops below a critical threshold to prevent deep discharge.
Compare PV array input power across multiple sites to detect panel degradation or shading issues.
Log minimum and maximum battery voltage each day to assess charging performance over time.
Review battery temperature remotely to ensure the charge controller operates within safe limits.
Installation
1Connect the EPEVER-TCP-RJ45 converter to the RS-485 port on the XTRA or DuoRacer charge controller using the supplied RJ45 cable.
2Connect the EPEVER-TCP-RJ45 converter to your local network via Ethernet, ensuring it is on the same subnet as the ModbusCloud gateway.
3Set a unique Modbus slave address on the charge controller if multiple devices share the same network.
4Connect and power on the ModbusCloud gateway (MCG or MLP series) and verify it can reach the converter's IP address.
5Import the EPEVER DuoRacer template in the ModbusCloud platform, enter the converter's IP address and the correct Modbus slave ID, and confirm data appears on the dashboard.
Things to watch for
01
Do I need the EPEVER-TCP-RJ45 converter or can I use any RS-485 to TCP adapter?
The template is designed for use with the official EPEVER-TCP-RJ45 converter. Third-party RS-485 to TCP adapters may work but can differ in default port settings or framing, which could cause communication errors.
02
Why do some values like PV input power show incorrect or very large numbers?
PV array input power, load power, battery current, and consumed energy today use uint32 registers spanning two consecutive addresses. The template handles this automatically, but if registers were manually reconfigured, verify the data type is set to uint32.
03
What baud rate and communication settings does the EPEVER controller use?
EPEVER controllers typically default to 115200 baud, 8 data bits, 1 stop bit, no parity on the RS-485 side. The TCP converter handles serial framing, so you only need to confirm the IP address and Modbus TCP port (default 502) on the gateway side.
04
Can I control the load output or change charge parameters through this template?
No. This template is read-only and does not include write commands. All control of the charge controller must be done locally on the device or through EPEVER's own configuration tools.
Registers (15)
15 read / 0 write
Name
Address
Function
Type
Unit
Access
Battery temperature
12560
FC04
uint16
°C
R
Device temperature
12561
FC04
uint16
°C
R
Battery voltage
13082
FC04
uint16
V
R
Battery's real rated voltage
12573
FC04
uint16
V
R
Battery SOC
12570
FC04
uint16
%
R
Consumed energy today
13060
FC04
uint32
Wh
R
PV array input power
12546
FC04
uint32
W
R
PV array input voltage
12544
FC04
uint16
V
R
PV array input current
12545
FC04
uint16
A
R
Load voltage
12556
FC04
uint16
V
R
Load current
12557
FC04
uint16
A
R
Load power
12558
FC04
uint32
W
R
Battery current
13083
FC04
uint32
A
R
Maximum battery voltage today
13058
FC04
uint16
V
R
Minimum battery voltage today
13059
FC04
uint16
V
R
Working with Modbus in your projects?
ModbusCloud is the hardware-plus-software platform that installers use to monitor, visualise and control Modbus devices from one portal. This template is one of hundreds you can use right away.
