The Edge Operating System Powering Disruptive Benefits
MOS350: The Central Engine of Edge Computing's Transformation. At the core of realizing the disruptive potential of edge computing is the MOS 350 Edge Operating System. This system serves as the central orchestrator and controller for clusters of devices operating at the network's edge, unlocking a suite of six disruptive benefits:
- Autonomous Machine Operation: By managing devices locally, MOS 350 enables independent decision-making and action without constant reliance on the cloud.
- Real-Time & Context-Aware Automation: It facilitates processing data and triggering actions with minimal latency, informed by the immediate environment.
- Reliable Operation with Intermittent Connectivity: MOS 350 ensures critical tasks continue even when network access is unstable or unavailable.
- Highly Secure Operations: Furthermore, it prioritizes security, delivering highly secure operations at the edge.
- Cost-Effective Low-Code Rapid Development: From a development and deployment perspective, MOS 350 likely offers tools and frameworks that simplify the creation and deployment of edge applications.
- Interoperability between Legacy & Modern Devices: Finally, it fosters bridging the gap between existing infrastructure and newer technologies at the edge.
In essence, MOS350 is a crucial component for organizations looking to leverage the power of edge computing, offering a robust and versatile platform to manage distributed devices and realize significant operational and strategic advantages.
As a developer, what you need to know to get started:
Hardware: Pick any supported hardware from the list below:
- Compulab – IMX8MP
- InHand – EC900
- Teltonika – RUT955
- Teltonika – RUT240
- Rainforest - Eagle RFE200
If your hardware is not on the list, we can port MOS350 onto your hardware.
Quick Introduction to MosEMS build on Mos350
MOS350 Important Folder Structure
These folders will be under the user /home/mos350 home folder in case of Debian-based devices and under /home/root for OpenWrt-based devices.
- dapp: Application Folder. Any application in this folder should implement
libMOS_l.socore functions. Applications are automatically executed by MOS350 and are monitored by the fusion layer for any failures or memory leaks, maintaining stable operation. - dcfg: This folder holds all configuration and Digital Twin files representing real-world devices that are paired with any MOS application. Please do not manually remove any files from this folder if you are not yet an expert in the MOS platform.
- dlib: Library files can be placed in this folder; they are loaded into the application context by the MOS Fusion layer.
- dsrc: This folder is for all custom scripts. For example, a GPIO-triggered custom script file should be placed here.
