advertisement

In the rapidly evolving world of compact robotics, each component choice carries significant weight. For development teams, product managers, and technology directors, these decisions directly influence project schedules, system reliability, and ultimately developer performance metrics. A recent discussion in the GitHub community perfectly illustrates this challenge: an aerospace engineering student, squishybenben2, sought advice on how to select the ideal motor controller for a Cubli 1U, a miniature cubic satellite designed to be balanced by reaction wheels. It's not just about choosing a piece; It's about understanding the intricate interplay between hardware limitations, application demands, and the broader implications for development efficiency and delivery success. Let's delve into the expert insights that have emerged that offer valuable lessons for anyone building high-performance embedded systems. The 1U Cubli challenge: precision in a tiny space The project presented a formidable challenge: designing a Cubli 1U (a simple 100mm × 100mm × 100mm cube) capable of balancing 1 and 3 axes. The main components included three Sunnysky 4008 380KV BLDC motors, a 4S LiPo battery, an ESP32 microcontroller, an AS5600 encoder for LQR state feedback, and an MPU6050 IMU. The control strategy involved an LQR controller running on the ESP32, sending torque set points via UART to the motor controllers. The critical limitations for motor controller selection were clear: Extreme size limitation: Three controllers had to fit inside the 1U cube along with the battery and other electronics. Reliable Control: A robust current/torque control mode was non-negotiable for precise reaction wheel operation. Power Compatibility: Should be seamlessly integrated with a 4S LiPo battery (~16.8V). Initial contenders included the B-G431B-ESC1 (with reported overheating concerns) and the SimpleFOC Mini (raising questions about current headroom), along with the Flipsky FSESC 6.7 Mini. Internal layout diagram of a 1U Cubli showing very compact motor, battery and ESP32 controllers, emphasizing space limitations. Engine Requirements: Beyond the Spec Sheet Before testing drivers, the community first analyzed the specific demands of a reaction wheel system. Unlike continuous drive applications, reaction wheels require: High acceleration and fast torque response: essential for dynamic balance. Short, intense current bursts: Expected during rapid changes in torque, potentially peaking at 20-25 A. No continuous operation at full speed: This crucial distinction significantly affects thermal considerations. Therefore, any suitable controller needed to support 4S LiPo, handle ≥20A safely, provide true FOC (field oriented control) for precise torque control, be compact enough for the 1U cube, and offer stable UART communication from the ESP32. Crucially, it also needed to manage its thermal load within the enclosed space. Driver Rating: A Deep Dive into Options Community expert satasiyakrish1 meticulously evaluated the proposed drivers: 1.B-G431B-ESC1 Advantages: True FOC, good current control, very compact. Cons: Overheating issues reported, limited thermal mass, not ideal for closed spaces without careful management. Initial Verdict: Risky for a 3-axis Cubli due to thermal issues. 2. SimpleFOC Mini Advantages: Extremely compact and easy to integrate for light loads. Cons: Limited current margin, reduced thermal margin, less mature ecosystem. Initial verdict: Not recommended for the bursts of torque inherent in reaction wheels. 3. Flipsky FSESC 6.7 Mini (based on VESC) Pros: Mature VESC firmware, excellent current/torque control, handles 4S easily, high current margin (significant margin), integrated UART, thermal monitoring, great community support. Cons: Slightly larger than B-G431B, higher cost. Initial Verdic

advertisement

advertisement