Interoperability standards proposed for EnOcean energy-harvesting nodes

November 15, 2013 // By Graham Prophet
Generic Profiles define a new communication convention for the data exchange in energy harvesting wireless networks, allowing a broader range of EnOcean-based solutions from a mix of vendors, in any installation

The EnOcean Alliance has specified a generic language for communication between energy harvesting wireless solutions: Generic Profiles. These enable product manufacturers (OEMs) to develop new interoperable EnOcean-based solutions more easily and quickly; for example a greater variety of multi-purpose wireless sensors. Generic Profiles define the grammatical rules for all options of data encoding for ultra-low power and energy harvesting radio communication. Using this generic language, the same product can be mapped dynamically to different applications. As a result, Generic Profiles offer a standardised path for future applications. A summary of Generic Profiles can be found at Members of the EnOcean Alliance can download the complete version in the member portal.

The increasing number of energy harvesting wireless product providers in the EnOcean Alliance results in a greater variety of applications employing battery-less wireless communication. These are covered by the EnOcean Equipment Profiles (EEP), which define the structure of the communication content for particular applications. Generic Profiles extend this spectrum by defining a generalised language. This is particularly suitable for new product designs, which are intended to describe the energy harvesting wireless data encoding, independently of the application.

“In the future, new product developments can use the generic system specification for seamless interoperable communication. This applies above all to dynamic solutions, such as temperature sensors which can be used in warm or cold environments. Here, the sensors need the flexibility to cover different ranges of temperature. OEMs can now insert the generic language definition, instead of several profiles for the various use cases,” says Marian Hönsch, Product Marketing – Software Architect, EnOcean GmbH, and Generic Profiles Team Leader, EnOcean Alliance. “Depending on the use case, OEMs have the freedom of choice to integrate specific EEPs, Generic Profiles or both.”

Networks can combine EEP-based devices with products using Generic Profiles. In this case, only the receiving side, for example, a controller solution, needs to cover both wireless interfaces. Wired systems