Ripple Correlation Control with Capacitive Compensation for Photovoltaic Applications

Jason Galtieri, Philip T. Krein

Research output: Chapter in Book/Report/Conference proceedingConference contribution

Abstract

A ripple correlation control (RCC) algorithm with capacitive compensation is introduced for photovoltaic applications. In principle, RCC convergence times and steady-state error are reduced with higher switching frequencies, but circuit parasitics have typically limited RCC operation to tens of kHz. With capacitive compensation, phase information is retained at higher frequencies and the practical switching range is extended to 100 kHz. Simulations show that even approximate estimates of parasitic capacitance, with margins of error as high as 20% or so, can greatly extend RCC operating frequency. A 100 kHz boost prototype is constructed and used to verify that phase information is recovered with capacitive compensation.

Original languageEnglish (US)
Title of host publication2018 IEEE 19th Workshop on Control and Modeling for Power Electronics, COMPEL 2018
PublisherInstitute of Electrical and Electronics Engineers Inc.
ISBN (Print)9781538655412
DOIs
StatePublished - Sep 10 2018
Event19th IEEE Workshop on Control and Modeling for Power Electronics, COMPEL 2018 - Padova, Italy
Duration: Jun 25 2018Jun 28 2018

Publication series

Name2018 IEEE 19th Workshop on Control and Modeling for Power Electronics, COMPEL 2018

Other

Other19th IEEE Workshop on Control and Modeling for Power Electronics, COMPEL 2018
Country/TerritoryItaly
CityPadova
Period6/25/186/28/18

Keywords

  • DC-DC converters
  • boost converter
  • nonlinear control
  • photovoltaic energy
  • ripple correlation

ASJC Scopus subject areas

  • Modeling and Simulation
  • Energy Engineering and Power Technology
  • Electrical and Electronic Engineering
  • Control and Optimization

Fingerprint

Dive into the research topics of 'Ripple Correlation Control with Capacitive Compensation for Photovoltaic Applications'. Together they form a unique fingerprint.

Cite this