① Voice of the Customer:
Devon Sandomir, a German user with extremely high performance demands, owns dual high‑resolution high‑refresh monitors, a high‑performance Windows desktop, and a MacBook connected through a Thunderbolt 4 dock—this is a typical hybrid‑ecosystem workstation. In his email, he described the entire signal chain in detail, from resolution and refresh rate to GPU and DP output behavior of the TB4 dock, with impressive precision.
His core question was straightforward:
“In such a complex system, can the DKS202‑M24 reliably run a dual‑host dual‑monitor high‑refresh setup?”
② What Was the Customer Really Struggling With
On the surface, the question was “Can it support 144Hz/165Hz?”
But his description revealed deeper frustration:
• His old KVM kept “blinking and disconnecting” at 3440×1440 @165Hz
• Especially when the MacBook was connected through the TB4 dock, his Huawei monitor kept losing signal
• He suspected the monitor was defective and spent days replacing cables, reinstalling systems, and updating drivers—yet nothing worked, and the frustration kept growing
This wasn’t a simple “buy the right model” problem. It was:
Which part of the hybrid chain was actually failing?
Without a verifiable explanation, “We support 144Hz” wouldn’t ease his concerns.
③ The Diagnosis: From “Specs Look Fine” to Identifying “VBUS Interference.”
Our technical team initially confirmed that the DKS202‑M24 should theoretically support his needs—3440×1440@144Hz and 2560×1440@240Hz.
But the “blink and drop” behavior he described didn’t resemble bandwidth issues. It felt more like repeated DP hot‑plug events.
So we began checking:
• The DP output mechanism of the TB4 dock
• Compatibility of USB‑C→DP cables
• Lab‑recreated chains to observe DP hot‑plug behavior
We eventually discovered the root cause in an extremely subtle yet common detail:
Many USB‑C→DP cables inject 5V (VBUS) into the DP input.
Direct‑to‑monitor connections work fine, but once routed through a KVM, this “extra 5V” repeatedly triggers DP link resets—matching the blink and disconnection he experienced.
This was the hidden cause he couldn’t find after days of troubleshooting.
④ Actions and Changes: His Confusion Filled a Gap in Our Documentation
In our reply, we didn’t stop at “It supports high refresh rate”. Instead, we broke down the underlying risk:
• The issue originated from the VBUS carried by certain USB‑C→DP cables
• Replacing them with pure DP Alt‑Mode cables without VBUS resolves the issue completely
• These problems are easy to overlook in mixed Mac/PC/TB4 dock setups
He immediately understood why his previous days of effort failed—this was his first verifiable technical explanation.
But the real change happened internally:
• We decided to add explicit “no‑VBUS cable” guidance to future KVM setup documentation
• We added typical chain diagrams and risk examples to the hybrid‑ecosystem FAQ
• We began collecting more data on TB4 dock + cable combinations for compatibility documentation
All to ensure no other user repeats his experience.
⑤ Customer Feedback and Reverse Inspiration
After switching cables, the DKS202‑M24 finally ran “the 144Hz I chose, not the forced 60Hz” on dual monitors.
He even described it as “escaping the torture of cheap KVMs.”
More importantly, he provided a very user‑centric suggestion:
Modern desktops have more devices than ever, and compact keyboards are increasingly common—fixed hotkeys are no longer always convenient. He hoped for more flexible switching methods.
We adopted this suggestion, and it has entered evaluation for future models.
⑥ Conclusion: He Helped Us See What We Previously Overlooked
This user made us realize that in high‑refresh hybrid ecosystems, the hardest part isn’t performance—it’s identifying which link in the chain is failing.
The VBUS risk in USB‑C→DP cables was a missing yet crucial piece in our documentation.
His feedback also pushed us to rethink switching‑method design, shifting from “what we provide” to “what the user’s actual desk setup needs.”
This is co‑creation:
Not because he bought the product, but because his experience made our documentation, compatibility references, and future design directions better and more complete.
