MC24xx

[martgras]

@phpphph

Can we continue the discussion about the device here until we found a solution.
Change logging to VERBOSE
Make sure the mcp2420 TX PIN is connect to PIN 16 of the ESP32 and MCP2420 RX is connected to PIN 17 on ESP
(if that doesn't work try TX => 17 and RX => 16)

substitutions:
  updates: 60s
  unique_id: solarstation

esphome:
  name: MCtest
  platform: ESP32
  board: esp32dev

# Enable logging
logger:
  level: VERBOSE

Please change logging to VERBOSE


uart:
  id: mod_bus
  tx_pin: 17
  rx_pin: 16
  baud_rate: 9600
  stop_bits: 1

modbus:
  #flow_control_pin: 23
  send_wait_time: 200ms
  id: mod_bus_mcp2420

modbus_controller:
  - id: mcp2420
    ## the Modbus device addr
    address: 0x1
    modbus_id: mod_bus_mcp2420
    command_throttle: 200ms
    setup_priority: -10
    update_interval: ${updates}

sensor:  
  - platform: modbus_controller
    modbus_controller_id: mcp2420
    id: array_rated_voltage
    name: "array_rated_voltage"
    address: 0xA
    unit_of_measurement: "V"
    register_type: read
    value_type: U_WORD
    accuracy_decimals: 0


  - platform: modbus_controller
    modbus_controller_id: mcp2420
    id: array_rated_current
    name: "array_rated_current"
    address: 0xB
    unit_of_measurement: "A"
    register_type: read
    value_type: U_WORD
    accuracy_decimals: 0

  - platform: modbus_controller
    modbus_controller_id: mcp2420
    name: "Battery Power SOC"
    address: 0x100
    unit_of_measurement: "%"
    register_type: read
    value_type: U_WORD
    accuracy_decimals: 0

Then add the output you get from ESP logging here

[phpphph]

[V][modbus_controller:028]: Sending next modbus command to device 1 register 0x0A count 2
[23:05:25][V][modbus:182]: Modbus write: 01.04.00.0A.00.02.51.C9 (8)
[23:05:25][V][modbus_controller:424]: Command sent 4 0xA 2
[23:05:25][V][component:186]: Component modbus_controller took a long time for an operation (0.25 s).
[23:05:25][V][component:187]: Components should block for at most 20-30ms.
[23:05:25][V][modbus_controller:028]: Sending next modbus command to device 1 register 0x0A count 2
[23:05:25][V][modbus:182]: Modbus write: 01.04.00.0A.00.02.51.C9 (8)
[23:05:25][V][modbus_controller:424]: Command sent 4 0xA 2
[23:05:25][V][component:186]: Component modbus_controller took a long time for an operation (0.24 s).
[23:05:25][V][component:187]: Components should block for at most 20-30ms.
[23:05:25][C][uart.arduino_esp8266:095]: UART Bus:
[23:05:25][C][uart.arduino_esp8266:096]: TX Pin: GPIO1
[23:05:25][C][uart.arduino_esp8266:097]: RX Pin: GPIO3
[23:05:25][C][uart.arduino_esp8266:099]: RX Buffer Size: 256
[23:05:25][C][uart.arduino_esp8266:101]: Baud Rate: 9600 baud
[23:05:25][C][uart.arduino_esp8266:102]: Data Bits: 8
[23:05:25][C][uart.arduino_esp8266:103]: Parity: NONE
[23:05:25][C][uart.arduino_esp8266:104]: Stop bits: 1
[23:05:25][C][uart.arduino_esp8266:106]: Using hardware serial interface.
[23:05:25][W][uart.arduino_esp8266:121]: You're using the same serial port for logging and the UART component. Please disable logging over the serial port by setting logger->baud_rate to 0.
[23:05:25][V][modbus_controller:028]: Sending next modbus command to device 1 register 0x0A count 2
[23:05:25][V][modbus:182]: Modbus write: 01.04.00.0A.00.02.51.C9 (8)
[23:05:25][V][modbus_controller:424]: Command sent 4 0xA 2
[23:05:25][V][component:186]: Component modbus_controller took a long time for an operation (0.25 s).
[23:05:25][V][component:187]: Components should block for at most 20-30ms.
[23:05:25][C][modbus:129]: Modbus:
[23:05:25][C][modbus:131]: Send Wait Time: 200 ms
[23:05:25][V][modbus_controller:028]: Sending next modbus command to device 1 register 0x0A count 2
[23:05:25][V][modbus:182]: Modbus write: 01.04.00.0A.00.02.51.C9 (8)
[23:05:25][V][modbus_controller:424]: Command sent 4 0xA 2
[23:05:25][V][component:186]: Component modbus_controller took a long time for an operation (0.25 s).
[23:05:25][V][component:187]: Components should block for at most 20-30ms.
[23:05:25][C][logger:233]: Logger:
[23:05:25][C][logger:234]: Level: VERBOSE
[23:05:25][C][logger:235]: Log Baud Rate: 115200
[23:05:25][C][logger:236]: Hardware UART: UART0
[23:05:25][V][modbus_controller:028]: Sending next modbus command to device 1 register 0x0A count 2
[23:05:26][V][modbus:182]: Modbus write: 01.04.00.0A.00.02.51.C9 (8)
[23:05:26][V][modbus_controller:424]: Command sent 4 0xA 2
[23:05:26][V][component:186]: Component modbus_controller took a long time for an operation (0.25 s).
[23:05:26][V][component:187]: Components should block for at most 20-30ms.
[23:05:28][C][modbus_controller.sensor:010]: modbus_controller.sensorModbus Controller Sensor 'array_rated_voltage'
[23:05:28][C][modbus_controller.sensor:010]: modbus_controller.sensor State Class: ''
[23:05:28][C][modbus_controller.sensor:010]: modbus_controller.sensor Unit of Measurement: 'V'
[23:05:28][C][modbus_controller.sensor:010]: modbus_controller.sensor Accuracy Decimals: 0
[23:05:28][V][modbus_controller:028]: Sending next modbus command to device 1 register 0x0A count 2
[23:05:28][V][modbus:182]: Modbus write: 01.04.00.0A.00.02.51.C9 (8)
[23:05:28][V][modbus_controller:424]: Command sent 4 0xA 2
[23:05:28][V][component:186]: Component modbus_controller took a long time for an operation (0.25 s).
[23:05:28][V][component:187]: Components should block for at most 20-30ms.
[23:05:28][C][modbus_controller.sensor:010]: modbus_controller.sensorModbus Controller Sensor 'array_rated_current'
[23:05:28][C][modbus_controller.sensor:010]: modbus_controller.sensor State Class: ''
[23:05:28][C][modbus_controller.sensor:010]: modbus_controller.sensor Unit of Measurement: 'A'
[23:05:28][C][modbus_controller.sensor:010]: modbus_controller.sensor Accuracy Decimals: 0
[23:05:28][V][modbus_controller:028]: Sending next modbus command to device 1 register 0x0A count 2
[23:05:28][V][modbus:182]: Modbus write: 01.04.00.0A.00.02.51.C9 (8)
[23:05:28][V][modbus_controller:424]: Command sent 4 0xA 2
[23:05:28][V][component:186]: Component modbus_controller took a long time for an operation (0.25 s).
[23:05:28][V][component:187]: Components should block for at most 20-30ms.
[23:05:28][C][modbus_controller.sensor:010]: modbus_controller.sensorModbus Controller Sensor 'Battery Power SOC'
[23:05:28][C][modbus_controller.sensor:010]: modbus_controller.sensor State Class: ''
[23:05:28][C][modbus_controller.sensor:010]: modbus_controller.sensor Unit of Measurement: '%'
[23:05:28][C][modbus_controller.sensor:010]: modbus_controller.sensor Accuracy Decimals: 0
[23:05:28][V][modbus_controller:028]: Sending next modbus command to device 1 register 0x0A count 2
[23:05:28][V][modbus:182]: Modbus write: 01.04.00.0A.00.02.51.C9 (8)
[23:05:28][V][modbus_controller:424]: Command sent 4 0xA 2
[23:05:28][V][component:186]: Component modbus_controller took a long time for an operation (0.25 s).
[23:05:28][V][component:187]: Components should block for at most 20-30ms.
[23:05:29][C][ota:082]: Over-The-Air Updates:
[23:05:29][C][ota:083]: Address: solar-mppt.local:8266
[23:05:29][C][ota:086]: Using Password.
[23:05:29][V][modbus_controller:028]: Sending next modbus command to device 1 register 0x0A count 2
[23:05:29][V][modbus:182]: Modbus write: 01.04.00.0A.00.02.51.C9 (8)
[23:05:29][V][modbus_controller:424]: Command sent 4 0xA 2
[23:05:29][V][component:186]: Component modbus_controller took a long time for an operation (0.25 s).
[23:05:29][V][component:187]: Components should block for at most 20-30ms.
[23:05:29][C][api:134]: API Server:
[23:05:29][C][api:135]: Address: solar-mppt.local:6053
[23:05:29][C][api:139]: Using noise encryption: NO
[23:05:29][V][modbus_controller:028]: Sending next modbus command to device 1 register 0x0A count 2
[23:05:30][V][modbus:182]: Modbus write: 01.04.00.0A.00.02.51.C9 (8)
[23:05:30][V][modbus_controller:424]: Command sent 4 0xA 2
[23:05:30][V][component:186]: Component modbus_controller took a long time for an operation (0.25 s).
[23:05:30][V][component:187]: Components should block for at most 20-30ms.
[23:05:30][V][modbus_controller:028]: Sending next modbus command to device 1 register 0x0A count 2
[23:05:30][V][modbus:182]: Modbus write: 01.04.00.0A.00.02.51.C9 (8)
[23:05:30][V][modbus_controller:424]: Command sent 4 0xA 2
[23:05:30][V][component:186]: Component modbus_controller took a long time for an operation (0.24 s).
[23:05:30][V][component:187]: Components should block for at most 20-30ms.
[23:05:32][C][modbus_controller:244]: ModbusController:
[23:05:32][C][modbus_controller:245]: Address: 0x01
[23:05:32][C][modbus_controller:247]: sensormap
[23:05:32][C][TAG:250]: Sensor 0x4000A00FFFFFFFF start=0xA count=1 size=2
[23:05:32][C][TAG:250]: Sensor 0x4000A02FFFFFFFF start=0xA count=1 size=2
[23:05:32][C][TAG:250]: Sensor 0x4010000FFFFFFFF start=0x100 count=1 size=2
[23:05:32][V][modbus_controller:028]: Sending next modbus command to device 1 register 0x0A count 2
[23:05:32][V][modbus:182]: Modbus write: 01.04.00.0A.00.02.51.C9 (8)
[23:05:32][V][modbus_controller:424]: Command sent 4 0xA 2
[23:05:32][V][component:186]: Component modbus_controller took a long time for an operation (0.25 s).
[23:05:32][V][component:187]: Components should block for at most 20-30ms.
[23:05:32][V][modbus_controller:028]: Sending next modbus command to device 1 register 0x0A count 2
[23:05:32][V][modbus:182]: Modbus write: 01.04.00.0A.00.02.51.C9 (8)
[23:05:32][V][modbus_controller:424]: Command sent 4 0xA 2
[23:05:32][V][component:186]: Component modbus_controller took a long time for an operation (0.24 s).
[23:05:32][V][component:187]: Components should block for at most 20-30ms.
[23:05:32][V][modbus_controller:028]: Sending next modbus command to device 1 register 0x0A count 2
[23:05:32][V][modbus:182]: Modbus write: 01.04.00.0A.00.02.51.C9 (8)
[23:05:32][V][modbus_controller:424]: Command sent 4 0xA 2
[23:05:32][V][component:186]: Component modbus_controller took a long time for an operation (0.24 s).
[23:05:32][V][component:187]: Components should block for at most 20-30ms.
[23:05:32][V][modbus_controller:028]: Sending next modbus command to device 1 register 0x0A count 2
[23:05:32][V][modbus:182]: Modbus write: 01.04.00.0A.00.02.51.C9 (8)
[23:05:32][V][modbus_controller:424]: Command sent 4 0xA 2
[23:05:32][V][component:186]: Component modbus_controller took a long time for an operation (0.24 s).
[23:05:32][V][component:187]: Components should block for at most 20-30ms.
[23:05:32][V][modbus_controller:028]: Sending next modbus command to device 1 register 0x0A count 2
[23:05:33][V][modbus:182]: Modbus write: 01.04.00.0A.00.02.51.C9 (8)
[23:05:33][V][modbus_controller:424]: Command sent 4 0xA 2
[23:05:33][V][component:186]: Component modbus_controller took a long time for an operation (0.24 s).
[23:05:33][V][component:187]: Components should block for at most 20-30ms.
[23:05:33][V][modbus_controller:028]: Sending next modbus command to device 1 register 0x0A count 2
[23:05:33][V][modbus:182]: Modbus write: 01.04.00.0A.00.02.51.C9 (8)
[23:05:33][V][modbus_controller:424]: Command sent 4 0xA 2
[23:05:33][V][component:186]: Component modbus_controller took a long time for an operation (0.24 s).
[23:05:33][V][component:187]: Components should block for at most 20-30ms.
[23:05:33][V][modbus_controller:028]: Sending next modbus command to device 1 register 0x0A count 2
[23:05:34][V][modbus:182]: Modbus write: 01.04.00.0A.00.02.51.C9 (8)
[23:05:34][V][modbus_controller:424]: Command sent 4 0xA 2
[23:05:34][V][component:186]: Component modbus_controller took a long time for an operation (0.23 s).
[23:05:34][V][component:187]: Components should block for at most 20-30ms.
[23:05:34][V][modbus_controller:028]: Sending next modbus command to device 1 register 0x0A count 2
[23:05:34][V][modbus:182]: Modbus write: 01.04.00.0A.00.02.51.C9 (8)
[23:05:34][V][modbus_controller:424]: Command sent 4 0xA 2
[23:05:34][V][component:186]: Component modbus_controller took a long time for an operation (0.24 s).
[23:05:34][V][component:187]: Components should block for at most 20-30ms.
[23:05:34][V][modbus_controller:028]: Sending next modbus command to device 1 register 0x0A count 2
[23:05:34][V][modbus:182]: Modbus write: 01.04.00.0A.00.02.51.C9 (8)
[23:05:34][V][modbus_controller:424]: Command sent 4 0xA 2
[23:05:34][V][component:186]: Component modbus_controller took a long time for an operation (0.24 s).
[23:05:34][V][component:187]: Components should block for at most 20-30ms.
[23:05:35][V][modbus_controller:028]: Sending next modbus command to device 1 register 0x0A count 2
[23:05:35][V][modbus:182]: Modbus write: 01.04.00.0A.00.02.51.C9 (8)
[23:05:35][V][modbus_controller:424]: Command sent 4 0xA 2
[23:05:35][V][component:186]: Component modbus_controller took a long time for an operation (0.24 s).
[23:05:35][V][component:187]: Components should block for at most 20-30ms.
[23:05:35][V][modbus_controller:028]: Sending next modbus command to device 1 register 0x0A count 2
[23:05:35][V][modbus:182]: Modbus write: 01.04.00.0A.00.02.51.C9 (8)
[23:05:35][V][modbus_controller:424]: Command sent 4 0xA 2
[23:05:35][V][component:186]: Component modbus_controller took a long time for an operation (0.24 s).
[23:05:35][V][component:187]: Components should block for at most 20-30ms.
[23:05:35][V][modbus_controller:028]: Sending next modbus command to device 1 register 0x0A count 2
[23:05:36][V][modbus:182]: Modbus write: 01.04.00.0A.00.02.51.C9 (8)
[23:05:36][V][modbus_controller:424]: Command sent 4 0xA 2
[23:05:36][V][component:186]: Component modbus_controller took a long time for an operation (0.24 s).
[23:05:36][V][component:187]: Components should block for at most 20-30ms.
[23:05:36][V][modbus_controller:028]: Sending next modbus command to device 1 register 0x0A count 2
[23:05:36][V][modbus:182]: Modbus write: 01.04.00.0A.00.02.51.C9 (8)
[23:05:36][V][modbus_controller:424]: Command sent 4 0xA 2
[23:05:36][V][component:186]: Component modbus_controller took a long time for an operation (0.24 s).
[23:05:36][V][component:187]: Components should block for at most 20-30ms.
[23:05:36][V][modbus_controller:028]: Sending next modbus command to device 1 register 0x0A count 2
[23:05:37][V][modbus:182]: Modbus write: 01.04.00.0A.00.02.51.C9 (8)
[23:05:37][V][modbus_controller:424]: Command sent 4 0xA 2
[23:05:37][V][component:186]: Component modbus_controller took a long time for an operation (0.24 s).
[23:05:37][V][component:187]: Components should block for at most 20-30ms.
[23:05:37][V][modbus_controller:028]: Sending next modbus command to device 1 register 0x0A count 2
[23:05:37][V][modbus:182]: Modbus write: 01.04.00.0A.00.02.51.C9 (8)
[23:05:37][V][modbus_controller:424]: Command sent 4 0xA 2
[23:05:37][V][component:186]: Component modbus_controller took a long time for an operation (0.24 s).
[23:05:37][V][component:187]: Components should block for at most 20-30ms.
[23:05:37][V][modbus_controller:028]: Sending next modbus command to device 1 register 0x0A count 2
[23:05:37][V][modbus:182]: Modbus write: 01.04.00.0A.00.02.51.C9 (8)
[23:05:38][V][modbus_controller:424]: Command sent 4 0xA 2
[23:05:38][V][component:186]: Component modbus_controller took a long time for an operation (0.24 s).
[23:05:38][V][component:187]: Components should block for at most 20-30ms.
[23:05:38][V][modbus_controller:028]: Sending next modbus command to device 1 register 0x0A count 2
[23:05:38][V][modbus:182]: Modbus write: 01.04.00.0A.00.02.51.C9 (8)
[23:05:38][V][modbus_controller:424]: Command sent 4 0xA 2
[23:05:38][V][component:186]: Component modbus_controller took a long time for an operation (0.24 s).
[23:05:38][V][component:187]: Components should block for at most 20-30ms.
[23:05:38][V][modbus_controller:028]: Sending next modbus command to device 1 register 0x0A count 2
[23:05:38][V][modbus:182]: Modbus write: 01.04.00.0A.00.02.51.C9 (8)
[23:05:38][V][modbus_controller:424]: Command sent 4 0xA 2
[23:05:38][V][component:186]: Component modbus_controller took a long time for an operation (0.24 s).
[23:05:38][V][component:187]: Components should block for at most 20-30ms.
[23:05:38][V][modbus_controller:028]: Sending next modbus command to device 1 register 0x0A count 2
[23:05:39][V][modbus:182]: Modbus write: 01.04.00.0A.00.02.51.C9 (8)
[23:05:39][V][modbus_controller:424]: Command sent 4 0xA 2
[23:05:39][V][component:186]: Component modbus_controller took a long time for an operation (0.23 s).
[23:05:39][V][component:187]: Components should block for at most 20-30ms.
[23:05:39][V][modbus_controller:028]: Sending next modbus command to device 1 register 0x0A count 2
[23:05:39][V][modbus:182]: Modbus write: 01.04.00.0A.00.02.51.C9 (8)
[23:05:39][V][modbus_controller:424]: Command sent 4 0xA 2
[23:05:39][V][component:186]: Component modbus_controller took a long time for an operation (0.24 s).
[23:05:39][V][component:187]: Components should block for at most 20-30ms.
[23:05:39][V][modbus_controller:028]: Sending next modbus command to device 1 register 0x0A count 2
[23:05:40][V][modbus:182]: Modbus write: 01.04.00.0A.00.02.51.C9 (8)
[23:05:40][V][modbus_controller:424]: Command sent 4 0xA 2
[23:05:40][V][component:186]: Component modbus_controller took a long time for an operation (0.24 s).
[23:05:40][V][component:187]: Components should block for at most 20-30ms.
[23:05:40][V][modbus_controller:028]: Sending next modbus command to device 1 register 0x0A count 2
[23:05:40][V][modbus:182]: Modbus write: 01.04.00.0A.00.02.51.C9 (8)
[23:05:40][V][modbus_controller:424]: Command sent 4 0xA 2
[23:05:40][V][component:186]: Component modbus_controller took a long time for an operation (0.24 s).
[23:05:40][V][component:187]: Components should block for at most 20-30ms.
[23:05:40][V][modbus_controller:028]: Sending next modbus command to device 1 register 0x0A count 2
[23:05:41][V][modbus:182]: Modbus write: 01.04.00.0A.00.02.51.C9 (8)
[23:05:41][V][modbus_controller:424]: Command sent 4 0xA 2
[23:05:41][V][component:186]: Component modbus_controller took a long time for an operation (0.24 s).
[23:05:41][V][component:187]: Components should block for at most 20-30ms.
[23:05:41][V][modbus_controller:028]: Sending next modbus command to device 1 register 0x0A count 2
[23:05:41][V][modbus:182]: Modbus write: 01.04.00.0A.00.02.51.C9 (8)
[23:05:41][V][modbus_controller:424]: Command sent 4 0xA 2
[23:05:41][V][component:186]: Component modbus_controller took a long time for an operation (0.24 s).
[23:05:41][V][component:187]: Components should block for at most 20-30ms.
[23:05:41][V][modbus_controller:028]: Sending next modbus command to device 1 register 0x0A count 2
[23:05:41][V][modbus:182]: Modbus write: 01.04.00.0A.00.02.51.C9 (8)
[23:05:41][V][modbus_controller:424]: Command sent 4 0xA 2
[23:05:41][V][component:186]: Component modbus_controller took a long time for an operation (0.24 s).
[23:05:41][V][component:187]: Components should block for at most 20-30ms.
[23:05:42][V][modbus_controller:028]: Sending next modbus command to device 1 register 0x0A count 2
[23:05:42][V][modbus:182]: Modbus write: 01.04.00.0A.00.02.51.C9 (8)
[23:05:42][V][modbus_controller:424]: Command sent 4 0xA 2
[23:05:42][V][component:186]: Component modbus_controller took a long time for an operation (0.24 s).
[23:05:42][V][component:187]: Components should block for at most 20-30ms.
[23:05:42][V][modbus_controller:028]: Sending next modbus command to device 1 register 0x0A count 2
[23:05:42][V][modbus:182]: Modbus write: 01.04.00.0A.00.02.51.C9 (8)

[phpphph]

I copied part of the log content. Please check it.

[phpphph]

I don't have any idle esp32 devices for the time being. Does the use of esp8266 have any impact?

[phpphph]

This is the state in homeassistant

[martgras]

From your screen shot it seems that register type should be holding instead of read but I don't see any response at all not even an error.

  - platform: modbus_controller
    modbus_controller_id: mcp2420
    id: array_rated_current
    name: "array_rated_current"
    address: 0xB
    unit_of_measurement: "A"
    register_type: holding
    value_type: U_WORD
    accuracy_decimals: 0
...

When you test from windows using the terminal software does it still work if DTR is unchecked?

And please enclose the log result in 3 backticks - much easier to read ``` logs ```

[phpphph]

In the serial port monitor, if the DTR option is not selected, data can be received normally

[phpphph]

[V][modbus_controller:424]: Command sent 3 0xB 1
[23:42:19][V][component:186]: Component modbus_controller took a long time for an operation (0.24 s).
[23:42:19][V][component:187]: Components should block for at most 20-30ms.
[23:42:19][V][modbus_controller:028]: Sending next modbus command to device 1 register 0x0B count 1
[23:42:19][V][modbus:182]: Modbus write: 01.03.00.0B.00.01.F5.C8 (8)

[martgras]

Maybe logging is the problem
Set logging baud rate to 0

baud_rate (Optional, int): The baud rate to use for the serial UART port. Defaults to 115200. Set to 0 to disable logging via UART.

[martgras]

Or try to use different pins for the connection to the modbus device like 14 and 12 to avoid that it clashes with the uart used for serial logging

[phpphph]

Or try to use different pins for the connection to the modbus device like 14 and 12 to avoid that it clashes with the uart used for serial logging

I don't have an idle esp32, so I can only use esp8266 temporarily to test. I will try to change the GPIO pins in the future.

[phpphph]

I changed register_type to holding this time, and then got the data, but some data needs to be converted by formula

[martgras]

I don't think an esp32 will change it.
But they give you more options.
I think you picked the wrong interface on the solar controller.
Which interface are you using rs232, rs485 or TTL?
For rs485 with D+ and D- you need a converter

[martgras]

Sorry missed your response.
So you got some data now - great
To convert you can use filters.
Probably multiply and offset
I'm away from my pc now but the document you sent should contain the required calculation.

For my epever I have divide most values by 100 using multiply 0.01
See https://github.com/martgras/esphome/wiki/EPEVER%C2%AE-MPPT-Solar-Charge-Controller-Tracer-AN-Series

[phpphph]

I checked the manual of the controller, this interface can use either RS232/485 or TTL. The ch340 USB TTL module I used in Windows debugging can successfully obtain the correct data, so I think directly connect the communication pins of the controller to There is no problem connecting the esp device, and the data is also obtained. The next step is to add the remaining functions, such as PV voltage, PV current, PV power (W), battery voltage, and battery charging current. . .

[martgras]

Nice - I'll have a look at the document tomorrow. Once esp gets data setting up remaing registers shouldn't be a big problem

[phpphph]

Thank you very much for helping me. I don't know which city you are in? My time here is 1:45 in the morning, because I use Google Translate to communicate with you, it may seem that my reply is a little weird😁😁. We look forward to your perfecting the program, and we look forward to the esphome example in the future, because this controller has a very good market share in our country.

[martgras]

Sounds interesting
Btw I added the configuration to the wiki https://github.com/martgras/esphome/wiki/MC24xx

[phpphph]

Sounds interesting Btw I added the configuration to the wiki https://github.com/martgras/esphome/wiki/MC24xx

I think you can also contribute this example to the Esphome website.

[phpphph]

Sounds interesting Btw I added the configuration to the wiki https://github.com/martgras/esphome/wiki/MC24xx

Are you interested in doing the "SU-03T" speech recognition project?
I have this module now, you only need to help me do the code part, and I will do the actual testing for the rest.
I believe this voice recognition project will add more interesting DIY to ESPhome and HomeAssistant.

[phpphph]

听起来很有趣 Btw 我将配置添加到 wiki https://github.com/martgras/esphome/wiki/MC24xx

I think it is also possible to create two "sensors" in the MC24xx program, and multiply the data of "Battery Voltage" and "recharging current" to get "W" (recharging power)

Then put this "recharging power" ÷ "Solar Power" = "conversion efficiency"

This "conversion efficiency" is a data that many photovoltaic enthusiasts like to see.

[martgras]

Added the conversion factor to the wiki.
For SU-03T I don't have time right now - I know offline is nice but I have my Alexa :)

[widapro]

Thank you very much for the work you have done. I am trying to repeat the above but I am not getting a response from the controller (MC2420)
I'm using an ESP32 (board: nodemcu-32s) and connect the TX of the controller to the RX (GPIO16) and TX of the controller (GPIO17). I also tried to connect to the GPIO1 and GPIO3 pins of the ESP and swap TX with RX. I also connect the GND of the controller to the GND of the ESP.
The ESP configuration is identical to the one on the wiki.
In the logs I have the following:

11:37:07 | [D] | [modbus_controller:032] | Modbus command to device=1 register=0x0A countdown=0 no response received - removed from send queue
11:37:07 | [D] | [uart_debug:158] | >>> "\x01\x03\x01\x02\x00\b\xE40"
11:37:07 | [D] | [uart_debug:158] | >>> "\x01\x03\x01\x02\x00\b\xE40"
11:37:07 | [D] | [uart_debug:158] | >>> "\x01\x03\x01\x02\x00\b\xE40"
11:37:08 | [D] | [uart_debug:158] | >>> "\x01\x03\x01\x02\x00\b\xE40"
11:37:08 | [D] | [uart_debug:158] | >>> "\x01\x03\x01\x02\x00\b\xE40"
11:37:08 | [D] | [modbus_controller:032] | Modbus command to device=1 register=0x102 countdown=0 no response received - removed from send queue
11:37:08 | [D] | [uart_debug:158] | >>> "\x01\x03\x01\v\x00\x15\xF4;"
11:37:08 | [D] | [uart_debug:158] | >>> "\x01\x03\x01\v\x00\x15\xF4;"
11:37:08 | [D] | [uart_debug:158] | >>> "\x01\x03\x01\v\x00\x15\xF4;"
11:37:09 | [D] | [uart_debug:158] | >>> "\x01\x03\x01\v\x00\x15\xF4;"
11:37:09 | [D] | [uart_debug:158] | >>> "\x01\x03\x01\v\x00\x15\xF4;"
11:37:09 | [D] | [modbus_controller:032] | Modbus command to device=1 register=0x10B countdown=0 no response received - removed from send queue
11:37:09 | [D] | [uart_debug:158] | >>> "\x01\x04\x01\x00\x00\x02p7"
11:37:09 | [D] | [uart_debug:158] | >>> "\x01\x04\x01\x00\x00\x02p7"
11:37:10 | [D] | [uart_debug:158] | >>> "\x01\x04\x01\x00\x00\x02p7"
11:37:10 | [D] | [uart_debug:158] | >>> "\x01\x04\x01\x00\x00\x02p7"
11:37:10 | [D] | [uart_debug:158] | >>> "\x01\x04\x01\x00\x00\x02p7"
11:37:10 | [D] | [modbus_controller:032] | Modbus command to device=1 register=0x100 countdown=0 no response received - removed from send queue

Am I connected correctly? Do I need to use additional pins from the controller connector (3.3V)?

[widapro]

The issue was resolved by adding a "inverted: true" parameter to the UART. Physical rearrangement of RX and TX pins did not help.
Here is a complete description of the UART working unit for esp32 and SRNE MC2420

uart:
  id: mod_bus
  tx_pin:
    number: GPIO17
    inverted: true
  rx_pin: 
    number: GPIO16
    inverted: true
  baud_rate: 9600
  stop_bits: 1
  data_bits: 8
  parity: NONE