> For the complete documentation index, see [llms.txt](https://docs.auterion.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.auterion.com/hardware-integration/airframe-integration/wiring-without-breakout-boards.md).

# Wiring without Breakout Boards

The breakout boards shipped with the [Evaluation Kit](/hardware-integration/skynode/evaluation-kit.md) offer flexibility during exploration and prototype phase. For a tighter hardware integration, devices can be wired directly to the Pico-Clasp connectors on Skynode such that the breakout boards become obsolete.

## Required tools

* [Molex Pico-Clasp connectors](https://www.digikey.com/en/products/detail/molex/5011894010/1531524?s=N4IgjCBcoBw1oDGUBmBDANgZwKYBoQB7KAbRACYwwA2AVggF0CAHAFyhAGVWAnASwB2AcxABfUQXKkQAW0IYcADwAEzPokLLEGNFmYgGooA)
* [Pico-Clasp crimp tool](https://www.digikey.com/en/products/detail/molex/0638191500/1832244)
* [Pico-Clasp crimp contacts](https://www.digikey.com/en/products/detail/molex/5013340100/1531513)
* Alternatively [Pre-crimped Pico-Clasp cables](https://www.digikey.com/en/products/detail/molex/0797581017/6564342)

![](/files/tYlsLgFJk8vQhxUZGDTs)

## Schematic

{% file src="/files/jSzbFD2a34tpt6ZgDAeK" %}
Skynode Pico-Clasp Pinout
{% endfile %}

## Wiring Devices to the Pico-Clasp Connectors

### Example: Freefly RTK GPS module

| Pin # on GPS JST Connector |    Signal   | Pin # on Pico-Clasp Primary (J4) |
| :------------------------: | :---------: | :------------------------------: |
|              1             |   VCC\_5V   |               22 \*              |
|              2             |   GPS\_RX   |                18                |
|              3             |   GPS\_TX   |                20                |
|              4             |   I2C\_SCL  |                19                |
|              5             |   I2C\_SDA  |                21                |
|              6             |    BUTTON   |                 3                |
|              7             | BUTTON\_LED |                 5                |
|              8             |     GND     |               7 \*               |

*\*There are also other options to chose here as those signals appear multiple times on the Pico-Clasp connector J4. Make sure to use the correct supply voltage for your peripheral. For the GPS this would be VDD\_5V\_CAN1\_GPS1 (pin 22 or 40). For other peripherals check the Datasheet under "Peripheral Power Domains".*

![Crimp the ends of the GPS cable](/files/ax5I0RgGYq7gP5LMla5g)

![Insert the crimped ends to the correct positions on the Picoclasp connector](/files/FxF4kHvIECS4fcetHcTH)

{% hint style="info" %}
The I2C pins exist only once one each Pico-Clasp connector. If you would like to connect multiple I2C devices on the same I2C bus you can split the I2C line using a Y-cable
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.auterion.com/hardware-integration/airframe-integration/wiring-without-breakout-boards.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.