> For the complete documentation index, see [llms.txt](https://docs.cartographer3d.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cartographer3d.com/original-plugin/fine-tuning/extras.md).

# Extras

<details>

<summary>Adjust Z Offset based on Bed Type (OrcaSlicer)</summary>

<img src="https://3044346320-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjpCp1KnR8izt0cnWQfZF%2Fuploads%2FKExa02N8fPFmDSKpRXXM%2Fbed-types.gif?alt=media&amp;token=79c99228-365b-4821-af50-72ff1466389f" alt="" data-size="original"> <img src="https://3044346320-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjpCp1KnR8izt0cnWQfZF%2Fuploads%2FokO3YixBpoGUbCXdbdMH%2Fimage.png?alt=media&amp;token=c9978504-019d-4040-a0cc-863c51f0bea6" alt="" data-size="original">

In your Machine start G-Code modify your PRINT\_START macro to be similar to this based on your personal needs. The main one to worry about <mark style="color:green;">ADDING</mark> is `BED_TYPE="[curr_bed_type]"`

```gcode
START_PRINT EXTRUDER_TEMP=[nozzle_temperature_initial_layer] BED_TEMP=[bed_temperature_initial_layer_single] CHAMBER_TEMP=[chamber_temperature] FILAMENT_TYPE=[filament_type] BED_TYPE="[curr_bed_type]"
```

This will pass which bed type your using to use in the modified PRINT\_START macro below

<mark style="color:red;">THE FOLLOWING GOES LAST IN YOUR PRINT\_START MACRO</mark>

```gcode
{% if params.BED_TYPE == "Cool Plate" %}
  SET_GCODE_OFFSET Z_ADJUST=0.00
{% endif %}
{% if params.BED_TYPE == "Engineering Plate" %}
  SET_GCODE_OFFSET Z_ADJUST=0.00
{% endif %}
{% if params.BED_TYPE == "High Temp Plate" %}
  SET_GCODE_OFFSET Z_ADJUST=0.00
{% endif %}
{% if params.BED_TYPE == "Textured PEI Plate" %}
  SET_GCODE_OFFSET Z_ADJUST=0.00
{% endif %}
```

</details>

<details>

<summary>Adjusting Z Offset via Slicer</summary>

Finding you need additional or less z-offset on a per filament basis? Go into your slicer and find the Filament settings page. You will be able to add the custom g-code below that will run after your PRINT\_START macro giving this option!

```gcode
SET_GCODE_OFFSET Z_ADJUST=0.01
```

You could also set up duplicate filament settings and use them for different bed types to send a different offset depending on which bed your using and use that filament profile to slice!

### SuperSlicer - Per Filament

<img src="https://3044346320-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjpCp1KnR8izt0cnWQfZF%2Fuploads%2FygjAOnoQ459UR5ViFboe%2Fimage.png?alt=media&amp;token=9ad47bcf-8e91-4db7-94dd-6fe6484a22a2" alt="" data-size="original">

### OrcaSlicer - Per Filament

<img src="https://3044346320-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjpCp1KnR8izt0cnWQfZF%2Fuploads%2FaSf6FgH9rexE2jFRgmrO%2Fimage.png?alt=media&amp;token=d7dd23bc-9536-4a2c-9146-cf53579eaeaf" alt="" data-size="original">

### What does it do?

It will add an modify the z-offset based on your filaments custom z-offset gcode, giving you either MORE or LESS squish based on filament settings.

<img src="https://3044346320-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjpCp1KnR8izt0cnWQfZF%2Fuploads%2Fk4RxnekdlUoofO9eLyT0%2Fimage.png?alt=media&amp;token=59ab968f-bb98-4561-a7c8-9b27407a1908" alt="" data-size="original">

</details>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.cartographer3d.com/original-plugin/fine-tuning/extras.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
