How fipatech/cdfr2025 works
Project type and purpose
• This is a robotics control system (“CDFR2025”) consisting of:
• Embedded firmware running on an STM32F4 microcontroller (firmware/…)
• A ROS 2-based software stack on a companion computer (software/ros2_ws/…)
• A Node.js server component (software/server/…)
• Purpose: low-level real-time control, sensor processing, UI on the device; high-level strategy & perception on ROS 2; web/API access via Node.js.
File structure
• firmware/robot_firmware
• Core C code under Core/Inc & Core/Src
• FreeRTOS tasks
• STM32 HAL and BSP drivers under Drivers/…
• TouchGFX UI middleware under Middlewares/ST/touchgfx
• Build project files for EWARM, MDK, CubeIDE, GCC
• software/ros2_ws
• bringup: launch ROS graph
• imu_fusion: sensor‐fusion node (likely IMU + odometry)
• match_control: high-level strategy loader (YAML-driven)
• rplidar_ros2: LiDAR driver
• uart_bridge: serial↔ROS bridge
• software/server
• index.js: Node.js backend (REST/WebSocket API)
README
• No further architecture description there, so inference from code.
Main components & interactions
a. Embedded MCU
• Hardware: IMU, encoders (odometry), servos, UART, LCD+touch
• Firmware stacks:
– STM32 HAL + BSP → low-level drivers
– FreeRTOS → task scheduling
– Core modules: odometry, command_manager, strategy_manager, servo_controller, uart_handler
– TouchGFX MVC UI layer
b. Companion Computer (ROS 2)
• Nodes:
– uart_bridge: publishes sensor topics, subscribes command topics
– imu_fusion: fuses IMU + odometry → filtered pose
– rplidar_ros2: publishes LiDAR scans
– match_control: loads strategy YAML, reacts to sensor topics → publishes setpoints
• Launch: bringup.launch.py to start the graph
c. Node.js Server
• Exposes APIs or websockets for monitoring & control
• Connects either directly to ROS 2 (via rosbridge) or uses custom messaging
Architectural patterns & principles
• Embedded: layered architecture (HAL → middleware → application logic → UI)
• Real-time OS with tasks communicating via queues/circular buffers
• TouchGFX: Model-View-Presenter pattern
• ROS 2: distributed micro-services (nodes) communicating via topics/services
• Node.js: event-driven, non-blocking server