Pins and Connections

Table of Contents

• Introduction
• Pins
  • Example 1
• Connections
  • Example 2

Introduction

INSTINCT allows to work with a variety of data types that can be read, processed, exported or displayed. A Flow must therefore not only include Nodes, they also need to be connected via their Pins (see Getting Started).

Pins

Each Node comes with at least one Pin. Pins can be either an input or an output Pin, depending on the side they are on a Node. All current available Pins to connect Nodes are described in the Demo Node.

Even if two Pins are of the same data type, e.g. both beeing a Flow (see Demo Node), they can still be different in the data they include. In oder too see which data a Pin accepts, hovering over it displays the data.

Example 1

The PosVelAttLogger Node accepts Flows containing only position (Pos), position and velocity (PosVel) or position, velocity and attitude (PosVelAtt) data as an input. The RtklibPosConverter Node outputs PosVel, the Imu Simulator Node PosVelAtt. This means both can be connected with the PosVelAttLogger.

Connections

Connections are only legal if they are of the same data type and matching type (intput/output-Pin).

Example 2

1. Demo Node showing type of Pins.
2. Legal connection: Pins have correct type (SppSolution and Flow), one is an out- while the other an input.
3. Illegal connection: Both Pins are input-Pins.
4. Illegal connection: Pins are of different data type.

Note

Illegal connections will be marked red and removed immediately.

Hovering over a Pin shows the data that is taken in or given out.

Left-click and drag a Pin offers to + Create Node that has suitable connections.

left-click and drag a in-/output-Pin also hides all illegal connections on other out-/input-Pins.

---

Last updated: 2024-02-26