Implementation of fault tolerant control for modular multilevel converter using EtherCAT communication

Paul Dan Burlacu, Laszlo Mathe, Marcos Rejas, Heverton Pereira, Ariya Sangwongwanich, Remus Teodorescu

Research output: Contribution to book/anthology/report/conference proceedingArticle in proceedingResearchpeer-review

34 Citations (Scopus)

Abstract

Modular Multilevel Converter (MMC) is very promising technology this days. It offers fault tolerant capabilities and ensures high efficiency with low output voltage harmonic content which results in need for smaller filter size. A disadvantage of the system is that the control becomes more cumbersome due to the high number of the employed submodules. A very efficient way to control the MMC is by using a real time communication platform between the sub-modules and a central unit. Thus, the central unit can deal with the overall control and some of the tasks can be distributed to the submodules. This communication platform has to ensure a perfect synchronization between the modules, and it should be also fault tolerant. The analysis of a MMC based on EtherCAT is presented in this paper from implementation and module fault point of view. The experimental tests show that the MMC operates after communication or module hardware fault occurred.
Original languageEnglish
Title of host publicationProceedings of the 2015 IEEE International Conference on Industrial Technology (ICIT)
Number of pages8
PublisherIEEE Press
Publication date16 Jun 2015
Pages3064-3071
Article number7125551
DOIs
Publication statusPublished - 16 Jun 2015
Event2015 IEEE International Conference on Industrial Technology (ICIT) - Seville, Spain
Duration: 17 Mar 201519 Mar 2015

Conference

Conference2015 IEEE International Conference on Industrial Technology (ICIT)
Country/TerritorySpain
CitySeville
Period17/03/201519/03/2015

Fingerprint

Dive into the research topics of 'Implementation of fault tolerant control for modular multilevel converter using EtherCAT communication'. Together they form a unique fingerprint.

Cite this