How tranphuongnam2912/trajectory-tracking-of-two-wheeled-mobile-robot works
Main Components
• Simulation & Modeling Environment:
– MATLAB/Simulink components (folders for ASMC, Fuzzy, Neural Network, PID, SMC) where control algorithms are modeled and simulated.
• Embedded Controller:
– ESP32-based microcontroller firmware (the Embedded_code folder with .ino files that implement the various control strategies and sensor/actuator interactions, including code for controllers and trajectory tracking).
• Communication Interface:
– Python GUI (GUI_CAR.py) acting as the remote interface that connects via WiFi to the ESP32.
– WiFi module on ESP32 to both receive commands and send data (SSID, password configuration instructions in the README).
• Mechanical & Hardware Design:
– Solidworks design files (both 2D and 3D, assembly, parts) that represent the physical structure of the robot.
• Documentation & Validation:
– Documentation under the docs directory providing further details (e.g., control system theory, performance analysis).
Relationships and Data Flow
• MATLAB/Simulink “Control Algorithm Development” as a starting block, which feeds into both simulation results and serves as a testing ground before hardware integration.
• From simulation, indicate a “Control Strategy Selection” component that branches into the different controllers (PID, SMC, Fuzzy, Neural Network).
• The physical robot hardware (actuators, sensors interfaced with the microcontroller).
• The WiFi network used for remote connectivity.
• Python GUI as an external client that communicates with the ESP32 over WiFi, providing real-time kontrol, monitoring, and feedback.
• Physical design component (Solidworks) to complete the loop, showing that the mechanical design is integrated with the electronic control and simulation models.
Architectural Patterns & Technologies
• Separation of Concerns:
– Simulation/modeling is clearly separated from embedded implementation and the physical system.
• Modular Control Strategies:
– Each control algorithm (PID, SMC, Fuzzy, Neural Network) is developed both in simulation (MATLAB subdirectories) and implemented in embedded C code (.ino files for Arduino/ESP32).
• Integration and Communication:
– The integration layer involves translating simulated results into real-world code, while the Python GUI manages remote connectivity through WiFi.
• Key Technologies:
– MATLAB/Simulink for modeling and simulation.
– Arduino IDE (with C for the ESP32) for the embedded controller.
– Python (for GUI and network-based remote control).
– Solidworks for hardware/mechanical designs.
Elements
• Labeled Components:
– Each block (e.g., MATLAB/Simulink, PID Controller, SMC Controller, Fuzzy Controller, Neural Network Controller, ESP32 Embedded Unit, Python GUI, Physical Robot Hardware, Solidworks Designs, WiFi interface) should be clearly labeled.
• From simulation to embedded controller (code transfer and validation).
• From the ESP32 to sensors/actuators and to the WiFi interface.
• Between the Python GUI and the ESP32 (bidirectional communication for control commands and telemetry).
• Blue for simulation/modeling tools.
• Red for embedded/hardware control.
• Yellow/orange for middleware (communication interface such as WiFi and Python GUI).
Additional Detail
• Role of each control algorithm and highlight that the chosen approach in simulation is ultimately validated in practice.
• Optionally, include a “Testing & Validation” stage where simulation results and experimental data (perhaps documented in “docs”) are compared.
• Remember to denote configuration dependencies (such as the requirement to adjust WiFi SSID/password and IP address in the ESP32 code and Python script).