Shared files, issues and examples for 2026 Controls. To be included as a submodule, in the lib folder, in the nacelle and Load controllers.
.github- GitHub config.vscode- VSCode config2026Core- Library rootNet- Old Network stuff, partially maintained by @BobSaidHi. Turned out this much abstraction to make networking implementations interchangeable was more trouble than it was worthNet-Application- Network layer network stuffNet-Link- Link layer network stuffNet-Phy- Physical layer network stuffNetAdapter_A- Abstract class describing necessary components & interface to send data
TurbinePacket- Network data format specification and usage examplePID- PID stuffCommonConfig.hpp- Shared configuration. Turns out a lot of config is controller specific.Tags.hpp- Shared TAGS for ESP logging (incomplete)
docs- documentationconfig- Doxygen configcpp- Notes on C++doxygen-out- Autogenerated Doxygen API dosFSM- Shared FSM diagramming and planning- Miscellaneous Windows Scripts/ batch files (
.bat)
Hardware-Devboard- Development board selectionHardware-Pinouts- Development board pinouts
- [This repo] Common Files (Include in Nacelle & Load as git sub-module):
CalPolyWindPower/2026-Controls_Core(Included as a sub-module in both the nacelle & load side controller) - Nacelle: 2026-
CalPolyWindPower/Controls_Nacelle - Load: 2026-
CalPolyWindPower/Controls_Load - Controller & Code Performance Experiments
CalPolyWindPower/ArduinoBenchmark