How canyon-robotics-the-misfits/lib15442c works
Main Component Layers (Top to Bottom)
a. Application Layer (Top)
• How external VEX robot applications would interface with the library
• Entry points through the main API headers
b. Core Library Components (Middle)
• Into distinct functional modules:
• Chassis Control Module
• Motion Control Module
• Device Management Module
• Math Utilities Module
• Trajectory Planning Module
• Sensor Integration Module
c. Hardware Abstraction Layer (Bottom)
• PROS Framework Integration
• VEX Hardware Interface
Component Details and Relationships
a. Chassis Control Module (lib15442c/chasis)
• Drive Controller
• Tank Drive Implementation
• Odometry Systems (Multiple implementations)
• Monte Carlo Localization
• To Motion Control Module
b. Motion Control Module (lib15442c/motion)
• PID Controllers
• RAMSETE Controller
• Drive-to Behaviors
• Motion Primitives
• To Trajectory Module
c. Device Management Module (lib15442c/device)
• Motor Abstractions
• Pneumatic Control
• Sensor Management
• To Hardware Layer
d. Math Utilities Module (lib15442c/math)
• Angle Management
• Vector Operations
• Pose Calculations
• Used by all other modules
e. Trajectory Module (lib15442c/trajectory)
• Trajectory Generation
• Path Planning
• Cubic Hermite Splines
• To Motion Control
Important Details
a. Three main odometry implementations:
• Tracking wheels
• GPS sensor
• Monte Carlo localization
b. Motion control hierarchy:
• High-level trajectory planning
• Mid-level motion algorithms
• Low-level motor control
c. Math utilities as a shared resource