inoCORE — the runtime¶
inoCORE is what runs on the device. It executes the control logic, draws the visualisation, serves WebVisu and talks to the buses — all from the package that inoGUI produced. It never parses text and is never recompiled because a screen changed.
This section is an outline
The pages under it are being written.
Which processors¶
| Family | State |
|---|---|
| ESP32 — classic, S3 | The reference platform. Everything is verified against it. |
| STM32 — selected parts | Supported. |
The modules, dev kits and boards these run on are listed in the hardware reference.
What is here¶
| Page | What it will cover |
|---|---|
| The control cycle | How a cycle is executed and why it is never allowed to stretch. |
| Diagnostics | What the runtime reports about itself, and how to read it. |
The rule the whole runtime is built around¶
Logic outranks communication, which outranks graphics. Under load, frames are dropped. The control cycle is never extended. A display may stutter; the machine's control must not.
Not a safety device
inoCORE is not intended for safety functions. Emergency stop, guard doors, light curtains and end-of-travel limits must be hard-wired.