# Table of Contents
- [Hardware Setup (Main PC) | DMA](#hardware-setup-main-pc-dma)
- [Speed Test (2nd PC) | DMA](#speed-test-2nd-pc-dma)
- [DATA Driver Setup (2nd PC) | DMA](#data-driver-setup-2nd-pc-dma)
- [JTAG Driver Setup (2nd PC) | DMA](#jtag-driver-setup-2nd-pc-dma)
- [Troubleshooting | DMA](#troubleshooting-dma)
- [35t Firmware Flashing | DMA](#35t-firmware-flashing-dma)
- [DNA ID | DMA](#dna-id-dma)
- [Makcu Setup | DMA](#makcu-setup-dma)
- [Makcu Driver | DMA](#makcu-driver-dma)
- [Makcu Flashing | DMA](#makcu-flashing-dma)
- [1k Fuser Overview | DMA](#1k-fuser-overview-dma)
- [1k Fuser Setup | DMA](#1k-fuser-setup-dma)
- [EDID Spoofing | DMA](#edid-spoofing-dma)
- [Troubleshooting & Indicators | DMA](#troubleshooting-indicators-dma)
- [Cables & Controls | DMA](#cables-controls-dma)
- [Intro & Requirements | DMA](#intro-requirements-dma)
- [KM Box Net Setup | DMA](#km-box-net-setup-dma)
- [KM Box B+ Setup | DMA](#km-box-b-setup-dma)
- [Unknown](#unknown)
- [Unknown](#unknown)
- [Unknown](#unknown)
- [Unknown](#unknown)
- [Unknown](#unknown)
- [Unknown](#unknown)
- [Unknown](#unknown)
- [Unknown](#unknown)
- [Unknown](#unknown)
- [75t / 100t Firmware Flashing | DMA](#75t-100t-firmware-flashing-dma)
- [Unknown](#unknown)
- [Unknown](#unknown)
- [Unknown](#unknown)
- [Unknown](#unknown)
- [Unknown](#unknown)
- [Unknown](#unknown)
- [Unknown](#unknown)
- [Unknown](#unknown)
- [Unknown](#unknown)
- [Unknown](#unknown)
- [Unknown](#unknown)
---
# Hardware Setup (Main PC) | DMA
For the complete documentation index, see [llms.txt](https://ducks-services.gitbook.io/dma/llms.txt)
. This page is also available as [Markdown](https://ducks-services.gitbook.io/dma/dma-card/hardware-setup-main-pc.md)
.
### π 1. Power Down Your Game PC[](https://ducks-services.gitbook.io/dma#id-1.-power-down-your-game-pc)
* Completely shut down your **main PC (Game PC)** before inserting the DMA card.
* * *
### π§© 2. Insert the DMA Card[](https://ducks-services.gitbook.io/dma#id-2.-insert-the-dma-card)
* Plug your DMA card into **any available PCI-e slot** on your Game PC.

* * *
### π 3. Connect to 2nd PC[](https://ducks-services.gitbook.io/dma#id-3.-connect-to-2nd-pc)
* Use the included **USB data cable** to connect the **Data Port** on the DMA card to your **2nd PC** (second PC).

* * *
### βοΈ 4. Enter BIOS on Game PC[](https://ducks-services.gitbook.io/dma#id-4.-enter-bios-on-game-pc)
* Power on your Game PC and **enter BIOS/UEFI setup**:
* Usually done by pressing `DEL`, `F2`, or `ESC` during boot (varies by motherboard).
* * *
### π« 5. Disable Virtualization (Required)[](https://ducks-services.gitbook.io/dma#id-5.-disable-virtualization-required)
Virtualization interferes with DMA memory access and **must be disabled**.
#### Intel CPUs:[](https://ducks-services.gitbook.io/dma#intel-cpus)
* Disable:
* `VT-d`
* `Intel Virtualization Technology`
* `IOMMU` (if available)
#### AMD CPUs:[](https://ducks-services.gitbook.io/dma#amd-cpus)
* Disable:
* `SVM`
* `IOMMU`
* * *
### β οΈ 6. Optional (If Available)[](https://ducks-services.gitbook.io/dma#id-6.-optional-if-available)
* **Disable NX-Bit / Execute Disable Bit** _(Only if listed in your BIOS. If not, skip this step.)_
* **Set PCIe Slot to Gen1** _(Recommended for maximum compatibility. Found under_ `_Advanced > PCI Settings_` _or similar.)_
* * *
### π§± 7. Disable Memory Integrity in Windows[](https://ducks-services.gitbook.io/dma#id-7.-disable-memory-integrity-in-windows)
On your **Game PC**, do the following:
1. Open **Windows Security**
2. Navigate to: `Device Security > Core Isolation > Core Isolation Details`
3. **Turn off "Memory Integrity"**
> If this section wonβt load, the setting may already be disabled or unsupported β no action needed.
π [Reference β Microsoft Guide](https://support.microsoft.com/en-us/windows/options-to-optimize-gaming-performance-in-windows-11-a255f612-2949-4373-a566-ff6f3f474613)
* * *
### β
You're Done[](https://ducks-services.gitbook.io/dma#youre-done)
Your DMA card is now installed and your Game PC is properly configured.
> π₯οΈ **Next Step:** It is now **recommended to proceed with the second PC (2ndPC) setup** to complete the process. Refer to the [35t Driver Setup (2nd PC)](https://ducks-services.gitbook.io/dma/dma-card/data-driver-setup-2nd-pc)
> or [75t Driver Setup (2nd PC)](https://ducks-services.gitbook.io/dma/dma-card/jtag-driver-setup-2nd-pc)
> for instructions.
If you run into issues, double-check that virtualization is fully disabled and all hardware connections are secure.
* * *
[NextJTAG Driver Setup (2nd PC)](https://ducks-services.gitbook.io/dma/dma-card/jtag-driver-setup-2nd-pc)
Last updated 7 months ago
---
# Speed Test (2nd PC) | DMA
For the complete documentation index, see [llms.txt](https://ducks-services.gitbook.io/dma/llms.txt)
. This page is also available as [Markdown](https://ducks-services.gitbook.io/dma/dma-card/speed-test-2nd-pc.md)
.
### π **Steps:**[](https://ducks-services.gitbook.io/dma/dma-card/speed-test-2nd-pc#steps)
1. Ensure the cable is in the **DATA Port.**
2. **Download** the [DMA Speed Test tool](https://mega.nz/file/mzJxGQBB#tvKWMwKbYCKSrtcbbz0DY7WsaiSbt_XBfYyV1SIZMsI)
.
3. **Run the tool** on your **2nd PC**.
4. Select **Full Test** and wait for the results.
* * *
### π **Speed Test Ratings**[](https://ducks-services.gitbook.io/dma/dma-card/speed-test-2nd-pc#speed-test-ratings)
* **< 4000:** Low
* **4000+:** Warning
* **5200+:** Good
* **6500+:** Amazing
* **7500+:** Elite
* * *
### π **Throughput Test Ratings**[](https://ducks-services.gitbook.io/dma/dma-card/speed-test-2nd-pc#throughput-test-ratings)
* **< 125:** Low
* **125+:** Warning
* **150+:** Good
* **200+:** Amazing
* **220+:** Elite
* * *

### β **Important Note**[](https://ducks-services.gitbook.io/dma/dma-card/speed-test-2nd-pc#important-note)
If your results are below **Good** or you encounter errors, refer to the [**DMA Troubleshooting**](https://ducks-services.gitbook.io/dma/dma-card/troubleshooting)
section **before contacting support**.
* * *
> Once youβve confirmed that your **DMA card is functioning correctly**, the next step is to **flash your firmware**.
>
> * If you purchased firmware from us (**recommended**), we will need your **DNA ID** to build it.
>
> * Find your DNA ID here: [DNA ID Guide](https://ducks-services.gitbook.io/dma/dma-firmware/dna-id)
>
>
> * If you purchased firmware from another supplier or already have your firmware ready to flash:
>
> * View the **35T flashing steps** here: [35T Firmware Flashing](https://ducks-services.gitbook.io/dma/dma-firmware/35t-firmware-flashing)
>
> * View the **75T flashing steps** here: [75T Firmware Flashing](https://ducks-services.gitbook.io/dma/dma-firmware/75t-firmware-flashing)
>
>
* * *
[PreviousDATA Driver Setup (2nd PC)](https://ducks-services.gitbook.io/dma/dma-card/data-driver-setup-2nd-pc)
[NextTroubleshooting](https://ducks-services.gitbook.io/dma/dma-card/troubleshooting)
Last updated 11 months ago
---
# DATA Driver Setup (2nd PC) | DMA
For the complete documentation index, see [llms.txt](https://ducks-services.gitbook.io/dma/llms.txt)
. This page is also available as [Markdown](https://ducks-services.gitbook.io/dma/dma-card/data-driver-setup-2nd-pc.md)
.
### π **Check Your Current Driver Status**[](https://ducks-services.gitbook.io/dma/dma-card/data-driver-setup-2nd-pc#check-your-current-driver-status)
1. Open **Device Manager** (Windows key + type `Device Manager`)
2. Look for one of these scenarios:

#### β
**Correct Driver (No action needed)**[](https://ducks-services.gitbook.io/dma/dma-card/data-driver-setup-2nd-pc#correct-driver-no-action-needed)
* Device appears as: **FTDI FT601 USB 3.0 Bridge Device**
* Located under: **Universal Serial Bus devices**
* **Status**: Working properly β Skip this guide
#### β οΈ **Missing Driver (Install now)**[](https://ducks-services.gitbook.io/dma/dma-card/data-driver-setup-2nd-pc#missing-driver-install-now)
* Device appears as: **FTDI SuperSpeed-FIFO Bridge**
* Located under: **Other devices**
* **Status**: Yellow exclamation mark β Proceed below
#### β **Wrong Driver (Remove first)**[](https://ducks-services.gitbook.io/dma/dma-card/data-driver-setup-2nd-pc#wrong-driver-remove-first)
* Device appears as: **FTDI SuperSpeed-FIFO Bridge**
* Located under: **Universal Serial Bus devices**
* **Action**: Right-click β **Uninstall device** β Check 'Delete driver'
* Then proceed with installation below
### βοΈ **Driver Installation**[](https://ducks-services.gitbook.io/dma/dma-card/data-driver-setup-2nd-pc#driver-installation)
#### π₯ **Step 1: Download Driver**[](https://ducks-services.gitbook.io/dma/dma-card/data-driver-setup-2nd-pc#step-1-download-driver)
**Download Driver**
* [FTD3XX Driver v1.3.0.10](https://ftdichip.com/wp-content/uploads/2024/06/FTD3XXDriver_WHQLCertified_1.3.0.10_Installer.zip)
β **Click to download**
**Backup Driver (if above doesn't work):**
* [FTD3XX Driver v1.3.0.8](https://cdn.discordapp.com/attachments/1439679375938158793/1459633951600808038/FTD3XXDriver_WHQLCertified_1.3.0.8_Installer_2023.zip?ex=6979158c&is=6977c40c&hm=7fb9387b0063b43e9706f675980675b52f9b881fc035a2ed87ae66c8d5cd22dc&)
β **Click to download**
#### βοΈ **Step 2: Install Driver**[](https://ducks-services.gitbook.io/dma/dma-card/data-driver-setup-2nd-pc#step-2-install-driver)
1. **Extract** the downloaded `.zip` file
2. **Run** the `.exe` installer
3. Follow the installation wizard
4. Restart your computer if prompted
#### π **Step 3: Verify Installation**[](https://ducks-services.gitbook.io/dma/dma-card/data-driver-setup-2nd-pc#step-3-verify-installation)
1. Re-open **Device Manager**
2. Should now see: **FTDI FT601 USB 3.0 Bridge Device** under **Universal Serial Bus devices**
3. If issues persist, try the **backup driver**
> β
The driver should now install successfully. You're now ready to proceed with [DMA testing](https://ducks-services.gitbook.io/dma/dma-card/speed-test-2nd-pc)
> .
* * *
[PreviousJTAG Driver Setup (2nd PC)](https://ducks-services.gitbook.io/dma/dma-card/jtag-driver-setup-2nd-pc)
[NextSpeed Test (2nd PC)](https://ducks-services.gitbook.io/dma/dma-card/speed-test-2nd-pc)
Last updated 6 months ago
---
# JTAG Driver Setup (2nd PC) | DMA
For the complete documentation index, see [llms.txt](https://ducks-services.gitbook.io/dma/llms.txt)
. This page is also available as [Markdown](https://ducks-services.gitbook.io/dma/dma-card/jtag-driver-setup-2nd-pc.md)
.
### π₯ 1. Download the Driver[](https://ducks-services.gitbook.io/dma/dma-card/jtag-driver-setup-2nd-pc#id-1.-download-the-driver)
* Download the JTAG Driver [here](https://mega.nz/file/X3Rm1DwY#bnWOAkz0if0lJhP-L9kYmy2Rlr8fjw6_I2jU8j6nDP0)
.
* Save it to your desktop or an easy-to-find folder.
* * *
### βοΈ 2. Run the Installer[](https://ducks-services.gitbook.io/dma/dma-card/jtag-driver-setup-2nd-pc#id-2.-run-the-installer)
* Double-click the downloaded file.
* Click **Install** and wait for the process to complete.

* * *
### β
3. Finish Installation[](https://ducks-services.gitbook.io/dma/dma-card/jtag-driver-setup-2nd-pc#id-3.-finish-installation)
* Once installation is complete, click **OK** to close the installer.

> You're now ready to proceed with [DMA testing](https://ducks-services.gitbook.io/dma/dma-card/speed-test-2nd-pc)
> .
* * *
[PreviousHardware Setup (Main PC)](https://ducks-services.gitbook.io/dma)
[NextDATA Driver Setup (2nd PC)](https://ducks-services.gitbook.io/dma/dma-card/data-driver-setup-2nd-pc)
Last updated 6 months ago
---
# Troubleshooting | DMA
For the complete documentation index, see [llms.txt](https://ducks-services.gitbook.io/dma/llms.txt)
. This page is also available as [Markdown](https://ducks-services.gitbook.io/dma/dma-card/troubleshooting.md)
.
### β `[FAIL] VMM INIT FAILED.`[](https://ducks-services.gitbook.io/dma/dma-card/troubleshooting#fail-vmm-init-failed)
**Cause:** Your DMA card or connection is "hung," often due to a fast reboot or system waking from sleep.
**Fix:**
* Fully shut down your **Game PC** (do **not** reboot).
* Wait **5β10 seconds**, then power it back on (a **cold boot**).
* This resolves the issue **99% of the time**.
* * *
### β `FPGA: ERROR: Unable to connect to USB/FT601 device [0,v0.0,0000]`[](https://ducks-services.gitbook.io/dma/dma-card/troubleshooting#fpga-error-unable-to-connect-to-usb-ft601-device-0-v0.0-0000)
**Cause:** FTDI driver not installed or incorrect port used.
**Fix:**
* Make sure the [**FTDI driver**](https://ducks-services.gitbook.io/dma/dma-card/data-driver-setup-2nd-pc)
is installed on your **Radar PC**.
* Confirm you are using the **Data Port** on the DMA card (not the power-only port).
* * *
### β `Failed to retrieve Physical Memory Map!`[](https://ducks-services.gitbook.io/dma/dma-card/troubleshooting#failed-to-retrieve-physical-memory-map)
**Cause:** Unstable or faulty USB connection.
**Fix:**
* Reseat your USB cable on both ends.
* Try a different **USB 3.0 cable** and **USB port**.
* As a last resort, re-install Windows on your **Game PC**.
* * *
### β `[SYMBOL] Offline symbols unavailable - file 'info.db' not found.`[](https://ducks-services.gitbook.io/dma/dma-card/troubleshooting#symbol-offline-symbols-unavailable-file-info.db-not-found)
**Cause:** PCILeech cannot retrieve symbol data for memory interpretation.
**Fix:**
* Ensure the tool was **unzipped completely**.
* Check that both `symsrv.dll` and `dbghelp.dll` are in the same folder.
* Verify you have **active internet** and no firewalls are blocking access.
* Still stuck? β€ [Download latest `info.db` manually](https://github.com/ufrisk/MemProcFS/releases)
and place it in your tool folder.
* * *
### β οΈ `FPGA: TINY PCIe TLP Algorithm auto-selected!`[](https://ducks-services.gitbook.io/dma/dma-card/troubleshooting#fpga-tiny-pcie-tlp-algorithm-auto-selected)
**Cause:** DMA card running at lower speeds due to poor USB connection or firmware.
**Fix:**
* Check USB cable is **firmly connected** on both ends.
* Try a **different USB port**.
* In some cases, outdated or restricted firmware may reduce speed.
* * *
### β `[CORE] Initialization Failed. Unable to locate valid DTB / auto-identify OS`[](https://ducks-services.gitbook.io/dma/dma-card/troubleshooting#core-initialization-failed.-unable-to-locate-valid-dtb-auto-identify-os)
**Cause:** Incorrect BIOS settings or unstable USB link.
**Fix:**
* Review and apply **all required BIOS changes** on your **Game PC**.
* Double-check USB cable stability and port selection.
* As a last resort, re-install Windows on the **Game PC**.
* * *
### β `DMA Test Tool β Test Result: FAIL / General Failures`[](https://ducks-services.gitbook.io/dma/dma-card/troubleshooting#dma-test-tool-test-result-fail-general-failures)
**Cause:** Speed or throughput below operational threshold.
#### π Common Triggers:[](https://ducks-services.gitbook.io/dma/dma-card/troubleshooting#common-triggers)
* **Speed under 4000 Mem/sec**
* **Throughput under 125 MB/s**
#### π Fixes:[](https://ducks-services.gitbook.io/dma/dma-card/troubleshooting#fixes)
1. Use a **USB 3.0 data-rated** cable (not charging-only).
2. Make sure cable is seated **securely**.
3. Switch to **High Performance** power plan on Radar PC.
4. Try different USB ports and cables.
5. **Reseat** the DMA card in its PCIe slot.
6. Ensure **bracket isn't interfering** with USB connection.
7. Check that your **Radar PC meets system requirements**.
8. Some firmware (e.g., Vanguard/Faceit bypass) may cause reduced speed.
> π§ͺ **Recommendation:** Run the DMA speed test for **~360 seconds** to check for connection stability (dropouts). If stable, slightly low speeds may still work fine.
* * *
### β DMA Software: Not Loading / Entities Missing / Glitchy Behavior[](https://ducks-services.gitbook.io/dma/dma-card/troubleshooting#dma-software-not-loading-entities-missing-glitchy-behavior)
**Cause:** **Paged Out Memory** β the target process's memory is moved to the page file due to high memory pressure.
#### β οΈ Why This Matters:[](https://ducks-services.gitbook.io/dma/dma-card/troubleshooting#why-this-matters)
* DMA cannot read from the Windows page file, leading to undefined behavior in cheat/radar software.
#### π§ Fix:[](https://ducks-services.gitbook.io/dma/dma-card/troubleshooting#fix)
* **Install more RAM** in your **Game PC**.
* (Optional) Disable the **System Page File** in Windows _(Not Recommended: May cause system instability or BSOD if memory is exhausted)._
* * *
### π© Still Stuck?[](https://ducks-services.gitbook.io/dma/dma-card/troubleshooting#still-stuck)
If none of the above solutions work, please [**open a support ticket**](https://ducks-services.com/discord)
with:
* A description of your issue
* A screenshot or full error log
* Your DMA card model and current setup details
Weβre here to help.
* * *
[PreviousSpeed Test (2nd PC)](https://ducks-services.gitbook.io/dma/dma-card/speed-test-2nd-pc)
[NextDNA ID](https://ducks-services.gitbook.io/dma/dma-firmware/dna-id)
Last updated 1 year ago
---
# 35t Firmware Flashing | DMA
For the complete documentation index, see [llms.txt](https://ducks-services.gitbook.io/dma/llms.txt)
. This page is also available as [Markdown](https://ducks-services.gitbook.io/dma/dma-firmware/35t-firmware-flashing.md)
.
35t Firmware Flashing Video[](https://ducks-services.gitbook.io/dma/dma-firmware/35t-firmware-flashing#id-35t-firmware-flashing-video)
---------------------------------------------------------------------------------------------------------------------------------------
[https://ducks-services.com/uploads/pages\_media/35tflash.MP4ducks-services.com](https://ducks-services.com/uploads/pages_media/35tflash.MP4)
### π 1. Connect to JTAG Port[](https://ducks-services.gitbook.io/dma/dma-firmware/35t-firmware-flashing#id-1.-connect-to-jtag-port)
* Plug the **USB cable** into the **JTAG port** on your DMA card.
* * *
### π¦ 2. Install JTAG Driver[](https://ducks-services.gitbook.io/dma/dma-firmware/35t-firmware-flashing#id-2.-install-jtag-driver)
Make sure the [**JTAG Driver**](https://ducks-services.gitbook.io/dma/~/revisions/JpVzONbaEFULHqa0sxde/dma-card/jtag-driver-setup-2nd-pc)
is installed on your second PC.
* * *
### π οΈ 3. Open Flashing Tool[](https://ducks-services.gitbook.io/dma/dma-firmware/35t-firmware-flashing#id-3.-open-flashing-tool)
* Download and launch the [**Flashing Tool**](https://www.ducks-services.com/applications/core/interface/file/attachment.php?id=1688&key=ac395c1379f7e6734b504229c7cccccb)
.
* Click the **blank button** and select your firmware file.

* * *
### βΆοΈ 4. Start Flashing Process[](https://ducks-services.gitbook.io/dma/dma-firmware/35t-firmware-flashing#id-4.-start-flashing-process)
* Press **Start** to begin flashing.
* The process should take about **1 minute** to complete.

* * *
### β
5. Confirm Completion[](https://ducks-services.gitbook.io/dma/dma-firmware/35t-firmware-flashing#id-5.-confirm-completion)
* Once you see the **"Update Complete"** prompt, the flash was successful.
* Restart the DMA device.
* * *
### π 6. Reconnect for Data[](https://ducks-services.gitbook.io/dma/dma-firmware/35t-firmware-flashing#id-6.-reconnect-for-data)
* Switch the USB cable from the **JTAG port** to the **DATA port** on the DMA card.
* * *
### π 7. Run a Speed Test[](https://ducks-services.gitbook.io/dma/dma-firmware/35t-firmware-flashing#id-7.-run-a-speed-test)
* Perform a [**Speed Test**](https://ducks-services.gitbook.io/dma/dma-card/testing-2nd-pc)
to ensure the card is functioning correctly.
* * *
[PreviousDNA ID](https://ducks-services.gitbook.io/dma/dma-firmware/dna-id)
[Next75t / 100t Firmware Flashing](https://ducks-services.gitbook.io/dma/dma-firmware/75t-100t-firmware-flashing)
Last updated 6 months ago
---
# DNA ID | DMA
For the complete documentation index, see [llms.txt](https://ducks-services.gitbook.io/dma/llms.txt)
. This page is also available as [Markdown](https://ducks-services.gitbook.io/dma/dma-firmware/dna-id.md)
.
### π₯ 1. Download the DNA ID Tool[](https://ducks-services.gitbook.io/dma/dma-firmware/dna-id#id-1.-download-the-dna-id-tool)
Download the DNA ID tool from the link below:
> π [Download DNA ID Tool](https://mega.nz/file/u65DGLBD#RuutSPcUPxvF_ixb8U0CMc97Ov-HrKvE2p9JruM-mZc)
* * *
### π§· 2. Connect Your DMA Card via JTAG[](https://ducks-services.gitbook.io/dma/dma-firmware/dna-id#id-2.-connect-your-dma-card-via-jtag)
* Plug your **DMA card** into your PC.
* Connect to the **JTAG port** on the card using the included USB cable.
* Do **not** connect through the data port β use only the **JTAG port** for this step.
* * *
### π§° 3. Install JTAG Drivers[](https://ducks-services.gitbook.io/dma/dma-firmware/dna-id#id-3.-install-jtag-drivers)
* Once the files are downloaded, run and install the included drivers.
* * *
### βΆοΈ 4. Run the Tool[](https://ducks-services.gitbook.io/dma/dma-firmware/dna-id#id-4.-run-the-tool)
* Locate the `.bat` file inside the downloaded folder that corresponds to your **specific DMA card model** (e.g., 35t, 75t, 100t, etc.).
* Right-click the `.bat` file and select **Run as Administrator**.
* Wait a few seconds for the script to complete.
* * *
### π 5. Find the DNA Line[](https://ducks-services.gitbook.io/dma/dma-firmware/dna-id#id-5.-find-the-dna-line)
Once the tool runs successfully, it will output a line like this:
Copy
DNA = XXXXX (XXXXXXXXXXXXXX)
* * *
### π€ 6. Send Us Your DNA[](https://ducks-services.gitbook.io/dma/dma-firmware/dna-id#id-6.-send-us-your-dna)
* Copy the **entire DNA line** and send it along with your firmware order # in a DMA ticket.
* Example:
Copy
DNA = 1144 (00FABB98F2318E7D)
This value is required to generate your **DNA-locked firmware**. If anything looks off or you get an error, reach out to support with a screenshot.
* * *
[PreviousTroubleshooting](https://ducks-services.gitbook.io/dma/dma-card/troubleshooting)
[Next35t Firmware Flashing](https://ducks-services.gitbook.io/dma/dma-firmware/35t-firmware-flashing)
Last updated 6 months ago
---
# Makcu Setup | DMA
For the complete documentation index, see [llms.txt](https://ducks-services.gitbook.io/dma/llms.txt)
. This page is also available as [Markdown](https://ducks-services.gitbook.io/dma/makcu/makcu-setup.md)
.

* Connect the **LEFT cable** (Main PC) to your **main PC**.
* Connect the **MIDDLE cable** to your **secondary PC**.
* Connect the **RIGHT cable** to your **mouse**.
Next, head to the [Makcu Driver](https://ducks-services.gitbook.io/dma/makcu/makcu-driver)
guide.
[Previous75t / 100t Firmware Flashing](https://ducks-services.gitbook.io/dma/dma-firmware/75t-100t-firmware-flashing)
[NextMakcu Driver](https://ducks-services.gitbook.io/dma/makcu/makcu-driver)
Last updated 7 months ago
---
# Makcu Driver | DMA
For the complete documentation index, see [llms.txt](https://ducks-services.gitbook.io/dma/llms.txt)
. This page is also available as [Markdown](https://ducks-services.gitbook.io/dma/makcu/makcu-driver.md)
.
Driver Installation & COM Port Setup[](https://ducks-services.gitbook.io/dma/makcu/makcu-driver#driver-installation-and-com-port-setup)
----------------------------------------------------------------------------------------------------------------------------------------
### π₯ 1. Install the Driver[](https://ducks-services.gitbook.io/dma/makcu/makcu-driver#id-1.-install-the-driver)
* [**Download the driver here**](https://mega.nz/file/WjYlmbCZ#UIRcAeeGYsbyL89e_KkAFvG2Km5T3BZL_PVU58XayUU)
.
* Extract the contents to a folder.
* Right-click the `.inf` file and select **Install**. 
* * *
### βοΈ 2. Configure COM Port (Second PC)[](https://ducks-services.gitbook.io/dma/makcu/makcu-driver#id-2.-configure-com-port-second-pc)
1. On your second PC, open **Device Manager**.
2. Expand the **Ports (COM & LPT)** section.

3. Right-click your COM device and select **Properties**.
4. Go to the **Port Settings** tab and click **Advanced**.

5. Set the COM port number to **any value lower than 10**.
6. Click **OK** to save changes.

* * *
### π 3. Restart Makcu for Changes to Apply[](https://ducks-services.gitbook.io/dma/makcu/makcu-driver#id-3.-restart-makcu-for-changes-to-apply)
* If the **Makcu AIO Tool** is open, close it.
* Unplug and replug the **left-most cable** on the Makcu to restart it.
> β
After completing these steps, your device is ready for the flashing process.
* * *
[PreviousMakcu Setup](https://ducks-services.gitbook.io/dma/makcu/makcu-setup)
[NextMakcu Flashing](https://ducks-services.gitbook.io/dma/makcu/makcu-flashing)
Last updated 7 months ago
---
# Makcu Flashing | DMA
For the complete documentation index, see [llms.txt](https://ducks-services.gitbook.io/dma/llms.txt)
. This page is also available as [Markdown](https://ducks-services.gitbook.io/dma/makcu/makcu-flashing.md)
.
Pre-Setup[](https://ducks-services.gitbook.io/dma/makcu/makcu-flashing#pre-setup)
----------------------------------------------------------------------------------
### 1\. π» Run from Your 2nd PC[](https://ducks-services.gitbook.io/dma/makcu/makcu-flashing#id-1.-run-from-your-2nd-pc)
* To avoid leaving **temporary files** on your main PC, run the **AIO Tool** from your **second PC**.
* The tool unpacks files into a local temp folder during use.
### 2\. π₯ Download the AIO Tool[](https://ducks-services.gitbook.io/dma/makcu/makcu-flashing#id-2.-download-the-aio-tool)
* Get the tool from [**this link**](https://github.com/terrafirma2021/MAKCM_v2_files)
.
### 3\. π Open the AIO Tool[](https://ducks-services.gitbook.io/dma/makcu/makcu-flashing#id-3.-open-the-aio-tool)
* Launch the AIO Tool and allow it to **update automatically**.
### 4\. π Required Hardware[](https://ducks-services.gitbook.io/dma/makcu/makcu-flashing#id-4.-required-hardware)
* Youβll need **one USB cable** to flash the PCB.
* This master cable will be connected to the **second PC** during the process.
* * *
Flashing Video Guide[](https://ducks-services.gitbook.io/dma/makcu/makcu-flashing#flashing-video-guide)
--------------------------------------------------------------------------------------------------------
[https://ducks-services.com/uploads/pages\_media/334709823\_MakcuGuide.MP4ducks-services.com](https://ducks-services.com/uploads/pages_media/334709823_MakcuGuide.MP4)
* * *
Flashing Steps[](https://ducks-services.gitbook.io/dma/makcu/makcu-flashing#flashing-steps)
--------------------------------------------------------------------------------------------
### π οΈ 1. Open the MAKCU[](https://ducks-services.gitbook.io/dma/makcu/makcu-flashing#id-1.-open-the-makcu)
* Remove the top cover by **pulling it directly off**.

### β¬
οΈ 2. Flash the Left Side[](https://ducks-services.gitbook.io/dma/makcu/makcu-flashing#id-2.-flash-the-left-side)
1. Hold the **LEFT button**.
2. Plug the USB cable into the **LEFT USB port**.
3. The tool should display: **"MCU connected in flash mode"**.

4. In the AIO Tool, click **Flash Left**.

5. Wait for the process to complete.
6. Unplug the USB cable from the **left port**.
### β‘οΈ3. Flash the Right Side[](https://ducks-services.gitbook.io/dma/makcu/makcu-flashing#id-3.-flash-the-right-side)
1. Hold the **RIGHT button**.
2. Plug the USB cable into the **RIGHT USB port**.
3. In the AIO Tool, click **Flash Right**.

4. Wait for the flash to finish.
* * *
[PreviousMakcu Driver](https://ducks-services.gitbook.io/dma/makcu/makcu-driver)
[Next1k Fuser Overview](https://ducks-services.gitbook.io/dma/1k-hdmi-fuser/1k-fuser-overview)
Last updated 6 months ago
---
# 1k Fuser Overview | DMA
For the complete documentation index, see [llms.txt](https://ducks-services.gitbook.io/dma/llms.txt)
. This page is also available as [Markdown](https://ducks-services.gitbook.io/dma/1k-hdmi-fuser/1k-fuser-overview.md)
.

### π‘ **Indicator Lights:**[](https://ducks-services.gitbook.io/dma/1k-hdmi-fuser/1k-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:**[](https://ducks-services.gitbook.io/dma/1k-hdmi-fuser/1k-fuser-overview#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:**[](https://ducks-services.gitbook.io/dma/1k-hdmi-fuser/1k-fuser-overview#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.
* * *
[PreviousMakcu Flashing](https://ducks-services.gitbook.io/dma/makcu/makcu-flashing)
[Next1k Fuser Setup](https://ducks-services.gitbook.io/dma/1k-hdmi-fuser/1k-fuser-setup)
Last updated 7 months ago
---
# 1k Fuser Setup | DMA
For the complete documentation index, see [llms.txt](https://ducks-services.gitbook.io/dma/llms.txt)
. This page is also available as [Markdown](https://ducks-services.gitbook.io/dma/1k-hdmi-fuser/1k-fuser-setup.md)
.
### π₯οΈ 1. Initial Setup[](https://ducks-services.gitbook.io/dma/1k-hdmi-fuser/1k-fuser-setup#id-1.-initial-setup)
* Disconnect all displays except for the **main monitor**.
* Connect the main monitor to the **Fuser** (not directly to the GPU).
* Ensure all HDMI cables connected to the Fuser are **HDMI 2.0**.
* * *
### βοΈ 2. Configure Display Settings[](https://ducks-services.gitbook.io/dma/1k-hdmi-fuser/1k-fuser-setup#id-2.-configure-display-settings)
**On Both PCs:**
* Right-click on an empty area of the desktop.
* Select **Display Settings**.
* Scroll down to the **Multiple displays** section and select **Extend these displays**.
**On the 2nd PC:**
* Go to **Start > Settings > Personalization > Background/Wallpaper**.
* Under **Personalize your background**, select **Solid Color** and choose **Black**.

* * *
### π 3. Reconnect Cables to the Fuser[](https://ducks-services.gitbook.io/dma/1k-hdmi-fuser/1k-fuser-setup#id-3.-reconnect-cables-to-the-fuser)
* Ensure **all three HDMI 2.0 cables** are connected to the Fuser.
* Make sure the monitor is **no longer directly connected** to the GPU.
* * *
### π οΈ Troubleshooting[](https://ducks-services.gitbook.io/dma/1k-hdmi-fuser/1k-fuser-setup#troubleshooting)
**π±οΈ Desktop Apps Are Merged / Two Search Bars Visible**
* Press **K2** (Main Screen Mode) when no overlay is active.
**πΊ Second Monitor Shows "No Signal"**
* Ensure the 2nd monitor is turned **on**.
* The 2nd monitor should be connected to its **respective PC**, not the Fuser.
**β‘ Refresh Rate Issues (Limited to 60Hz or 90Hz)**
* This indicates **not all HDMI cables are HDMI 2.0**.
* Use **three HDMI 2.0 cables** for the Fuser setup.
* * *
### π Important Notes[](https://ducks-services.gitbook.io/dma/1k-hdmi-fuser/1k-fuser-setup#important-notes)
* The Fuser requires 3 HDMI 2.0 cables for full functionality.
* Once set up correctly, switching modes (K1/K2/K3) will allow seamless integration between both PCs.
* * *
[Previous1k Fuser Overview](https://ducks-services.gitbook.io/dma/1k-hdmi-fuser/1k-fuser-overview)
[NextEDID Spoofing](https://ducks-services.gitbook.io/dma/1k-hdmi-fuser/edid-spoofing)
Last updated 7 months ago
---
# EDID Spoofing | DMA
For the complete documentation index, see [llms.txt](https://ducks-services.gitbook.io/dma/llms.txt)
. This page is also available as [Markdown](https://ducks-services.gitbook.io/dma/1k-hdmi-fuser/edid-spoofing.md)
.
### π 1. Obtain the EDID of the Main Monitor[](https://ducks-services.gitbook.io/dma/1k-hdmi-fuser/edid-spoofing#id-1.-obtain-the-edid-of-the-main-monitor)
**1\. Install MonitorAssetManager**
* Download and install [**MonitorAssetManager**](https://www.ducks-services.com/applications/core/interface/file/attachment.php?id=1687&key=886ad4dcd057dab466bee6834dd668de)
(`mi_setup.exe`).
* After installation, run `MonInfo.exe`.
**2\. Save the EDID File**
* In `MonInfo.exe`, select your **main monitor** (usually the first one listed).
* Go to **File > Save as...**
* Save the file as an **EDID** `**.bin**` **file** in a location youβll remember.
* * *
### π 2. Inject the EDID into the HDMI Synthesizer[](https://ducks-services.gitbook.io/dma/1k-hdmi-fuser/edid-spoofing#id-2.-inject-the-edid-into-the-hdmi-synthesizer)
**1\. Connect the Synthesizer Device**
* Connect one end of a **Type-C cable** to the HDMI synthesizerβs **Type-C port**.
* Connect the other end to your **PCβs USB port** (where the `.bin` file is saved).
* Plug the synthesizer into a **power source** and turn it on.
**2\. Open the Injection Tool**
* Download and launch the [**EDID Injection Tool**](https://www.ducks-services.com/applications/core/interface/file/attachment.php?id=1686&key=811e997101c8e105338b977d25392982)
.
* _Note:_ If your system lacks Chinese language support, some text may appear as `???` β this will not affect functionality.

**3\. Perform the Injection**
* In the tool, select the **serial port number** (check in **Device Manager** if unsure).
* Choose the **injection location** that matches your monitorβs resolution.
* Select the **"Load Parameter File"** injection method.
* Open the previously saved **EDID** `**.bin**` **file**.
* Click **Inject Parameters** and wait for completion.
* The screen may briefly go black during the process.
* A success prompt will appear when finished.
**4\. Finalize the Connection**
* Disconnect the **Type-C cable**.
* Connect your PC to the monitor using a **HDMI cable**.
* * *
### π₯οΈ 3. Set Up the Monitor[](https://ducks-services.gitbook.io/dma/1k-hdmi-fuser/edid-spoofing#id-3.-set-up-the-monitor)
**1\. Adjust Display Settings**
* Right-click on the desktop and select **Display Settings**.
* Verify the **resolution** is correct.
* Scroll to **Advanced Display Settings**.
* Select the injected monitor model.
* Set the **refresh rate** to the optimal value for your monitor.
* * *
[Previous1k Fuser Setup](https://ducks-services.gitbook.io/dma/1k-hdmi-fuser/1k-fuser-setup)
[NextIntro & Requirements](https://ducks-services.gitbook.io/dma/4k-dc500-fuser/intro-and-requirements)
Last updated 7 months ago
---
# Troubleshooting & Indicators | DMA
For the complete documentation index, see [llms.txt](https://ducks-services.gitbook.io/dma/llms.txt)
. This page is also available as [Markdown](https://ducks-services.gitbook.io/dma/4k-dc500-fuser/troubleshooting-and-indicators.md)
.
#### Indicator Lights (Front Panel)[](https://ducks-services.gitbook.io/dma/4k-dc500-fuser/troubleshooting-and-indicators#indicator-lights-front-panel)
* **DC** β Monitor detected
* **RX0** β Host PC detected
* **RX1** β Secondary PC detected
* **RH** β Overlay enabled
If a light is **off**, that signal is not detected DC500 User Manual
* * *
#### On-Screen Info (Press K1)[](https://ducks-services.gitbook.io/dma/4k-dc500-fuser/troubleshooting-and-indicators#on-screen-info-press-k1)
Shows:
* MAIN: Host resolution & Hz
* SECOND: Secondary resolution & Hz
* ALPHA: Overlay strength
* BD: Firmware date
* UID: Device ID
* EDID: Mode A or B
* SEC: Activation status
* * *
#### EDID Modes (Critical)[](https://ducks-services.gitbook.io/dma/4k-dc500-fuser/troubleshooting-and-indicators#edid-modes-critical)
* **Mode A (Default)** β Universal compatibility
* **Mode B** β Native display compatibility
If you get **no image**, switch to **Mode B** (Long-press K1 for 5 seconds β auto reboot)
* * *
#### Common Fixes (90% of Issues)[](https://ducks-services.gitbook.io/dma/4k-dc500-fuser/troubleshooting-and-indicators#common-fixes-90-of-issues)
**No Image but All Lights On**
1. Long-press **K3** (factory reset)
2. Power off everything β reconnect cables
3. Reset monitor to factory defaults
4. Switch EDID Mode (K1 long press)
**Black Screen When Launching Games**
* Disable **G-SYNC**
* Match in-game resolution to desktop
* Reset GPU control panel settings
**Repeating / Tiled Screen**
* Set **same resolution on both PCs**
* Switch EDID Mode
* Factory reset (K3)
**Artifacts / Image Shift**
* Factory reset (K3)
* Reboot fuser
* * *
### Final Notes[](https://ducks-services.gitbook.io/dma/4k-dc500-fuser/troubleshooting-and-indicators#final-notes)
* Always use **certified HDMI 2.1 FRL 48 Gbps or DP 1.4+ cables**
* Plug cables into the **GPU**, not motherboard ports
* When in doubt: **K3 long-press reset**
[PreviousCables & Controls](https://ducks-services.gitbook.io/dma/4k-dc500-fuser/cables-and-controls)
[NextKM Box Net Setup](https://ducks-services.gitbook.io/dma/km-box/km-box-net-setup)
Last updated 6 months ago
---
# Cables & Controls | DMA
For the complete documentation index, see [llms.txt](https://ducks-services.gitbook.io/dma/llms.txt)
. This page is also available as [Markdown](https://ducks-services.gitbook.io/dma/4k-dc500-fuser/cables-and-controls.md)
.
#### Correct Cable Layout (Most Common Mistake)[](https://ducks-services.gitbook.io/dma/4k-dc500-fuser/cables-and-controls#correct-cable-layout-most-common-mistake)
**HDMI Setup**
* **Main PC GPU β HDMI RX0**
* **Secondary PC GPU β HDMI RX1**
* **Monitor β HDMI TX**
**DisplayPort Setup**
* **Main PC GPU β DP RX0**
* **Secondary PC GPU β DP RX1**
* **Monitor β DP TX**
> RX0 and RX1 can be swapped by holding **K4** for 3β5 seconds DC500 User Manual
* * *
#### Power & Ports[](https://ducks-services.gitbook.io/dma/4k-dc500-fuser/cables-and-controls#power-and-ports)
* **DC12V** β Main power
* **12V 3A (optional)** β Backup power
* **USB-C** β Debug / firmware updates (if needed)
* * *
#### Button Functions (Front Panel)[](https://ducks-services.gitbook.io/dma/4k-dc500-fuser/cables-and-controls#button-functions-front-panel)
**K1 β Info**
* Short press: Show resolution, refresh rate, alpha value
* Long press (5s): Switch EDID Mode (A β B)
**K2 β Increase Overlay Strength**
* Raises chroma-key (alpha) value
**K3 β Decrease / Reset**
* Short press: Lower alpha
* Long press (5s): **Factory reset** (fixes most issues)
**K4 β Layer Control**
* Short press: Enable / disable secondary overlay
* Long press (3β5s): Swap upper & lower layers
[PreviousIntro & Requirements](https://ducks-services.gitbook.io/dma/4k-dc500-fuser/intro-and-requirements)
[NextTroubleshooting & Indicators](https://ducks-services.gitbook.io/dma/4k-dc500-fuser/troubleshooting-and-indicators)
Last updated 6 months ago
---
# Intro & Requirements | DMA
For the complete documentation index, see [llms.txt](https://ducks-services.gitbook.io/dma/llms.txt)
. This page is also available as [Markdown](https://ducks-services.gitbook.io/dma/4k-dc500-fuser/intro-and-requirements.md)
.
#### What the DC500 Does[](https://ducks-services.gitbook.io/dma/4k-dc500-fuser/intro-and-requirements#what-the-dc500-does)
The DC500 is a **hardware video fuser** that combines:
* A **Host (gaming) PC**
* A **Secondary PC** into **one single display output** without software capture or latency.
It supports **extremely high refresh rates** at 1080p, 1440p, and 4K depending on interface and GPU.
* * *
#### Supported Interfaces[](https://ducks-services.gitbook.io/dma/4k-dc500-fuser/intro-and-requirements#supported-interfaces)
β οΈ **You must use only ONE interface type at a time**
* **HDMI 2.1 (FRL 48 Gbps)**
* **DisplayPort 1.4 / 2.1**
β HDMI + DP mixing is **not supported**
* * *
#### Resolution & Refresh Rate Support[](https://ducks-services.gitbook.io/dma/4k-dc500-fuser/intro-and-requirements#resolution-and-refresh-rate-support)
**HDMI 2.1**
* 1080p: up to **480β540Hz**
* 1440p: up to **320β355Hz**
* 4K: up to **144β158Hz**
**DisplayPort 1.4**
* 1080p: up to **480Hz**
* 1440p: up to **320Hz**
* 4K: up to **144Hz**
> Actual limits depend on GPU generation and DSC behavior DC500 User Manual
* * *
#### Minimum Hardware Requirements[](https://ducks-services.gitbook.io/dma/4k-dc500-fuser/intro-and-requirements#minimum-hardware-requirements)
**Host & Secondary PC GPUs**
* HDMI: NVIDIA RTX 3060 / AMD RX 6500 XT or better
* DP: NVIDIA GTX 10-series / AMD RX 500-series or newer
**Secondary PC CPU**
* Minimum **6 threads**
**Monitor**
* HDMI 2.1 FRL 48 Gbps **or**
* DP 1.4 / DP 2.1 input
[PreviousEDID Spoofing](https://ducks-services.gitbook.io/dma/1k-hdmi-fuser/edid-spoofing)
[NextCables & Controls](https://ducks-services.gitbook.io/dma/4k-dc500-fuser/cables-and-controls)
Last updated 6 months ago
---
# KM Box Net Setup | DMA
For the complete documentation index, see [llms.txt](https://ducks-services.gitbook.io/dma/llms.txt)
. This page is also available as [Markdown](https://ducks-services.gitbook.io/dma/km-box/km-box-net-setup.md)
.
### KM Box Connection & Network Setup[](https://ducks-services.gitbook.io/dma/km-box/km-box-net-setup#km-box-connection-and-network-setup)
### π 1. Connect the KM Box[](https://ducks-services.gitbook.io/dma/km-box/km-box-net-setup#id-1.-connect-the-km-box)
* **Port #1** β Connect to your **second PC** using the included USB cable.
* **Port #2** β Connect to your **main PC** using the included USB cable.
* **Port #3 or #4** β Connect your **keyboard or mouse** (either port works).

* * *
### βοΈ 2. Configure Network Settings[](https://ducks-services.gitbook.io/dma/km-box/km-box-net-setup#id-2.-configure-network-settings)
1. Open **Control Panel** and go to **Network and Internet**.

2. Click **Network and Sharing Center**.

3. Click **Change adapter settings**.

4. Locate the **KM Box network adapter**.
* If itβs not showing, unplug and replug the KM Box.

5. Right-click the adapter and select **Properties**.
6. Select **Internet Protocol Version 4 (TCP/IPv4)** and make sure itβs **enabled**.

7. Click **Properties**.

* * *
### π 3. Assign a Static IP Address[](https://ducks-services.gitbook.io/dma/km-box/km-box-net-setup#id-3.-assign-a-static-ip-address)
* Select **Use the following IP address** and enter:

* **IP Address:** `192.168.2.100`
* **Subnet Mask:** `255.255.255.0`

* * *
### πΎ 4. Save & Finish[](https://ducks-services.gitbook.io/dma/km-box/km-box-net-setup#id-4.-save-and-finish)
* Close all dialog boxes.
* Your KM Box is now ready to use.
* * *
[PreviousTroubleshooting & Indicators](https://ducks-services.gitbook.io/dma/4k-dc500-fuser/troubleshooting-and-indicators)
[NextKM Box B+ Setup](https://ducks-services.gitbook.io/dma/km-box/km-box-b+-setup)
Last updated 12 months ago
---
# KM Box B+ Setup | DMA
For the complete documentation index, see [llms.txt](https://ducks-services.gitbook.io/dma/llms.txt)
. This page is also available as [Markdown](https://ducks-services.gitbook.io/dma/km-box/km-box-b+-setup.md)
.
KM Box Mouse Emulation Setup[](https://ducks-services.gitbook.io/dma/km-box/km-box-b+-setup#km-box-mouse-emulation-setup)
--------------------------------------------------------------------------------------------------------------------------
### 1\. π Connect the KM Box[](https://ducks-services.gitbook.io/dma/km-box/km-box-b+-setup#id-1.-connect-the-km-box)
* **Port #1** β Connect to your **second PC** using the included USB cable.
* **Port #2** β Connect to your **main PC** using the included USB cable.
* **Port #3 or #4** β Connect your **keyboard or mouse** (either port works).

* * *
### 2\. π Find a Mouse to Emulate[](https://ducks-services.gitbook.io/dma/km-box/km-box-b+-setup#id-2.-find-a-mouse-to-emulate)
1. Go to [**http://www.linux-usb.org/usb.ids**](http://www.linux-usb.org/usb.ids)
.
2. Browse the list to find the mouse you want your KM Box to mimic.
3. Note down its **Product ID (PID)** and **Vendor ID (VID)** for later use.
* * *
### 3\. π» Prepare the KM Box Script[](https://ducks-services.gitbook.io/dma/km-box/km-box-b+-setup#id-3.-prepare-the-km-box-script)
1. Connect your **KM Box** to your **second PC**.
2. Download and run [`**upycraft.exe**`](https://randomnerdtutorials.com/install-upycraft-ide-windows-pc-instructions/)
.
* If a **"Font"** message appears, ignore it and proceed by clicking **Board** or **Serial** under the **Tools** menu.
3. In the script:
* Locate the **dynamic PID and VID** command lines and `device.enable(1)`.
* Remove the `#` from the start of these three lines.
* _(See Picture #1 for before, and Picture #2 for after)_.
* #1

* #2

* * *
### 4\. βοΈ Set Static PID & VID[](https://ducks-services.gitbook.io/dma/km-box/km-box-b+-setup#id-4.-set-static-pid-and-vid)
1. Locate the static PID and VID values `(046d, c07d)` in the script.
2. Replace them with the **PID** and **VID** you noted in Step 2.
3. Remove the `#` comment symbol if present.
* * *
### 5\. πΎ Save & Upload the Script[](https://ducks-services.gitbook.io/dma/km-box/km-box-b+-setup#id-5.-save-and-upload-the-script)
1. Press **Ctrl + S** to save changes.
2. In the **Tools** menu, click **Download and Run**.
* * *
### 6\. π Reboot the KM Box[](https://ducks-services.gitbook.io/dma/km-box/km-box-b+-setup#id-6.-reboot-the-km-box)
1. Unplug both **blue USB cables** to power down the KM Box until the screen turns off.
2. Plug them back in.
3. Your main PC should now detect a **new mouse** and begin installing it, along with the updated **VID/PID**.
* * *
[PreviousKM Box Net Setup](https://ducks-services.gitbook.io/dma/km-box/km-box-net-setup)
Last updated 12 months ago
---
# Unknown
\# DMA
## DMA
- \[Hardware Setup (Main PC)\](https://ducks-services.gitbook.io/dma/dma-card/hardware-setup-main-pc.md)
- \[JTAG Driver Setup (2nd PC)\](https://ducks-services.gitbook.io/dma/dma-card/jtag-driver-setup-2nd-pc.md): Ensure the DMA cable is properly connected to the JTAG port for this step.
- \[DATA Driver Setup (2nd PC)\](https://ducks-services.gitbook.io/dma/dma-card/data-driver-setup-2nd-pc.md): Ensure the DMA cable is properly connected to the DATA port for this step.
- \[Speed Test (2nd PC)\](https://ducks-services.gitbook.io/dma/dma-card/speed-test-2nd-pc.md)
- \[Troubleshooting\](https://ducks-services.gitbook.io/dma/dma-card/troubleshooting.md): Use this guide to diagnose and resolve common DMA issues. Follow each section based on the error message you receive.
- \[DNA ID\](https://ducks-services.gitbook.io/dma/dma-firmware/dna-id.md): Some of our custom firmware builds are DNA-locked, meaning they are tied to the unique ID of your DMA card. Follow the steps below to retrieve your DNA ID, which is required to generate your firmware.
- \[35t Firmware Flashing\](https://ducks-services.gitbook.io/dma/dma-firmware/35t-firmware-flashing.md)
- \[75t / 100t Firmware Flashing\](https://ducks-services.gitbook.io/dma/dma-firmware/75t-100t-firmware-flashing.md)
- \[Makcu Setup\](https://ducks-services.gitbook.io/dma/makcu/makcu-setup.md)
- \[Makcu Driver\](https://ducks-services.gitbook.io/dma/makcu/makcu-driver.md)
- \[Makcu Flashing\](https://ducks-services.gitbook.io/dma/makcu/makcu-flashing.md): How to Flash Your Makcu for Smooth, Error-Free Use
- \[1k Fuser Overview\](https://ducks-services.gitbook.io/dma/1k-hdmi-fuser/1k-fuser-overview.md)
- \[1k Fuser Setup\](https://ducks-services.gitbook.io/dma/1k-hdmi-fuser/1k-fuser-setup.md)
- \[EDID Spoofing\](https://ducks-services.gitbook.io/dma/1k-hdmi-fuser/edid-spoofing.md): Note: Our latest fusers no longer include a USB-C port and do not require EDID spoofing.
- \[Intro & Requirements\](https://ducks-services.gitbook.io/dma/4k-dc500-fuser/intro-and-requirements.md)
- \[Cables & Controls\](https://ducks-services.gitbook.io/dma/4k-dc500-fuser/cables-and-controls.md)
- \[Troubleshooting & Indicators\](https://ducks-services.gitbook.io/dma/4k-dc500-fuser/troubleshooting-and-indicators.md)
- \[KM Box Net Setup\](https://ducks-services.gitbook.io/dma/km-box/km-box-net-setup.md)
- \[KM Box B+ Setup\](https://ducks-services.gitbook.io/dma/km-box/km-box-b+-setup.md)
---
# Unknown
\> For the complete documentation index, see \[llms.txt\](https://ducks-services.gitbook.io/dma/llms.txt). Markdown versions of documentation pages are available by appending \`.md\` to page URLs; this page is available as \[Markdown\](https://ducks-services.gitbook.io/dma/dma-card/hardware-setup-main-pc.md).
# Hardware Setup (Main PC)
### π 1. Power Down Your Game PC
\* Completely shut down your \*\*main PC (Game PC)\*\* before inserting the DMA card.
\*\*\*
### π§© 2. Insert the DMA Card
\* Plug your DMA card into \*\*any available PCI-e slot\*\* on your Game PC.