Networked Shared Control

NSC (Networked Shared Control) refers to both the event-driven, cooperative multitasking operating system and a distributed automation system designed for real-time control across a low-power, peer-to-peer network.

Originally developed for industrial and building automation, it enables multiple embedded devices to collaborate without a central controller.

Key Characteristics

• Distributed: not centralized
• Visual-first: but programmable
• Event-driven: not cyclic/scanned
• Peer-to-peer: not master-slave
• Extensible via reusable and compounding components
• Low-power and efficient: via RS485 LE + SFPB, all nodes are equal — any node can initiate communication with another at any time.

Example Applications

• Distributed process automation
• Building control systems, home automation
• Remote input/output coordination
• Energy and water management
• Greenhouse/farm automation
• Embedded applications (via advanced SDK)

Easy to program

Visual Programming with Optional C-like Code

While the system supports low-level coding with a C-style syntax, MaticStudio offers a visual programming environment where developers define event-driven behaviors by linking events to actions.

• Visual programming is the default and most intuitive mode
• Manual code editing is reserved for advanced users or optimization

Automatic RPC generation

MaticStudio transparently generates Remote Procedure Calls between devices when cross-device interactions are defined in the visual logic — no messaging code is needed.

• Eliminates the complexity of writing inter-device communication logic
• Enables true distributed behavior without the usual protocol boilerplate

Extensible

The system is modular and extensible through Virtual Components, which are distributed as COB files. These provide advanced logic and optional UI components for SCADA integration.

SFPB: Simple Field Bus Protocol

The physical network uses low-power RS485, running SFPB — a lightweight, peer-to-peer field protocol with no master-slave model.

• Devices are autonomous and cooperative
• Any node can initiate communication
• Scales naturally across up to 126 devices

This highlights a major departure from traditional fieldbus systems (like Modbus RTU or CANopen), which often use polling or master-slave timing.

Advanced SDK

The NSC Framework offers an SDK which fits the devices based on the NSC system, for fast and efficient firmware.

The NSC AppWizard can guide through the creation of the event boilerplate structure and RPC messaging, that can be compiled with AVR-GCC.

The compiled firmware can be uploaded using the standard ISP for AVR.