> For the complete documentation index, see [llms.txt](https://docs.champcheats.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.champcheats.com/dma-docs/1k-hdmi-fuser/fuser-overview.md).
# Fuser Overview
**💡 Indicator Lights:**
* **\[D1]**: Power indicator (solid light when powered on)
* **\[D2]**: Fusion function indicator (solid light when fusion is on, off when fusion is off)
* **\[H2]**: DP secondary input signal indicator (solid light when functioning normally)
* **\[H1]**: DP primary input signal indicator (solid light when functioning normally)
***
**▶️ Button Functions:**
* **Power**: Power switch
* **\[K1] Secondary Screen Mode** – Displays only the 2nd PC screen while disabling the main screen
* **\[K2] Main Screen Mode** – Displays only the main PC screen while disabling the 2nd screen.
* **\[K3] Fuser Activation & Adjustment** – Enables the fuser and allows adjustment of its strength (black level).
* **\[K4] Factory Reset & Re-engagement** – Restores factory settings and re-engages the fuser if needed.
***
**🔌 Port Guide:**
* **Output:** Connect to the primary display. (Only the fuser should connect to main monitor)
* **Input1:** Connect to the GPU of your main PC.
* **Input2:** Connect to the GPU of your secondary PC.
* **DC12V:** Power input.
***
### :check: You're Done
You now have a basic understanding of the 1K HDMI Fuser and how the cables are connected.
---
# 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.champcheats.com/dma-docs/1k-hdmi-fuser/fuser-overview.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.
