# Production (V1) Carrier Board Connectors

The NXP reference board design production version units have a slightly different connector set than what has tradionally been included in the standard V6X design and also the Holybro V6X-RT units.\
\
The key differentiators are:\
 \- No separate IO processor required. All PWMs including redundant coming from RT1176

* Three CAN ports
* 100BaseT1 two wire ethernet
* Additional SE05x secure element on the base board in addition to the FMUMRT1176
  * NFC antenna interface to secure element
* DSM and AUX RC ports in addition to "RC IN"

\ <br>

<figure><img src="/files/QzRBUFRmSlq7XXw9d7nM" alt=""><figcaption><p>12 RC-PWM outputs are available </p></figcaption></figure>

<figure><img src="/files/s6ym7hrUFWFRk287di7B" alt=""><figcaption><p>Dual redundant power inputs. </p></figcaption></figure>

<figure><img src="/files/MEokUH7LjWZg8wpP8A3D" alt=""><figcaption><p>Right side view interfaces</p></figcaption></figure>

## Right side interfaces&#x20;

They include:

* AD\@I/0 Analog and GPIO
* CAN1, CAN2: Dual CAN-FD interfaces employing CAN-SIC (Signal Improvement) CAN phys.
* I2C interface
* USB-C interface and USB on JST-GH pins. (parallel pin connections not independent)<br>

![](/files/7SNSpg0EXVPGYqegOUjN)

<figure><img src="/files/hXRNaJxQLtdOcm04eJWj" alt=""><figcaption></figcaption></figure>

## Left Side Connections

* CAN3: (extra additional ) CAN-FD interfaces employing CAN-SIC (Signal Improvement) CAN phys.
* T1-ETH: 100BaseT1 Two wire 100MBPS Ethernet&#x20;
* TELEM1/2/3: 3x Telemetry ports with Hardware handshaking
* UART\&I2C: 4th UART, no hardware handshake, I2C, NFC\_GPIO included
* Debug interface compliant to Pixhawk-DEBUG-FULL standard (aka DCD-F), including SWD and Console access.\
  \
  \ <br>

  <figure><img src="/files/ZA2KBnCx8kMDOxA0ma9x" alt=""><figcaption><p>Front connectors</p></figcaption></figure>

## Front side connectors

* DSM: DSM RC radio input
* NFC: NFC connection to carrier board Secure Element. (interface may be accessible even when not powered?)
* GPS1: PX4 full GPS connector including Arming Button interface, beeper, magnetometer and RGB LED&#x20;
* GPS2: Aux GPS, reduced pinout on connector.
* SPI: External SPI interface including two hardware chip selects, nSYNC, DRDY1/2 and SPI\_nRST

## PWM and SBUS IBUS RC input

![](/files/k5M4l64Ca2Cj8B6m4pQm)  ![](/files/Y0TZaxpD1D5a54C6GfPE)

Typical connection for SBUS/IBUS  input  from RC remote controller. (note: Alternative RC interfaces possible)

## Debugger and serial console connection

<figure><img src="/files/RWLKm492R1iCWC3PG9hh" alt=""><figcaption><p>Use Cognipilot Neural probe or DCD-LZ-ADAPT or similar adapter to connect a debugger or serial console to the Pixhawk-debug-full port (AKA DCD-F)</p></figcaption></figure>

Use Cognipilot Neural probe or DCD-LZ-ADAPT or similar adapter to connect a debugger or serial console to the Pixhawk-debug-full port (AKA DCD-F)\
\
<https://docs.px4.io/main/en/debug/swd_debug.html>\ <br>

## Indicator LEDs

Note the legend for the LEDs is actually shown above the 4 led holes in the enclosure.

<figure><img src="/files/5mtfbNoqzm0c2xARYvbz" alt=""><figcaption><p>LED indicators show Ethernet connection and activity, Power supply present, and the staus of the ANALOG pin input setting. (see schematics for ASEL usage)</p></figcaption></figure>

### ASEL analog input select indicator

<figure><img src="/files/WHc5WCgCjsNkIDcyUZgS" alt=""><figcaption><p>Schematic showing alternative function. D5 = ASEL LED.<br></p></figcaption></figure>

Schematic showing alternative function. D5 = ASEL LED.\
J14 pin 7 'ADC1\_6v6\_Aux', can be selected to connect either 'ADC1\_6v6' or  Vdd Servo rail to the ADC to read the voltage. \ <br>

<figure><img src="/files/17a7wFobe7Sa8sHvmhLV" alt=""><figcaption><p>PWM labelling on side indicates the ground pin (Brown or Black wire) and the Signal/PWM pin (orange, white or blue)</p></figcaption></figure>


---

# Agent Instructions: 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:

```
GET https://nxp.gitbook.io/vmu-rt1176/production-v1-carrier-board-connectors.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.