EVA-ICS v4 modbus-controller monitoring integratie

Modifications
, , , , , ,
1

Hi all,

I am currently trying to connect an EVA-ICS v4 automation platform to connect to the modbus server on a cerbo-gx.

I have some troubles understanding the connections on unit id, registers, etc. Is there someone in this community who can give me an example.

I am using the cerbo-gx simulator running scenario m.

What I currently have managed:

```yaml

# Modbus master controller service
command: svc/eva-controller-modbus
bus:
  path: var/bus.ipc
config:
  modbus:
    protocol: tcp
    path: venus-gx-simulator:502
    unit: 1
  panic_in: null
  retries: 2
  queue_size: 32768
  pull_cache_sec: 3600
  pull_interval: 1.0
  pull:
    - count: 1
      reg: 512
      unit: 225
      map:
        - offset: 0
          oid: sensor:unit-1/com.victronenergy.battery
          type: int16
  action_queue_size: 32
  actions_verify: true
timeout:
  startup: 10
user: nobody
react_to_fail: false

Hope anyone can get me started. Thnx in advance.

2

is the problem the missing g in victronenergy?

3

nope, that is an internal name. It is mainly about how to configure count, reg, unit, offset and type which are specifying the modbus register etc. An example for the Battery SoC is suffient, the rest I can construct myself them. I only need a mapping for the downloaded excel from Victron to EVA-ICS configuration.

4

I figured it out by reverse enigineering the open source code,

pull:
  - count: 1
    reg: h266
    unit: 225
    map:
      - offset: 0
        oid: sensor:unit-1/com.victronenery.battery
        type: uint16

provides the right response. For ayone who would like to try this too.