> For the complete documentation index, see [llms.txt](https://docs.wcproducts.com/welcome/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wcproducts.com/welcome/system-and-structure/tube-plugs/general-info/tube-plug-assembly.md).

# Tube Plug Assembly

The WCP Tube Plugs are designed to be a slip to light-press fit in most tubing. A dead blow hammer or soft mallet may be used to tap the plug into place as needed.

{% hint style="info" %}
Due to variations and quality in tubing from various suppliers the Tube Plugs may be a bit tighter than expected. If this is the case, a bit of extra force may be needed to install the plugs. The outside can also be sanded down or machined for a slip fit if desired.
{% endhint %}

We have found that threading a #10-32 bolt into the large face of the Tube Plug can help prevent the plug from being pushed too far into the tube.

<figure><img src="https://1844070818-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FV88rOhyRqwyr1rYHFvV1%2Fuploads%2FnKEtEReJfT9Ah3BBXxAD%2FTube%20Plugs%20-%20Assembly.svg?alt=media&amp;token=e8ee32e5-3634-44e6-b8ed-57c6e4c1d510" alt="" width="563"><figcaption></figcaption></figure>

## Fastening Options

The Tube Plugs are designed to be secured into tubing using #10-32 x 3/8” L BHCS but these can be substituted for many other fasteners that teams use. A light weight alternative to bolts is to drill the holes out for a 3/16” rivet. Alternately, for a heavy duty connection, the holes can be drilled and tapped to 1/4"-20.&#x20;

While all mounting holes may be used if desired, we suggest installing four fasteners on the front face and two fasteners on each side face when possible for a secure and stable mounting solution.

{% hint style="info" %}
The image below shows the recommended bolt locations.&#x20;
{% endhint %}

<figure><img src="https://1844070818-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FV88rOhyRqwyr1rYHFvV1%2Fuploads%2FyW04nutg6vF9EFCyMVnE%2FTube%20Plugs%20-%202x2%20Bolt%20Locations.svg?alt=media&amp;token=b730e83f-657f-488c-bee9-323ae62682ae" alt="" width="563"><figcaption><p>2"x2" Tube Plug</p></figcaption></figure>

<figure><img src="https://1844070818-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FV88rOhyRqwyr1rYHFvV1%2Fuploads%2F9Bd3QfTzUHsRTelqJITJ%2FTube%20Plugs%20-%201x1%20Bolt%20Locations.svg?alt=media&amp;token=ce683075-21f4-45bc-88a7-ceeff7718e9a" alt="" width="563"><figcaption><p>1"x1" Tube Plug</p></figcaption></figure>


---

# 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.wcproducts.com/welcome/system-and-structure/tube-plugs/general-info/tube-plug-assembly.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.