Controller

Table of Contents

For the following devices driver implementations are available in OpenEMS Edge.

1. BYD Battery-Box Commercial

Implemented Natures

  • Battery

Source Code

2. Soltaro Battery Rack

Implemented Natures

  • Battery

Source Code

3. KACO blueplanet gridsave

  • Applies to

    • KACO blueplanet gridsave 50.0 TL3

    • KACO blueplanet gridsave 92.0 TL3

  • Implemented Natures

    • StartStoppable

    • SymmetricBatteryInverter

    • ManagedSymmetricBatteryInverter

Source Code

4. SunSpec PV inverter

Generic implementation of SunSpec PV inverters. It is tested with - KACO blueplanet TL.3 series - SolarEdge SE12.5K - SE27.6K

Implemented Natures

  • ManagedSymmetricPvInverter

  • SymmetricMeter

Source Code

5. Core services for OpenEMS Edge

5.1. ComponentManager

A service that provides easy access to OpenEMS-Components and Channels. It also provides some sub-services:

DefaultConfigurationWorker

Applies a default configuration, i.e. activates certain OpenEMS Components that are to be enabled by default on deployment, like Modbus-TCP-Slave Api and JSON/REST Api.

OsgiValidateWorker

Checks if configured Components are actually enabled.

OutOfMemoryHeapDumpWorker

Checks for heap-dump files which get created if OpenEMS Edge crashed because of an OutOfMemory-Error in a previous run.

5.2. Cycle

Provides the core runtime Cycle of OpenEMS Edge

5.3. Host

A service that provides host and operating system specific commands like configuration of TCP/IP network.

5.4. Meta

A service that provides 'OpenemsConstants' as Channels so that they are available via Apis; example: _meta/Version for the current version of OpenEMS Edge.

5.5. Sum

A service that holds summed up information on the power and energy flows, like aggregated production, consumption and energy storage charge/discharge.

6. FENECON BYD Container

Implemented Natures

  • SymmetricEss

  • ManagedSymmetricEss

Source Code

7. ESS Cluster

Combines multiple energy storage systems (ESS) to one common ESS. This way every Controller can easily work with multiple ESS in parallel. Distribution of power requests to each ESS is controlled via the Power-Class .

Source Code

8. FENECON Commercial 40 AC/DC/Hybrid

Implemented Natures

  • SymmetricEss

  • ManagedSymmetricEss

  • EssDcCharger

Source Code

9. Generic Energy Storage System

Represents an Energy Storage System consisting of a Battery-Inverter and a Battery.

Source Code

10. KACO blueplanet gridsave 50.0 TL3

Implemented Natures

  • SymmetricEss

  • ManagedSymmetricEss

Source Code

11. Maschinenfabrik Rheinhausen (MR) Gridcon

Implemented Natures

  • SymmetricEss

  • ManagedSymmetricEss

Source Code

12. REFU Battery Inverter

Project specific implementation of a REFU inverter. This will not directly apply to all REFU battery inverters.

Implemented Natures

  • SymmetricEss

  • ManagedSymmetricEss

  • AsymmetricEss

  • ManagedAsymmetricEss

Source Code

13. REFUstore 88K

Implemented Natures

  • SymmetricEss

  • ManagedSymmetricEss

Manufacturer Product Page Source Code

14. Sinexcel Battery Inverter

Implemented Natures

  • SymmetricEss

  • ManagedSymmetricEss

Source Code

15. SMA SunnyIsland 6.0H

Implemented Natures

  • SymmetricEss

  • ManagedSymmetricEss

  • AsymmetricEss

  • ManagedAsymmetricEss

  • SinglePhaseEss

  • ManagedSinglePhaseEss

Source Code

16. EVCS Cluster

Distributes the charging power (Depending on the implementation) to the priorized charging stations. The implementations calculate the maximum power that can be used by all charging stations.

Possible Cluster implementations:

Cluster for peak shaving
The peak shaving cluster is calculating the power depending on the grid power that can be used per phase, the maximum allowed storage power and the current values of grid, storage and EVCS consumption.

Cluster for self consumption
The self consumption cluster is calculating the power depending on the excess power.

Source Code

17. KEBA KeContact c-series Charging Station

This component implements the KEBA c-series charging station, which is controlled and read out using the proprietary UDP protocol. It collects all relevant informations into the given Nature Channels and its own Channels and sends charging commands that have been set by another controllers.

Implemented Natures: * Evcs (Electric Vehicle Charging Station) * ManagedEvcs

Source Code

18. ABL Charging Station

This component implements the ABL EMH 3 series charging station, which is controlled and read out using the OCPP protocol. It provides specific informations for the AbstractOcppEvcsComponent.

Implemented Natures: * Evcs (Electric Vehicle Charging Station) * MeasuringEvcs

Extended abstract class: * AbstractOcppEvcsComponent

Source Code

19. Electric Vehicle Charging Station OCPP Common

The Open Charge Point Protocol (OCPP) is an application protocol for communication between Electric vehicle charging stations (EVCS) and a central management system.

The whole bundle contains a library of the OCPP functions. It also provides a default abstract ocpp EVCS component that can be used by every specific charging station and a OcppServer interface that provides a minimum functionality, to be able to send data to a charging station.

Implemented Natures: * Evcs (Electric Vehicle Charging Station * MeasuringEvcs (Can get measured informations)

Source Code

20. IES KeyWatt Charging Station

This component implements the IES KeyWatt CCS charging station with a single plug, which is controlled and read out using the OCPP protocol. It provides specific informations for the AbstractOcppEvcsComponent.

Implemented Natures: * Evcs (Electric Vehicle Charging Station * ManagedEvcs * MeasuringEvcs (Can get measured informations)

Extended abstract class: * AbstractOcppEvcsComponent

Source Code

21. OCPP Server

The OCPP Server is implementing a central management system. The server maintains connections to the EVCS’s, i.e.

  • connects to the charging stations

  • distributes their information to each EVCS component

  • send commands to the charging stations

Source Code

22. FENECON DESS

Applies to multiple similar products like the FENECON by BYD PRO Hybrid.

Implemented Natures

  • SymmetricEss

  • AsymmetricEss

  • EssDcCharger

  • AsymmetricMeter (for Grid and AC-connected PV)

  • SymmetricMeter (for Grid and AC-connected PV)

Source Code

23. FENECON Mini 3-3 | 3-6

Implemented Natures

  • SinglePhaseEss

  • AsymmetricEss

  • SymmetricEss

  • SymmetricMeter (for Grid and PV)

Source Code

24. FENECON Pro 9-12

Implemented Natures

  • SymmetricEss

  • ManagedSymmetricEss

  • AsymmetricEss

  • ManagedAsymmetricEss

  • AsymmetricMeter (for PV)

  • SymmetricMeter (for PV)

Source Code

25. GoodWe ET-Series

Battery-Inverter:

  • SymmetricEss

Charger:

  • EssDcCharger

Grid-Meter:

  • SymmetricMeter

  • AsymmetricMeter

Source Code

26. KMtronic Modbus Relay Board

This bundle implements the Kmtronic Modbus Relay board. Relay outputs can be used to turn ON/OFF lights, motors and signal alarms. This relay has 8 output channels.

Implemented Natures

  • DigitalOutput

26.1. Configuration

  • Id Unique ID of this Component (id), e.g. "io0", "io1"

  • Modbus-ID ID of Modbus bridge. (modbus.id)

  • Modbus Unit-ID The Unit-ID of the Modbus device. (modbusUnitId)

26.1.1. Example Configuration

  • Id : io0

  • Modbus-ID : modbus3

  • Modbus Unit-ID : 1

Source Code

27. RevolutionPi Digital IO Module

This bundle implements the Kunbus RevolutionPI DigitalIO enhancement board. It can be used to turn ON/OFF a data output or to read in digital data input. It provides 14 digital input and 14 digital output channels.

Implemented Natures: - DigitalOutput - DigitalInput

27.1. Dependencies

The RevolutionPi Digital IO OpenEms Bundle depends on the librevpi-dio-java git library project. A binary version of this library is already included in this OpenEMS Bundle. See https://github.com/clehne/librevpi-dio-java for more information.

27.2. Notes

Prepare Kunbus RevPi:

The Digital IO hardware enhancement module on your Kunbus RevolutionPi system needs to be enabled before starting OpenEMS (see Kunbus-Website for configuration settings).

28. Shelly WiFi Relay Switch

This bundle implements Shelly WiFi Relay Switches.

Compatible with - Shelly 2.5 - Shelly Plug S

Implemented Natures - DigitalOutput

Source Code

29. WAGO Fieldbus Coupler 750-352

Implemented Natures

  • DigitalOutput

  • DigitalInput

This component reads the current WAGO fieldbus coupler configuration and dynamically creates its Input and Output Channels accordingly.

Make sure to update the WAGO fieldbus coupler configuration before activating this component. Open the WAGO fieldbus web interface, click "IO config" and "create ea-config.xml" to update the configuration. Default username is admin, default password is wago.

The following examples assume the Component-ID is io0 and the addresses are valid for the first WAGO extension. For extensions 2, 3,…​ just increase the number behind M. Channel names follow this logic:

29.1. WAGO 750-523 "1-channel relay output"

wago.com

io0/RelayM1

Input/Output

the relay

io0/RelayM1Hand

Input

state of the manual switch

29.2. WAGO 750-501 "2-channel digital output"

wago.com

io0/DigitalOutputM1C1

Input/Output

the first digital output

io0/DigitalOutputM1C2

Input/Output

the first digital output

29.3. WAGO 750-400 "2-channel digital input"

wago.com

io0/DigitalInputM1C1

Input

the first digital input

io0/DigitalInputM1C2

Input

the second digital input

Source Code

30. KOSTAL PIKO

Implemented Natures

  • SymmetricEss

  • SymmetricMeter (for Grid meter)

  • EssDcCharger (for PV)

Source Code

31. ABB B23 Meter

Implemented Natures

  • SymmetricMeter

  • AsymmetricMeter

Source Code

32. Artemes AM-2

Implemented Natures

  • SymmetricMeter

  • AsymmetricMeter

Source Code

33. B-Control | TQ-Systems EM300 Meter

Implemented Natures

  • SymmetricMeter

  • AsymmetricMeter

Source Code

34. Carlo Gavazzi EM300 Meter

Applies to - CARLO GAVAZZI EM330 - CARLO GAVAZZI EM340

Implemented Natures - SymmetricMeter - AsymmetricMeter

Source Code

35. Discovergy Smart-Meter

Reads data of a Discovergy Smart-Meter via online REST-Api. See https://api.discovergy.com for details.

Implemented Natures

  • SymmetricMeter

  • AsymmetricMeter

Source Code

36. Janitza Meters UMG 96RM-E | UMG 604

Implemented Natures

  • SymmetricMeter

  • AsymmetricMeter

Source Code

37. Microcare SDM 630 Meter

This implementation is functionally compatible with a number of energy meters with the name "SDM 630".

Implemented Natures

  • SymmetricMeter

  • AsymmetricMeter

Source Code

38. PQ Plus UMD 97 Meter

Applies also to UMD 96, UMD 97, UMD 98, UMD 807, UMD 701, UMD 704, UMD 705, UMD 706, UMD 707, UMD 709, UMD 710, UMD 913, UMC 26

Implemented Natures

  • SymmetricMeter

  • AsymmetricMeter

Source Code

39. Schneider Acti9 Smartlink Meter

Implemented Natures

  • SymmetricMeter

  • AsymmetricMeter

To configure the meter, first add a modbus tcp bridge connecting to the correct IP address, then configure this meter to use the configured modbus bridge. The unit ID is by default 1.

Source Code

40. SOCOMEC Meter

Just configure Meter.Socomec.Singlephase or Meter.Socomec.Threephase. The actual type and modbus protocol of the Socomec meter is identified automatically.

Source Code

41. SunSpec Meter

Generic implementation of SunSpec Meters.

Implemented Natures

  • AsymmetricMeter

  • SymmetricMeter

Source Code

42. Virtual Symmetric Add

This is a virtual meter which is used to sum up the values from multiple symmetric meters. The use case for this feature is, Usually when there are multiple meters reading values from different systems, The average values from the systems make more sense for calculation and statistics.

Implemented Natures

  • SymmetricMeter

42.1. Configuration

  • Component-ID Unique ID of this Component (id), e.g. "ctrlIoAlarm0", "ctrlIoAlarm1"

  • Alias Human-readable name of this Component; defaults to Component-ID (alias)

  • Is enabled Is this Component enabled?

  • Meter-Type Type of the Meters (Grid meter or Production meter)

  • Meter IDs Ids of the meters to be summed up,

42.2. Example Configuration

  • Component-ID : meter0

  • Alias : virtualMeter

  • Meter-Type : PRODUCTION

  • Meter IDs : [meter1, meter2, meter3]

Meter IDs is a list of the meters which needs summing of the values.

The above example configuration describes, The values from the three meters configured (meter1, meter2, meter3) are summed up and average values is set to the corresponding channel address.

Source Code

43. Weidmueller 525 Meter

Implemented Natures

  • SymmetricMeter

  • AsymmetricMeter

Source Code

44. OneWire Thermometer

Implemented Natures

  • Thermometer

Source Code

45. Persistence Model Predictor

Predicts values using the 'same-as-last-day' approach.

46. PV-Inverter Cluster

Combines multiple PV-Inverters to one common PV-Inverter. This way every Controller can easily work with multiple PV-Inverters in parallel.

Source Code

47. KACO blueplanet PV inverter

Implementation of the KACO blueplanet series PV inverters.

Implemented Natures

  • ManagedSymmetricPvInverter

  • SymmetricMeter

Source Code

48. SMA Sunny Tripower PV inverter

Implementation of the SMA Sunny Tripower PV inverters.

Tested on - SMA SUNNY TRIPOWER 15000TL / 20000TL / 25000TL

Implemented Natures: - SymmetricMeter - ManagedSymmetricPvInverter

Source Code

49. Solar-Log

Implemented Natures

  • SymmetricPvInverter

  • SymmetricMeter

Source Code

50. SunSpec PV inverter

Generic implementation of SunSpec PV inverters. It is tested with - KACO blueplanet TL.3 series - SolarEdge SE12.5K - SE27.6K

Implemented Natures

  • ManagedSymmetricPvInverter

  • SymmetricMeter

Source Code

51. Simulated OpenEMS Components

This bundle provides simulated OpenEMS Components for the Natures. They are useful for testing and demoing without real hardware.

51.1. Simulator-App

The Simulator-App is a very specific component that needs to be handled with care. It provides a full simulation environment to run an OpenEMS Edge instance in simulated realtime environment.

Be aware that the SimulatorApp Component takes control over the complete OpenEMS Edge Application, i.e. if you enable it, it is going to delete all existing Component configurations!

To run a simulation: - Run OpenEMS Edge using the EdgeApp.bndrun - Configure a read-write JSON/REST Api - Send a JSON-RPC Request like the following, providing full configurations for all required OpenEMS Edge Components

{
    "method": "componentJsonApi",
    "params": {
        "componentId": "_simulator",
        "payload": {
            "method": "executeSimulation",
            "params": {
                "components": [
                    {
                        "factoryPid": "Scheduler.AllAlphabetically",
                        "properties": [
                            {
                                "name": "id",
                                "value": "scheduler0"
                            }
                        ]
                    },
                    {
                        "factoryPid": "Simulator.GridMeter.Reacting",
                        "properties": [
                            {
                                "name": "id",
                                "value": "meter0"
                            }
                        ]
                    },
                    {
                        "factoryPid": "Simulator.Datasource.CSV.Direct",
                        "properties": [
                            {
                                "name": "id",
                                "value": "datasource1"
                            },
                            {
                                "name": "source",
                                "value": "1000\n2000\n2500\n2000"
                            },
                            {
                                "name": "timeDelta",
                                "value": 5
                            }
                        ]
                    },
                    {
                        "factoryPid": "Simulator.NRCMeter.Acting",
                        "properties": [
                            {
                                "name": "id",
                                "value": "meter1"
                            },
                            {
                                "name": "datasource.id",
                                "value": "datasource1"
                            }
                        ]
                    },
                    {
                        "factoryPid": "Simulator.EssSymmetric.Reacting",
                        "properties": [
                            {
                                "name": "id",
                                "value": "ess0"
                            },
                            {
                                "name": "maxApparentPower",
                                "value": 10000
                            },
                            {
                                "name": "capacity",
                                "value": 10000
                            },
                            {
                                "name": "initialSoc",
                                "value": 50
                            }
                        ]
                    },
                    {
                        "factoryPid": "Controller.Symmetric.Balancing",
                        "properties": [
                            {
                                "name": "id",
                                "value": "ctrlBalancing0"
                            },
                            {
                                "name": "ess.id",
                                "value": "ess0"
                            },
                            {
                                "name": "meter.id",
                                "value": "meter0"
                            }
                        ]
                    }
                ],
                "clock": {
                    "start": "2000-01-01T13:00:00.00Z",
                    "end": "2000-01-01T14:00:00.00Z",
                    "timeleapPerCycle": 1000
                }
            }
        }
    }
}

Source Code

52. SolarEdge PV Inverter + Grid-Meter

Implementation of the SolarEdge PV inverters.

Implemented Natures

  • SymmetricMeter

  • AsymmetricMeter

Source Code

53. Tesla Powerwall 2

Implementation of the Tesla Powerwall 2 energy storage system

Implemented Natures

  • SymmetricEss

Source Code

54. InfluxDB

Persists all data of OpenEMS Edge Channels to an InfluxDB timeseries database.

Source Code

55. RRD4J

Persists data of OpenEMS Edge Channels to RRD4J files.

Source Code

56. KACO blueplanet hybrid 10.0 TL3

Implemented Natures

  • SymmetricEss

  • ManagedSymmetricEss

(proprietary)