Giters

eModbus / eModbus

Modbus library for RTU, ASCII and TCP protocols. Primarily developed on and for ESP32 MCUs.

Home Page:https://emodbus.github.io

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Confused about the server/client stuff

Miq1 opened this issue · comments

commented

Hey, sorry to hijack this, but I keep getting confused with the modbus server/client stuff.

Let me explain what I want to do. Maybe you can help me figure out if the solution described in this thread is something for me:

Data source is a controller for an electric wall charger (with modbus 485). Register table is here: Modbus RS485.pdf. It is supported by this EV charge controller: evcc.
But I need to add it to the software via modbus over LAN/Wifi. It has to read and write registers

Is this bridge (RTU client => ESP32 BRIDGE => TCP server) correct for this use case? What confuses me is, that this snippet seems to "just" send to a modbus TCP server and as how I understand it, evcc is not a server but polls the modbus device for information or sends modbus write commands to it.

Originally posted by @emign in #211 (comment)