Services / 01

Test environments that behave like the real installation.

We build emulators, simulators and hardware-in-the-loop rigs that let you test devices and software reproducibly: at your desk, in the lab and in the CI pipeline.

Fig. 01Test environment
  1. EmulationDevice profilesSensor · meter · charge point
  2. Device under testYour device, your softwareunchanged, over real interfaces
  3. EvaluationTest run with reportlocal, in the lab, in CI

The device under test cannot tell the difference from the real counterpart.

Typical duration
4–10 weeks
Starting point
Overview of devices and interfaces
Deliverable
Running test environment with documentation
Operation
Local, in the lab or in the cloud

Test Environments & Simulation

What is included

  • Device emulators, for example for meters, inverters, charge points and battery cells, over CAN, Modbus, SunSpec, OCPP and EEBUS
  • Virtual charge points and meters as a cloud environment for integration tests
  • Hardware-in-the-loop rigs with fault injection
  • Simulation of control, grid and fault signals, for example power limitation under § 14a EnWG
  • Development and test environments as infrastructure as code, rebuildable at any time
  • Verification against real devices, so the emulation keeps its promise

Situations we keep running into

Tests only run on the real installation

Challenge

Every test needs access to devices in the field or in the lab. Appointments, weather and availability set the pace of development.

How we help

We emulate the counterpart so that your device takes it for the original. Tests then run at any time, in parallel and without travel.

Every vendor behaves differently

Challenge

Devices from different vendors speak the same protocol but not the same dialect. The differences only show up at the customer.

How we help

We model vendor variants as switchable profiles and verify them against real devices. You test the variety before it ships.

The test environment exists on one machine only

Challenge

The setup has grown over years. Nobody can rebuild it, and new colleagues need weeks before they can work.

How we help

We describe the environment as code. One command rebuilds it, locally or in the cloud.

Next step

Let’s talk about your project.

A short conversation usually settles faster than a specification whether and how we can help.