How alexgyver/gyverlibs works
This repository isn’t a single “app” with one runtime process – it’s an archive of many modular Arduino libraries written from scratch (or modified) for hardware control, algorithmic processing, and system-level functions. In other words, the “system” is a collection of independently useful libraries that an Arduino developer can mix and match for various embedded projects.
Main Components
a. “Hardware / Device Control Libraries” (Железки):
– This category includes libraries for controlling physical devices and actuators. For example: GyverButton (button control), GyverEncoder (encoder processing), GyverMotor, GyverStepper, AccelMotor, GyverRGB, GyverTM1637, ServoSmooth, etc.
b. “Peripheral / MCU Control Libraries” (Периферия МК):
– Libraries that extend the raw capabilities of the microcontroller such as directADC, directTimers, GyverPWM, GyverWDT.
c. “Algorithmic & Control Libraries” (Алгоритмы):
– These include logic that “regulates” or “processes” sensor data, such as PWMrelay, GyverFilters, GyverTimer, GyverPID, and GyverRelay.
d. “Core/System & Utility Libraries” (Системное):
– Libraries that provide infrastructure features: buildTime, GyverTimers, GyverHacks, GyverPower, GyverRTOS.
e. “Lightweight/Micro Libraries” (Лёгкие библиотеки):
– Minimal libraries for sensors and communication such as microBME280, microLED, microWire, microDS3231, microLiquidCrystal_I2C, microDS18B20, GyverUART, minimLibs.
Dependencies and Interactions
• In many cases, the libraries are “standalone” but follow a similar API design for embedded use (for example, they often provide “tick()” methods or built‐in timers). Indicate these common design patterns using annotations (for instance, note that many of the “Hardware Control” libraries expose a periodic “tick” function that must be called within an Arduino loop or ISR, reflecting a cooperative “task scheduling” pattern).
• Libraries into “subsystems” based on their functional purpose. For instance, all display-related libraries (GyverOLED, SevenSegmentsDisp, TM1637_Gyver, TM74HC595_Gyver) can be clustered together.
Instructing the Principal Software Engineer
• Begin at the highest level with the overall repository and then “drill down” into categories.
– Rectangles for “Hardware Device Libraries”
– Rounded rectangles for “MCU Peripheral Libraries”
– Ovals or circles for “Algorithm & Control Utilities”
– A separate grouping for “System/RTOS and Utility Functions”
• Directional indicators for data flows when one library’s output is intended for another’s input (for example, sensor data processed in GyverFilters might feed into GyverPID or GyverRelay).
Capturing Essential Architectural Elements
• Be very detailed in grouping: separate the design into as many suitably named components as possible without oversimplifying.
• Acknowledge that many libraries share similar “tick” or “update” methods, suggesting that a runtime scheduler (or cooperative multitasking – as implied by GyverRTOS) could be conceptualized at the center of the system.
– The modular nature of the repository
– The clear separation of concerns by category
– The relationships (and dependencies) between common libraries
– The low-level, hardware-focused design typical in Arduino ecosystems