Certification & Devices
Test conditions for EEBUS Certification
What your device, your network setup and your documentation have to fulfil before it can be tested in the EEBUS Living Lab Cologne. Read this page before you apply for a test slot.
Test specifications & forms
Test specifications, implementation guidelines, parameter lists and declaration forms.
Scope of the tests
Placeholder – describe here what is examined during a test: the EEBUS communication of the device under test, on protocol level (SHIP and SPINE) and on application level (the certified Use Cases). One or two paragraphs are enough at this point.
Placeholder – state which part of the product is actually the device under test, and that the certificate is always issued for a defined test scope rather than for a whole product portfolio.
What is not part of the tests
Placeholder – short, explicit list of what the lab does not check, so expectations are clear before a slot is booked.
Prerequisites at a glance
Three groups of conditions have to be met. Each of them is detailed further down this page.
Device
Physical sample, firmware version, power supply and any accessories needed to operate it.
Network
Addressing, discovery and connectivity behaviour the lab network expects.
Documentation
Parameter lists, declarations and configuration data submitted with the device.
Network requirements
The lab network is manufacturer-independent. Devices are expected to behave exactly as they would in a customer installation.
Test access to the device
So that the lab can run the tests independently, the device has to expose its relevant runtime state and offer a reliable way back to its initial state.
Runtime signals – example set
Placeholder – the final signal names per Use Case go here, ideally grouped by role.
- ✓ Reset function — placeholder for how the device is returned to its initial state between test cases.
- ✓ Access to the interface — placeholder for how the lab reads the signals (developer interface, log output, tooling).
- ✓ Configuration data — placeholder for credentials, pairing information and settings supplied with the device.
Roles and documents
Which specifications, parameter lists and forms apply depends on the Use Cases a device implements and on the role it takes in them.
Not sure which combination applies to your product? Two worked examples – a controllable device and an energy management system – can be added below this table once the content is final.
Key distinction
SHIP establishes and protects the communication channel. SPINE defines the energy-related information exchanged through it.
Before you apply
We recommend this order within the specification:
- 1 Placeholder – validate the implementation against the current test specifications.
- 2 Placeholder – confirm the network and interface requirements above.
- 3 Placeholder – prepare the documents listed for your Use Cases and roles.
- 4 Placeholder – request a slot and agree the delivery window with the lab.
