A nice coincidence. Recently, I wrote a bit about choosing a microcontroller and some issues that crop up when people not used to microcontroller design are tasked with automating systems.
My supposition is that, traditionally, most folks in the industry concentrate on designing and choosing microcontrollers and tool sets from the perspective of an expert in embedded design. However, the new world has a lot of people tasked with microcontroller hardware and software design that are not electronics or software engineers. Mechanical engineers are tasked with integrating electronic controls into their systems. Pure digital engineers are being tasked with adding analog sections into their designs. Hardware engineers are having to learn microcontroller firmware programming. That changes the ground rules.
Last week, I signed into a virtual conference on motor control (I started writing this post as I was listening to the virtual conference, but didn’t get around to finishing it until today). I signed in late to start listening to the keynote address by John Hanks of National Instruments, who, at that moment, discussing this very subject. As he described it, domain experts in such fields as solar, wind and other areas are being asked to add additional automation into those systems. As domain experts, they may know more about their field than an EE or SE, but they likely have not been trained in the application of hardware, firmware and software development.
Interestingly, this group has a lot in common with the electronics hobbyist community. In both cases, the concepts and the tools are frequently quite new to them. In both cases, the budget for training and tools is frequently pretty minimal. In both cases, we have smart people who many not be trained in our field.
Those of us that create tools and offer services in this industry need to keep this trend in mind if we want to fully serve the new engineering audience.
See us at ESC, booth 827