> For the complete documentation index, see [llms.txt](https://spascual90.gitbook.io/fenix-autopilot/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://spascual90.gitbook.io/fenix-autopilot/installation-commissioning/commissioning.md).

# Commissioning

## Commissioning Process

This chapter explains how to commission your tiller pilot after installation. This consists of a number of simple functional tests followed by a short sea trial.

Before first use of Fenix Autopilot, user shall go through the complete Commissioning process.

## Functional tests

#### Switch on

1\. Switch on the main power breaker.

2\. The autopilot should beep and display the compass heading. 

This shows the autopilot is active. Note: If the tiller pilot does not beep or display the compass heading, please refer to the Fault Finding section.

#### Operating sense

The operating sense defines the direction the tiller pilot will apply helm when a course change key is pressed or the boat goes off course. To check the operating sense:

1\. Place the pushrod end over the tiller pin.

2\. Press +10.

3\. The helm should move to produce a turn to starboard

If the helm produces a turn to port, refer to the following instructions on reversing the operating sense.

#### Reversing the operating sense

{% hint style="warning" %}
Feature not available in Fenix V0.1.
{% endhint %}

## Check Interfaces

{% hint style="danger" %}
To be completed
{% endhint %}

#### Checking the Serial I/F

#### Checking the Virtuino App interface

#### Checking the OpenCPN interface

## Initial sea trial

{% hint style="danger" %}
To be completed
{% 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://spascual90.gitbook.io/fenix-autopilot/installation-commissioning/commissioning.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.