> 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/more-about-our-products/other-polymaker-information/carboard-spool-no-problem.md). # Carboard Spool = No Problem Polymaker has addressed a common issue for 3D printing enthusiasts using multi-material systems like the Bambu Lab AMS: the compatibility of cardboard spools. Traditionally, cardboard spools had soft paperboard edges that were prone to wear and damage, especially with the repeated forward-and-backward motion inside automatic material stations. This sometimes resulted in cardboard dust, poor feeding, and spools that would slip or jam. Responding to user feedback, Polymaker introduced new cardboard spool designs with **hardened or sealed edges**. These reinforced edges provide a much more durable and smooth rolling surface, dramatically reducing friction and the risk of the spool snagging or disintegrating during use. As a result, the upgraded spools now **spin reliably in the AMS and similar multi-material systems**, making them virtually as effective as plastic spools while offering the environmental benefit of cardboard construction. {% embed url="" %} --- # 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://wiki.polymaker.com/polymaker-products/more-about-our-products/other-polymaker-information/carboard-spool-no-problem.md?ask=&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.