# Set up mash kettle

## Create the mash kettle

In the *Mash Plan* section, create the mash kettle via the gear icon at the top right.

![Create mash kettle](/files/rU5vMJ4ICs9NfZ1O1jW1)

## Configure the cooker

First, configure the cooker itself. This example uses a GGM IDS induction cooker.

The first setting is the IDS type (`IDS1` or `IDS2`). Then configure these control pins:

* PIN white \[relay] - Default: D7
* PIN yellow \[Command] - Default: D6
* PIN blue \[Interrupt] - Default: - (unused)

GPIO D6 and D7 are preconfigured for the GGM IDS cable (JST-HX) and also match the screw terminal layout. The interrupt pin is usually left unused and is mainly needed for troubleshooting.

Next, assign a temperature sensor to the mash kettle. Choose it from the sensor list that already exists. In this basic setup, only *Sensor IDS2* is available.

*Note*: *Each kettle needs a fixed temperature sensor. The actual temperature from this sensor is continuously compared with the target rest temperature during mashing.*

![Configure mash kettle](/files/hbCff0G6tF6M36GWOlyy)

The parameters in the "Temperature control" tab are explained in detail in the parameter section. For this first setup, keep the default values.

![Configure mash kettle](/files/9hxJZUOqiCd4pqY226ZY)

## Set up PID control

After the basic setup, open the PID Manager tab. PID calculates the required heating power to reach each rest temperature and keep it stable.

The AutoTune PID chapter explains step by step how to determine suitable PID parameters.

## Deep dive (Power User)

Technical details about decoupled IDS send behavior from 1.60 onward: [IDS RMT send logic 1.60 (Power User)](/brautomat32/info-1/ids-rmt-160.md)


---

# 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://innuendopi.gitbook.io/brautomat32/info-1/ids.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.