# Kit Contents

The MR-CANHUBK344 comes as a kit that includes the items specified on the packing slip documents. Note a reduced kit is also expected to be made available. In the full version the following hardware components are included:

* MR-CANHUBK344 board
* DCD-LZ debug breakout board
  * This is an adapter board that gives access to a standard 10-pin, 0.05" SWD debug connector, as well as a debug/console UART header compatible with a standard 3.3V USB-to-UART cable.
* USB-to-UART adapter cable (attaches to the DCD-LZ board)
* Power adapter cables
  * Including JST-GH to commonly used red JST-SYP connector, barrel plug connector, and XT60 LiPo battery connector.
* 6x CAN cables
* 6x CAN Termination boards
* 1x 100Base-T1 “two wire” Ethernet cable using JST-GH connectors
  * Note: automotive applications will specify alternative connectortypes. You may wish to fabricate an adapter cable.
* Generic JST-GH cables for UART/SPI/I2C, used for customizing to your specific needs 
* Small 0.91” OLED display
* NFC antenna, to be connected to the Secure Element

The JST-GH connectors will follow the Dronecode pinout standards where one exists for that type of interface. Otherwise confirm the pinout using the schematics.

The JST-GH connectors are intended to work directly with other NXP Mobile Robotics boards such as [NavQPlus](https://nxp.gitbook.io/navqplus/), [UCANS32K1](https://nxp.gitbook.io/ucans32k1/), RDDRONE-BMS772, MR-BMS771, and RDDRONE-FMUK66, RDDRONE-FMURT6, or MR-FMURT1176.

{% hint style="info" %}
The intent with these "Dronecode standard" cables, and particularly with the generic UART/SPI/I2C 4/6/7-pin cables, is that you ***may cut or otherwise adapt them to attach to your specific interface requirements.***
{% endhint %}

<figure><img src="/files/qm0PRtoNly75SikbyVsy" alt="" width="335"><figcaption><p>JST-GH style connectors</p></figcaption></figure>

<figure><img src="/files/REDygFeTazQWpLXGykd7" alt="" width="244"><figcaption><p>JST-SYP / JST-SYR style connectors</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/mr-canhubk344/kit-contents.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.