Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
m30 rs485 compatible energy meter
#11
Hi! im ready to order the m30 and a few other stuffs. Need a RS485 meter to connect to the M30 . The attached image rs485 has a specific Yaml file? I can't find information for the 80AMP model. Only for the 40Amp. Any help to proceed the purchase?


Attached Files Image(s)
   
Reply
#12
already repied your question in another topic. not need let this meter connect to M30, you should connect to Pi's RS485 port.
Reply
#13
thanks for the fast response. Don't use a Raspberry Pi.
Maybe im asking something wrong. How to use those ports in the M30?

Ohh Great. A little question. The https://youtu.be/xEvOK3R12kc Use this yaml
for a8
uart:
  id: mod_bus
  tx_pin: 33
  rx_pin: 32
  baud_rate: 9600
  stop_bits: 1
  parity: EVEN

But for m30
uart:
  id: modbus_uart
  rx_pin: 32
  tx_pin: 33
  baud_rate: 115200
  stop_bits: 1
  data_bits: 8
  parity: NONE

Need to change in the yaml for the m30 the Uart to the similar in a8?



wich will be correct ?


Attached Files Image(s)
   
Reply
#14
M30 RS485 port not connected with ESP32's gpio. it's just a MODBUS SLAVE device. if you MUST want use by ESPHome, connect this RS485 wire with other KinCony ESP32 board's RS485 port.
Reply
#15
(07-11-2024, 11:11 AM)admin Wrote: M30 RS485 port not connected with ESP32's gpio.  it's just a MODBUS SLAVE device. if you MUST want use by ESPHome,  connect this RS485 wire with other KinCony ESP32 board's RS485 port.

Ohh!great  so I can use with the A24 pro for example? in The oficial yaml file for the a24 and the a32 pro there is no info for the rs485.. Can you share how to use the RS485 with the a24? Thanks a lot!!

Maybe adding this to the config yaml file make the magic?
uart:
  id: mod_bus
  tx_pin: 33
  rx_pin: 32
  baud_rate: 9600
  stop_bits: 1
  parity: EVEN

modbus:
  id: modbus1
  uart_id: mod_bus

modbus_controller:
  - id: a24
    address: 0x01
    modbus_id: modbus1
    setup_priority: -10
    update_interval: 5s


sensor:
  - platform: modbus_controller
    modbus_controller_id: a24
    name: "Voltage"
    id: modbus_voltage
    register_type: holding
    address: 0x64
    unit_of_measurement: "V"
    value_type: FP32
    accuracy_decimals: 2

  - platform: modbus_controller
    modbus_controller_id: a24
    name: "Current"
    id: modbus_current
    register_type: holding
    address: 0x6A
    unit_of_measurement: "A"
    value_type: FP32
    accuracy_decimals: 2

  - platform: modbus_controller
    modbus_controller_id: a24
    name: "Active Power"
    id: modbus_Active_Power
    register_type: holding
    address: 0x76
    unit_of_measurement: "kW"
    value_type: FP32
    accuracy_decimals: 2

  - platform: modbus_controller
    modbus_controller_id: a24
    name: "Power Factor"
    id: modbus_Power_Factor
    register_type: holding
    address: 0x8E
    unit_of_measurement: ""
    value_type: FP32
    accuracy_decimals: 2

  - platform: modbus_controller
    modbus_controller_id: a24
    name: "Grid Frequency"
    id: modbus_Grid_Frequency
    register_type: holding
    address: 0x90
    unit_of_measurement: "hz"
    value_type: FP32
    accuracy_decimals: 2

  - platform: modbus_controller
    modbus_controller_id: a24
    name: "Total Energy"
    id: modbus_Total_Energy
    register_type: holding
    address: 0x0
    unit_of_measurement: "kWh"
    value_type: FP32
    accuracy_decimals: 2
Reply
#16
Do not submit duplicate questions
Reply


Forum Jump:


Users browsing this thread:
1 Guest(s)