Harnesses and function links
Connect parts with harnesses, choose the interface pair a harness carries, link functions and understand what makes two interfaces compatible
Goal
Connect two parts so that the connection is complete and passes DRC, and understand the three layers every connection is made of.
How connections are layered
Function links
Inside the interface link, function links pair the individual signals: SDA to SDA, SCL to SCL. Each function is backed by a resource (a pin or port) on its part. See Resource allocation.
Create and configure a harness
Animated GIF · Steps:
Hover over the edge of a part until the orange handle appears, then drag to the other part. A grey harness labelled UNKNOWN appears and the Inspector opens for it.
Under Interface selection, open Interface pair and choose a pair, or let Protoboard pick the best compatible pair.
Protoboard matches the functions by name and assigns pins. The harness turns green when every required function is linked and assigned.
If some functions stay unlinked, open Function Links and click Auto Assign, or pick the pair and pin in each row.
Give the harness a name, for example
Left motor control. The name shows on the canvas.
Keyboard alternative: select a part in the Inspector's object tree, activate Create harness, choose the other part and activate Create.


Fan-out
One side of a harness can carry several instances of the same interface, so a single bus can reach several devices. Add instances with + add next to the A or B interface. Each instance needs its own wiring and pins.
What makes two interfaces compatible
Protoboard checks each interface pair against the part definitions:
Protocol type matches
I2C on one side, SPI on the other
Roles pair up
Two I2C masters
Domain matches
An electrical interface paired with a pneumatic one
Electrical ranges overlap
A 5 V output into a 3.3 V-only input
Physical connector fits, when specified
Two connectors of the same gender
Role pairs are defined per protocol in the ProtoPart protocol spec: master and slave for I2C and SPI, host and device for USB and UART, output and input (or source and sink) for power, driver and actuator for DC motors, and so on. The full list is in Interfaces and Harnesses. Simple net-like connections, such as a wire to a terminal, accept any electrical interface.
Harness colours
Green
Configured
Every required function is linked and has a pin
Yellow
Partially configured
The interface link exists but wiring or pins are missing
Grey
Not configured
No interface link yet
Red
Incompatible
The interfaces can't connect
In high contrast mode each state also has its own line pattern. The HARNESS LEGEND at the right of the canvas explains each state and its fix. See How DRC works.
Other harness actions
Right-click a harness for Auto-route this harness and Move source handle or Move target handle.
Remove a link inside a harness from the Inspector, or delete the whole harness with the Delete key.
Common failures
Related pages
Resource allocation: which pin carries which signal
How DRC works: states and reasons
Interfaces and Harnesses: protocols and roles reference
Last updated

