Home / Documentation

Documentation

Guides to the eebus crate: the EEBUS standard, the SHIP transport, the SPINE model, and the grid use cases behind §14a EnWG — with runnable Rust.

This documentation explains what EEBUS requires and how this crate expresses it.

Where to start

If you have never met EEBUS, read What EEBUS is first: the players, the layers, and why a German grid regulation made this a certifiable protocol.

If you know the standard and want the code, go straight to Getting started and then the use case you need: LPC and LPP for limiting power, MPC and MGCP for measuring it, E-mobility for wallboxes and cars, inverters, PV and batteries for the generation side, and heat pumps for the hot water, the building's temperature and the compressor that heats it.

If you are evaluating the crate, Architecture, Conformance and Certification are the pages that answer "is this real", and Which functions can be exchanged in part answers the one SPINE question that has no short answer — it is the generated table of all 142 functions.

Conventions

Citations name the document and the section: SHIP §12.2.3 is the SHIP Technical Specification, SPINE IG §3.2.1 the SPINE implementation guide, [LPC-002] a numbered requirement from a use-case implementation guide. Every one of them appears in the source too, next to the code that satisfies it.

The API reference — every type, every function — lives on docs.rs.