Smart Home Automation Forum - N10

N series Energy Meter for Loxone UDP Protocol

Mon, 04 May 2026 16:19:04 +0800

Energy Loxone Protocol
=======================

Overview
--------
This document describes the Loxone string protocol for Energy module.
Default delimiter is comma (,). Chip ID: 1-6, Channel: 1-10.

Commands
--------

1. GET_ENERGY_CURRENT - Get current (A) for specific channel
Request: RELAY-GET_ENERGY_CURRENT-255,{chip},{channel}
Response: RELAY-GET_ENERGY_CURRENT-255,{chip},{channel},{value},OK
Example:
Request: RELAY-GET_ENERGY_CURRENT-255,1,1
Response: RELAY-GET_ENERGY_CURRENT-255,1,1,2.350,OK

2. GET_ENERGY_POWER - Get power (W) for specific channel
Request: RELAY-GET_ENERGY_POWER-255,{chip},{channel}
Response: RELAY-GET_ENERGY_POWER-255,{chip},{channel},{value},OK
Example:
Request: RELAY-GET_ENERGY_POWER-255,1,1
Response: RELAY-GET_ENERGY_POWER-255,1,1,512.5,OK

3. GET_ENERGY_KWH - Get energy (kWh) for specific channel
Request: RELAY-GET_ENERGY_KWH-255,{chip},{channel}
Response: RELAY-GET_ENERGY_KWH-255,{chip},{channel},{value},OK
Example:
Request: RELAY-GET_ENERGY_KWH-255,1,1
Response: RELAY-GET_ENERGY_KWH-255,1,1,1250,OK

4. GET_ENERGY_VOLT - Get voltage (V) for chip
Request: RELAY-GET_ENERGY_VOLT-255,{chip}
Response: RELAY-GET_ENERGY_VOLT-255,{chip},{value},OK
Example:
Request: RELAY-GET_ENERGY_VOLT-255,1
Response: RELAY-GET_ENERGY_VOLT-255,1,220.50,OK

5. GET_ENERGY_FREQ - Get frequency (Hz) for chip
Request: RELAY-GET_ENERGY_FREQ-255,{chip}
Response: RELAY-GET_ENERGY_FREQ-255,{chip},{value},OK
Example:
Request: RELAY-GET_ENERGY_FREQ-255,1
Response: RELAY-GET_ENERGY_FREQ-255,1,50.00,OK

6. GET_ENERGY_TEMP - Get temperature © for chip
Request: RELAY-GET_ENERGY_TEMP-255,{chip}
Response: RELAY-GET_ENERGY_TEMP-255,{chip},{value},OK
Example:
Request: RELAY-GET_ENERGY_TEMP-255,1
Response: RELAY-GET_ENERGY_TEMP-255,1,35.5,OK

7. GET_ENERGY_PF - Get power factor for chip
Request: RELAY-GET_ENERGY_PF-255,{chip}
Response: RELAY-GET_ENERGY_PF-255,{chip},{value},OK
Example:
Request: RELAY-GET_ENERGY_PF-255,1
Response: RELAY-GET_ENERGY_PF-255,1,0.95,OK

8. GET_ENERGY_SUM - Get total energy (kWh) for chip
Request: RELAY-GET_ENERGY_SUM-255,{chip}
Response: RELAY-GET_ENERGY_SUM-255,{chip},{value},OK
Example:
Request: RELAY-GET_ENERGY_SUM-255,1
Response: RELAY-GET_ENERGY_SUM-255,1,12500,OK

Nx-Energy-meter-udp-loxone.png (Size: 141.99 KB / Downloads: 66)
protocol download:

Nx-energy_loxone_protocol.txt (Size: 2.34 KB / Downloads: 42)

N10 smart energy meter ESP32 system block diagram

Sat, 02 May 2026 19:50:27 +0800

N10 smart energy meter ESP32 system block diagram

KinCony-N10-smart-energy-meter-diagram.png (Size: 1.53 MB / Downloads: 69)

[SOLVED] N10 - no KWH shown

Fri, 01 May 2026 08:47:28 +0800

Hi, I have just received my N10 and its all working - except the kwh is always zero in homeassistant and on the "monitor" page on kc3

I have tried the ESPhome firmware and the KC3 firmware > MQTT > Homeassistant with the same results - screenshots below for reference

When i used the ESPhome firmware i used this config file which mentions fixing the kwh https://www.kincony.com/forum/attachment.php?aid=9373

I found this post - https://www.kincony.com/forum/showthread.php?tid=9107, and tried flashing via USBC port but it will not work - must this use the RS485?

Thank you

  Screenshot 2026-05-01 085712.png (Size: 30.68 KB / Downloads: 97)
  Screenshot 2026-05-01 085842.png (Size: 10.55 KB / Downloads: 96)
  Screenshot 2026-05-01 090209.png (Size: 53.89 KB / Downloads: 82)

N10 wire case diagram for 1 phase load

Fri, 03 Apr 2026 08:22:52 +0800

N10 wire case diagram for 1 phase load

N10-1-phase.JPG (Size: 102.43 KB / Downloads: 107)

N60 N30 N20 N10 ARM CPU firmware V20_260324SP

Tue, 24 Mar 2026 12:59:27 +0800

fixed bug can't remember energy data when power off.
you can download by bootloader.exe tool by RS485.
ARM BIN file download:

  N10203060_KU_V20_260324SP.zip (Size: 14.42 KB / Downloads: 82)

bootloader.exe tool:
   KC868 Controller Bootloader.zip

1. set baud rate=38400bps.
2. open com port.
3. power on Nx board, during LED fast blink when the "bootloader Detect" button right now. Then board will go to bootloader mode.
4. open BIN file
5. press "Download" button, begin download firmware, after finished, press "Run" button, ARM CPU begin work.

how to read BL0910 energy chip RAW data by modbus pull via RS485

Tue, 24 Mar 2026 10:13:44 +0800

1: open NX_chip.mbp in modbus pull software.

  modbus-open-config.png (Size: 92.01 KB / Downloads: 96)

2: set COM port. you can use USB-RS485 adapter connect to your computer:

  modbus-pull-COM-setting.png (Size: 87.06 KB / Downloads: 106)

3:
you can read BL0910-1 chip from address 100 , register count: 68
you can read BL0910-2 chip from address 200 , register count: 68
you can read BL0910-3 chip from address 300 , register count: 68
you can read BL0910-4 chip from address 400 , register count: 68
you can read BL0910-5 chip from address 500 , register count: 68
you can read BL0910-6 chip from address 600 , register count: 68

  modbus-pull-read-BL0910-1.png (Size: 96.25 KB / Downloads: 101)

  modbus-pull-read-BL0910-2.png (Size: 98.36 KB / Downloads: 110)

  modbus-pull-read-BL0910-3.png (Size: 94.91 KB / Downloads: 114)

  modbus-pull-read-BL0910-4.png (Size: 96.68 KB / Downloads: 106)

  modbus-pull-read-BL0910-5.png (Size: 95.49 KB / Downloads: 110)

  modbus-pull-read-BL0910-6.png (Size: 95.27 KB / Downloads: 119)

  NX_chip.zip (Size: 654 bytes / Downloads: 87)

N10 configure yaml for ESPhome 0.001kwh precision

Mon, 23 Mar 2026 09:54:55 +0800

note: ARM CPU firmware version should >= V20_260305SP
ARM CPU firmware download: https://www.kincony.com/forum/showthread.php?tid=9107

Code:
esphome:

  name: n10

  friendly_name: n10

esp32:

  board: esp32-s3-devkitc-1

  framework:

    type: arduino

logger:

  # baud_rate: 0

api:

ota:

  platform: esphome

ethernet:

  type: W5500

  clk_pin: GPIO42

  mosi_pin: GPIO43

  miso_pin: GPIO44

  cs_pin: GPIO41

  interrupt_pin: GPIO2

  reset_pin: GPIO1

uart:

  id: uart_modbus

  rx_pin: 9

  tx_pin: 10

  baud_rate: 115200

  stop_bits: 1

  data_bits: 8

  parity: NONE

web_server:

  port: 80

text_sensor:

  - platform: ethernet_info

    ip_address:

      name: ESP IP Address

      id: eth_ip

    dns_address:

      name: ESP DNS Address

    mac_address:

      name: ESP MAC Address

font:

  - file: "gfonts://Roboto"

    id: roboto

    size: 15

i2c:

  sda: 18

  scl: 17

display:

  - platform: ssd1306_i2c

    model: "SSD1306 128x64"

    address: 0x3C

    lambda: |-

      it.printf(0, 15, id(roboto), "IP: %s", id(eth_ip).state.c_str());

modbus:

  id: mb1

  uart_id: uart_modbus

modbus_controller:

  - id: energy_meter

    modbus_id: mb1

    address: 1

    update_interval: 5s

    command_throttle: 200ms

sensor:

  # Protocol notes for this PR:

  # - current: U_DWORD_R, scaled by 0.001 A

  # - power:   S_DWORD_R, scaled by 0.1 W

  # - energy:  FP32_R, unit kWh

  # - voltage/frequency remain U_WORD * 0.01

  # - temperature remains FP32_R

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 100

    register_type: holding

    name: bl0910_1_current_1

    id: n10_1_current_1

    unit_of_measurement: A

    device_class: current

    state_class: measurement

    accuracy_decimals: 3

    value_type: U_DWORD_R

    filters:

      - multiply: 0.001

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 102

    register_type: holding

    name: bl0910_1_current_2

    id: n10_1_current_2

    unit_of_measurement: A

    device_class: current

    state_class: measurement

    accuracy_decimals: 3

    value_type: U_DWORD_R

    filters:

      - multiply: 0.001

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 104

    register_type: holding

    name: bl0910_1_current_3

    id: n10_1_current_3

    unit_of_measurement: A

    device_class: current

    state_class: measurement

    accuracy_decimals: 3

    value_type: U_DWORD_R

    filters:

      - multiply: 0.001

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 106

    register_type: holding

    name: bl0910_1_current_4

    id: n10_1_current_4

    unit_of_measurement: A

    device_class: current

    state_class: measurement

    accuracy_decimals: 3

    value_type: U_DWORD_R

    filters:

      - multiply: 0.001

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 108

    register_type: holding

    name: bl0910_1_current_5

    id: n10_1_current_5

    unit_of_measurement: A

    device_class: current

    state_class: measurement

    accuracy_decimals: 3

    value_type: U_DWORD_R

    filters:

      - multiply: 0.001

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 110

    register_type: holding

    name: bl0910_1_current_6

    id: n10_1_current_6

    unit_of_measurement: A

    device_class: current

    state_class: measurement

    accuracy_decimals: 3

    value_type: U_DWORD_R

    filters:

      - multiply: 0.001

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 112

    register_type: holding

    name: bl0910_1_current_7

    id: n10_1_current_7

    unit_of_measurement: A

    device_class: current

    state_class: measurement

    accuracy_decimals: 3

    value_type: U_DWORD_R

    filters:

      - multiply: 0.001

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 114

    register_type: holding

    name: bl0910_1_current_8

    id: n10_1_current_8

    unit_of_measurement: A

    device_class: current

    state_class: measurement

    accuracy_decimals: 3

    value_type: U_DWORD_R

    filters:

      - multiply: 0.001

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 116

    register_type: holding

    name: bl0910_1_current_9

    id: n10_1_current_9

    unit_of_measurement: A

    device_class: current

    state_class: measurement

    accuracy_decimals: 3

    value_type: U_DWORD_R

    filters:

      - multiply: 0.001

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 118

    register_type: holding

    name: bl0910_1_current_10

    id: n10_1_current_10

    unit_of_measurement: A

    device_class: current

    state_class: measurement

    accuracy_decimals: 3

    value_type: U_DWORD_R

    filters:

      - multiply: 0.001

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 120

    register_type: holding

    name: bl0910_1_power_1

    id: n10_1_watt_1

    unit_of_measurement: W

    device_class: power

    state_class: measurement

    accuracy_decimals: 1

    value_type: S_DWORD_R

    filters:

      - multiply: 0.1

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 122

    register_type: holding

    name: bl0910_1_power_2

    id: n10_1_watt_2

    unit_of_measurement: W

    device_class: power

    state_class: measurement

    accuracy_decimals: 1

    value_type: S_DWORD_R

    filters:

      - multiply: 0.1

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 124

    register_type: holding

    name: bl0910_1_power_3

    id: n10_1_watt_3

    unit_of_measurement: W

    device_class: power

    state_class: measurement

    accuracy_decimals: 1

    value_type: S_DWORD_R

    filters:

      - multiply: 0.1

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 126

    register_type: holding

    name: bl0910_1_power_4

    id: n10_1_watt_4

    unit_of_measurement: W

    device_class: power

    state_class: measurement

    accuracy_decimals: 1

    value_type: S_DWORD_R

    filters:

      - multiply: 0.1

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 128

    register_type: holding

    name: bl0910_1_power_5

    id: n10_1_watt_5

    unit_of_measurement: W

    device_class: power

    state_class: measurement

    accuracy_decimals: 1

    value_type: S_DWORD_R

    filters:

      - multiply: 0.1

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 130

    register_type: holding

    name: bl0910_1_power_6

    id: n10_1_watt_6

    unit_of_measurement: W

    device_class: power

    state_class: measurement

    accuracy_decimals: 1

    value_type: S_DWORD_R

    filters:

      - multiply: 0.1

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 132

    register_type: holding

    name: bl0910_1_power_7

    id: n10_1_watt_7

    unit_of_measurement: W

    device_class: power

    state_class: measurement

    accuracy_decimals: 1

    value_type: S_DWORD_R

    filters:

      - multiply: 0.1

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 134

    register_type: holding

    name: bl0910_1_power_8

    id: n10_1_watt_8

    unit_of_measurement: W

    device_class: power

    state_class: measurement

    accuracy_decimals: 1

    value_type: S_DWORD_R

    filters:

      - multiply: 0.1

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 136

    register_type: holding

    name: bl0910_1_power_9

    id: n10_1_watt_9

    unit_of_measurement: W

    device_class: power

    state_class: measurement

    accuracy_decimals: 1

    value_type: S_DWORD_R

    filters:

      - multiply: 0.1

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 138

    register_type: holding

    name: bl0910_1_power_10

    id: n10_1_watt_10

    unit_of_measurement: W

    device_class: power

    state_class: measurement

    accuracy_decimals: 1

    value_type: S_DWORD_R

    filters:

      - multiply: 0.1

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 140

    register_type: holding

    name: bl0910_1_energy_1

    id: n10_1_energy_1

    unit_of_measurement: kWh

    device_class: energy

    state_class: total_increasing

    accuracy_decimals: 3

    value_type: FP32_R

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 142

    register_type: holding

    name: bl0910_1_energy_2

    id: n10_1_energy_2

    unit_of_measurement: kWh

    device_class: energy

    state_class: total_increasing

    accuracy_decimals: 3

    value_type: FP32_R

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 144

    register_type: holding

    name: bl0910_1_energy_3

    id: n10_1_energy_3

    unit_of_measurement: kWh

    device_class: energy

    state_class: total_increasing

    accuracy_decimals: 3

    value_type: FP32_R

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 146

    register_type: holding

    name: bl0910_1_energy_4

    id: n10_1_energy_4

    unit_of_measurement: kWh

    device_class: energy

    state_class: total_increasing

    accuracy_decimals: 3

    value_type: FP32_R

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 148

    register_type: holding

    name: bl0910_1_energy_5

    id: n10_1_energy_5

    unit_of_measurement: kWh

    device_class: energy

    state_class: total_increasing

    accuracy_decimals: 3

    value_type: FP32_R

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 150

    register_type: holding

    name: bl0910_1_energy_6

    id: n10_1_energy_6

    unit_of_measurement: kWh

    device_class: energy

    state_class: total_increasing

    accuracy_decimals: 3

    value_type: FP32_R

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 152

    register_type: holding

    name: bl0910_1_energy_7

    id: n10_1_energy_7

    unit_of_measurement: kWh

    device_class: energy

    state_class: total_increasing

    accuracy_decimals: 3

    value_type: FP32_R

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 154

    register_type: holding

    name: bl0910_1_energy_8

    id: n10_1_energy_8

    unit_of_measurement: kWh

    device_class: energy

    state_class: total_increasing

    accuracy_decimals: 3

    value_type: FP32_R

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 156

    register_type: holding

    name: bl0910_1_energy_9

    id: n10_1_energy_9

    unit_of_measurement: kWh

    device_class: energy

    state_class: total_increasing

    accuracy_decimals: 3

    value_type: FP32_R

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 158

    register_type: holding

    name: bl0910_1_energy_10

    id: n10_1_energy_10

    unit_of_measurement: kWh

    device_class: energy

    state_class: total_increasing

    accuracy_decimals: 3

    value_type: FP32_R

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 160

    register_type: holding

    name: bl0910_1_energy_sum

    id: n10_1_energy_sum

    unit_of_measurement: kWh

    device_class: energy

    state_class: total_increasing

    accuracy_decimals: 3

    value_type: FP32_R

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 162

    register_type: holding

    name: bl0910_1_voltage

    id: n10_1_voltage

    unit_of_measurement: V

    device_class: voltage

    state_class: measurement

    accuracy_decimals: 2

    value_type: U_WORD

    filters:

      - multiply: 0.01

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 163

    register_type: holding

    name: bl0910_1_frequency

    id: n10_1_frequency

    unit_of_measurement: Hz

    device_class: frequency

    state_class: measurement

    accuracy_decimals: 2

    value_type: U_WORD

    filters:

      - multiply: 0.01

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 164

    register_type: holding

    name: bl0910_1_temperature

    id: n10_1_temperature

    unit_of_measurement: °C

    device_class: temperature

    state_class: measurement

    accuracy_decimals: 1

    value_type: FP32_R

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 166

    register_type: holding

    name: bl0910_1_power_factor

    id: n10_1_power_factor

    accuracy_decimals: 3

    state_class: measurement

    value_type: FP32_R

yaml download:

n10_esphome.txt (Size: 12.27 KB / Downloads: 90)

N10 port modbus

Tue, 03 Mar 2026 18:41:09 +0800

There's no way to change the speed and port using Modbus. Please fix this or send me a firmware update with port 4 instead of the default 1. Thank you.

Problem when connecting USB-C

Fri, 24 Oct 2025 02:27:46 +0800

Hello,
I just bought N10 module, i connected it to 24V power and it works. However when i try to put USB-C cable from computer to Kincony for download firmware it suddenly have short cut and my 24V power supply turn off , i must take off usb-c for it to work again, this situation is from early begining.I get deffective Unit ?

Thanks.

N10 configure yaml for ESPhome

Mon, 13 Oct 2025 18:22:57 +0800

Code:
esphome:

  name: n10

  friendly_name: n10

esp32:

  board: esp32-s3-devkitc-1

  framework:

    type: arduino

# Enable logging

logger:

  # baud_rate: 0

# Enable Home Assistant API

api:

ota:

  platform: esphome

ethernet:

  type: W5500

  clk_pin: GPIO42

  mosi_pin: GPIO43

  miso_pin: GPIO44

  cs_pin: GPIO41

  interrupt_pin: GPIO2

  reset_pin: GPIO1

uart:

  rx_pin: 9

  tx_pin: 10

  baud_rate: 115200

  stop_bits: 1

  data_bits: 8

  parity: NONE

web_server:

  port: 80

text_sensor:

  - platform: ethernet_info

    ip_address:

      name: ESP IP Address

      id: eth_ip

      address_0:

        name: ESP IP Address 0

      address_1:

        name: ESP IP Address 1

      address_2:

        name: ESP IP Address 2

      address_3:

        name: ESP IP Address 3

      address_4:

        name: ESP IP Address 4

    dns_address:

      name: ESP DNS Address

    mac_address:

      name: ESP MAC Address

font:

  - file: "gfonts://Roboto"

    id: roboto

    size: 15

i2c:

  sda: 18

  scl: 17

display:

  - platform: ssd1306_i2c

    model: "SSD1306 128x64"

    address: 0x3C

    lambda: |-

      it.printf(0, 15, id(roboto), "IP: %s", id(eth_ip).state.c_str());

modbus:

modbus_controller:

  - address: 1

    update_interval: 5s

sensor:

  - platform: modbus_controller

    address: 100

    register_type: holding

    name: bl0910_1_current_1

    id: n10_1_current_1

    unit_of_measurement: A

    device_class: current

    accuracy_decimals: 3

    value_type: U_DWORD_R

    filters:

      - multiply: 0.001

  - platform: modbus_controller

    address: 102

    register_type: holding

    name: bl0910_1_current_2

    id: n10_1_current_2

    unit_of_measurement: A

    device_class: current

    accuracy_decimals: 3

    value_type: U_DWORD_R

    filters:

      - multiply: 0.001

  - platform: modbus_controller

    address: 104

    register_type: holding

    name: bl0910_1_current_3

    id: n10_1_current_3

    unit_of_measurement: A

    device_class: current

    accuracy_decimals: 3

    value_type: U_DWORD_R

    filters:

      - multiply: 0.001

  - platform: modbus_controller

    address: 106

    register_type: holding

    name: bl0910_1_current_4

    id: n10_1_current_4

    unit_of_measurement: A

    device_class: current

    accuracy_decimals: 3

    value_type: U_DWORD_R

    filters:

      - multiply: 0.001

  - platform: modbus_controller

    address: 108

    register_type: holding

    name: bl0910_1_current_5

    id: n10_1_current_5

    unit_of_measurement: A

    device_class: current

    accuracy_decimals: 3

    value_type: U_DWORD_R

    filters:

      - multiply: 0.001

  - platform: modbus_controller

    address: 110

    register_type: holding

    name: bl0910_1_current_6

    id: n10_1_current_6

    unit_of_measurement: A

    device_class: current

    accuracy_decimals: 3

    value_type: U_DWORD_R

    filters:

      - multiply: 0.001

  - platform: modbus_controller

    address: 112

    register_type: holding

    name: bl0910_1_current_7

    id: n10_1_current_7

    unit_of_measurement: A

    device_class: current

    accuracy_decimals: 3

    value_type: U_DWORD_R

    filters:

      - multiply: 0.001

  - platform: modbus_controller

    address: 114

    register_type: holding

    name: bl0910_1_current_8

    id: n10_1_current_8

    unit_of_measurement: A

    device_class: current

    accuracy_decimals: 3

    value_type: U_DWORD_R

    filters:

      - multiply: 0.001

  - platform: modbus_controller

    address: 116

    register_type: holding

    name: bl0910_1_current_9

    id: n10_1_current_9

    unit_of_measurement: A

    device_class: current

    accuracy_decimals: 3

    value_type: U_DWORD_R

    filters:

      - multiply: 0.001

  - platform: modbus_controller

    address: 118

    register_type: holding

    name: bl0910_1_current_10

    id: n10_1_current_10

    unit_of_measurement: A

    device_class: current

    accuracy_decimals: 3

    value_type: U_DWORD_R

    filters:

      - multiply: 0.001

  - platform: modbus_controller

    address: 120

    register_type: holding

    name: bl0910_1_power_1

    id: n10_1_watt_1

    unit_of_measurement: W

    device_class: power

    accuracy_decimals: 1

    value_type: U_DWORD_R

    filters:

      - multiply: 0.1

  - platform: modbus_controller

    address: 122

    register_type: holding

    name: bl0910_1_power_2

    id: n10_1_watt_2

    unit_of_measurement: W

    device_class: power

    accuracy_decimals: 1

    value_type: U_DWORD_R

    filters:

      - multiply: 0.1

  - platform: modbus_controller

    address: 124

    register_type: holding

    name: bl0910_1_power_3

    id: n10_1_watt_3

    unit_of_measurement: W

    device_class: power

    accuracy_decimals: 1

    value_type: U_DWORD_R

    filters:

      - multiply: 0.1

  - platform: modbus_controller

    address: 126

    register_type: holding

    name: bl0910_1_power_4

    id: n10_1_watt_4

    unit_of_measurement: W

    device_class: power

    accuracy_decimals: 1

    value_type: U_DWORD_R

    filters:

      - multiply: 0.1

  - platform: modbus_controller

    address: 128

    register_type: holding

    name: bl0910_1_power_5

    id: n10_1_watt_5

    unit_of_measurement: W

    device_class: power

    accuracy_decimals: 1

    value_type: U_DWORD_R

    filters:

      - multiply: 0.1

  - platform: modbus_controller

    address: 130

    register_type: holding

    name: bl0910_1_power_6

    id: n10_1_watt_6

    unit_of_measurement: W

    device_class: power

    accuracy_decimals: 1

    value_type: U_DWORD_R

    filters:

      - multiply: 0.1

  - platform: modbus_controller

    address: 132

    register_type: holding

    name: bl0910_1_power_7

    id: n10_1_watt_7

    unit_of_measurement: W

    device_class: power

    accuracy_decimals: 1

    value_type: U_DWORD_R

    filters:

      - multiply: 0.1

  - platform: modbus_controller

    address: 134

    register_type: holding

    name: bl0910_1_power_8

    id: n10_1_watt_8

    unit_of_measurement: W

    device_class: power

    accuracy_decimals: 1

    value_type: U_DWORD_R

    filters:

      - multiply: 0.1

  - platform: modbus_controller

    address: 136

    register_type: holding

    name: bl0910_1_power_9

    id: n10_1_watt_9

    unit_of_measurement: W

    device_class: power

    accuracy_decimals: 1

    value_type: U_DWORD_R

    filters:

      - multiply: 0.1

  - platform: modbus_controller

    address: 138

    register_type: holding

    name: bl0910_1_power_10

    id: n10_1_watt_10

    unit_of_measurement: W

    device_class: power

    accuracy_decimals: 1

    value_type: U_DWORD_R

    filters:

      - multiply: 0.1

  - platform: modbus_controller

    state_class: total_increasing

    device_class: energy

    address: 140

    register_type: holding

    name: bl0910_1_energy_1

    id: n10_1_energy_1

    unit_of_measurement: kWh

    accuracy_decimals: 1

    value_type: U_DWORD_R

  - platform: modbus_controller

    state_class: total_increasing

    device_class: energy

    address: 142

    register_type: holding

    name: bl0910_1_energy_2

    id: n10_1_energy_2

    unit_of_measurement: kWh

    accuracy_decimals: 1

    value_type: U_DWORD_R

  - platform: modbus_controller

    state_class: total_increasing

    device_class: energy

    address: 144

    register_type: holding

    name: bl0910_1_energy_3

    id: n10_1_energy_3

    unit_of_measurement: kWh

    accuracy_decimals: 1

    value_type: U_DWORD_R

  - platform: modbus_controller

    state_class: total_increasing

    device_class: energy

    address: 146

    register_type: holding

    name: bl0910_1_energy_4

    id: n10_1_energy_4

    unit_of_measurement: kWh

    accuracy_decimals: 1

    value_type: U_DWORD_R

  - platform: modbus_controller

    state_class: total_increasing

    device_class: energy

    address: 148

    register_type: holding

    name: bl0910_1_energy_5

    id: n10_1_energy_5

    unit_of_measurement: kWh

    accuracy_decimals: 1

    value_type: U_DWORD_R

  - platform: modbus_controller

    state_class: total_increasing

    device_class: energy

    address: 150

    register_type: holding

    name: bl0910_1_energy_6

    id: n10_1_energy_6

    unit_of_measurement: kWh

    accuracy_decimals: 1

    value_type: U_DWORD_R

  - platform: modbus_controller

    state_class: total_increasing

    device_class: energy

    address: 152

    register_type: holding

    name: bl0910_1_energy_7

    id: n10_1_energy_7

    unit_of_measurement: kWh

    accuracy_decimals: 1

    value_type: U_DWORD_R

  - platform: modbus_controller

    state_class: total_increasing

    device_class: energy

    address: 154

    register_type: holding

    name: bl0910_1_energy_8

    id: n10_1_energy_8

    unit_of_measurement: kWh

    accuracy_decimals: 1

    value_type: U_DWORD_R

  - platform: modbus_controller

    state_class: total_increasing

    device_class: energy

    address: 156

    register_type: holding

    name: bl0910_1_energy_9

    id: n10_1_energy_9

    unit_of_measurement: kWh

    accuracy_decimals: 1

    value_type: U_DWORD_R

  - platform: modbus_controller

    state_class: total_increasing

    device_class: energy

    address: 158

    register_type: holding

    name: bl0910_1_energy_10

    id: n10_1_energy_10

    unit_of_measurement: kWh

    accuracy_decimals: 1

    value_type: U_DWORD_R

  - platform: modbus_controller

    state_class: total_increasing

    device_class: energy

    address: 160

    register_type: holding

    name: bl0910_1_energy_sum

    id: n10_1_energy_sum

    unit_of_measurement: kWh

    accuracy_decimals: 1

    value_type: U_DWORD_R

  - platform: modbus_controller

    address: 162

    register_type: holding

    name: bl0910_1_voltage

    id: n10_1_voltage

    unit_of_measurement: V

    device_class: voltage

    accuracy_decimals: 1

    value_type: U_WORD

    filters:

      - multiply: 0.01

  - platform: modbus_controller

    address: 163

    register_type: holding

    name: bl0910_1_frequency

    id: n10_1_period

    unit_of_measurement: Hz

    device_class: frequency

    accuracy_decimals: 1

    value_type: U_WORD

    filters:

      - multiply: 0.01

  - platform: modbus_controller

    address: 164

    register_type: holding

    name: bl0910_1_tps1

    id: n10_1_tps_1

    unit_of_measurement: °C

    device_class: temperature

    accuracy_decimals: 1

    value_type: FP32_R

yaml download:

N10-HA.txt (Size: 10.03 KB / Downloads: 314)

N10 Energy RS485 Modbus Protocol

Mon, 13 Oct 2025 10:04:32 +0800

Code:
N10 Energy Module Modbus Protocol Specification

==============================================

1. Overview

-----------

This document specifies the Modbus communication protocol for the N10 Energy Module.

The device communicates using the Modbus RTU protocol and provides access to electrical

measurement parameters including current, power, energy consumption, voltage, frequency,

temperature, and power factor.

2. Module Characteristics

-------------------------

- Energy Monitoring Chips: 1

- Communication Protocol: Modbus RTU

- Wireless Technology: Not applicable (wired connection)

- Maximum Sensors Supported: 32

- Board Features: Display, Ethernet (W5500), 4G, SD Card support

- GPIO Availability: 2 free GPIOs (pins 15, 16)

3. Communication Parameters

---------------------------

- Protocol: Modbus RTU

- Baud Rate: 38400

- Function Codes:

  * 0x03: Read Holding Registers (for reading data)

  * 0x05: Write Single Coil (for control operations)

  * 0x10: Write Multiple Registers (for configuration)

4. Chip Addressing

------------------

The N10 Energy Module contains 1 measurement chip with base address:

+-------------+--------------+--------------------+

| Chip Number | Base Address | Physical Location  |

+-------------+--------------+--------------------+

| Chip 1      | 100          | Main board         |

+-------------+--------------+--------------------+

5. Data Structure

-----------------

The chip provides the following data (accessible via Function Code 0x03):

5.1 Current Measurements (RMS)

------------------------------

+----------------+------------+-------+--------+---------------+

| Register Offset| Parameter  | Units | Format | Resolution    |

+----------------+------------+-------+--------+---------------+

| 0              | RMS_1      | A     | uint32 | 0.001A/LSB    |

| 2              | RMS_2      | A     | uint32 | 0.001A/LSB    |

| 4              | RMS_3      | A     | uint32 | 0.001A/LSB    |

| 6              | RMS_4      | A     | uint32 | 0.001A/LSB    |

| 8              | RMS_5      | A     | uint32 | 0.001A/LSB    |

| 10             | RMS_6      | A     | uint32 | 0.001A/LSB    |

| 12             | RMS_7      | A     | uint32 | 0.001A/LSB    |

| 14             | RMS_8      | A     | uint32 | 0.001A/LSB    |

| 16             | RMS_9      | A     | uint32 | 0.001A/LSB    |

| 18             | RMS_10     | A     | uint32 | 0.001A/LSB    |

+----------------+------------+-------+--------+---------------+

Example: To read RMS_1 from Chip 1, read registers 100 and 101 (2 registers for uint32).

Display: Reading of 5432 represents 5.432A (5432 × 0.001A)

5.2 Power Measurements (WATT)

-----------------------------

+----------------+------------+-------+--------+---------------+

| Register Offset| Parameter  | Units | Format | Resolution    |

+----------------+------------+-------+--------+---------------+

| 20             | WATT_1     | W     | uint32 | 0.1W/LSB      |

| 22             | WATT_2     | W     | uint32 | 0.1W/LSB      |

| 24             | WATT_3     | W     | uint32 | 0.1W/LSB      |

| 26             | WATT_4     | W     | uint32 | 0.1W/LSB      |

| 28             | WATT_5     | W     | uint32 | 0.1W/LSB      |

| 30             | WATT_6     | W     | uint32 | 0.1W/LSB      |

| 32             | WATT_7     | W     | uint32 | 0.1W/LSB      |

| 34             | WATT_8     | W     | uint32 | 0.1W/LSB      |

| 36             | WATT_9     | W     | uint32 | 0.1W/LSB      |

| 38             | WATT_10    | W     | uint32 | 0.1W/LSB      |

+----------------+------------+-------+--------+---------------+

Example: To read WATT_1 from Chip 1, read registers 120 and 121 (2 registers for uint32).

Display: Reading of 12345 represents 1234.5W (12345 × 0.1W)

5.3 Energy Consumption Measurements

-----------------------------------

+----------------+-------------+-------+--------+---------------------+

| Register Offset| Parameter   | Units | Format | Resolution          |

+----------------+-------------+-------+--------+---------------------+

| 40             | Energy_1    | kWh   | uint32 | 1kWh/LSB            |

| 42             | Energy_2    | kWh   | uint32 | 1kWh/LSB            |

| 44             | Energy_3    | kWh   | uint32 | 1kWh/LSB            |

| 46             | Energy_4    | kWh   | uint32 | 1kWh/LSB            |

| 48             | Energy_5    | kWh   | uint32 | 1kWh/LSB            |

| 50             | Energy_6    | kWh   | uint32 | 1kWh/LSB            |

| 52             | Energy_7    | kWh   | uint32 | 1kWh/LSB            |

| 54             | Energy_8    | kWh   | uint32 | 1kWh/LSB            |

| 56             | Energy_9    | kWh   | uint32 | 1kWh/LSB            |

| 58             | Energy_10   | kWh   | uint32 | 1kWh/LSB            |

| 60             | Energy_Sum  | kWh   | uint32 | 1kWh/LSB            |

+----------------+-------------+-------+--------+---------------------+

Note: The maximum measurable energy per channel is 65535 kWh.

5.4 Other Measurements

----------------------

+----------------+-------------+-------+--------+---------------------+

| Register Offset| Parameter   | Units | Format | Resolution          |

+----------------+-------------+-------+--------+---------------------+

| 62             | RMS_V       | V     | uint16 | 0.01V/LSB           |

| 63             | Period      | Hz    | uint16 | 0.01Hz/LSB          |

| 64             | TPS1        | °C    | float  | 0.1°C/LSB           |

| 66             | PF          | -     | float  | Power Factor (0-1)  |

+----------------+-------------+-------+--------+---------------------+

6. Control Functions (Function Code 0x05)

------------------------------------------

The following control registers can be written to using the Modbus function code 0x05:

+----------+------------------------------+--------------------------------------------+

| Register | Function                     | Description                                |

+----------+------------------------------+--------------------------------------------+

| 500      | Warm Reset                   | Resets the device                          |

| 501      | Save Parameters to Flash     | Save communication parameters to flash     |

| 503      | Save Coefficients to Flash   | Save calibration coefficients to flash     |

| 504      | Clear Coefficients           | Reset all coefficients to 1.0 (use caution)|

| 510      | Restore Factory Settings     | Restore factory communication parameters   |

+----------+------------------------------+--------------------------------------------+

7. Energy Clearing Functions (Function Code 0x05)

--------------------------------------------------

The following registers clear energy consumption data when written with function code 0x05:

7.1 Clear All Channels on the Chip

-----------------------------------

+----------+--------------------------------+

| Register | Function                       |

+----------+--------------------------------+

| 520      | Clear all energy on Chip 1     |

+----------+--------------------------------+

7.2 Clear Individual Channels

------------------------------

+----------------+------------------------------------------------+

| Register Range | Function                                       |

+----------------+------------------------------------------------+

| 526-535        | Clear energy on Chip 1, channels 1-10          |

| 586            | Clear sum energy on Chip 1                     |

+----------------+------------------------------------------------+

8. Calibration Coefficients (Function Code 0x03 to read, 0x10 to write)

------------------------------------------------------------------------

All coefficients are stored as floating-point values in CDBA format.

8.1 Current (RMS) Coefficients for Chip 1

------------------------------------------

+----------+---------------------+---------+

| Register | Parameter           | Default |

+----------+---------------------+---------+

| 3000     | FACTOR OF RMS1      | 1.0     |

| 3002     | FACTOR OF RMS2      | 1.0     |

| 3004     | FACTOR OF RMS3      | 1.0     |

| 3006     | FACTOR OF RMS4      | 1.0     |

| 3008     | FACTOR OF RMS5      | 1.0     |

| 3010     | FACTOR OF RMS6      | 1.0     |

| 3012     | FACTOR OF RMS7      | 1.0     |

| 3014     | FACTOR OF RMS8      | 1.0     |

| 3016     | FACTOR OF RMS9      | 1.0     |

| 3018     | FACTOR OF RMS10     | 1.0     |

+----------+---------------------+---------+

8.2 Power (WATT) Coefficients for Chip 1

-----------------------------------------

+----------+---------------------+---------+

| Register | Parameter           | Default |

+----------+---------------------+---------+

| 3020     | FACTOR OF WATT1     | 1.0     |

| 3022     | FACTOR OF WATT2     | 1.0     |

| 3024     | FACTOR OF WATT3     | 1.0     |

| 3026     | FACTOR OF WATT4     | 1.0     |

| 3028     | FACTOR OF WATT5     | 1.0     |

| 3030     | FACTOR OF WATT6     | 1.0     |

| 3032     | FACTOR OF WATT7     | 1.0     |

| 3034     | FACTOR OF WATT8     | 1.0     |

| 3036     | FACTOR OF WATT9     | 1.0     |

| 3038     | FACTOR OF WATT10    | 1.0     |

+----------+---------------------+---------+

8.3 Energy Coefficients for Chip 1

-----------------------------------

+----------+-----------------------+---------+

| Register | Parameter             | Default |

+----------+-----------------------+---------+

| 3040     | FACTOR OF ENERGY1     | 1.0     |

| 3042     | FACTOR OF ENERGY2     | 1.0     |

| 3044     | FACTOR OF ENERGY3     | 1.0     |

| 3046     | FACTOR OF ENERGY4     | 1.0     |

| 3048     | FACTOR OF ENERGY5     | 1.0     |

| 3050     | FACTOR OF ENERGY6     | 1.0     |

| 3052     | FACTOR OF ENERGY7     | 1.0     |

| 3054     | FACTOR OF ENERGY8     | 1.0     |

| 3056     | FACTOR OF ENERGY9     | 1.0     |

| 3058     | FACTOR OF ENERGY10    | 1.0     |

| 3060     | FACTOR OF ENERGY SUM  | 1.0     |

+----------+-----------------------+---------+

9. Programming Notes

--------------------

1. After modifying communication parameters, write to register 501 to save them to flash.

2. After modifying calibration coefficients, write to register 503 to save them to flash.

3. Read the entire data structure for the chip by reading 68 registers starting at base

   address 100.

4. For 32-bit values (uint32, float), read/write two consecutive registers.

5. When writing float values, use the CDBA format.

6. All energy measurements have a maximum value of 65535 kWh per channel.

10. Comparison with Other N-Series Modules

------------------------------------------

+------------------+------------------+------------------+------------------+

| Feature          | N10             | N20              | N30              |

+------------------+------------------+------------------+------------------+

| Communication    | Modbus RTU      | Modbus RTU       | Modbus RTU       |

| Energy Chips     | 1               | 2                | 3                |

| Channels         | 10              | 20               | 30               |

| Base Addresses   | 100             | 100, 200         | 100, 200, 300    |

| Data Structure   | Standard        | Dual-chip        | Triple-chip      |

| Installation     | Wired           | Wired            | Wired            |

+------------------+------------------+------------------+------------------+

11. Conclusion

--------------

The N10 Energy Module provides single-chip energy monitoring with Modbus RTU

communication, making it ideal for small-scale installations requiring precise

electrical measurement and monitoring. The device offers 10 channels of current,

power, and energy monitoring with comprehensive calibration and control capabilities.

==============================================================================

Document generated for N10 Energy Module Modbus Protocol

For technical support, please contact Kincony support team.

protocol document download:

N10_Energy_Modbus_Protocol.txt (Size: 11.62 KB / Downloads: 243)

N60/N30/N20/N10/M30 CT selection and Load MAX current formula

Thu, 04 Sep 2025 07:47:15 +0800

CT-1.png (Size: 47.07 KB / Downloads: 335)
every CT clamp input channel will have two resistance. for example, CT2 channel are R23, R24

CT-2.png (Size: 119.56 KB / Downloads: 345)
use the formula let input voltage <700mV

if your CT clamp sensor is 2000:1
Load current=30A,
input voltage = 5.1R*2*30A/2000=153mA (VIPN)

so if input voltage <700mA , use 5.1R resistance on PCB, 2000:1 MAX can detect 137A AC220V load.

if you want support more large current, you can change the resistance or change CT 2000:1 with other models. Just use by the formula.

N60 N30 N20 N10 firmware BL0910 energy chip register RAW data structure

Sun, 03 Aug 2025 11:31:20 +0800

N60-meter-data-structure.png (Size: 31.39 KB / Downloads: 378)

[arduino code examples for N10]-05 collect N10 all data demo

Sun, 03 Aug 2025 11:27:07 +0800

Code:
/*

 * Made by KinCony IoT: https://www.kincony.com

 * 

 * Demo Program for Reading Data from KinCony N60 Energy Meter (60-channel version)

 * via RS485 Modbus using ESP32 and NonBlockingModbusMaster library.

 * 

 * This example:

 * - Initializes RS485 Modbus communication

 * - Reads current, power, energy, voltage, frequency, temperature, power factor from 6 chips

 * - Prints all data to Serial Monitor

 * - Uses TaskScheduler to run periodic tasks

 */

#include "TaskScheduler.h"

#include "HardwareSerial.h"

//#include "modbus-rtu.h"

#include "NonBlockingModbusMaster.h"  // Include non-blocking Modbus master library

/////defined anything here====================

#define MAX_U16DATA_LEN  68  // Number of 16-bit registers to read per chip

// Define RS485 serial and control pins

#define TX_PIN 8

#define DE_PIN 3

#define RX_PIN 18

// Define Modbus function codes

typedef enum{

  FC_READ_COIL = 1,

  FC_READ_HOLDREG = 3,

  FC_READ_INPUTREG = 4,

  FC_FORCE_COIL = 5,

  FC_FORCE_COILS = 15,

  FC_WRITE_REG = 6,

  FC_WRITE_REGS = 16,

}FC_DEF;

// Define structure to hold all the electrical parameters per chip

typedef struct

{

    uint32_t RMS_1;        //0    //XX.XXX    A        0.001A/LSB

    uint32_t RMS_2;

    uint32_t RMS_3;

    uint32_t RMS_4;

    uint32_t RMS_5;

    uint32_t RMS_6;

    uint32_t RMS_7;

    uint32_t RMS_8;

    uint32_t RMS_9;

    uint32_t RMS_10; 

    uint32_t WATT_1;        //20 XXXX.X    W        0.1W/LSB

    uint32_t WATT_2;

    uint32_t WATT_3;

    uint32_t WATT_4;

    uint32_t WATT_5;

    uint32_t WATT_6;

    uint32_t WATT_7;

    uint32_t WATT_8;

    uint32_t WATT_9;

    uint32_t WATT_10;//

    uint32_t Energy_1;        //40 XXXXXX    kWh   1kWh/LSB,MAX:65535kWh

    uint32_t Energy_2;

    uint32_t Energy_3;

    uint32_t Energy_4;

    uint32_t Energy_5;

    uint32_t Energy_6;

    uint32_t Energy_7;

    uint32_t Energy_8;

    uint32_t Energy_9;

    uint32_t Energy_10; //

    uint32_t Energy_Sum; //60

    uint16_t RMS_V;            //62 XXX.X    V            0.01V/LSB

    uint16_t Period;        //63 XX.XX    Hz        0.01Hz/LSB

    float TPS1;            //64 XX.XX ℃            0.1℃/LSB

    float PF;  //66

}Elect_StructDef_JKE;

typedef union{

  Elect_StructDef_JKE jke_n60_str[6]; ////6 chips each have MAX_STRU_LEN data

  ushort read_regs_arr[6][MAX_U16DATA_LEN];

}COLLECT_UNION;

////define instance here================================================================

COLLECT_UNION jke_n60_data_union = {0};

HardwareSerial collectSerial(2);

Scheduler ts;   // Task scheduler

NonBlockingModbusMaster nbModbusMaster;

////define macros here===================

static void collectAllChipData();

static void PrintfInfo();

////define my work task==================================

Task collectDataTask(200,TASK_FOREVER,[]()

{

  collectAllChipData();

});

Task heartBeatTask(1000,TASK_FOREVER,[]()

{

  ////do anything in heartBeatTask to make sense for anyone or other.

  Serial.println("heartbeat task is running.");

});

void setup() {

  // put your setup code here, to run once:

  // Open serial communications and wait for port to open:

    Serial.begin(115200);

    collectSerial.begin(115200,SERIAL_8N1,9,10);///RX & TX

    float bitduration = 1.f / 115200;

    float charlen = 10.0f; // 8 bits + 1 stop, parity ?

    float preDelayBR = bitduration * charlen * 3.5f * 1e6  + 1; // in us

    float postDelayBR = bitduration * charlen * 3.5f * 1e6 + 1; // in us 

    nbModbusMaster.initialize(collectSerial, preDelayBR, postDelayBR,1000);

  ////add task to scheduler

  ts.addTask(collectDataTask);

  ts.addTask(heartBeatTask);

  ////start task

  collectDataTask.enable(); ///start task

  heartBeatTask.enable();

}

bool isMbConnect = false;

int cnt_chip = 0;

void loop() {

  static int retryCount = 0;

  // put your main code here, to run repeatedly:

  ts.execute();

  if (nbModbusMaster.justFinished()) 

  {

    // check for errors

    int err = nbModbusMaster.getError(); // 0 for OK

    if (err) {

      isMbConnect = false;   

      Serial.print("Error: "); nbModbusMaster.printHex(err, Serial); Serial.println();

      if ((err == nbModbusMaster.ku8MBResponseTimedOut) ) {

        retryCount++; 

        Serial.println("Mbtask Retry");

        nbModbusMaster.retry(); // send same cmd again

      }

    } else {

      retryCount = 0; // success

    }

    if (err == 0) {

      isMbConnect = true;

      if(cnt_chip==5)

      {

        PrintfInfo();

      } 

      for (int i = 0; i < nbModbusMaster.getResponseBufferLength(); i++) {

        jke_n60_data_union.read_regs_arr[cnt_chip][i] = nbModbusMaster.getResponseBuffer(i);

        //nbModbusMaster.printHex(nbModbusMaster.getResponseBuffer(i), Serial); Serial.print(" ");

      } 

      cnt_chip++; 

      if(cnt_chip >= 6) cnt_chip = 0;

    }

  }

}

static void PrintfInfo()

{

  char send_buf[100] = {0}; 

  uint32_t *ptr; 

  uint16_t *ptr2;

  float *ptr3;

  memset(send_buf,0,100);

    ///// PRINTF ALL DATA READ FROM CHIP REGISTER.

    for(int j=0;j<6;j++)

    {

    sprintf(send_buf,">>chip/socket : %d Info:",j+1);

    Serial.println(send_buf);      

    ptr= &jke_n60_data_union.jke_n60_str[j].RMS_1;

    ptr2 = &jke_n60_data_union.jke_n60_str[j].RMS_V;

    ptr3 = &jke_n60_data_union.jke_n60_str[j].TPS1;

    for(int i=0;i<35;i++) 

    {

      if(i < 10)       

      {

        sprintf(send_buf,"RMS_%d:    %.2f A,",i+1,*(ptr+i) * 0.001);

        Serial.println(send_buf); 

      }

      else if(i < 20)       

      {

        sprintf(send_buf,"WATT_%d:    %.2f W,",i+1-10,*(ptr+i) * 0.1);

        Serial.println(send_buf); 

      }

      else if(i < 30)       

      {

        sprintf(send_buf,"Energy_%d:    %d kWh,",i+1-20,*(ptr+i) );

        Serial.println(send_buf); 

      }

      else if(i == 30)       

      {

        sprintf(send_buf,"Energy_sum:    %d kWh,",*(ptr+i) );

        Serial.println(send_buf);

        memset(send_buf,0,100);

      }

      else if(i == 31)       

      {

        sprintf(send_buf,"RMS_V:    %.2f V,",*ptr2 *0.01); ///62

        Serial.println(send_buf);

        memset(send_buf,0,100);

      }

      else if(i == 32)       

      {

        sprintf(send_buf,"Period:    %.2f Hz,",*(ptr2+1) *0.01);

        Serial.println(send_buf);

        memset(send_buf,0,100);

      }

      else if(i == 33)       

      {

        sprintf(send_buf,"Chip_Temp:    %.1f ^C,",*ptr3  );

        Serial.println(send_buf);

        memset(send_buf,0,100);

      }

      else if(i == 34)       

      {

        sprintf(send_buf,"PF:    %.4f .",*(ptr3+1) );

        Serial.println(send_buf);

        memset(send_buf,0,100);

      }

    }

    if(j==5)

      Serial.println(">>Data Finished!>>");  

  }

}

static void collectAllChipData()

{

  int read_addr_start = (cnt_chip+1) * 100; 

  String str = "";

  uint16_t size = MAX_U16DATA_LEN;

  nbModbusMaster.readHoldingRegisters(1, read_addr_start, size);

}

arduino ino file download:

  collect_n60_data_demo.zip (Size: 2.45 KB / Downloads: 409)
BIN file (you can use esp32 download tool download to ESP32-S3 with address 0x0 then directly to use) download:

  collect_n60_data_demo.ino.merged.zip (Size: 189.94 KB / Downloads: 417)

before run the code, you need to install NonBlockingModbusMaster arduino library.

  NonBlockingModbusMaster.png (Size: 110.95 KB / Downloads: 435)

modify library .h file replace the number as photo.

  N60-library-setting-change-number.png (Size: 171.03 KB / Downloads: 437)

after running code, will print all data by USB port:

Code:
y_5:    0 kWh,

Energy_6:    0 kWh,

Energy_7:    0 kWh,

Energy_8:    0 kWh,

Energy_9:    0 kWh,

Energy_10:    0 kWh,

RMS_V:    233.58 V,

Period:    49.70 Hz,

Chip_Temp:    25.5 ^C,

PF:    0.0000 .

>>Data Finished!>>

heartbeat task is running.

>>chip/socket : 1 Info:

RMS_1:    0.00 A,

RMS_2:    0.00 A,

RMS_3:    0.00 A,

RMS_4:    0.00 A,

RMS_5:    0.00 A,

RMS_6:    0.00 A,

RMS_7:    0.00 A,

RMS_8:    0.00 A,

RMS_9:    0.00 A,

RMS_10:    0.00 A,

WATT_1:    0.00 W,

WATT_2:    0.00 W,

WATT_3:    0.00 W,

WATT_4:    0.00 W,

WATT_5:    0.00 W,

WATT_6:    0.00 W,

WATT_7:    0.00 W,

WATT_8:    0.00 W,

WATT_9:    0.00 W,

WATT_10:    0.00 W,

Energy_1:    0 kWh,

Energy_2:    0 kWh,

Energy_3:    0 kWh,

Energy_4:    0 kWh,

Energy_5:    0 kWh,

Energy_6:    0 kWh,

Energy_7:    0 kWh,

Energy_8:    0 kWh,

Energy_9:    0 kWh,

Energy_10:    0 kWh,

Energy_sum:    0 kWh,

RMS_V:    0.00 V,

Period:    9.53 Hz,

Chip_Temp:    24.4 ^C,

PF:    0.0000 .

>>chip/socket : 2 Info:

RMS_1:    0.00 A,

RMS_2:    0.00 A,

RMS_3:    0.00 A,

RMS_4:    0.00 A,

RMS_5:    0.00 A,

RMS_6:    0.00 A,

RMS_7:    0.00 A,

RMS_8:    0.00 A,

RMS_9:    0.00 A,

RMS_10:    0.00 A,

WATT_1:    0.00 W,

WATT_2:    0.00 W,

WATT_3:    0.00 W,

WATT_4:    0.00 W,

WATT_5:    0.00 W,

WATT_6:    0.00 W,

WATT_7:    0.00 W,

WATT_8:    0.00 W,

WATT_9:    0.00 W,

WATT_10:    0.00 W,

Energy_1:    0 kWh,

Energy_2:    0 kWh,

Energy_3:    0 kWh,

Energy_4:    0 kWh,

Energy_5:    0 kWh,

Energy_6:    0 kWh,

Energy_7:    0 kWh,

Energy_8:    0 kWh,

Energy_9:    0 kWh,

Energy_10:    0 kWh,

Energy_sum:    0 kWh,

RMS_V:    0.00 V,

Period:    9.53 Hz,

Chip_Temp:    23.8 ^C,

PF:    0.0000 .

>>chip/socket : 3 Info:

RMS_1:    0.00 A,

RMS_2:    0.00 A,

RMS_3:    0.00 A,

RMS_4:    0.00 A,

RMS_5:    0.00 A,

RMS_6:    0.00 A,

RMS_7:    0.00 A,

RMS_8:    0.00 A,

RMS_9:    0.00 A,

RMS_10:    0.00 A,

WATT_1:    0.00 W,

WATT_2:    0.00 W,

WATT_3:    0.00 W,

WATT_4:    0.00 W,

WATT_5:    0.00 W,

WATT_6:    0.00 W,

WATT_7:    0.00 W,

WATT_8:    0.00 W,

WATT_9:    0.00 W,

WATT_10:    0.00 W,

Energy_1:    0 kWh,

Energy_2:    0 kWh,

Energy_3:    0 kWh,

Energy_4:    0 kWh,

Energy_5:    0 kWh,

Energy_6:    0 kWh,

Energy_7:    0 kWh,

Energy_8:    0 kWh,

Energy_9:    0 kWh,

Energy_10:    0 kWh,

Energy_sum:    0 kWh,

RMS_V:    0.00 V,

Period:    9.53 Hz,

Chip_Temp:    25.0 ^C,

PF:    0.0000 .

>>chip/socket : 4 Info:

RMS_1:    0.00 A,

RMS_2:    0.00 A,

RMS_3:    0.00 A,

RMS_4:    0.00 A,

RMS_5:    0.00 A,

RMS_6:    0.00 A,

RMS_7:    0.00 A,

RMS_8:    0.00 A,

RMS_9:    0.00 A,

RMS_10:    0.00 A,

WATT_1:    0.00 W,

WATT_2:    0.00 W,

WATT_3:    0.00 W,

WATT_4:    0.00 W,

WATT_5:    0.00 W,

WATT_6:    0.00 W,

WATT_7:    0.00 W,

WATT_8:    0.00 W,

WATT_9:    0.00 W,

WATT_10:    0.00 W,

Energy_1:    0 kWh,

Energy_2:    0 kWh,

Energy_3:    0 kWh,

Energy_4:    0 kWh,

Energy_5:    0 kWh,

Energy_6:    0 kWh,

Energy_7:    0 kWh,

Energy_8:    0 kWh,

Energy_9:    0 kWh,

Energy_10:    0 kWh,

Energy_sum:    0 kWh,

RMS_V:    0.00 V,

Period:    9.53 Hz,

Chip_Temp:    23.8 ^C,

PF:    0.0000 .

>>chip/socket : 5 Info:

RMS_1:    0.00 A,

RMS_2:    0.00 A,

RMS_3:    0.00 A,

RMS_4:    0.00 A,

RMS_5:    0.00 A,

RMS_6:    0.00 A,

RMS_7:    0.00 A,

RMS_8:    0.00 A,

RMS_9:    0.00 A,

RMS_10:    0.00 A,

WATT_1:    0.00 W,

WATT_2:    0.00 W,

WATT_3:    0.00 W,

WATT_4:    0.00 W,

WATT_5:    0.00 W,

WATT_6:    0.00 W,

WATT_7:    0.00 W,

WATT_8:    0.00 W,

WATT_9:    0.00 W,

WATT_10:    0.00 W,

Energy_1:    0 kWh,

Energy_2:    0 kWh,

Energy_3:    0 kWh,

Energy_4:    0 kWh,

Energy_5:    0 kWh,

Energy_6:    0 kWh,

Energy_7:    0 kWh,

Energy_8:    0 kWh,

Energy_9:    0 kWh,

Energy_10:    0 kWh,

Energy_sum:    0 kWh,

RMS_V:    0.00 V,

Period:    9.53 Hz,

Chip_Temp:    25.5 ^C,

PF:    0.0000 .

>>chip/socket : 6 Info:

RMS_1:    0.00 A,

RMS_2:    0.00 A,

RMS_3:    0.00 A,

RMS_4:    0.00 A,

RMS_5:    0.00 A,

RMS_6:    0.00 A,

RMS_7:    0.00 A,

RMS_8:    0.00 A,

RMS_9:    0.00 A,

RMS_10:    0.00 A,

WATT_1:    0.00 W,

WATT_2:    3.20 W,

WATT_3:    0.00 W,

WATT_4:    0.00 W,

WATT_5:    0.00 W,

WATT_6:    0.00 W,

WATT_7:    0.00 W,

WATT_8:    0.00 W,

WATT_9:    0.00 W,

WATT_10:    0.00 W,

Energy_1:    0 kWh,

Energy_2:    0 kWh,

Energy_3:    0 kWh,

Energy_4:    0 kWh,

Energy_5:    0 kWh,

Energy_6:    0 kWh,

Energy_7:    0 kWh,

Energy_8:    0 kWh,

Energy_9:    0 kWh,

Energy_10:    0 kWh,

Energy_sum:    0 kWh,

RMS_V:    233.50 V,

Period:    49.71 Hz,

Chip_Temp:    25.7 ^C,

PF:    0.0000 .

>>Data Finished!>>

heartbeat task is running.

>>chip/socket : 1 Info:

RMS_1:    0.00 A,

RMS_2:    0.00 A,

RMS_3:    0.00 A,

RMS_4:    0.00 A,

RMS_5:    0.00 A,

RMS_6:    0.00 A,

RMS_7:    0.00 A,

RMS_8:    0.00 A,

RMS_9:    0.00 A,

RMS_10:    0.00 A,

WATT_1:    0.00 W,

WATT_2:    0.00 W,

WATT_3:    0.00 W,

WATT_4:    0.00 W,

WATT_5:    0.00 W,

WATT_6:    0.00 W,

WATT_7:    0.00 W,

WATT_8:    0.00 W,

WATT_9:    0.00 W,

WATT_10:    0.00 W,

Energy_1:    0 kWh,

Energy_2:    0 kWh,

Energy_3:    0 kWh,

Energy_4:    0 kWh,

Energy_5:    0 kWh,

Energy_6:    0 kWh,

Energy_7:    0 kWh,

Energy_8:    0 kWh,

Energy_9:    0 kWh,

Energy_10:    0 kWh,

Energy_sum:    0 kWh,

RMS_V:    0.00 V,

Period:    9.53 Hz,

Chip_Temp:    24.2 ^C,

PF:    0.0000 .

>>chip/socket : 2 Info:

RMS_1:    0.00 A,

RMS_2:    0.00 A,

RMS_3:    0.00 A,

RMS_4:    0.00 A,

RMS_5:    0.00 A,

RMS_6:    0.00 A,

RMS_7:    0.00 A,

RMS_8:    0.00 A,

RMS_9:    0.00 A,

RMS_10:    0.00 A,

WATT_1:    0.00 W,

WATT_2:    0.00 W,

WATT_3:    0.00 W,

WATT_4:    0.00 W,

WATT_5:    0.00 W,

WATT_6:    0.00 W,

WATT_7:    0.00 W,

WATT_8:    0.00 W,

WATT_9:    0.00 W,

WATT_10:    0.00 W,

Energy_1:    0 kWh,

Energy_2:    0 kWh,

Energy_3:    0 kWh,

Energy_4:    0 kWh,

Energy_5:    0 kWh,

Energy_6:    0 kWh,

Energy_7:    0 kWh,

Energy_8:    0 kWh,

Energy_9:    0 kWh,

Energy_10:    0 kWh,

Energy_sum:    0 kWh,

RMS_V:    0.00 V,

Period:    9.53 Hz,

Chip_Temp:    23.8 ^C,

PF:    0.0000 .

>>chip/socket : 3 Info:

RMS_1:    0.00 A,

RMS_2:    0.00 A,

RMS_3:    0.00 A,

RMS_4:    0.00 A,

RMS_5:    0.00 A,

RMS_6:    0.00 A,

RMS_7:    0.00 A,

RMS_8:    0.00 A,

RMS_9:    0.00 A,

RMS_10:    0.00 A,

WATT_1:    0.00 W,

WATT_2:    0.00 W,

WATT_3:    0.00 W,

WATT_4:    0.00 W,

WATT_5:    0.00 W,

WATT_6:    0.00 W,

WATT_7:    0.00 W,

WATT_8:    0.00 W,

WATT_9:    0.00 W,

WATT_10:    0.00 W,

Energy_1:    0 kWh,

Energy_2:    0 kWh,

Energy_3:    0 kWh,

Energy_4:    0 kWh,

Energy_5:    0 kWh,

Energy_6:    0 kWh,

Energy_7:    0 kWh,

Energy_8:    0 kWh,

Energy_9:    0 kWh,

Energy_10:    0 kWh,

Energy_sum:    0 kWh,

RMS_V:    0.00 V,

Period:    9.53 Hz,

Chip_Temp:    25.0 ^C,

PF:    0.0000 .

>>chip/socket : 4 Info:

RMS_1:    0.00 A,

RMS_2:    0.00 A,

RMS_3:    0.00 A,

RMS_4:    0.00 A,

RMS_5:    0.00 A,

RMS_6:    0.00 A,

RMS_7:    0.00 A,

RMS_8:    0.00 A,

RMS_9:    0.00 A,

RMS_10:    0.00 A,

WATT_1:    0.00 W,

WATT_2:    0.00 W,

WATT_3:    0.00 W,

WATT_4:    0.00 W,

WATT_5:    0.00 W,

WATT_6:    0.00 W,

WATT_7:    0.00 W,

WATT_8:    0.00 W,

WATT_9:    0.00 W,

WATT_10:    0.00 W,

Energy_1:    0 kWh,

Energy_2:    0 kWh,

Energy_3:    0 kWh,

Energy_4:    0 kWh,

Energy_5:    0 kWh,

Energy_6:    0 kWh,

Energy_7:    0 kWh,

Energy_8:    0 kWh,

Energy_9:    0 kWh,

Energy_10:    0 kWh,

Energy_sum:    0 kWh,

RMS_V:    0.00 V,

Period:    9.53 Hz,

Chip_Temp:    23.6 ^C,

PF:    0.0000 .

>>chip/socket : 5 Info:

RMS_1:    0.00 A,

RMS_2:    0.00 A,

RMS_3:    0.00 A,

RMS_4:    0.00 A,

RMS_5:    0.00 A,

RMS_6:    0.00 A,

RMS_7:    0.00 A,

RMS_8:    0.00 A,

RMS_9:    0.00 A,

RMS_10:    0.00 A,

WATT_1:    0.00 W,

WATT_2:    0.00 W,

WATT_3:    0.00 W,

WATT_4:    0.00 W,

WATT_5:    0.00 W,

WATT_6:    0.00 W,

WATT_7:    0.00 W,

WATT_8:    0.00 W,

WATT_9:    0.00 W,

WATT_10:    0.00 W,

Energy_1:    0 kWh,

Energy_2:    0 kWh,

Energy_3:    0 kWh,

Energy_4:    0 kWh,

Energy_5:    0 kWh,

Energy_6:    0 kWh,

Energy_7:    0 kWh,

Energy_8:    0 kWh,

Energy_9:    0 kWh,

Energy_10:    0 kWh,

Energy_sum:    0 kWh,

RMS_V:    0.00 V,

Period:    9.53 Hz,

Chip_Temp:    24.8 ^C,

PF:    0.0000 .

>>chip/socket : 6 Info:

RMS_1:    0.00 A,

RMS_2:    0.00 A,

RMS_3:    0.00 A,

RMS_4:    0.00 A,

RMS_5:    0.00 A,

RMS_6:    0.00 A,

RMS_7:    0.00 A,

RMS_8:    0.00 A,

RMS_9:    0.00 A,

RMS_10:    0.00 A,

WATT_1:    0.00 W,

WATT_2:    1.50 W,

WATT_3:    0.00 W,

WATT_4:    0.00 W,

WATT_5:    0.00 W,

WATT_6:    0.00 W,

WATT_7:    0.00 W,

WATT_8:    0.00 W,

WATT_9:    0.00 W,

WATT_10:    0.00 W,

Energy_1:    0 kWh,

Energy_2:    0 kWh,

Energy_3:    0 kWh,

Energy_4:    0 kWh,

Energy_5:    0 kWh,

Energy_6:    0 kWh,

Energy_7:    0 kWh,

Energy_8:    0 kWh,

Energy_9:    0 kWh,

Energy_10:    0 kWh,

Energy_sum:    0 kWh,

RMS_V:    233.57 V,

Period:    49.71 Hz,

Chip_Temp:    25.5 ^C,

PF:    0.0000 .

>>Data Finished!>>

heartbeat task is running.

heartbeat task is running.

>>chip/socket : 1 Info:

RMS_1:    0.00 A,

RMS_2:    0.00 A,

RMS_3:    0.00 A,

RMS_4:    0.00 A,

RMS_5:    0.00 A,

RMS_6:    0.00 A,

RMS_7:    0.00 A,

RMS_8:    0.00 A,

RMS_9:    0.00 A,

RMS_10:    0.00 A,

WATT_1:    0.00 W,

WATT_2:    0.00 W,

WATT_3:    0.00 W,

WATT_4:    0.00 W,

WATT_5:    0.00 W,

WATT_6:    0.00 W,

WATT_7:    0.00 W,

WATT_8:    0.00 W,

WATT_9:    0.00 W,

WATT_10:    0.00 W,

Energy_1:    0 kWh,

Energy_2:    0 kWh,

Energy_3:    0 kWh,

Energy_4:    0 kWh,

Energy_5:    0 kWh,

Energy_6:    0 kWh,

Energy_7:    0 kWh,

Energy_8:    0 kWh,

Energy_9:    0 kWh,

Energy_10:    0 kWh,

Energy_sum:    0 kWh,

RMS_V:    0.00 V,

Period:    9.53 Hz,

Chip_Temp:    24.0 ^C,

PF:    0.0000 .

>>chip/socket : 2 Info:

RMS_1:    0.00 A,

RMS_2:    0.00 A,

RMS_3:    0.00 A,

RMS_4:    0.00 A,

RMS_5:    0.00 A,

RMS_6:    0.00 A,

RMS_7:    0.00 A,

RMS_8:    0.00 A,

RMS_9:    0.00 A,

RMS_10:    0.00 A,

WATT_1:    0.00 W,

WATT_2:    0.00 W,

WATT_3:    0.00 W,

WATT_4:    0.00 W,

WATT_5:    0.00 W,

WATT_6:    0.00 W,

WATT_7:    0.00 W,

WATT_8:    0.00 W,

WATT_9:    0.00 W,

WATT_10:    0.00 W,

Energy_1:    0 kWh,

Energy_2:    0 kWh,

Energy_3:    0 kWh,

Energy_4:    0 kWh,

Energy_5:    0 kWh,

Energy_6:    0 kWh,

Energy_7:    0 kWh,

Energy_8:    0 kWh,

Energy_9:    0 kWh,

Energy_10:    0 kWh,

Energy_sum:    0 kWh,

RMS_V:    0.00 V,

Period:    9.53 Hz,

Chip_Temp:    23.8 ^C,

PF:    0.0000 .

>>chip/socket : 3 Info:

RMS_1:    0.00 A,

RMS_2:    0.00 A,

RMS_3:    0.00 A,

RMS_4:    0.00 A,

RMS_5:    0.00 A,

RMS_6:    0.00 A,

RMS_7:    0.00 A,

RMS_8:    0.00 A,

RMS_9:    0.00 A,

RMS_10:    0.00 A,

WATT_1:    0.00 W,

WATT_2:    0.00 W,

WATT_3:    0.00 W,

WATT_4:    0.00 W,

WATT_5:    0.00 W,

WATT_6:    0.00 W,

WATT_7:    0.00 W,

WATT_8:    0.00 W,

WATT_9:    0.00 W,

WATT_10:    0.00 W,

Energy_1:    0 kWh,

Energy_2:    0 kWh,

Energy_3:    0 kWh,

Energy_4:    0 kWh,

Energy_5:    0 kWh,

Energy_6:    0 kWh,

Energy_7:    0 kWh,

Energy_8:    0 kWh,

Energy_9:    0 kWh,

Energy_10:    0 kWh,

Energy_sum:    0 kWh,

RMS_V:    0.00 V,

Period:    9.53 Hz,

Chip_Temp:    25.3 ^C,

PF:    0.0000 .

>>chip/socket : 4 Info:

RMS_1:    0.00 A,

RMS_2:    0.00 A,

RMS_3:    0.00 A,

RMS_4:    0.00 A,

RMS_5:    0.00 A,

RMS_6:    0.00 A,

RMS_7:    0.00 A,

RMS_8:    0.00 A,

RMS_9:    0.00 A,

RMS_10:    0.00 A,

WATT_1:    0.00 W,

WATT_2:    0.00 W,

WATT_3:    0.00 W,

WATT_4:    0.00 W,

WATT_5:    0.00 W,

WATT_6:    0.00 W,

WATT_7:    0.00 W,

WATT_8:    0.00 W,

WATT_9:    0.00 W,

WATT_10:    0.00 W,

Energy_1:    0 kWh,

Energy_2:    0 kWh,

Energy_3:    0 kWh,

Energy_4:    0 kWh,

Energy_5:    0 kWh,

Energy_6:    0 kWh,

Energy_7:    0 kWh,

Energy_8:    0 kWh,

Energy_9:    0 kWh,

Energy_10:    0 kWh,

Energy_sum:    0 kWh,

RMS_V:    0.00 V,

Period:    9.53 Hz,

Chip_Temp:    23.6 ^C,

PF:    0.0000 .

>>chip/socket : 5 Info:

RMS_1:    0.00 A,

RMS_2:    0.00 A,

RMS_3:    0.00 A,

RMS_4:    0.00 A,

RMS_5:    0.00 A,

RMS_6:    0.00 A,

RMS_7:    0.00 A,

RMS_8:    0.00 A,

RMS_9:    0.00 A,

RMS_10:    0.00 A,

WATT_1:    0.00 W,

WATT_2:    0.00 W,

WATT_3:    0.00 W,

WATT_4:    0.00 W,

WATT_5:    0.00 W,

WATT_6:    0.00 W,

WATT_7:    0.00 W,

WATT_8:    0.00 W,

WATT_9:    0.00 W,

WATT_10:    0.00 W,

Energy_1:    0 kWh,

Energy_2:    0 kWh,

Energy_3:    0 kWh,

Energy_4:    0 kWh,

Energy_5:    0 kWh,

Energy_6:    0 kWh,

Energy_7:    0 kWh,

Energy_8:    0 kWh,

Energy_9:    0 kWh,

Energy_10:    0 kWh,

Energy_sum:    0 kWh,

RMS_V:    0.00 V,

Period:    9.53 Hz,

Chip_Temp:    25.3 ^C,

PF:    0.0000 .

>>chip/socket : 6 Info:

RMS_1:    0.00 A,

RMS_2:    0.00 A,

RMS_3:    0.00 A,

RMS_4:    0.00 A,

RMS_5:    0.00 A,

RMS_6:    0.00 A,

RMS_7:    0.00 A,

RMS_8:    0.00 A,

RMS_9:    0.00 A,

RMS_10:    0.00 A,

WATT_1:    0.00 W,

WATT_2:    1.50 W,

WATT_3:    0.00 W,

WATT_4:    0.00 W,

WATT_5:    0.00 W,

WATT_6:    0.00 W,

WATT_7:    0.00 W,

WATT_8:    0.00 W,

WATT_9:    0.00 W,

WATT_10:    0.00 W,

Energy_1:    0 kWh,

Energy_2:    0 kWh,

Energy_3:    0 kWh,

Energy_4:    0 kWh,

Energy_5:    0 kWh,

Energy_6:    0 kWh,

Energy_7:    0 kWh,

Energy_8:    0 kWh,

Energy_9:    0 kWh,

Energy_10:    0 kWh,

Energy_sum:    0 kWh,

RMS_V:    233.49 V,

Period:    49.71 Hz,

Chip_Temp:    25.7 ^C,

PF:    0.0000 .

>>Data Finished!>>

heartbeat task is running.

[arduino code examples for N10]-04 Print TEXT on SSD1306 OLED displayer

Sun, 03 Aug 2025 11:21:58 +0800

Code:
/*

 * Made by KinCony IoT: https://www.kincony.com

 * 

 * This Arduino program demonstrates how to display text on an SSD1306 128x64 OLED display using the U8g2 library.

 * The program draws two lines of text on the display:

 * - The first line is "KINCONY" in a larger font.

 * - The second line is "www.kincony.com" in a smaller font.

 * 

 * The display is connected via I2C (software implementation) with:

 * - SCL (clock) on pin IO17

 * - SDA (data) on pin IO18

 * 

 * The display's I2C address is set to 0x3C.

 */

#include   // Include the U8g2 library for controlling the OLED display

#include      // Include the Wire library for I2C communication

// Initialize the display using the software I2C method (SCL = IO18, SDA = IO8)

U8G2_SSD1306_128X64_NONAME_F_SW_I2C u8g2(U8G2_R0,  17, 18, U8X8_PIN_NONE);  // Screen rotation: U8G2_R0

// Function to display page 1 content

void page1() {

  // Set font size 18 for the larger "KINCONY" text

  u8g2.setFont(u8g2_font_timR18_tf);  // Use the Times Roman font, size 18

  u8g2.setFontPosTop();               // Set the text position at the top of the display

  u8g2.setCursor(5, 0);               // Position the cursor at coordinates (5, 0)

  u8g2.print("KINCONY");              // Display the text "KINCONY" on the screen

  // Set font size 12 for the smaller "www.kincony.com" text

  u8g2.setFont(u8g2_font_timR12_tf);  // Use the Times Roman font, size 12

  u8g2.setCursor(0, 40);              // Position the cursor at coordinates (0, 40)

  u8g2.print("www.kincony.com");      // Display the text "www.kincony.com"

}

// Setup function, runs once when the program starts

void setup() {

  // Set the I2C address for the display to 0x3C

  u8g2.setI2CAddress(0x3C*2);  // I2C address shift for 8-bit format

  // Initialize the display

  u8g2.begin();

  // Enable UTF-8 character printing for the display

  u8g2.enableUTF8Print();  // Allow UTF-8 encoded text to be printed

}

// Main loop function, continuously runs after setup()

void loop() {

  // Begin the display drawing process

  u8g2.firstPage();  // Prepare the first page for drawing

  do {

    // Call the page1() function to draw content on the display

    page1();

  } while (u8g2.nextPage());  // Continue to the next page until all pages are drawn

}

arduino ino file download:

4-oled-ssd1306.zip (Size: 1.11 KB / Downloads: 378)
BIN file (you can use esp32 download tool download to ESP32-S3 with address 0x0 then directly to use) download:

4-oled-ssd1306.ino.merged.zip (Size: 202.58 KB / Downloads: 420)