Differences

This shows you the differences between two versions of the page.

--- mosh:protocol_overview [2025/06/27 15:33] – [🧩 Element Manager] mosh
+++ mosh:protocol_overview [2026/06/10 13:54] (current) – mosh
@@ Line 1: / Line 1: @@
+<WRAP important>
+This page is retained for historical reference and may not reflect the current MOSH/IMC/MTRP architecture.
+See [[guide:architecture_map]] for the current model.
+</WRAP>
 ====== Architectural Overview ======
-The following diagram illustrates the overall architecture of the MOSH library.
-{{:mosh:mosh_architecture.png?1024|}}
 ===== 🧩 Element Manager =====
@@ Line 25: / Line 25: @@
 =====🔌 Virtual Wire Manager=====
-The Virtual Wire Manager is responsible for routing messages between elements based on their assigned virtual wire IDs. It acts as a logical patch panel, allowing input elements (like buttons, sensors, or timers) to trigger actions on output elements (like LEDs, relays, or motors) without direct coupling.
+The [[mosh:virtual_wire_manager|Virtual Wire Manager]] is responsible for routing messages between elements based on their assigned virtual wire IDs. It acts as a logical patch panel, allowing input elements (like buttons, sensors, or timers) to trigger actions on output elements (like LEDs, relays, or motors) without direct coupling.
 By abstracting the connection layer, the Virtual Wire Manager enables modular, transport-agnostic automation across distributed nodes. It ensures that status or property change messages are delivered in real time to all elements subscribed to a given wire, regardless of their physical location or transport layer.
 Virtual wires form the backbone of decentralized automation in MOSH.
-===== Message Framer =====
-The Message Framer is responsible for a variety of MOSH functions. Some of these functions include:
+=====📡 Transport Manager=====
+The Transport Manager oversees all communication interfaces used by a MOSH node. It handles registration, configuration, and routing for multiple simultaneous transports—including ESP-NOW, Serial, Wi-Fi, and others.
+Each transport is wrapped in a standardized MOSH class, allowing MOSH Core to send and receive messages without needing to know the specifics of the underlying radio or link.
+The Transport Manager:
-  * The final construction of MOSH Messages
+  * Maintains active transport instances
-  * Accepting message requests from the Virtual-Wire Manager
+  * Assigns network and node IDs per transport
-  * Accepting/Sending messages to/from the Transport Manager
+  * Manages message framing, delivery constraints, and acknowledgments
+  * Supports both point-to-point and broadcast-capable transports
-===== Transport Manager =====
+The Transport Manager makes MOSH hardware-agnostic, enabling seamless communication across diverse networks and physical layers.