Plugins are packages that add capabilities to DARTWIC. An Engine side provides work such as a device driver; an Interface side provides controls, editors, or display elements. A package can have either side or both.

Open the Settings gear in the left sidebar and choose Plugins to inspect installed packages and each side’s load status. Use Browse plugins to find and install a package. From these pages, you can read its documentation, open its settings, update it, or remove an installed side.

Choose a Plugin

Choose the package according to what you want to add. For example, a driver package can supply both the Engine’s device connection and the Interface forms used to configure it.

The Plugin overview explains the package types. The catalog entry’s README describes that plugin’s actual capabilities, supported devices, and setup requirements.

Install from the Plugin Browser

Connect to the Engine you want to extend, then open Settings → Plugins → Browse plugins.

Search for the driver or tool and select its card. Read the README and minimum host versions, then choose Install. The browser selects compatible published packages.

The Interface side loads immediately. Engine code requires a restart; accept the prompt when you are ready to interrupt running work. After reconnection, check that the sides you need show Installed and Loaded.

Install an Unlisted GitHub Plugin

Your team may use a plugin that is published on GitHub but has not been added to the catalog. You can open its repository directly and still review its requirements before installation.

Choose Open plugin from GitHub in the catalog toolbar, enter its repository URL, and View plugin. Review its details and install through the same workflow. For manual installation and package requirements, see Packaging and Installation.

Installation Status

After installing a driver, you might still be waiting for an Engine restart before its module types become available. The status badges distinguish files that have been installed from code that has loaded and is ready to use. Check each side before configuring its features.

Registration badges identify module/task types, editors, settings, and schematic nodes. A driver still needs module and task configuration before it can communicate with a device.

Plugin Updates and Removal

You can update a plugin when its author publishes fixes or remove it when the installation no longer needs it. A device driver may be used by several projects, so check where it is used before removing it.

Use the update or remove control beside the installed side and read its result. Native changes queue until restart; Interface changes apply immediately. Check which version loaded afterward.

Engine installations share plugins across workspaces. If another Engine locks a file, stop the holder and retry. See Packaging and Installation for installation details.

Create Your Own Plugin

If no existing package supplies what you need, you can write an extension and install it through the same system. Start with the example plugin. Follow Building a Hardware Driver for a device connection with tasks, Engine Plugin for C++ services, or Interface Plugin for operator tools and display nodes. Those guides cover implementation; this page covers choosing, installing, and using the resulting package.