This conveyor-sorting manipulator combines 48 V hub motors, incremental encoder feedback, ODrive control, spline-based trajectory generation, and vision-based object tracking. The central engineering lesson is that point-to-point commands produced abrupt acceleration, stopping, and direction changes; routing motion through a spline-defined path reduced those shock-producing transitions.
Document the Drive and Feedback Constraints
| Component | Reported specification | Engineering decision |
|---|---|---|
| Magic Pie 2 motor | 48 V, 56 magnets, up to 70 N·m | Use verified motor and drive data when calculating joint torque, speed, and thermal limits. |
| Motor power | Reported as “1500 kw” | Do not use this ambiguous value for sizing. Confirm the intended unit and rating from the motor documentation or nameplate. |
| Power supply | MeanWell RSP-3000-48 | Verify that its output and protection requirements match the combined axes and expected motion profile. |
| Encoder | OMRON E6B2CWZ6C, 2500pr, with Z-index | Confirm how the controller interprets the reported encoder resolution before calculating joint position scaling. |
| Motor current | Drive and motors reported capable of 40 A; demonstrated operation used 10 A during the first video segment | Treat 10 A as the demonstrated setting, not proof of the arm’s full load capability. |
The project used incremental encoders because absolute encoders were reported as unsupported by ODrive at that stage. This is a historical project constraint, not evidence of current ODrive behavior. Any redesign should verify present controller compatibility before selecting absolute feedback.
Replace Point-to-Point Commands with a Spline Path
Direct point-to-point movement caused sudden stops, acceleration changes, and reversals that imposed shock loads on the structure. The implemented correction was to construct a three-dimensional spline through reference points and command motion along that continuous trajectory.
- Define the reference points through which the manipulator must pass.
- Construct a spline through those points in three-dimensional space.
- Generate successive motion commands from positions on the spline instead of issuing isolated point-to-point moves.
- Run the trajectory at the demonstrated 10 A setting and observe stops, reversals, and structural response before increasing current or speed.
Coordinate Vision, Conveyor Tracking, and Motion
The application used YOLO and MASK R-CNNN for image recognition, together with software that tracked objects and generated the robotic-arm trajectory. Conveyor tests were performed at different speeds, so the motion planner must consume an updated object position rather than treating the detected location as stationary.
Verify the complete chain by confirming that an object is detected, tracked as the conveyor advances, assigned a reachable trajectory, and intercepted without abrupt motion. The evidence does not provide camera timing, conveyor velocity, controller update rate, or latency measurements, so those values must be measured before calculating interception error or maximum conveyor speed.
Plan Mechanical and Feedback Improvements
Planned changes included replacing the gripper with pneumatic suction cups, optimizing trajectory handling, reducing motor and structural mass to improve payload and speed, and moving to absolute encoders. ODrive was also used to record motion while the arm was moved by hand and then replay that motion.
Validate each modification independently. Confirm suction retention for the actual waste stream, recheck joint torque after mass changes, verify absolute-encoder compatibility before purchase, and test recorded-motion playback within the arm’s mechanical limits.
FAQ
How do I reduce shock loads on a conveyor robotic arm?
Replace isolated point-to-point commands with a spline constructed through the required three-dimensional reference points, then verify stops and direction changes at the demonstrated 10 A setting before raising current or speed.
Which encoder was used with the ODrive robotic arm?
The project used an OMRON E6B2CWZ6C incremental encoder reported as 2500pr with a Z-index. Confirm the controller’s resolution interpretation before calculating position scaling.
Can I size the robotic arm from the reported 1500 kw motor value?
No. The reported value or unit is ambiguous, so verify the Magic Pie 2 nameplate or manufacturer documentation before performing power, supply, cable, or protection calculations.
