Feature: Embedded design
Te PCB schematic stage also requires
research, selection and testing of components. Integrating the control chip and amplifier, the latter would also require a dedicated circuit, which could add yet another 12 months or so. Te final aspect of the soſtware
development process is application and motion parameter development, requiring a timespan of up to 16 months. All in all, with a potential development
taking up to 58 months, divided into a three-person team the project can take up to 18 months or more.
Buying in a motion controller Most of these steps can be removed by using a ready-to-go PCB-based motion controller. Development time can shrink to about a year, without sacrificing motion control features. As well as functionality such as profile and servo position control, integrating user-downloadable code written with C language libraries also extends their control flexibility. Another advantage of an off-the-shelf
motion controller is that it can be more cost-effective if lower volume is required. Quicker development also means faster time to market. Demands of end users and
the competitive landscape might make this the preferable approach, even for higher volume projects.
OEMs can also choose a hybrid approach that features PCB- mounted motion control modules. These single-axis modules can handle up to 1kW and
execute user-written application software, extending control flexibility
The hybrid approach OEMs can also choose a hybrid approach that features PCB-mounted motion control modules. Tese single-axis modules can handle up to 1kW and execute user-written application soſtware, extending control flexibility. Just like an off-the-shelf controller, these modules include advanced motion functions such as profiling, field-orientated control, safety and are easy and fast to integrate. Mounted on a user-designed, application- specific interconnect board, these modules require much simplified wiring, needing just connectors and capacitors. Like the buy-in option, the engineering
resources required are significantly lower with the hybrid approach. Following simplified hardware integration, engineers can move directly to application development. Te approach still allows OEMs to create a controller to fit their own form factor. Given the right volume, procurement
cost of the hybrid approach can also return a lower rate than the buy-in option.
www.electronicsworld.co.uk May 2023 23
Page 1 |
Page 2 |
Page 3 |
Page 4 |
Page 5 |
Page 6 |
Page 7 |
Page 8 |
Page 9 |
Page 10 |
Page 11 |
Page 12 |
Page 13 |
Page 14 |
Page 15 |
Page 16 |
Page 17 |
Page 18 |
Page 19 |
Page 20 |
Page 21 |
Page 22 |
Page 23 |
Page 24 |
Page 25 |
Page 26 |
Page 27 |
Page 28 |
Page 29 |
Page 30 |
Page 31 |
Page 32 |
Page 33 |
Page 34 |
Page 35 |
Page 36 |
Page 37 |
Page 38 |
Page 39 |
Page 40 |
Page 41 |
Page 42 |
Page 43 |
Page 44
