> For the complete documentation index, see [llms.txt](https://wiki.polymaker.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.polymaker.com/polymaker-products/printer-profiles/legacy-profiles-by-material/pps/fiberon-tm-pps-cf10.md).

# Fiberon™ PPS-CF10

{% tabs %}
{% tab title="Bambu Lab" %}
{% file src="/files/U99MjD8R3CrgLWWSghfG" %}
For Bambu Lab X1E using Bambu Studio - Uploaded by Polymaker
{% endfile %}
{% endtab %}

{% tab title="Creality" %}

{% endtab %}

{% tab title="Prusa" %}

{% endtab %}

{% tab title="Ultimaker" %}

{% endtab %}

{% tab title="Others" %}
{% file src="/files/HVZ7IbAjsTc49AQJxk2Z" %}
For QIDI Q1 Pro using OrcaSlicer - Uploaded by Polymaker
{% endfile %}
{% endtab %}
{% endtabs %}

Can't find the profile you are looking for? Join our very active [Discord](https://discord.polymaker.com/) where thousands of members may have already made the profile you need.

***NOTE FOR ALL PROFILES:** These profiles were made to create successful prints for the user who created them - but every model may need tweaks to create the best print possible. If you have any upgrades or changes to your printer - you may need to tweak the above profiles as well.*


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://wiki.polymaker.com/polymaker-products/printer-profiles/legacy-profiles-by-material/pps/fiberon-tm-pps-cf10.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 `build a script that syncs our docs to a CMS` 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.