Covers Engine Plugin SDK 2.0.0 · Interface Plugin SDK 0.2.0

Overview

Build drivers and operator tools with the public example plugin.

Plugins extend the engine, the interface, or both. An engine plugin adds native modules, tasks, operations, and DCode functions. An interface plugin adds resources, task and module editors, settings, and schematic nodes.

Start from the example

Clone the DARTWIC example plugin. It is a standalone project with matching SDK snapshots and build scripts; you do not need the DARTWIC engine source.

git clone https://github.com/voit-systems/dartwic-example-plugin.git my-dartwic-plugin
cd my-dartwic-plugin
npm ci
npm run verify

Use a tagged example version compatible with your installed host. Keep its bundled SDKs together; copying a newer header or interface type into an older SDK is not a supported upgrade.

Build	Guide	Requirements
Hardware driver or native service	Engine Plugin	C++ toolchain, CMake, vcpkg, and Node.js for the starter scripts.
Hardware I/O with fixed channels and native DCode automation	Building a Hardware Driver	An engine plugin plus the native DCode toolchain on the engine computer.
Operator page or configuration UI	Interface Plugin	Node.js and the bundled interface SDK.
Package for local use or distribution	Packaging and Installation	Built output for every side enabled in the manifest.

Files you will edit

plugin.json                 # identity, version, supported hosts, included sides
engine/include/             # your C++ declarations
engine/src/                 # your native implementation and defaults
interface/src/              # your interface contributions
files/                      # optional files installed under the engine config root

The example’s engine/include/sdk and interface/sdk are versioned SDK snapshots. The generated plugin/ directory contains build output. Make source changes in the directories above, then rebuild.

For a complete API list, use the generated Engine SDK reference or Interface SDK reference.