Define motor load and current events, compare actual driver and supply limits, then validate controlled operation and retain the hardware settings.
Record motor type, supply range, required shaft speed, load torque and the relevant acceleration or holding cases. Resolve force and lever angle before selecting a transmission. Keep mechanical shaft power separate from electrical winding and battery power.
Use the exact motor data or controlled measurements at the intended voltage, drive mode, speed and load. Record continuous winding current, startup/stall event current, duration and repetition. Determine whether ratings and measurements refer to phase, winding, RMS, peak or battery-input current.
Match motor topology, channel count and current basis to the driver. Compare operating input range and documented continuous and event limits under the actual cooling conditions. Review input logic, enable state, current regulation, fault response and manufacturer-required flyback or recirculation paths.
Build the rail budget including logic, sensors and simultaneous drive events. Check the DC source’s individual rails and combined power, then the complete wire/connector current path. Review regenerative energy handling and whether the source can absorb it.
Secure the mechanism, establish a safe stop and begin with the manufacturer’s commissioning sequence and suitable current limiting. Verify direction, enable/disable behavior and fault response before increasing load. Measure current, bus voltage and temperature over the intended duty cycle.
Save the motor/driver pairing, wiring, control configuration, current limits and measured duty cases with hardware and firmware revisions. For battery operation, budget a complete mission from battery-side state power. Repeat validation after load, gearing or control changes.
Calculate load torque and geared shaft requirements on the actual force geometry.
Record actual current requirements and leave the application basis unresolved until verified. · Compare the documented driver envelope and explicit compatibility state. · Replace assumed current events with the measured operating cases. · Export the accepted envelope and unresolved operating conditions.
Sum subsystem continuous and simultaneous peak battery-side power. · Update measured rail power and peak overlap.
Check actual source rails and pulse allowances.
Compare documented wire and connector candidates.
Compare usable pack energy with complete measured mission states.
Loading your checklist…
Current limits depend on the rating definition, duration and thermal conditions.
Keep regulated-rail and source-side energy measurements distinct.
A matching number in amperes is insufficient when one value is phase current and the other is battery current.
Document the chosen response to loss of command, power or sensor feedback.