Network Map shows connections between your Interface, Engine, and other nodes. Open it from the left sidebar, then select a node for details or a connection for traffic. Use fit view to bring the map back into view.

Connections

Your connected Engine sits in the center. Operators using desktop or web Interfaces appear on the left, with their profiles and connection details.

Clients appear below the Engine. These include Python analysis scripts, Node.js services, C++ applications, and other tools that use a client library or custom client implementation.

Peers appear on the right. They can be other DARTWIC Engines, custom applications exposing their own data and commands, or device and flight-computer connections supplied by plugins.

Clients and Peers

See Networking and Peers for registration and session details; the guides below cover using or building each connection.

Clients

Use Python for scripts and analysis, Node.js for services, C++ for native applications, or React for browser dashboards. To implement your own client or client library, follow Custom Client.

Operators

Operator commands carry user identity and can explicitly take or release manual channel control where permitted; ordinary clients cannot. See Control Authority and Overrides.

Your own application can also connect as an operator: include a non-empty interface_type and its username in the register_client metadata. For an existing application, supply those fields through its registration layer when reconnecting; they are not options exposed by every high-level client library. Custom Client covers the registration flow. Operator identity does not grant administrator access; registration permissions still apply.

Peers

Use a C++ Engine Protocol Peer to share DARTWIC channels, events, and logs, or a C++ TEMPEST Protocol Peer for custom messages. Building a Custom Peer covers plugin-provided transports and device protocol bridges.

Connect and Reconnect a Peer

As an administrator, choose Add peer or the cable control on the Engine node. For another DARTWIC Engine, select Engine Protocol Peer — TEMPEST TCP, enter its TEMPEST IP, base TEMPEST Port, and Password, then choose Add peer. The remote Engine must be running; check the resulting connection state.

Give Engines distinct node names and separate ports when running on one computer. Other protocols use different connection types; see Connection Types and Peer Connections.

Remote channels appear with their owner’s prefix, such as TEST_STAND:tank_pressure. Use the full name in graphs and schematics. Export saved peer data through Data.

Viewing Network Traffic

The Engine uses a subsystem of DARTWIC for communication, called TEMPEST, which speaks to clients and peers in a certain way.

Operations are requests and responses; telemetry carries updates such as channel readings. You can select a client or peer, and filter its traffic with Operations, Telemetry, or Connections, then select a message to inspect its payload.

You can also select the radio icon next to the node in the Node Bar to see its network activity.

Telemetry RX or DOWNLINK shows delivery activity, but channel timestamps tell you whether measurements are fresh. See Operations and Telemetry and Remote Channel Freshness for details.

Sending Network Traffic

Viewing the network traffic also allows you to view the registered operation and telemetry list for that TEMPEST peer or client. Selecting one will open up a side panel and you can configure arguments, and send a registered operation or telemetry payload manually.

Pinned Operations

You can also save a configured operation payload a a Pinned Operation, by saving a name and pressing the pin button.

Pinning an operation allows you to manually call operations easier with preconfigured arguments and one send button.

Send from DCode

You can also send operations through DCode.

With an Engine peer named TEST_STAND connected, open a DCode script and activate this read-only request for its runtime information:

result = tempest_operation("TEST_STAND", "dartwic/get-runtime-metadata", {})

Replace TEST_STAND with your connected node’s name. The call waits for a response; select that peer’s network traffic to inspect the request and reply. TEMPEST Operations in DCode explains arguments and saved operations; tempest_publish sends custom telemetry instead.

Disconnection and Recovery

A Remote node connection failed event explains connection failures. Last received values can remain visible while disconnected; treat them as earlier observations.

A peer’s Disconnect action also removes its saved target, so you must add it again to reconnect. To disconnect only your Interface from its Engine, use the navbar’s node menu. See Disconnection and Recovery.