How peng-zhihui/dummy-robot works
Project Type and Purpose
• This is a full-stack mechatronic system for a super‑compact robotic arm (“Dummy‑Robot”).
• It spans hardware (PCB designs & 3D models), embedded firmware (STM32F4 core controller + STM32F1 motor drivers + teaching pendant), and host‑side software (PC GUI, CLI tool, mobile app).
File‐Structure Highlights
• 0.SubModules/Peak ⇒ Teaching pendant (hardware & firmware submodule)
• 1.Hardware ⇒ PCB projects: REF core board, REF base board, stepper‐driver boards (20/42/57), LED ring, wireless locators, gripper modules
• 2.Firmware ⇒
• Core‑STM32F4‑fw (FreeRTOS, HAL/CMSIS, BSP, robot algorithms, user apps)
• Ctrl‑Step‑Driver‑STM32F1‑fw (closed‑loop stepper drivers, CAN/UART protocol)
• submodule Peak firmware
• 4.Model ⇒ 3D CAD parts for arm, enclosure, suitcase
• 5.Docs ⇒ images & documentation
• README.md ⇒ system overview, architecture, communication protocols, command modes, technology stack
Main Components
a. Host Layer
• PC App (DummyStudio in Unity3D)
• CLI tool (reftool based on fibre)
• (Future) Mobile App
b. Teaching Pendant (“Peak”)
c. Embedded Core Controller
• STM32F405 MCU running Core‑STM32F4‑fw
• Subsystems: BSP (OLED via software‑I2C, IMU, EEPROM), RabbitMQ(?) – actually fibre RPC, FreeRTOS scheduler, Robot‑kinematics library, UserApp interface
• Interfaces: USB/UART for PC/CLI, wireless/UART for pendant, CAN bus for drivers
d. Motor Drivers
• Multiple STM32F1‑based boards (20/42 stepper drivers)
• ADC & chopped‑MOSFET or discrete FETs, encoder feedback, CAN/UART firmware
e. Mechanical & Power
• Stepper motors with encoders
• CAN bus + 24 V power trunk (4‑wire: V+, GND, CAN‑H, CAN‑L)
• 3D‑printed links and suitcases
Relationships & Data Flows
• PC GUI / CLI → (USB/UART) → Core Controller → (CAN bus) → Motor Drivers → Motors
• Pendant → (wireless/UART) → Core Controller
• Core Controller → (software‑I2C) → OLED display / status LEDs
• Motors & encoders ↔ Motor Drivers ↔ Core Controller (feedback for kinematics)
Architectural Patterns & Technologies
• Layered Firmware:
• Drivers (STM32 HAL, CMSIS)
• BSP modules (GPIO, UART, CAN, I2C)
• Middleware (FreeRTOS, u8g2 graphics, fibre RPC)
• Robot library (kinematics, trajectory planners)
• UserApp (protocol handlers, command modes)
• Bus Topology: CAN trunk for all motor drivers, star‑like connections for USB/UART interfaces
• Modular Hardware: interchangeable PCBs for different functions
• Protocol abstraction: ASCII, CAN, USB CDC classes