esp32-development

To add an ESP32 actuator driver, implement the IActuatorDriver interface, register it in the ActuatorManager factory, and run the PlatformIO build command. This workflow ensures your driver integrates safely with runtime protections and the safety controller.

ESP32 development requires explicit GPIO safe-mode and pin reservation rules to prevent hardware conflicts. Following the specified startup order and reservation rules via the GPIOManager ensures safe pin allocation and avoids unsafe initialization mistakes.

Extend MQTT topics for ESP32 telemetry by applying the documented MQTT topic patterns and QoS guidance. You can update the TopicBuilder implementation to publish sensor data correctly through the centralized MQTTClient singleton.

Yes, ESP32 firmware development requires a strict startup initialization order for core singletons like GPIOManager, SensorManager, and ActuatorManager. Adhering to this sequence ensures reliable configuration and prevents emergency handling failures.

The best way to configure ESP32 circuit-breaker and emergency-stop controls is to follow the explicit safety and reliability patterns. Wiring your actuator driver to the runtime protection and safety controller ensures proper emergency-stop sequencing and error-code handling.

Update ESP32 NVS keys and sensor configurations by interacting with the ConfigManager and SensorConfig structures. The centralized API registry provides the necessary signatures and lifecycle guidance for securely persisting and managing your device settings.