📄️ Architecture Overview
Welcome to the engine room of Nextino! This document provides a high-level overview of the framework's architecture, its core components, and how they work together to create a structured and scalable environment for your embedded applications.
📄️ The Lifecycle of a Module
Every module in the Nextino framework follows a consistent and predictable lifecycle, managed entirely by the SystemManager. Understanding this lifecycle is key to writing clean, efficient, and bug-free modules.
📄️ The Configuration System
One of the most powerful features of the Nextino framework is its Configuration-Driven Architecture. Instead of hard-coding which modules your project uses, you define everything in simple config.json files. 🤖
📄️ The Scheduler
One of the biggest challenges in traditional Arduino programming is managing time. The simple delay() function is easy to use, but it's a trap 덫: it completely freezes your microcontroller, preventing it from doing anything else.
📄️ Communication Patterns
In a modular framework like Nextino, a critical question is: "How do modules talk to each other?" 🤔
📄️ The ResourceManager
In any embedded system with multiple components, one of the most common and difficult-to-debug problems is resource conflict: two different parts of the code trying to control the same hardware pin or peripheral at the same time.
📄️ The Device Identity Service
In the world of IoT, every device needs a unique identity. Whether it's for connecting to an MQTT broker, registering with a cloud service, or simply for unique logging, a stable and unique ID is crucial.
📄️ The Command Router
One of the most powerful features for debugging and controlling an embedded device is a Command-Line Interface (CLI). Nextino provides a flexible and powerful core service called the CommandRouter that acts as a central "brain" 🧠 for processing text-based commands.