# Commissioning the Pixy 2

{% hint style="info" %}
Further information of the Pixy 2 can be found [here](https://docs.pixycam.com/wiki/doku.php?id=wiki:v2:start).

The Pixy 2 can be commissioned and parameterized by the **PixyMon** software. A quick manual can be found [here](https://docs.pixycam.com/wiki/doku.php?id=wiki:v2:pixy_regular_quick_start). 
{% endhint %}

Within the PixyMon Software the Pixy 2 parameter for line tracking can be optimized. Following pictures show the nearly optimal settings for line tracking on the NXPCup track.

![Tuning tab](/files/-Lp8ygfA-Clc0IfDVbcE)

## I2C Communication

For an I2C communication follow up this [guide](https://docs.pixycam.com/wiki/doku.php?id=wiki:v2:porting_guide). The default address is 0x54. The demo code using the FMU on this [page](https://nxp.gitbook.io/nxp-cup/developer-guide/development-tools/rddrone-fmuk66-development/commissioning-the-rddrone-fmuk66/the-example-application) runs with the default I2C address.‌

## SPI Communication

For an I2C communication follow up this [guide](https://docs.pixycam.com/wiki/doku.php?id=wiki:v2:porting_guide). The demo code using the ARC board runs with SPI.


---

# 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/nxp-cup/2019-dfrobot-chassis-developer-guide/assembly/installing-the-pixy-2.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.