EPEVER WiFi Adapter 2.4G RJ45 D
Users can remotely monitor the connected devices and program parameters via the EPEVER server platform, mobile APP.
The EPEVER WiFi 2.4G RJ45 D WiFi adapter is mainly used for real-time transmission of various power generation data from EPEVER controllers, inverters, hybrid inverter chargers, etc. to the EPEVER cloud server. It supports wireless monitoring and parameter setting of on-site devices via cloud servers, mobile apps, or large screens.
Note: the WiFi 2.4G RJ45 D module is specifically designed to be compatible with the Solar Guardian app.
Solar Guardian APP currently supports XTRA, Triron, Tracer-AN(10-40A), Tracer-AN(50-100A), IPower-Plus, IPT, HPS-AL, HPS-AHL, UPower-Hi, Tracer-CPN series.
| Parameter | EPEVER WiFi 2.4G RJ45 D |
| Working voltage | 5V± 0.5V(Powered by RS485 com. port) |
| Power consumption | Peak emission: 150mA; Idle: 310uA |
| Enclosure | IP54 |
| Communication method | RS485 |
| Communication parameters | 115200Bps, 8N1 |
| Communication protocol | EPEVER communication protocol V1.1 |
| Interface standard | EPEVER general communication standardV1-1.0 |
| Working frequency | 2.4 ~ 2.4835GHz |
| Environment temperature | -40℃~ 85℃ |
| Dimension | 63* 19* 10mm |
| Net weight | 7.7g |
| Note: The WiFi adapter working voltage is 4.5V~5.5V and peak emission is 150mA, which is only suitable for devices that meet this requirement. | |
EPEVER WiFi 2.4G RJ45 D-Datasheet-EN
EPEVER WiFi 2.4G RJ45 D-Datasheet-EN
EPEVER WiFi 2.4G RJ45 D-Manual-EN-V1.3
EPEVER WiFi 2.4G RJ45 D-Manual-EN-V1.3
Product Highlights
2.4G WiFi Networking Communication
Works with Controllers, Inverters, and Inverter Charger with RJ45 Interface
Plug-and-Play with Easy Setup
Communication Port Powered Directly, No External Power Required
Communication Distance: Up to 20 Meters
Support Two Working Modes: Offlfline Monitoring; WIFI Data Upload to the Cloud
Tamas –
Greetings,
Very good product, I use it for an UPower-HI without issues.
My question: I would like to collect telemetry data in my own database instead of solarguardian. I can set a different mqtt server on configuration page and I get the subscription from the inverter (to /iot/mt/DEVICE topic). But then nothing happens, I guess the inverter is waiting for some sort of commands. Analysing the communication to solar guardian didn’t help me as it seemd to be a different protocol. Does solar guardian cloud have an API to get the data or do you have a manual how to use to mqtt?
Thank you