moveOS consists of a lightweight Kernel and supporting libraries that greatly help in developing and deploying movable and immovable smart-objects spanning a variety of domains. The main, desirable features:
⭐ Ease of use
⭐ Lightweight deployments
⭐ Energy efficiency
⭐ Real-time responsiveness
⭐ Encouraging the task and event-based designs
⭐ Natively supporting the State Machines
⭐ Graphical and headless deployments
⭐ Remote interfacing through stand-alone graphical and cloud-based services
⭐ Ready-to-use security and extensible modules
⭐ Low-code and no-code facilities
⭐ ROS integration
⭐ High configurability, extensibility and agility
From the beginning, the moveOS is intended to be deployed on bare-metal devices, Windows and Linux distributions; though, its behavior can change depending on deployed environments and underlying hardware features. The requisite workflow is envisioned as:
graph TD;
A(Design / Logic Implementation) --> B(Hosted Execution at Windows / Linux Distribution)
B --> A
A -.-> C{Stable Design?}
C -.-> |Yes|D(Deployment to Device)
C -.-> |No|A
moveOS comprises of two types of modules i.e., Compiled with the Kernel itself, and the ones loaded as pure modules that can be unloaded at any time - just like the Linux Kernel modules.
Documentation is kept in docs folder.
For using the OS and libraries:
- Defining tasks
- Defining State Machines
How it is arranged?
- Architectural Overview
- Conditional Compilation Definitions