> 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-wiki/polymaker-wiki-zh/da-yin-ji-qiao/hou-chu-li/nian-jie.md).

# 粘合

### **3D Gloop**

专为 3D 打印材料配制的专用粘合剂包括 PLA Gloop、ABS/ASA Gloop 和 PET Gloop，旨在解决打印件特有的粘合难题。这些产品通过部分溶解塑料表面来实现分子级的粘合，从而形成无缝焊接。虽然瓶身设计可能会限制在狭窄空间内的使用，但 PLA Gloop 表现出可靠的性能，而 PET Gloop 在处理 PET/PETG（传统上难以粘合的材料）时效果尤为显著。这些粘合剂在 3D 打印社区中广受好评，少量涂抹在打印表面时，还能增强底板附着力并起到表面平滑的作用。

### **Loctite/Gorilla Glue 强力胶凝胶 (Super Glue Gel)**

Loctite Super Glue Gel 和 Gorilla Glue Super Glue Gel 是粘合 PLA 和 ABS 等硬质塑料的热门选择。Loctite 的凝胶配方便于精确涂抹，在一分钟内即可透明干燥，且不易意外溢出。然而，残留的胶水往往会残留在瓶子的硬塑料外壳中，需要取出才能充分利用。虽然这些粘合剂适用于小型或无法夹紧的零件，但不适用于尼龙，且在长期受力下可能会失效。

### **Devcon Plastic Welder**

Devcon Plastic Welder 是一种双组分环氧树脂，其形成的粘合强度超过了许多打印材料的层间附着力。它适用于高应力应用，需要混合并固化 10 分钟（初步固定）和 24 小时（完全强度）。尽管由于存放时间或条件原因，组分流动性偶尔会出现不一致，但对于需要夹紧的组件，它仍然是 3D Gloop 的强力替代品。

### **J-B Weld**

J-B Weld 在混合粘合方面表现出色，例如将塑料组件粘合到金属上。其钢增强环氧树脂可形成近乎永久的粘合，通常需要破坏性方法（如打磨或熔化）才能分离。它在功能性应用中很受欢迎，可在 12–24 小时内完全固化，并能承受极端的机械应力。

**材料特定建议**

* **PLA/ABS/PETG**：优先选择 3D Gloop 进行无缝焊接；使用强力胶凝胶进行快速修复。
* **尼龙**：避免使用粘合剂——由于粘合性能较差，建议选择机械紧固件（螺丝、卡扣）。
* **金属-塑料混合件**：J-B Weld 可确保耐用且承重的接头。

**注意**：表面处理（打磨、清洁）对于所有粘合剂都至关重要。在全面使用前，请先测试其与涂层打印底板的兼容性。

{% embed url="<https://www.youtube.com/shorts/zEatV92ys9A>" %}


---

# 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-wiki/polymaker-wiki-zh/da-yin-ji-qiao/hou-chu-li/nian-jie.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.