Overview

The engine runs independently of the interface. It loads a project, hosts hardware modules, executes automation, accepts or rejects commands, records data, and serves connected clients.

Runtime components

Configure and start

A release engine reads its configuration from the parent of its executable’s bin/ directory. DARTWIC_CONFIG_DIR can select another root. The startup log prints the resolved configuration directory so you can verify which instance you launched.

The engine-local config.json locates the workspace and holds credentials and optional local overrides. Shared node name, server address/base port, and active project are tracked in workspace/global_data/engine_config.json. Plugins are installed below plugins/; project resources live beneath the configured workspace. Keep separate configuration roots for independent engine instances.

Follow First Session for a packaged launch and connection. Use Modules to add device instances and DCode to activate scripts.

Design the data path

A module publishes a measurement to RAPID. Dependent calculations and event conditions can run inline during that update. Scheduled tasks execute separately, and telemetry, recording, and Share delivery are asynchronous.

Read Execution and Timing before choosing where to put a limit response. Read Commanding and Control before exposing outputs to tasks or clients.

Guides

The generated TEMPEST reference lists operation and telemetry contracts. Engine implementation details are separate from the public plugin SDK.