Here is a figure I did use in a recent presentation explaining why power electronics software is so hard to develop:
Hence, in order to create quality embedded software for power electronics applications, one must have advanced knowledge on :
- the load (motor type, dynamics, etc),
- the electrical source (topology of the power converter, devices technologies, etc.),
- the electronics, i.e. the device on which the software is going to run and also transducers that are going to interface with the device and the system,
- and embedded software development, of course.
- the ‘power engineer’ doesn’t know about software development and often minimize its importance (this most of the time leads to bad software development practices which makes the situation worse),
- the ‘software engineer’ doesn’t know about power applications since this is way out of his traditionnal type of applications (web, internet, applicative) and neglect to consider that he is working with energy (i.e. error is not leading to a blue screen but to a damaged system or to personel injury).