Quick Takeaways
- Dunkermotoren has highlighted QuickStart Control for CANopen-based motion control implementation in modular machine designs.
- The update focuses on shifting repeated motion functions from a central controller toward the drive system.
- The reported approach uses CANopen with CiA 301 and CiA 402 device profiles.
- Buyers should check how the selected motor, gearbox, encoder, brake, and drive family fit the same control environment.
Industry Update
Automation International reported on October 1 that Dunkermotoren has integrated QuickStart Control functionality with CANopen communication for machine builders and original equipment manufacturers working on motion control projects.
The reported approach is aimed at reducing repeated programming work by allowing commonly used motion functions to run within the drive hardware. Instead of writing a separate control sequence for every motion task in the main controller, engineers can work from predefined drive-level functions where the application supports that architecture.
The source also notes that the system operates on CANopen architecture and uses the CiA 301 and CiA 402 device profiles. For modular equipment, Dunkermotoren connects the approach to its dCore, dMove, dPro, and dGo drive families, with combinations that may include motors, gearboxes, encoders, and brakes.
Buyer Considerations
For motor and drive buyers, the practical question is not only whether a motor fits the torque, speed, voltage, and mounting requirements. The control architecture now matters earlier in sourcing because a drive-level function set can affect commissioning time, software reuse, and the way a machine family is scaled.
Engineering teams comparing BLDC motors, gear motors, encoders, brakes, and drive electronics should ask suppliers which CANopen profiles are supported, how predefined motion functions are configured, and whether the same method can be reused across multiple axes or machine variants.
OEMs should also confirm the service and maintenance implications. A drive-based motion approach can simplify repeated functions, but buyers still need clear documentation for diagnostics, parameter backup, firmware handling, and replacement parts across the installed machine base.
Motor series to compare for this kind of project.
Frequently Asked Questions
What changed in this Dunkermotoren update?
The update highlights QuickStart Control with CANopen communication, allowing certain repeated motion functions to be handled at the drive level for suitable machine designs.
Why should motor buyers care about drive-level motion functions?
Drive-level functions can influence commissioning, software reuse, and how easily a machine builder can standardize motor, gearbox, encoder, brake, and drive combinations across related equipment.
Does this replace the need to check motor sizing?
No. Buyers still need to verify torque, speed, duty cycle, voltage, mounting, environmental conditions, feedback device requirements, and brake requirements before selecting a motor system.
Which applications could be most relevant?
Modular automation equipment, packaging machinery, handling systems, compact machine axes, and OEM platforms with repeated motion sequences may be the most relevant candidates to evaluate.
Source
This article summarizes publicly available source information. Confirm technical details, pricing and compliance requirements with the original source before making purchasing decisions.
Source date: 2026-10-03