Menu

Pin Designation System

Pin Numbering Convention

Splice follows the following pin numbering conventions:

  • All connectors are assigned an integer number of pins.
  • By default, pin labels are assigned starting from 1 (not 0)
  • Numbers increment without gaps

Custom Pin Mapping

For connectors requiring non-sequential numbering or custom labels, use the pin_mapping field. This field maps pin indices (as strings) to custom labels.

Example with numeric labels:

pin_mapping: {
  "0": "1",    // Pin 0 maps to the label 1 (Default)
  "1": "3",    // Pin 1 maps to the label 3
  "2": "4",    // Pin 2 maps to the label 4
}

Example with functional labels:

pin_mapping: {
  "0": "GND",    // Pin 0 maps to the label GND
  "1": "24V",    // Pin 1 maps to the label 24V
  "2": "TX",     // Pin 2 maps to the label TX
  "3": "RX"      // Pin 3 maps to the label RX
}

Bridged Positions

To denote electrically bridged pins, define a bridged_positions array using mapped pin labels:

pin_mapping: {
  "0": "GND_1",    // Pin 0 maps to the label GND_1
  "1": "GND_2",    // Pin 1 maps to the label GND_2
}
bridged_positions: [["GND_1", "GND_2"]]

This example shows pins labeled GND_1 and GND_2 are internally connected.

Pin Functions

A pin’s label identifies it (e.g. 1, A2); its function describes the signal role it carries (e.g. CAN_H, GND, UART_TX). Functions are optional and independent of the label.

Edit a pin’s function in the component Properties panel (Positions tab) or in the Bulk Editor’s Components tab. Functions are stored on the connector as an index-parallel pin_functions array:

pin_functions: ["CAN_H", "CAN_L", "GND", "12V"]

Pin functions are shown on the connector graphic in the diagram and are preserved when converting between a plan and a harness (they mirror the plan’s pin functions).