Access Official Technical PDF

Share Summary:LinkedInEmail

Energy harvesting can help address a central challenge in industrial IoT: how to power connected devices where conventional wired supplies or frequent battery replacement are impractical. Harvesting energy from the surrounding environment is only one part of the solution. Engineers must also consider power conversion and management, energy storage, the device’s load, software behavior and system integration.

These factors are closely linked. A sensor may collect energy intermittently, while its electronics need power to measure, process or communicate. Designing for that mismatch calls for a system-level approach—one that brings together expertise in hardware, software and the application itself.

Energy harvesting is a system design challenge

An energy-harvesting application typically brings together several functional elements: a transducer that captures energy, power-management electronics that condition it, storage that makes energy available when needed, and a low-power load that performs the intended task. The complete system must be designed around how these elements interact.

For industrial automation teams, this means assessing more than the energy source in isolation. The relevant questions include how the harvested energy is managed, what the connected device needs to do, and how the system behaves when available power changes. A design that accounts for each component but overlooks their interactions may fail to meet the requirements of the application.

Energy harvesting also sits within a broader micro-power management landscape. Even when a device uses a battery rather than an ambient energy source, low-power design techniques can be relevant to extending operating life and reducing maintenance needs. The appropriate architecture depends on the application and its power requirements.

Why industrial IoT needs cross-disciplinary design

Connected sensors and wireless sensor networks are among the application areas associated with energy harvesting. But a functioning device requires more than an energy source and a sensor. It must also execute its software and carry out its intended operation despite changes in power availability.

That requirement connects traditionally separate areas of engineering. Transducer design, storage, power management and low-power electronics need to be considered alongside software and system integration. Testing and measurement, user interaction and industrial design may also affect how a device is developed and used.

One software consideration is how a device handles interruptions in its power supply. At the EnerHarv 2018 workshop, Carnegie Mellon University’s Brandon Lucia discussed software designed for an “intermittent execution model”: code that can handle unexpected power interruptions and resume from where it was operating. This illustrates why power behavior cannot always be treated as a hardware-only concern. The software’s assumptions about continuous operation can matter when the supply is intermittent.

Design for real-world variation

Engineers also need to account for variation in components and operating conditions. At the same workshop, University of Southampton and ARM-ECS researcher Alex Weddell discussed part-to-part variation in photovoltaic cells, including differences within a common lot. Such variation can affect the calculations used to design an integrated device.

The practical point is broader than one component type: system assumptions need to be checked against the behavior of the parts used in the design. Designers should consider how energy capture, conversion, storage and consumption work together rather than relying on an idealized view of a single element.

For industrial applications, system-level evaluation can help teams identify where design assumptions need closer attention. It also makes collaboration between hardware, software and application specialists more important, particularly when a device’s operating conditions are not constant.

Collaboration helps build an energy harvesting ecosystem

The international EnerHarv 2018 workshop, held at Tyndall National Institute in Cork, Ireland, brought together contributors from academia and industry. Its program covered transducers, low-power loads, storage, power management and system integration, with presentations, demonstrations, posters and panel discussions.

The workshop’s emphasis on collaboration reflected a challenge facing emerging technologies: expertise can be distributed across organizations and disciplines. Contributors may focus on a specific component or technical problem without having a complete view of the system. Bringing those perspectives together can reveal dependencies and opportunities for cooperation.

That approach is relevant to industrial automation teams evaluating energy-harvesting devices. Component suppliers, system integrators, software developers and end users may each hold part of the information needed to define a workable design. Early discussion of application needs and operating conditions can help align those contributions.

Practical considerations for engineering teams

When evaluating an energy-harvesting concept, teams can begin by treating it as a complete system rather than a standalone power source. Useful areas to review include:

  • Application requirements: Define what the device must sense, process or communicate.
  • Power path: Consider how energy is captured, managed and stored for use by the load.
  • Operating behavior: Examine how the device responds when available power changes or is interrupted.
  • Component variation: Check whether differences among components affect system assumptions.
  • Integration: Bring hardware, software and application expertise into the design process.

These considerations do not guarantee that harvesting will suit every application. They provide a framework for assessing the design as a whole and for identifying where further evaluation is needed.

Conclusion

Energy harvesting has potential to support connected devices in industrial and other IoT applications, but its success depends on more than collecting energy. Power management, storage, low-power loads, software behavior, component variation and system integration all influence the result. For engineers and technical decision-makers, the key implication is to evaluate the complete application and involve the relevant disciplines early. That system-level perspective is essential to determining whether an energy-harvesting design can meet its intended needs.

Access Official Technical PDF

About The Author